The blog · LinkedIn post

The TPM Framework for Solving Complex Problems

How TPMs make complexity executable — because the visible problem is rarely the real problem.

Edwin T. Dunson June 19, 2026 8-slide carousel
View the original on LinkedIn ← All writing

When a program is in trouble, what leadership sees is a delayed project, a missed milestone, a budget issue. What's actually causing it almost always lives below the surface: unclear requirements, hidden dependencies, resource constraints, misaligned incentives, technical debt, communication gaps.

That gap — between the visible symptom and the real problem — is where technical program managers earn their keep. This is the five-move framework I use to close it: understand the problem, build a coalition, test assumptions early, make the invisible visible, and execute.

The best TPMs don't just manage the plan. They make complexity executable.
The TPM Framework for solving complex problems: understand the problem, build a coalition, test assumptions, make the invisible visible, execute.
1 / 8 — The five moves of the framework
Iceberg diagram: stakeholders see a delayed project, missed milestone, and budget issue; below the surface sit unclear requirements, hidden dependencies, resource constraints, misaligned incentives, technical debt, and communication gaps.
2 / 8 — Great TPMs solve below the surface
Build a coalition: the program manager at the hub of leadership, engineering, product, security, sales, operations, and customers.
3 / 8 — Complex problems are solved through relationships, not project plans
Test assumptions early: an assumption-test-learn-adjust-repeat loop that reduces risk before launch.
4 / 8 — Validate before the stakes get expensive
Make the invisible visible: dependencies, risks, decisions, ownership, and trade-offs turned into a visible program snapshot with owner, risk, due date, and path.
5 / 8 — Clarity turns resistance into momentum
The leadership pyramid: trust at the base, clarity in the middle, execution at the top.
6 / 8 — Trust, clarity, and execution
The best technical program managers reduce ambiguity, create alignment, and drive execution.
7 / 8 — Reduce ambiguity. Create alignment. Drive execution.
Closing slide: you are the program manager — the single-threaded owner. Own the outcome. Drive the clarity. Close the gaps.
8 / 8 — You are the Program Manager

What would you add to this framework?

Own the outcome. Drive the clarity. Close the gaps. If you'd run it differently, I'd like to hear it — join the conversation on the original post.

Comment on LinkedIn
← Back to all writing Get in touch →