Search this and every result is a list: eight questions for stakeholder buy-in, a dozen for a change readiness call, thirty for a discovery interview sorted by role. All of it answers what should I ask, and none of it answers what actually matters by the third engagement: did asking it ever produce anything. A question that read brilliantly in one workshop three years ago and one nobody has used since sit on the same page in the same font weight, because nothing in the format tells the two apart.
So the unit here is the question, not the guide. Every question in the Question Register carries a status computed from three numbers: how many times asked, across how many engagements, and how many times the answer was cited in a finding. An answer nobody used again is a miss, not a hit, however articulate it sounded. Three asks across two engagements at half a hit rate earns Core, the same floor under half earns Retired, anything short stays Trial. Small wording changes shift what a question gets back, so wording stays fixed once live.
The bank behind this pack, run at an operations practice across four engagements, carries twenty scored questions: eleven Core, six Trial, three Retired. One of them, on who actually approves a fix, clears Core at a 77.8 percent hit rate overall. It still fails cold, at 33.3 percent, against 100 percent after a walkthrough, which the Sequencing Note tracks. A thin answer gets diagnosed against Gordon Willis's four stage model rather than re-asked louder. Run the interviews with the stakeholder interview programme pack, or price the hypotheses with the hypothesis and workplan pack.
Consulting Discovery Questions Template