cp-initiation

A diagnostic question follows the structure: how can the client achieve a specific measurable outcome given key constraints within a timeframe. It must be testable, avoid naming a solution, and include numbers and deadlines so the team knows when it has been answered.

Score each stakeholder on power (1-5) and interest (1-5), then place them in a power/interest matrix: manage closely, keep satisfied, keep informed, or monitor. Document each key stakeholder's stance, main concern, and engagement plan, and actively seek out skeptics rather than mapping only supporters.

Skip initiation when the problem statement is already agreed and a workplan exists, when the request is a quick tactical task under one week with no scope ambiguity, or when re-entering an engagement mid-stream with an existing Problem Definition Document.

Red flags include a diagnostic question that names a solution, no client sponsor sign-off, scope that is not written down, purely qualitative success criteria, a stakeholder map missing skeptics, and a team that has never met the client before drafting the document.

It produces a Problem Definition Document containing the engagement header, business context, diagnostic question, in/out scope, stakeholder map, success criteria, engagement structure, constraints, initial hypotheses, and sponsor sign-off. The document freezes once the structure phase is approved.