CONSULTING SERVICE — CPP
The plan is correct.
So why doesn’t it move?
Metamorphose consulting is built around our own method, CPP (Calibrated Project Planning). We don’t stop at writing a correct plan — we calibrate it to the members who execute it and the client who approves it. That is why plans move and approvals go through.
THE PROBLEM
Standard frameworks cover whether a plan is correct.
Not whether it moves.
PMBOK and agile deal with the attributes of the plan itself — scope coverage, dependencies, estimate validity. In practice, plans that meet every one of those criteria are routinely not approved, or approved and then not executed.
Not approved
The content is right. Yet “could you explain a bit more” keeps coming, and the approval meeting slips.
Approved, but nothing moves
The plan passed. But the people on it can’t read it as their own work, and week one is already late.
Endless rework
It comes back no matter how often you fix it. Fixing adds no information, so the loop never ends.
The reason isn’t the team’s ability or motivation. The plan hasn’t been calibrated to its readers — that’s all.
WHAT IS CPP
CPP — Calibrated Project Planning
A set of calibration operations that fit a project plan to the cognitive capacity and decision rhythm of its two kinds of users: the members who execute it and the client who approves it.
4 INPUTS
Before calibrating, gather four inputs
CPP starts with interviews. A plan written without these four inputs won’t move, however carefully it’s made.
| # | Input | How we gather it | If missing |
|---|---|---|---|
| 1 | Each member’s ability and the information they hold | Past deliverables, day-to-day observation | Granularity can’t be set |
| 2 | The PM’s overall direction | Interview | Sequence can’t be set |
| 3 | Why the previous project failed | Stakeholder interviews | No starting point for calibration (most critical) |
| 4 | The client’s decision rhythm | Learned naturally while acting as the point of contact | Approval can’t be obtained |
6 AXES
Where CPP differs from ordinary project management
| Axis | Ordinary PM | CPP |
|---|---|---|
| Granularity | Break down into units the planner understands | Break down into units the assignee can write with the information they hold (split by information, not ability) |
| Sequence | Task dependencies | Sequence that includes politics, technology, resources and failure countermeasures |
| Narrative | Ordered by the planner’s own logic | A structure where trunk and branches are obvious to the reader |
| Ownership | A list of tasks | Granularity at which the assignee can decide for themselves |
| Client dialogue | Milestones set for internal convenience | Synchronized with the client’s decision timing (top priority, non-negotiable) |
| Wording | Conventional item names | Check whether item names imply a wrong premise (some rework is resolved by renaming alone) |
The axes are prioritized. Client dialogue comes first — without approval there is no project. Granularity is the first axis we’re willing to sacrifice (never stall the whole plan to fit the weakest assignee).
3 CONDITIONS
Whether CPP works depends on structure, not headcount
CPP is not a universal method. It works in units where three conditions hold.
So we check them before accepting an engagement — and carve out a unit where they hold first.
Access to holders ofpast knowledge
Without it, the planner fills gaps by imagination, diverges from the experienced people, and gets sent back. Fixing adds no information, so the loop never ends.
A singleapproving authority
Without it, reviewers’ demands contradict each other and whichever you follow, the other sends it back. The planner can’t resolve this. We confirm in writing whose approval is final.
Agreement on why thedeliverable exists
Without it, the argument shifts from content to “do we even need this,” and no amount of revision moves it forward.
The three conditions are independent of headcount. Even at several hundred people, CPP applies if you carve out a unit where they hold (one team, one phase). We do three things first: a knowledge-holder map, a single line of approval, and a definition of the unit’s boundary.
HOW WE WORK
How we work — the pass criterion is approval with no follow-up questions
- 1Check the 3 conditions
Before we accept: can we reach the people who know last time, is there one approver, and can you say what the deliverable is for? If not, we carve out a unit first.
- 2Gather the 4 inputs
Ability and information held, overall direction, why the last project failed, decision rhythm.
- 3Calibrate the plan
Six axes. Granularity split by “can this person write it with what they know?”
- 4Approval
No follow-up questions = pass. Questions are logged as narrative/wording gaps for next time.
- 5Drive and embed
We drive it as PMO, or hand the pattern to your own PMO as capability building.
PMO delivery (we run it)
We join as your PMO and drive the project from a CPP-calibrated plan.
PMO capability building
We hand the CPP pattern (4 inputs, 6 axes, 3 conditions) to your PMO staff so they can run it themselves.
Project A, one team in its start-up phase: restructuring the plan to show trunk and branches — same information — led to approval with no follow-up questions. In another project, rework stopped after renaming items only, with no change to content (the wording axis).
WHERE CPP APPLIES
Service areas — six domains where we apply CPP
Project Management (PMO)
Providing and strengthening PMO functions; integrated management of schedule, quality, cost and risk. Large programs are carved into units with their own delivery structure.
DX Strategy & Execution
End-to-end support from strategy to execution management, covering technology selection, vendor management and change management.
AI Solutions
From generative-AI strategy through PoC, production and adoption. Post-rollout adoption is handled by Metamon (AI adoption service).
Business Strategy
Mid-term plans and business portfolios — from external analysis to execution plans, working alongside leadership.
Information Governance
From security policy to operating structure, including cyber-incident response rules and exercises.
Internal Control
Building and strengthening internal control and compliance — from risk-management framework design to an operating structure that actually sticks.
PRICING
Pricing
Proposals are tailored to project scale, duration and scope.
Get in touch to start the conversation.
- CPP calibration of a plan (from one document)
- Issue diagnosis / current-state analysis
- Strategy and planning
- Workshops and training
- Ongoing PMO function
- Regular monthly meetings
- Issue handling and progress management
- Periodic reporting
- Urgent support and ad-hoc consultation
- PMO lead and project delivery
- Stakeholder management
- Risk and issue management
- Reports and minutes
CONTACT
Don’t take the same plan to the next meeting.
We look at whether it’s written for the people who execute, or the person who decides. We won’t send a sales deck. You don’t need to submit a plan.