Sponsored by
Recommendation First: The Decision the Room Is Waiting For
CPO Path #29 CW 41 2026
EXECUTIVE PREMISE
Technical credibility is often built by showing the analysis. Executive credibility is tested when the room asks for the decision.
For procurement leaders moving toward enterprise responsibility, a useful distinction is between knowing more before deciding and knowing what would actually change the decision.
WHY THIS MATTERS
The CEO Genome Project analysed in-depth assessments of 17,000 executives. Among executives rated poorly on decisiveness, only 6% were judged to decide too quickly; 94% were rated poorly because they decided too little, too late (Botelho et al., 2017).
That finding is not an argument for haste. It points instead to a pattern familiar to technically strong functions: analysis continuing after the remaining uncertainty no longer justifies delaying the call.
Michael Watkins describes the transition from functional to enterprise leadership partly as a move from specialist to generalist, from analyst to integrator, from problem-solver to agenda-setter, and from the wings to living "on center stage" (Watkins, 2012).
Procurement leaders encounter that transition every time an executive committee asks, in effect: What do you recommend?
THE REAL DYNAMIC
A procurement review can contain excellent analysis and still leave the executive audience without a usable decision.
Consider a supplier nomination. The team may understand cost breakdowns, capacity, quality history, tooling, country exposure and contractual risk. In the executive meeting, however, presenting each uncertainty in sequence can unintentionally transfer the integration work upward.
A more executive formulation reads differently:
Recommend Supplier A.
We rejected B because its capacity ramp misses the programme window, and C because the commercial advantage does not compensate for the qualification risk.
The assumption that would change our recommendation is tooling lead time: beyond 14 weeks, B becomes the stronger option.
After 15 November, waiting costs more than the remaining information is likely to improve the decision.
That is not manufactured certainty. It is a visible separation between what is known, what remains uncertain and what still matters to the choice.
Kahneman, Lovallo and Sibony make a related distinction: executives can examine not only the recommendation itself but also the process by which the recommending team reached it. Their 12-question checklist is designed to expose biases including self-interest, overconfidence, attachment to previous decisions and weak comparison sets. They cite a McKinsey study of more than 1,000 business investments in which companies that worked to reduce the effects of bias raised their returns by seven percentage points (Kahneman et al., 2011).
For procurement, that suggests one way to resolve the apparent tension between decisiveness and analytical integrity: accelerate the decision, and subject the recommendation to disciplined challenge.
In practice, the review can be reduced to three checks.
Check | Questions |
|---|---|
The recommending team | Who benefits from this recommendation? Which position has the team already become attached to? |
The recommendation | Which credible alternative was rejected? Which assumption carries most of the conclusion? Which external reference point challenges our internal estimate? |
The downside | If we are wrong, what becomes irreversible? What becomes more expensive if we wait? |
This preserves scrutiny without turning scrutiny into indefinite postponement.
There is also a behavioural side. Herminia Ibarra observes that leaders entering unfamiliar roles can mistake unfamiliar behaviour for inauthentic behaviour (Ibarra, 2015). For a leader accustomed to proving credibility through completeness, stating the recommendation first may initially feel uncomfortably assertive — which says more about habit than about the format.
WHAT STRONG LEADERS DO DIFFERENTLY
Before the next executive review, they prepare four lines before preparing the appendix.
Line | Content |
|---|---|
Decision requested | What exactly needs approval? |
Recommendation | What should the organisation do? |
Rejected alternatives | Which two serious alternatives were considered, and why were they rejected? |
Decision boundary | Which assumption would reverse the recommendation, and when does delay become more costly than the remaining uncertainty? |
The appendix still matters. It demonstrates that the recommendation can withstand challenge.
It simply no longer has to come first.
CPO PATH DIAGNOSTIC
Statement | Fully true | Partly true | Not true |
|---|---|---|---|
I can state my recommendation before explaining the analysis. | ☐ | ☐ | ☐ |
I distinguish unresolved information from information that could change the decision. | ☐ | ☐ | ☐ |
I can name the strongest rejected alternative. | ☐ | ☐ | ☐ |
I know the downside of being wrong and the cost of waiting. | ☐ | ☐ | ☐ |
My recommendation can withstand challenge without requiring certainty. | ☐ | ☐ | ☐ |
ONE-LINE VERDICT
Executive presence is not certainty in the absence of evidence; it is the ability to make a defensible call before the evidence becomes complete.
YOUR TURN
Which decision are you taking to your next executive review? Reply with one line, I read every answer.
QUICK WINS
Today: take the last deck you presented upward and write its four lines. Note how far into the deck the recommendation first appeared.
This week: open your next steering-committee item with the recommendation and the decision boundary, and move the analysis to the appendix.
This month: run the three checks on one pending sourcing decision before it reaches the executive level.
{{first_name}} - Did this episode add value to you?
I read every single message, and past posts already shaped this space. Reach out to me and tell me what you’re up to and the path you’ve chosen or post online your thoughts about this episode. I read every email and linked post.
Talk soon,
Pascal
Did this resonate with you?
Tools I use to improve efficiency and ensure stable processes:
A CRM so smart, it updates itself.
HubSpot's CRM is so smart, it now updates itself. Calls get logged and summarized the moment they end. New leads get researched and a first outreach drafted, automatically. Deals move forward on their own, with next steps flagged before you have to ask.
Even the one repetitive task you've been meaning to fix can now run itself, no code required. Customers using it are already seeing the difference.
This isn't the CRM you have to work hard to figure out. It's the one already working before you log in.
SOURCES
Botelho, E. L., Powell, K. R., Kincaid, S., & Wang, D. (2017). What sets successful CEOs apart. Harvard Business Review, 95(3), 70–77. https://hbr.org/2017/05/what-sets-successful-ceos-apart
Ibarra, H. (2015). The authenticity paradox. Harvard Business Review, 93(1/2), 52–59. https://hbr.org/2015/01/the-authenticity-paradox
Kahneman, D., Lovallo, D., & Sibony, O. (2011). Before you make that big decision. Harvard Business Review, 89(6), 50–60. https://hbr.org/2011/06/the-big-idea-before-you-make-that-big-decision
Watkins, M. D. (2012). How managers become leaders. Harvard Business Review, 90(6), 64–72. https://hbr.org/2012/06/how-managers-become-leaders
Thank you for your time and trust,
Pascal Hecker | Editor-In-Chief, CPO Path.