Knowing a framework can improve the quality of a question; judgement is knowing when the framework is incomplete, when assumptions are wrong and what to do next.
Why can a technically knowledgeable manager struggle when facing a real enterprise problem?
Because real situations do not arrive organised into textbook categories.
The fictional InnovaLast case and the accompanying assessment material make this point more clearly than many management frameworks do. The case-study instructions ask the analyst to identify problems, determine which problems are major, develop alternatives, recommend the best solution and explain implementation. They also warn against misunderstanding what is happening, oversimplifying deeper issues and proposing recommendations that are unrealistic or unaffordable.
The marking guide goes further. At its highest performance level, it rewards questioning the assumptions and values underpinning prior knowledge and resolving inconsistencies between what was previously expected and what is encountered in practice.
A reflective report from the same source batch reaches a similar conclusion from the learner's perspective: understanding portfolio-management concepts is easier than applying them in a changing real-world situation.
That is not merely an academic learning point.
It is the foundation of executive judgement.
The Strategic Context
Senior leaders rarely fail because they know no management frameworks.
They fail because they:
- diagnose the wrong problem;
- accept an assumption too quickly;
- mistake symptoms for causes;
- choose an attractive solution before comparing alternatives;
- ignore implementation constraints;
- become overconfident in prior experience;
- fail to recognise when conditions have changed.
Frameworks can reduce these errors by providing structure.
They become dangerous when structure is mistaken for reality.
A portfolio framework may tell leaders to prioritise investments. It cannot determine automatically which political, ethical, commercial and operational trade-offs should be accepted in a specific organisation.
A risk framework can help identify exposure. It cannot decide how much uncertainty a Board should accept to preserve an opportunity.
A stakeholder framework can map influence. It cannot resolve a genuine conflict between growth and customer retention when both require the same scarce resource.
Judgement is required because the decision contains context the framework cannot fully encode.
What Leaders Commonly Misread
The first mistake is starting with a solution.
Once an executive believes the organisation "needs a PMO", "needs AI", "needs a new facility" or "needs to offshore", subsequent analysis can become a search for supporting evidence.
The second is treating the visible problem as the real problem.
Late projects may be caused by poor planning, but they may also be caused by portfolio overload, slow governance or shared-resource constraints.
The third is assuming experience transfers cleanly.
Prior experience is valuable, but the same pattern can have a different cause in a different system.
The fourth is confusing decisiveness with speed.
Decisive leadership does not mean making every decision immediately. It means knowing what evidence is necessary, what uncertainty can be tolerated and when delay is itself costly.
The fifth is using analysis to avoid responsibility.
No framework removes the need for a recommendation. Leaders eventually have to choose.
Reframing the Issue
A better model is:
diagnose before you prescribe, challenge before you commit, and learn after you act.
This can be expressed as a seven-stage judgement cycle:
- Observe.
- Separate fact from interpretation.
- Diagnose the system.
- Challenge assumptions.
- Generate alternatives.
- Decide proportionately to evidence and reversibility.
- Learn from the result.
The cycle is iterative rather than linear.
New evidence can force leaders back to diagnosis.
That is not indecision. It is disciplined adaptation.
Step 1: Observe Without Collapsing Everything Into a Story
Leaders naturally create narratives.
Revenue fell because sales underperformed.
The project is late because the project manager is weak.
The stakeholder is difficult because they resist change.
These stories can be true. They can also be premature.
Observation requires separating:
- facts;
- reported opinions;
- assumptions;
- causal claims;
- predictions;
- missing information.
The original InnovaLast case is useful here because some reflective drafts interpret the chronology inaccurately or blur project, program and portfolio concepts. The lesson is important: secondary interpretation should not override primary evidence merely because it sounds confident.
Executives need the same discipline when reading Board papers, consultant reports and project dashboards.
Step 2: Diagnose the System Producing the Result
A symptom belongs to a system.
The fictional predecessor appliance company does not simply have a marketing problem. Cost structure, retailer economics, customer willingness to pay, competitor imitation and financing capacity interact.
The InnovaLast growth challenge is not simply a stakeholder problem. Manufacturing, facilities, technology, product development, market expansion, governance and strategic partnership interact.
Systems thinking asks:
What set of conditions is producing this result?
That question prevents local solutions from making the wider system worse.
Related article: Interdependencies Are Portfolio Risk: Why Project Dashboards Miss the System
Step 3: Challenge the Assumptions You Prefer
The marking guide's emphasis on questioning prior assumptions is especially useful for executives because seniority increases the risk of unchallenged beliefs.
A leader may believe:
- local manufacturing is essential to quality;
- offshore manufacturing is always cheaper;
- growth should receive priority over retention;
- a strategic investor will remain aligned;
- a PMO will improve control;
- a digital solution will reduce operating cost.
Each claim may be reasonable.
None should be accepted solely because an experienced leader believes it.
Strong judgement asks:
- what evidence supports the assumption?
- what evidence would contradict it?
- is the assumption still true under current conditions?
- what decision changes if it is wrong?
Step 4: Generate Real Alternatives
Weak decision papers compare the preferred solution with doing nothing.
Strong decision papers compare credible pathways.
For a manufacturing decision, alternatives might include:
- local modernisation;
- offshore production;
- strategic partnership;
- hybrid production;
- staged pilot;
- product redesign that changes the economics.
For a capability problem, alternatives might include building internally, buying externally, simplifying demand or changing the strategy.
The purpose is not to create option overload.
It is to prevent premature commitment.
Related article: Business Cases Are Investment Hypotheses, Not Permission Slips
Step 5: Evaluate Trade-Offs, Not Just Benefits
Every serious executive decision gives something up.
A strategic partner can add capital and reduce independence.
A faster transformation can increase change saturation.
A central PMO can improve enterprise visibility but create distance from delivery.
Local manufacturing can protect capability while consuming more capital.
Good recommendations make these trade-offs explicit.
This is what separates decision-grade advice from advocacy.
Step 6: Match the Evidence Threshold to Reversibility
Not every decision needs perfect information.
A low-cost experiment can proceed with uncertainty because it is easy to stop.
A major acquisition, facility commitment or equity transaction deserves stronger evidence because the decision is difficult to reverse.
A practical rule is:
The more irreversible the decision, the more uncertainty leaders should resolve before committing.
This prevents both reckless action and analysis paralysis.
Step 7: Turn Reflection Into Organisational Learning
The reflective-report material is valuable because it recognises gaps in applying theory and proposes further case analysis, discussion and risk-management learning.
At enterprise level, reflection should become more systematic.
After major decisions, leaders should ask:
- what did we believe?
- what actually happened?
- which assumptions were wrong?
- what signals did we miss?
- what will we change in future investment or governance?
This is not a lessons-learned ceremony at project close.
It is a feedback mechanism for executive judgement.
Decision Framework
Before accepting a major recommendation, use the following test.
Problem
Are we solving the underlying problem or the most visible symptom?
Evidence
Which claims are facts, which are interpretations and which are assumptions?
Alternatives
Have credible alternatives been considered fairly?
Trade-offs
What value, control, capacity or optionality is sacrificed by the recommendation?
Feasibility
Can the organisation execute the solution with its actual capability and constraints?
Reversibility
What happens if the decision is wrong, and how difficult is it to change course?
Learning
What evidence will tell us whether the decision is working, and when will we review it?
A recommendation that cannot answer these questions is not yet decision-grade.
From Strategy to Execution
Immediate action: require major decision papers to state assumptions, alternatives and the evidence that would change the recommendation.
Medium-term capability building: train portfolio, program and executive teams in structured diagnosis, scenario thinking and post-decision review rather than only in delivery methods.
Long-term strategic positioning: create a leadership culture in which changing one's view in response to better evidence is treated as strength rather than inconsistency.
The objective is not to make decision-making slow.
It is to make thinking explicit enough that the organisation can improve it.
Signals to Monitor
Watch for preferred solutions appearing before problem statements; repeated use of frameworks without context; recommendations that contain benefits but no trade-offs; leaders dismissing contradictory evidence because "we have seen this before"; lessons learned that do not change future decisions; and major commitments with no explicit assumptions or review triggers.
Another signal is the quality of executive questions. When meetings focus mainly on defending recommendations rather than testing them, judgement is becoming performative.
Questions for the Leadership Team
- What assumptions are we currently treating as facts?
- Which problem are we solving, and what evidence tells us it is the root problem?
- What credible alternative have we not explored because it challenges an existing preference?
- What do we give up if we choose the recommended option?
- How reversible is the decision, and is our evidence threshold appropriate?
- What would cause us to change our mind after implementation?
- How do we ensure lessons from prior decisions alter future portfolio choices?
Closing Perspective
Frameworks are valuable because they structure complexity.
Judgement is valuable because reality does not respect the boundaries of the framework.
The strongest leaders do not abandon models. They use them as instruments, challenge the assumptions behind them and remain accountable for the recommendation that follows.
The quality of a decision depends less on how confidently the framework is applied than on how accurately the system is diagnosed before action begins.
About EraNorth Insights
EraNorth Insights publishes practical analysis on strategy, projects, operations, transformation and decision intelligence for professional and organisational use. About EraNorth.