// diagnosis

Hi,

Convergent.

// diagnosis

Your product builds readiness.
Your interface should too.

Convergent is not selling information. It is training people to perform under pressure.

What makes the product valuable is not only the simulation itself, but the shift it creates in the person entering it.

Right now, the product can be understood. The bigger opportunity is to make it felt earlier — through a design system that signals clarity, tension, trust, and consequence before the simulation even begins.

That is where I would start.

// thesis

A simulation product needs more than polish.
It needs behavioral credibility.

A product like Convergent sits in a delicate space: it has to feel clear without becoming flat, serious without becoming cold, and immersive without relying on spectacle alone. That balance should shape the design from the ground up.

01

Clarity without emotional flattening

The interface should reduce ambiguity without removing the tension that makes the simulation meaningful.

02

Pressure should come from the scenario, not the UI

The user should feel the stakes of the conversation, not the friction of the product around it.

03

Feedback must feel credible enough to change behavior

If evaluation feels vague, ornamental, or disconnected from the interaction, the learning loop weakens.

// system requirements

Before defining a system,
I'd define what it must achieve.

01

Frame pressure without creating friction

The product should hold intensity without becoming visually noisy, mechanically heavy, or theatrically overdesigned.

02

Make performance legible in real time

Users should understand what is being evaluated, what matters, and why — without breaking the immersive quality of the simulation.

03

Unify product, feedback, and brand into one language

The simulation, the interface, and the surrounding narrative should feel like parts of the same system, not adjacent layers built in isolation.

That is the standard I would use to judge every design decision after that.

What that could feel like, in product.

Simulation preview She's waiting.
Simulation initiated.
Simulation environment — preview mode
Preparing the room...
DC
Diane Calloway
VP of Operations — Mid-size Logistics Co.
Advanced Analytical / Guarded

Methodical, skeptical of vendor promises, and highly attentive to accountability. She is not difficult — she is protecting her team from another avoidable failure.

Generic reassurance will cost trust here.
Situation Brief
Account Recovery — Third Escalation

Diane's team reported the same integration issue three weeks ago. It was marked resolved. It resurfaced.

You are entering a live call she asked for herself.

She has 20 minutes, limited patience, and already told her manager she is evaluating alternatives.

Expect interruption. Expect emotional precision to matter more than technical completeness. Expect the wrong kind of confidence to make things worse.

The simulation begins when you're ready.

01
Emotional Calibration
Are you responding to her actual register, or to the version you wish the conversation had?
02
Accountability Framing
Do you lead with ownership, or hide behind explanation?
03
Pressure Response
When challenged, do you stay clear and grounded — or become defensive, vague, or procedural?
She's waiting.

This is how I'd begin.

I saw a gap between the strength of the product and the experience communicating it.

This page is not a proposal — it is a demonstration of how I think about the problem and what the first steps would look like.

If useful, I'd be glad to walk you through the thinking.

Let's talk

Seba Vizzo

Hybrid designer with an architecture background.

I lead design from system to surface — brand, product, interaction, code. I work with AI as a production tool, not a buzzword. What you just scrolled through was built in one session.

Rosario, Argentina