Home·Results
Proof, not adjectives.
Case studies and client results
Where the work shows up as outcomes — case studies from coaching, fractional leadership, and special projects, plus what clients say. Reviews are added as engagements close. Nothing here is invented.
The M.O.R.E. Wall
Illustrative, AI-generated image of the M.O.R.E. Wall in use.
A live, moderated audience-participation display for a 400-person conference — built by one person, over four weekends, for about $25. Attendees answer the active prompt on their phone; once a moderator approves it, their words hit the big screen in about two seconds.
Three surfaces — the projected wall, the phone submission form, and the moderator panel — over one live database, changing together in real time as the facilitator rotates the prompt.
Sequence by risk, not by visibility
The interesting part wasn't the software — it was the sequence of decisions that got a working system into a room full of people on a fixed date, at a cost that made the idea viable. The same scope, quoted as a freelance engagement, came to eight deliverables and 23–29 engineering hours, in three bands from $1,200 to $5,500. It shipped for about $25 in direct costs. The gap isn't a trick — it's disciplined scope, the right sequence, and AI tooling doing the implementation while a person holds the judgment.
Prove the loop before polishing it
The one question that mattered: could someone submit on their phone, have it reviewed, and see it hit a big screen in about two seconds? Until that ran end to end, nothing else was worth building.
Design for the room, not the demo
A projector seen from the back of a hall, several hundred people submitting in one lunch window, a volunteer moderating on a phone, a venue network you can't trust — anything on the critical path worked without depending on the outside world.
Verify everything personally
Every change was deployed and looked at before the next one started — one at a time, never batched. Slower per step, dramatically faster overall, because failures surface attached to their cause.
Protect the client's exposure first
Nothing reaches the screen unreviewed. A live display in front of an association's membership is a reputational surface before it's a feature; the cost of one bad submission dwarfs a two-second approval step.
Seven phases, four weekends
The last weekend was held as buffer, not scheduled — fixed-date delivery fails on the things you didn't leave room for.
Judgment held; execution leveraged
Judgment
Every decision, every trade-off, every question of whether something is good enough — held by a person, start to finish, and never delegated.
Execution
AI tooling working directly against the codebase — implementing, reporting what it changed, and flagging what it had to decide along the way.
The leverage is in the pairing, not either half. Tooling without judgment produces confident, plausible, wrong work; judgment without leverage produces a plan and no product. Running both is what turns a $3,000 scope into a weekend.
Written up as they close
Critical Path is a new practice, so this page is deliberately short. Engagements get written up here as they close — and only as clients consent to being named. Nothing is invented in the meantime: no borrowed logos, no testimonials I can't stand behind.
If you'd like a reference conversation before hiring — to talk with someone who has worked with me — just ask, and I'll arrange it directly.
Start with one conversation.
Twenty minutes, no cost. Bring the decision you're stuck on, the role you're chasing, or the thing you want built. We'll find the critical path from there.