Dream up where your business is heading. We engineer the know-how to get there, so your people work in flow: one workflow at a time, proven before you pay.
Your first move: pick the one workflow that keeps getting stuck. Email Nav what should get better and how you’d know it did. We agree the outcome together, before anything is built.
Engineering below the horizon, the dream above it: the course climbs on toward Māhutonga, the Southern Cross. Illustrative chart. Not for navigation.
Chart DM01 · Dreamineering · Edition 3 · October 2026
Your workflows are your business.
Every quote, order, hire and invoice is a chain of decisions. Your workflows are where the dream meets the day. When one isn’t clear, flow breaks on the same three hazards, marked on the chart.
Nobody named the outcome
No one agreed what done looks like, or who it’s for.
Nobody owns the yes
Decisions wait on whoever is busiest.
Nobody can prove it worked
Tools ran, but nobody can say if it got better.
Face reality before you chart progress.
The map is not the territory. Six steps on the critical path, each with what you bring, the test it must pass, and what you keep, whether or not you sail on. Each gate must pass before the next step starts.
1Agree the outcome
Name the stuck workflow and what should get better, then set what agents may and may not do.
You bring
the workflow, its owner, a sponsor, a champion and your IT partner.
Pass when
one outcome in one sentence, signed by the owner. No owner, no voyage.
You keep
a one-page brief.
2Walk the real work
Your people walk us through real cases: the tools, decisions, handoffs and exceptions. We draw the flow together.
You bring
access to the tools, recent real cases, and the people who do the job.
Pass when
the people who do the work recognise the picture, and the bottleneck is named.
You keep
charts of how the work really runs.
3Set the baseline
Count volume, time, cost and errors as they are today. Agree the target and the stop rule.
You bring
today’s numbers, or a short period to count them.
Pass when
a baseline, a target and a stop rule, agreed in writing before anything is built.
You keep
the scorecard.
4Prove it alongside
Run the smallest end-to-end slice beside the current way, on real cases. Customers see no change yet.
You bring
approval for a safe test space, and time to check the results.
Pass when
it beats the baseline on real cases without harm, or we stop and you keep what we learned.
You keep
evidence, or a cheap reason to stop.
5Go live safely
Switch over with approvals, monitoring, a fallback and a tested rollback. Agents get more authority only as evidence earns it.
You bring
IT sign-off, and your champion’s time to train.
Pass when
controls tested, champion running it, the old way still one step back.
You keep
a running workflow, and its runbook.
6Measure, improve, hand over
Review against the scorecard every week until the target is met. Then your own Nav and first mates keep it running.
You bring
a short weekly review with the owner.
Pass when
the target met against the baseline, the owner accepts, the runbook works without us.
You keep
verified value, and a crew you can trust.
The needles we move.
Agents finishing their steps isn’t success; your outcome is. One scorecard, agreed before anything is built, each measure with an owner, a baseline and a target. If the needles don’t move, we stop or change.
Value
Net benefit, after build and running costs.
Speed
Time to first proven value; time end to end.
Quality
Cases that succeed. Rework and errors.
Adoption
Cases run the new way, of all that could be.
Operations
Cost per outcome, escalations, incidents.
Where you are today The target you agree
Daily
Look at what failed and clear what is blocking.
Weekly
Show real work against the target. Continue, change or stop.
Exit
Value verified, owner signs off, runbook works without us.
Technology can optimise the game. It can’t tell you which game is worth playing.
The quality of our intentions matters more than ever. AI amplifies whatever it is pointed at, the better and the worse sides of our nature. So before the machines speed up, a crew agrees its setpoint: the shared values it steers by.
Get those right and a crew can thrive in chaos. When cause and effect can’t be seen, you act first, then sense and respond, together. We believe AI and tokenised assets will make that the normal weather for every business.
From Matt’s essay The Setpoint (2026). Acting first in chaos is from Snowden and Boone’s Cynefin framework, Harvard Business Review (2007).
Flow is the goal, and the reward.
The right work, done well, with progress you can see. Psychologists call it flow. It happens to one person, and to whole teams at once. Dreamineering is the thinking behind it: directing intention and attention so the work keeps flowing.
One person in flow
Csikszentmihalyi found three conditions: a clear goal, immediate feedback, and a challenge that stretches your skill without swamping it.
A whole team in flow
Sawyer found flow can be shared: a goal everyone holds, close listening, building on each other’s ideas, everyone taking part. Caltech researchers measured it in 2021: teammates’ brain activity falls into step.
Agents don’t feel flow; they set up its conditions. They keep the goal in view, read the gauges and clear the waiting, so people can do their best work together.
A hive-mind of people and AI
When people, firms and agents share goals, data and trust, flow runs between businesses too. Innovative ecosystems that survive the speed-up, then thrive: that’s the hive-mind we’re building toward.
Sources: Csikszentmihalyi, Flow (1990). Sawyer, Group Genius (2007). Shehata et al., “Team Flow Is a Unique Brain State,” eNeuro (2021).
We all need a prompt in the right direction.
Each workflow is a recipe: the outcome, the steps, and the evidence it worked. Run it yourself, or bring us in.