i
The customer who never came back
You didn't lose them because your service was worse. You lost them because nobody owned what happened during the first sale.
The business knew how to win customers. It never decided how to keep them.
I don't start with software.I start with the decisions that shape it.
Somewhere in the last year, someone made a small decision that quietly shaped everything that followed.
The decision is already loud — let's talk
Honest advice—even if you don't hire me
Inside my mind
How I think before I build
Every rewrite.Every missed deadline.Every product that became impossible to change.
Began as a meeting that felt fine.
- You arrive
- You thought the risk lived in the code.
- You leave
- It lives in what you still haven't decided.
You have already seen this happen
ii
The competitor that felt faster
They weren't cheaper. They weren't better. They were simply easier to buy from.
Convenience quietly became their competitive advantage.
iii
The customer who asked twice
The first person promised one thing. The second had no idea. The customer didn't care who was right.
The business collected conversations. It never collected history.
iv
The promotion that worked too well
Customers arrived faster than the business could serve them. Growth exposed everything that had never been designed.
The business chased demand. It never prepared for it.
v
The decision nobody owned
Everyone thought someone else was handling it. Nobody was.
The customer noticed before the business did.
You did not watch bad programming.
You watched the consequences accumulate quietly.
Themostexpensivemistakesrarelylooklikemistakeswhentheyaremade.
The substitution
When software starts to hurt, companies buy relief. Relief is not a decision — which is why the hurt returns wearing a new invoice.
What businesses usually change
What better decisions create
- More engineersClear ownershipEvery handoff has a clear owner before the customer ever feels the gap.
- A new platformStronger foundationsNew capabilities build on what already works instead of replacing it.
- More processShared clarityEveryone works from the same understanding, not different assumptions.
- Another toolBetter visibilitySmall problems become visible before they become expensive.
- A longer roadmapBetter optionsDecisions remain easy to change while the cost of changing them is still low.
02 — Philosophy
Principles for the decisions that outlive you.
Experience walks out with the person. The next team inherits the decisions — or the mess.
Decide at the last responsible moment — not the last possible one.
Match your deliberation to the cost of being wrong.
Clarity compounds. Cleverness depreciates.
Principles sound elegant on a page. So how do they survive a Tuesday?
Complexity never appears.It accumulates.
03 — Frameworks
Questionsthat make the real decision show its face.
Not templates. Each one finds the decision the request is hiding.
01
The Door Test
How much deliberation does this decision deserve?
02
The Complexity Ledger
Where did the complexity actually go?
03
Constraint-First Design
What is actually fixed?
04
The Second Reader
Will this survive the person who inherits it?
These were not invented. They were earned.
04 — About
I used to believebetter code solvedbad software.
Then I watched clean code fail. Twice.
Both times the code was not the decision. It was the receipt for one.
That changed how I begin every project.
Goodengineeringdoesn'teliminatecomplexity.Itdecideswherecomplexitybelongs.