Consultancy as code: not a consulting report, but a decision prescription

A traditional consulting report has a structural problem: it completes the analysis but does not initiate the decision. It describes the situation clearly, lists the options, notes the risks, and then hands everything back to the reader. The report is closed, the file is placed on a shelf, and often nothing changes. Between analysis and decision lies a gap that most reports fail to cross.

In brief

• The gap between knowledge and action is well documented: a classic finding in the strategy literature is that even well-formulated strategies often fail during implementation.
• Kaplan and Norton’s work shows that the great majority of organizations struggle to execute their strategies.
• The problem is usually not the quality of the analysis, but the failure to connect it to a decision and an action.
• “Consultancy as code” structures the deliverable from the outset as an executable decision prescription: input, rule, threshold, action.

A report informs; a prescription drives a decision

The difference between a report and a prescription is the difference between information and instruction. A report says, “This is the situation and these are the options,” then leaves interpretation to the reader. A prescription says, “Under this condition, take this action; if this threshold is crossed, move to the next step.” It ties the decision to a rule.

This does not mean consulting analysis has no value; it concerns where the analysis ends. A conventional report ends with analysis. A decision prescription takes the analysis one step further and converts it into repeatable, actionable decision logic. It is the difference between “we understand this market” and “when this signal appears in this market, make this decision.”

Why is good analysis not enough on its own?

Because there is a structural gap between knowledge and action. One of the best-known findings in strategy research is that even well-formulated strategies often fail during implementation; the problem is usually not the intelligence of the strategy, but its execution. The work of Robert Kaplan and David Norton shows that an overwhelming majority of organizations fail to implement their strategies effectively.

One reason is that analysis and execution are disconnected. One team writes the report, another team is left to implement it, and the original intent is lost in between. Consultancy as code aims to close this gap: the deliverable contains the decision logic to be applied rather than leaving someone else to translate the analysis into action.

What does a decision prescription look like?

A decision prescription reduces a decision to repeatable logic. It contains four elements: input (which data is considered), rule (how that data is interpreted), threshold (the point at which action is required), and action (what is done and who approves it).

A pricing prescription, for example, might work as follows: the inputs are competitor price and margin; the rule is to review the price when margin falls below a defined range; the threshold is that moving outside the range requires executive approval; the action is to update the price and monitor the result. This is different from a “pricing report”: the report explains the situation, while the prescription operationalizes the decision. The Lab articles follow this logic. Each one does more than explain a topic; it provides a framework for deciding what to do about it.

The objection: “Not every decision fits a prescription”

This is a valid objection: not every decision can be reduced to a rule. Some decisions involve high uncertainty, a new context, or deep human judgment. Forcing those decisions into a rigid prescription can produce poor outcomes.

That is true, but it is not the purpose of consultancy as code. The goal is not to eliminate human judgment. It is to place recurring decisions within a framework so that human attention can be reserved for decisions that genuinely require judgment. The prescription handles the routine and leaves the exception to the human. A good decision prescription also defines the boundary between “follow the rule” and “escalate to a person.”

How does GDP approach it?

GDP delivers consulting output as a decision framework rather than merely as a report. In practice, within Decision Intelligence, this means selecting a critical decision; defining its inputs, rule, threshold, and action; and embedding that logic in a framework that can be run repeatedly rather than in a document that is read once. The result is not a report that sits on a shelf, but a decision tool that is actually used.

Frequently asked questions

What exactly does “consultancy as code” mean?

It means designing the consulting deliverable as an executable decision prescription rather than a static report. The deliverable does more than describe the situation; it defines which inputs, rules, and thresholds should govern a specific decision.

What is wrong with a traditional consulting report?

It ends with analysis rather than initiating a decision. It presents the situation and the options but leaves the reader to determine what to do. This gap between knowledge and action explains why many reports change nothing.

Why is strong analysis not enough?

Because, as strategy research shows, even well-formulated strategies frequently fail in execution. The problem is not the intelligence of the analysis, but the fact that it is not connected to a decision and an action.

Can every decision be reduced to a prescription?

No. Decisions involving high uncertainty or deep judgment should not be forced into rigid rules. The purpose is to structure recurring decisions and reserve human attention for exceptions: the prescription handles the routine, while people handle judgment.

Does this approach eliminate human judgment?

Quite the opposite. By placing routine decisions within a framework, it frees human judgment for the decisions that truly matter. A good decision prescription also includes the distinction between when to follow the rule and when to escalate to a person.

---

Academic and institutional sources: Robert Kaplan & David Norton (the strategy execution gap), the difficulty most organizations face in implementing their strategies; academic literature on strategy execution, even well-formulated strategies frequently fail during implementation.

Last reviewed: July 2026.

---