The eleven pillars
Hand-curated topical anchors covering the full discipline of project management.
Browse the corpus
95 pieces across 8 formats. Filter by pillar, format, or keyword.
Industry-specific patterns matter — generic PM advice has limits
PM in healthcare, construction, software, marketing, manufacturing, financial services. The sector-specific patterns that the universal playbook misses.
Leadership is observable — it is the residue of decisions over time
Team formation, motivation, conflict, leadership styles. The human core of project work, treated as a discipline you can practice rather than a vibe you have.
AI projects fail in new ways — the old PM playbook has known gaps
Running ML, LLM, and AI-product projects: model risk, evaluation, deployment, ethics, infrastructure cost. The new failure modes the traditional playbook does not cover.
Methodology choice is a context decision, not a religion
Agile, Waterfall, Lean, PRINCE2, hybrid — the methodology wars are a category error. Pick the one that fits the work and move on.
The path from IC to senior PM is not more certifications — it is deliberate practice on observable patterns
Career paths, certifications, soft skills, productivity systems. Becoming a measurably better PM over a measurable timeline.
Program management is project management when one project is no longer the unit
Multi-project programs, portfolio management, governance at scale. The discipline that emerges when the work is too coupled to plan independently.
The project lifecycle is a loop, not a sequence
The five-phase lifecycle on the PMBOK cover is a useful diagram and a misleading model. Real projects loop — and the loop is where the discipline lives.
Risk and quality are the same skill at different time horizons
Risk identification, mitigation, quality control, audits — all the same discipline: foresight, rendered in artifacts. The PMO's most under-invested capability.
Schedule and cost are coupled — treating them as independent is the failure mode
Estimation, scheduling, EVM, budgeting, procurement. The financial backbone of every project that ever shipped, and the most common place projects quietly come apart.
Most project failures are communication failures pretending to be other failures
Stakeholder identification, alignment, status cadence, escalation paths. The structural discipline that the soft-skill framing keeps obscuring.
The next decade of project management is being shaped now — the patterns are visible
AI in PM, distributed teams, hybrid methodologies, the next decade of project work. What is changing, and what to do about it before everyone else figures it out.
How AI Is Reshaping Project Management
AI in PM stops being a status-update bot and starts being a co-architect — drawing workstreams, wiring dependencies, and rearranging the plan as the project learns.
Why the Infinite Canvas Beats Lists for Project Management
Lists hide dependencies. Timelines hide structure. The infinite canvas surfaces both because the work is shown as a system, not a queue.
The Project Lifecycle Is a Loop, Not a Line
The five-phase project lifecycle is right; the arrows are wrong. Drawing it as a continuous loop forces the cadence question and surfaces the bottleneck phase.
Risk Registers as a Tool, Not a Tax
Most risk registers are a tax, not a tool. Two changes — write the trigger before the risk, write the mitigation owner in the same line — flip the register into something teams actually use.
Business Case Checklist for Implementation Leads Refereeing Two Stakeholders
When two stakeholders want different outcomes from the same implementation project, the business case is your referee. A short checklist for delivery managers.
Salvaging a Mid-Size Campaign Business Case After Silent Disagreement
When a campaign business case has been politely approved but not believed, executives need a corrective playbook before the team starts execution. A short, light guide.
Recovering an Implementation Business Case When the Original Owner Leaves
On mid-size implementation projects, the business case often lives with one person. When they leave, executives need a corrective playbook fast. A short light guide.
Handing Off a Software Project Business Case Without Losing the Why
Mid-size software projects change hands more than the business case admits. A retrospective playbook for delivery managers — including the four sections that always lose fidelity in handoff.
12 Business Case Mistakes Junior PMs Make on Mid-Size Creative Projects
Twelve specific business case mistakes new project managers make on mid-size creative projects — including the single-point-of-failure traps that surface only after a key person leaves.
Quiz: How Well Do You Understand Business Cases on Resource-Constrained Construction Projects?
A six-question retrospective for delivery managers running enterprise hardware or construction projects — testing whether your business case withstood the resource scarcity that always shows up.
Writing a Business Case That Survives a Handoff in a Startup Campaign
On startup campaigns, the business case usually loses fidelity at the first handoff. A short retrospective practice for delivery managers — and the three lines that don't get lost.
Go/No-Go Checklist for New PMs Running Hardware Projects
When forecasts on a hardware project are wrong in the same direction every time, a structured go/no-go checklist exposes the bias before sign-off. A moderate-rigor list for new project managers.
The Go/No-Go Question Enterprise Marketing Executives Should Ask Before Greenlight
Enterprise creative greenlights are gated by budget and concept. They should also be gated by one estimation question. A short preventive playbook for marketing executives.
Showing 24 of 95 matching pieces. Refine the filters above to narrow the set.
Free Office downloads
50 blank + filled PowerPoint, Excel, and Word files across 8 disciplines.
Head-to-head comparisons
6 side-by-side competitor breakdowns.
Send me the playbook
One email a week, hand-edited. New pieces, sharp PM thinking, no slop. Unsubscribe in one click.