Current way to work together
Choose before building.
What is changing? What is only noise? What would count as useful proof? A crowded field becomes one defensible move.
Product strategist. Creative director. Hands-on builder.
Too many possibilities. One useful product.
I find the bright idea inside the mess, give it a shape people can feel, and build the first working proof.
Cycles through choose, form, and build. The full explanation follows below.
The idea inside the idea
The bright bit is usually already in there.
It is buried under options, features, tools, and other people’s certainty. The first job is not to build faster. It is to find the part worth building.
Current way to work together
Make the idea felt.
Who is it for? What should change for them? The story, interface, and visual world start carrying the same idea.
Current way to work together
Build the smallest complete proof.
Not a theatre set. Something people can use, question, and improve. Enough product to answer the next real question.
Choose the move selected.
Things I am building
Glimpses, not theatre.
These are small, staged windows into working product ideas. Each one says what it is today. No fake client story. No pretending a test is a launch.
Working browser demo
Find the useful thread.
Three fragments arrive. One clear next move leaves. Try both states.
Note 01
The process takes too long, but nobody agrees where.
Note 02
There are six tool ideas and no test that separates them.
Note 03
The team needs one useful result before the next planning round.
First proof
Run one task end to end with a real user.
Keep the old process beside it. Measure time, clarity, and recovery.
Illustrative preview
Change the serving. Keep the source.
A living version can become more useful without pretending it was the original.
Original source
Sunday tomato sauce
Handwritten by Nanna. Source stays attached.
Checked cooking version
8 tomatoes
4 garlic cloves · 2 onions
In proof
Ask the question behind the dashboard.
Pick a question. The signal map changes, but the source trail stays visible.
Clarity signal
The offer changes names halfway through.
Use one name from first promise to final action.
- Page copy
- Product flow
- Support notes
Two ways in
Touch the work. Or bring your own.
Open ideas
Try what is already moving.
Small tools and product experiments. Some are open. Some are still proving what they should become.
Try the demos aboveCurrent paid service
Bring one important, messy idea.
We choose the move, give it a clear product form, and build the first proof. The work stays bounded by the next question it needs to answer.
Bring the messy versionThe workbench
Notice. Decide. Play. Shape. Prove.
The line is not perfectly straight. That is the point. Each pass leaves the idea clearer, smaller, and more useful.
Step 1 of 5
Notice
Look for the real tension, not the loudest feature request.
Decide
Choose what matters now, what stays manual, and what does not belong.
Play
Make room for the surprising route before the system hardens.
Shape
Join the promise, flow, visual world, and boundary into one product.
Prove
Put the smallest complete version in front of the real question.
Ongoing research
What I keep asking
What happens when software becomes emotionally fluent enough to persuade, soothe, and shape us?
I am interested in the product choices underneath persuasion, autonomy, attachment, vulnerability, and governance. Not as a side note. As part of what gets built.
The open studio
Bring me the messy version.
You do not need the perfect brief. Start with these three lines.
- What are you trying to change?
- Where is it stuck?
- What would a useful first result look like?
Concept behaviour only. This copies the questions to your device. It does not send a message or expose an unconfirmed email address.