For tech leads & engineering managers

Helping engineering leaders win the fights no one trained them for.

Tech debt that never gets funded. The AI-ROI question you can't answer. Productivity measured as output. I break down the frameworks — and the exact sentences — that move these conversations. Start with tech debt.

One framework a week on Framework Friday · No spam, unsubscribe anytime

Start here — it's free

The Tech Debt Cheat Sheet

How to actually pay down tech debt — without begging for a refactoring sprint. One page: the mindset, the 15–20% rule, the self-enforcing system, and the one number that keeps a team honest. I'll email it to you right now.

No spam, ever. Unsubscribe in one click.

Featured

The Tech Debt Framework Playbook

When the cheat sheet isn't enough — the whole system, ready to use.

  • The 15–20% rule — and why the full-rewrite temptation always fails
  • The self-enforcing system — the Artifact, the Ritual & the Rotating Owner that hold a team accountable with no tech lead
  • The GitHub label system — debt:incidental vs. debt:escalated
  • The fix-vs-log decision and the Definition-of-Done tweak that makes cleanup the default
  • The one number to watch — and the escape valve for when a P0 eats the budget
Get the Playbook — $17
The Tech Debt

Framework Playbook

$17 · one-time
What's here

Your path, from free to full system

Available

Free cheat sheet

The tech-debt system on one page. The fastest way to see if this clicks for you.

Available

The Playbook — $17

The complete tech-debt system: fund the cleanup without a refactoring sprint, and make it stick without a tech lead.

Coming soon

The next three fights

AI ROI, productivity without destroying it, and cutting tool sprawl are on the way. Join the list and hear first.

Meet Danielle

Practitioner guidance, not theory.

I'm a tech lead in enterprise engineering. Everything I share comes from working inside real teams — funding tech debt without a sprint, keeping metrics from becoming a scoreboard, and cutting tool sprawl. I break down one framework a week on Framework Friday.