How I work
I spent a career inside the old model. I still use those tools. What changed is the client — and the speed.
The process
Nine practices I bring to the work. We use them as the situation needs — not as a checklist, and not always in this order. One conversation can touch several. We return to them as the work unfolds.
Nothing changes yet. The system is measured as it truly runs.
Where the business is, where it hurts, and the 1-to-10 question that finds the gap worth closing.
How work actually flows — where effort pools, where it waits, and where it quietly leaks.
The constraint named and measured. The most obvious pain point, not the most elegant one.
The fix is scoped from evidence, and reviewed before anything is touched.
The smallest system that removes the constraint — with opportunity solution trees keeping the options honest.
How the pieces fit: your existing tools, the new system, and the seams between them — built to outlive any single contributor.
Where AI belongs in the design, where it doesn't, and the operating rules that govern it in your organization.
Working software in daily use — and the practice that keeps it that way.
Built in short, reviewable passes — every change tested before it ships. Staged, audited, reversible.
Verified against the real environment, with the people who use it — not a demo harness.
What worked, what didn't, and the lessons log that keeps the practice improving after I leave.
The difference
Same hours in the week. Different system underneath them.
The week as it usually feels
The week after the method is in
Every case study includes a wrong turn — that's deliberate. A case study with no wrong turns is marketing.