Approach
Generating mockups is easier than it has ever been. The harder, and more useful, work is deciding what the idea actually is and what form would genuinely help it move forward.
How I approach the work
I approach this work as a process of making ideas clearer. Much of what I do is interpretive: listening for what an idea is trying to become, surfacing the assumptions it rests on, and distinguishing what is essential from what can wait.
A prototype comes out of that work, not before it. It makes the clarified idea more visible, easier to discuss, and easier to assess — but the prototype is evidence of the thinking, not a substitute for it.
Imagine | Express | Demonstrate
Imagine
Ideas often become clearer when they can first be imagined more concretely.
Express
Clarity deepens when an idea is expressed with language and structure others can respond to.
Demonstrate
When it is demonstrated, people can see, discuss, and evaluate it together.
These are not rigid phases. They are recurring modes of work that help move an idea into a form that others can see, discuss, and evaluate.
Structured thinking
Clarity usually comes from structure. That may mean defining the central question, surfacing the assumptions an idea rests on, and distinguishing what is essential from what can wait.
This kind of work is often as much about framing as it is about making. A stronger frame tends to make better decisions possible.
Prototypes as thinking tools
A prototype does not need to be polished to be useful. Its purpose is to make an idea tangible enough to examine. In practice, that often means something digital: a simple interface, a small interactive demonstration, a visual explanation, or a set of materials people can review together. This is not physical fabrication.
Work is often built with AI-assisted tools such as Cursor so iteration stays fast and the materials stay clear enough to discuss, refine, and share. When useful, the work can also be organized for handoff in a GitHub repository that internal teams or outside developers can build on.
What matters is not completeness. What matters is whether the prototype helps move the conversation from abstraction toward shared understanding.
A bounded collaboration
This work is intentionally bounded. Engagements stay small enough that attention can rest on a specific question, concept, or decision.
That boundedness helps preserve clarity. It also keeps the work aligned with exploration rather than expanding into implementation or long-term operational ownership.
Practical details
How work is handed off
Prototypes are created to be useful beyond the engagement.
When appropriate, deliverables may include:
- A working demonstration
- A GitHub repository
- Structured documentation
- Notes on possible next technical steps
Work is organized using widely adopted tools — GitHub, modern hosting, standard documentation formats — so technical teams can continue without depending on me.
If a prototype remains active after the engagement, it is transferred into stakeholder-owned infrastructure.
The goal is clarity and momentum, not ownership.
Common questions
Do you build production systems?
No. This work focuses on early ideas, structured thinking, and prototypes that help clarify direction. Implementation and operational development typically continue with internal teams or external developers.
What happens after the prototype?
The goal is to leave behind something useful. This may include a working demonstration, structured notes, or a repository that others can build from. The work is intended to make next steps clearer.
Who owns the work?
Unless otherwise agreed, the stakeholder owns the prototype materials created during the engagement. The intention is always that the work can move forward without dependency.
Can our developers use this work?
Yes. Prototypes are typically structured so developers can understand the intent, explore the concepts, and use them as a starting point if helpful.
Do you stay involved after the engagement?
Sometimes briefly, if a point needs clarification. The work is intentionally bounded — the aim is to create clarity and momentum, not to become a long-term vendor.
What kinds of prototypes do you create?
Most are digital demonstrations, interface concepts, structured explorations, or small interactive examples that make ideas easier to discuss and evaluate.