Good work should
stand on its own.
Partnership needs shared understanding: what we know, what we’ve decided, and how we’ll put it into practice.
Clear decisions.
A shared record.
Working alongside you means making the thinking visible. I keep a record of what’s known, what’s inferred, and why decisions were made, so we can challenge an assumption without losing the thread. That same record helps the team carry the work forward.
One source of shared state.
One file, one stable name, never dated, never duplicated — because duplication is how a file starts lying. Wherever it disagrees with memory or a snapshot, the file wins. Every working session is responsible for it being true when the session ends.
Corrections listed, never silently fixed.
When the record is wrong, the error goes at the top: what it said, what's true, and how that was established. A record that changes without saying so is the exact failure it exists to prevent.
Stated versus inferred.
Every claim declares which it is: what the client said, or what I concluded. The most common error on any project is a true fact carried one step past its source and written down as an observation.
A do-not-reintroduce register.
Things removed on purpose, each with the reason and where it keeps resurfacing. Not a changelog — an immune system. It stops the team relitigating settled decisions and stops dead ideas creeping back in through copied templates.
Numbered rulings.
Decisions in sequence, each dated with its reasoning. When two decisions collide, the collision is recorded rather than papered over.
Five rungs, no partial credit.
Mapped. Built. End-to-end. Unattended. Independent. One step still done by hand holds the whole workflow at mapped. The top rung means someone who didn't build it can recover it from the runbook — and that's the definition of complete.
Preflight before work.
A health check runs before anything else, prints live counts, and fails loudly on what it can't read. Trust the check over the manifest, because hand-maintained counts drift.
“When you sell this business, someone is going to ask you to prove every claim you’ve made about it. I build the system that answers them.”jarreau bowen
Give me thirty minutes
with the problem.
Bring one workflow, team challenge, or stalled project. I’ll give you my initial diagnosis: where I think the bottleneck is, what leads me there, and the first thing I would do to test or address it.
If something needs more investigation, I’ll tell you what—and why.
Explore the free diagnosisOne problem. Thirty minutes. No deck required.