Four Pillars
The clarity model, developed by Terry Schmidt, taught with full attribution.
The Core Idea
Most project failure is a clarity problem that execution speed hides — right up until it becomes expensive to fix. The Four Pillars get a project from "I know roughly what this is about" to "I can defend this project's definition of success to a skeptical stakeholder," before a single task gets scheduled.
How It Works
Four pillars, in order:
- Clear Outcomes — what success actually looks like, specifically. Not "improve customer satisfaction." "Customers complete onboarding in under 30 minutes without contacting support."
- Success Measures — how you'll know you got there. Observable, specific, something everyone can agree on without a debate.
- Verification Methods — how you'll test whether those measures actually mean what you think they mean, before you trust them.
- Documented Assumptions — what you're quietly betting will happen, written down before a stakeholder finds the gap for you.
Clear Outcomes → Better Measures → Verified Methods → Documented Assumptions
↓ ↓ ↓ ↓
Team alignment Scope clarity Reduced risk Stakeholder trust
CanvasPM's contribution layer — separate from Schmidt's original framework: I teach the Four Pillars with GenAI as the accelerator, using AI to pressure-test each pillar on your real project — poking holes in the outcome statement, proposing measures that could be gamed, surfacing assumptions you haven't named yet. In training, we run this through a three-level escalation: your project as you currently understand it (L1), the version where two stakeholders disagree about what success means (L2), and the version where your outcome statement lands in a contract and gets read adversarially (L3).
In Practice
The Four Pillars are the core clarity tool in Level 1: Curious training — the first thing we build together, before anything else. It's the difference between walking into a stakeholder meeting hoping your plan holds up and walking in already knowing it will.