Product & Design · 4 min read
Making the Vision Tangible
How I use design and prototyping to help product teams see, question, and build a shared vision.
An idea can sound clear in a meeting and still mean something different to everyone in the room.
We use the same words. We agree on the problem. We leave with a direction. Then we start making the thing, and the differences appear. What felt simple turns out to need another step. A feature that seemed essential gets in the way. Two people discover they were picturing different experiences.
This is one reason design is such a big part of how I develop product ideas. I want to get to something people can experience while the direction is still open.
A prototype gives the conversation a place to land.
Give the idea a shape
I've spent much of my career working on consumer products, from mobile creation and sharing to fantasy sports and now visual thinking and AI. Across those settings, the question that interests me is how to turn a possibility into an experience people can understand and use.
A product brief helps explain the intent. A prototype lets us examine what that intent asks someone to do.
Where do they begin? What do they need to know? What are they expecting to happen next? Can they tell whether the result is useful?
Those questions get much easier to discuss when there is something in front of us. People can point to a moment, try a different path, and describe what feels wrong. The vision becomes specific enough to improve.
Make the important details real
I like moving quickly into high-fidelity prototypes. The right level of fidelity depends on what we need to learn.
Sometimes a sketch answers the question. Other times, the question lives in the details. The language, pacing, interaction, and hierarchy are part of the idea. Removing them can make it hard to tell whether the experience works.
This matters with AI products. A box that says “AI response” leaves most of the experience unresolved. We need to see what someone gives the system, how they judge the answer, how they correct it, and what they can do with it afterward.
The prototype should make those decisions visible. It should also make its own limits clear. A polished screen can look convincing while the behavior underneath it is still incomplete.
Give the team room to change it
A good prototype creates better questions. It makes the next disagreement more useful.
Instead of debating whether an idea sounds promising, we can ask whether a particular step earns its place. Whether the information arrives at the right time. Whether the experience supports the person we have in mind.
That is a leadership job as much as a design job. The team needs a shared understanding of what we are trying to learn, where the prototype is representative, and what remains unresolved. People should feel free to question the direction, even when the artifact looks finished.
Crystallizing a vision means making it clear enough for others to help shape it. The goal is a stronger shared direction, with the reasoning behind it visible.
Expand who can participate
At FantasyPros, part of my current work is helping colleagues use AI to turn ideas into prototypes. That brings product exploration closer to the people who understand a problem firsthand.
Someone does not need to begin with a complete specification. They can begin with a frustration, an example, and an idea of what better would feel like. We can work from there.
AI makes it easier to produce the first version. It also gives us more versions to evaluate. Framing the problem, recognizing a useful result, and deciding what deserves further investment become even more important.
Building MindMapOS has given me another place to explore that process. I'm developing web and iOS experiences around visual thinking, an area I've cared about for a long time. Being able to move between an idea and working software gives me more opportunities to examine the idea itself.
Keep the next decision in view
When I start a prototype, I try to identify the decision it should help us make.
It might be whether a workflow is understandable. Whether an interaction makes the product feel simpler. Whether we have found a direction the team can build around.
That keeps the work focused. We can make the parts that matter real, examine them together, and decide what to carry forward.
I enjoy that moment when an idea becomes tangible. People can finally see it, try it, and make it better. The conversation changes, and the vision starts to belong to the team.