The Air Changed the Moment We Shared the Screen
Online meeting. We share a screen with what we built. Still rough, maybe 60% complete. Honestly, I was not sure I should show it.
The instant it appears, the other side’s tone shifts. Even through a camera. The hint of leaning in. “Wait, this already works?” Less than a week since the kickoff hearing.
I have seen this reaction many times in the past month.
”Could You Do This Too?” Means We Have Won
On one project, we showed an aggregation-automation probe. The hearing had asked for “monthly report efficiency.”
When the screen appeared, the client said:
“Could this be automated by AI?”
Of course it could. We showed something that roughly worked, on the spot. Then the next sentence came.
“Honestly, we are doing this aggregation by hand right now. Could that work too?”
That is the real voice.
It did not surface in the hearing. “Monthly report efficiency” was the surface request. The actual pain was the daily manual work. Without a working demo, that voice would have stayed buried forever.
The Phenomenon of “Triggered Response”
In the previous post I wrote about a methodology called Making as Asking (zomon). Show a probe, watch the response, dig out the real issue.
There are four reaction types. The denial type (“not that”). The proximity type (“close, but here is wrong”). The silence type (confused, says nothing). And the most valuable: the triggered type.
“Looking at this, I just thought…” — and the client starts talking.
The probe ignites. Unverbalized issues that lived in the client’s head start spilling out. Pulled by what we showed: “Now that you mention it, we are stuck on this too.” “Honestly, this was what I most wanted, but I did not know if it was OK to ask.” Things flow like a broken dam.
Hearing sheets cannot pick this up. It only happens in front of something that moves.
Bystanders Start Joining the Discussion
The change after a probe is not limited to the active speakers.
Every project has the “stepped-back” member. They attend meetings but do not speak. They approve when needed. Not bad people. They simply cannot see how their own work connects.
When we show a working demo, those people start moving.
“We have the same problem in my department.” “Could sales use this feature too?” Their own work connects to what they see. Things abstract discussion never produced surface in front of a concrete artifact.
A single probe shifts the project’s temperature.
Once people are convinced the project matters, meeting attendance rises. Questions multiply. Slack responses speed up. No matter how brilliant a kickoff deck is, it cannot reproduce that thermal change.
Trust Accumulates Through Artifacts, Not Words
Running zomon at multiple sites, I noticed something. This is not a substitute for requirement definition. It is an apparatus for accumulating trust.
“That thing you showed last time — we shared it internally and the response was great.” Feedback like this starts arriving naturally. The probe circulates inside their organization, project visibility rises, and budget conversations move smoothly.
Requirement documents do not produce this. PowerPoint proposals do not produce this. Only working things have the power to run around inside an organization.
The probe becomes trust. Trust becomes scope. Scope reaches the real problem.
The chain does not start until the first probe ships.
Conditions for Zomon to Work in the Field
After a month across several projects, conditions become visible.
First, speed. From hearing to probe, one week at the longest. Three days is ideal. Without AI’s fabrication speed this cycle does not turn. It only works when one person who can touch design and code partners with AI.
Next, calibration of completeness. A probe is not a finished product. 60% is fine. Too clean and the client holds back. The moment they think “this is already done, maybe I cannot ask for changes” you lose. Too crude is also bad. “Minimal specificity that allows judgment” is the right level.
Last, no fear of denial. People who are afraid to hear “not that” cannot do this. Denial is a signal of direction, not a failure.
Keep Making, Keep Asking
Zomon is not just a beginning-of-project move.
Even after the real problem becomes visible, keep shipping probes. Even in the implementation phase, show progress. Each show returns a reaction. Each reaction sharpens the project’s resolution.
The act of showing something that moves is itself the force that pushes the project forward.
A timeline where you nail the requirement document before building, versus a timeline where you keep asking by making. Which one travels further is no longer in question.