Information is not neutral: the way a portfolio is represented can change the decision leaders are capable of making.
Two executive teams receive the same underlying portfolio data.
The first receives a forty-page pack: project status, financial tables, risk logs and a list of dependencies. The second receives the same evidence, but the critical dependencies are also represented as a network showing which initiatives rely on the same platforms, resources and predecessor outcomes.
The data are equivalent. The decision environment is not.
This matters because portfolio leadership is a cognitive task. Executives must interpret incomplete information, compare multiple criteria, recognise interactions and decide under time pressure. A reporting system that makes those interactions difficult to see increases the probability of local decisions with system-wide consequences.
The Strategic Context
Killen's 2013 experimental study examined how different representations of project interdependencies affected portfolio decision-making. The research compared non-graphical tabular lists, dependency matrices and network-based visual project maps in a controlled decision scenario.
The study sits within the concept of bounded rationality. Decision-makers rarely have complete information, unlimited cognitive capacity or unlimited time. Portfolio decisions amplify all three limitations because leaders must simultaneously consider strategy, financial value, risk, resources, project status and interdependencies.
Killen found that the type of representation was associated with decision quality. Visual tools, particularly network mapping, were correlated with stronger results in the experiment. The adequacy of time was also strongly related to decision quality and confidence. The study does not prove that one visual method will improve every real executive portfolio. Its classroom-based experimental context and simplified scenario limit generalisation. But the underlying lesson is strategically important: decision interface design deserves governance attention.
What Leaders Commonly Misread
The first misread is that more data produces better decisions. Beyond a point, additional information can increase cognitive load without increasing insight.
The second is that if the source data are the same, the presentation is merely cosmetic. Representation determines which patterns are visible, which comparisons are easy and which relationships remain hidden.
The third is that dashboards are passive reporting tools. A dashboard directs attention. By choosing what appears on the first page, what is aggregated, what is colour coded and what is omitted, the system shapes the conversation.
The fourth is that executives can compensate for poor representation through experience. Experience helps, but complex systems contain indirect and multi-step relationships that are difficult to hold in working memory.
Reframing the Issue
Portfolio reporting should be designed as decision architecture.
The purpose is not to show everything that is known. It is to make the information needed for a specific decision visible in a form that respects human cognitive limits.
That requires a shift from “What can the system report?” to “What must the decision-maker understand?”
Related article: Portfolio Reporting Should Change Decisions, Not Produce More Data
Dependencies Are Hard to See in Lists
A simple dependency list can tell leaders that Project A depends on Project B and Project B depends on Project C. What it may fail to make cognitively obvious is that a decision about Project C can propagate to Project A through the chain.
Dependency matrices improve structure, but Killen notes that matrices do not automatically reveal indirect multi-step relationships. Network representations can make those chains more visible by showing projects as connected nodes.
This matters because portfolio failures are often propagated failures. A platform delay affects a product launch. The product launch delays a market transition. The transition delay keeps a legacy system alive. The legacy system absorbs scarce technical capability required elsewhere.
Each event may be manageable in isolation. The chain is the strategic issue.
Related article: Interdependencies Are Portfolio Risk: Why Project Dashboards Miss the System
Time Is Part of the Decision System
Killen's research found a strong association between participants' perception that they had enough time and the quality and confidence of their decisions.
That should make leaders cautious about compressing major portfolio choices into the last fifteen minutes of a packed governance agenda.
Time pressure encourages shallow evaluation, rapid anchoring and premature closure. A sophisticated portfolio pack cannot compensate for a governance process that gives decision-makers no time to interrogate it.
The relevant design question is therefore not only “What information?” but also “When is it available, how much time is provided for interpretation, and which decisions deserve separate deliberation?”
High-reversibility choices can tolerate faster governance. Large irreversible allocations, complex dependency changes and strategic exits deserve more deliberate attention.
A Good Portfolio View Shows Relationships, Not Just Status
Traditional reporting tends to organise information by project because projects are convenient reporting units. The enterprise, however, experiences outcomes through relationships.
Executives may need views organised by:
- strategic objective;
- shared capability;
- customer journey;
- technology platform;
- regulatory obligation;
- dependency cluster;
- resource constraint;
- benefit pathway;
- risk concentration.
No single view is sufficient. The portfolio interface should allow leaders to rotate the system mentally.
A project-centric view answers, “How is each project performing?” A capability view asks, “Which initiatives compete for the same scarce capability?” A dependency view asks, “What else fails if this initiative slips?” A strategic view asks, “Where is the organisation investing against each objective?”
These are different questions requiring different representations.
Decision Framework: Design the Interface Around the Decision
Use six principles when designing portfolio information for executives.
1. Start with the decision
Define the decision before building the pack. A resource-reallocation decision requires different evidence from an investment-entry decision or a benefits review.
2. Separate signal from inventory
The full data set can remain available, but the primary interface should emphasise material changes, exceptions, dependencies and assumptions.
3. Visualise relationships when relationships drive consequence
Use network, sequence or dependency representations when indirect effects matter. Do not use a visual simply because it looks sophisticated.
4. Show uncertainty explicitly
Ranges, confidence, assumptions and scenario differences are often more useful than a single point estimate.
5. Provide alternative views
A complex portfolio should be inspectable by strategy, value, capability, risk and dependency. If the decision looks strong only from one view, that is itself useful evidence.
6. Allocate decision time deliberately
Treat executive attention as a scarce portfolio resource. Major choices require protected interpretation time, not just a longer paper.
From Strategy to Execution
Immediate action is to select one upcoming portfolio decision and redesign the information around that decision rather than around the existing reporting template. Remove anything that does not change the choice. Add any relationship that could materially alter it.
Medium-term capability building means developing a consistent portfolio information model across projects so that dependency, capacity and benefit data can be connected. This does not require a single technology platform, but it does require common definitions and ownership.
Long-term strategic positioning involves treating decision design as a leadership capability. Portfolio teams should become skilled not only at collecting data but at structuring complex evidence so that executives can interrogate trade-offs quickly without losing systemic relationships.
Signals to Monitor
Be concerned when executives repeatedly ask for information that already exists in the pack but cannot be found. That is a representation failure.
Other warning signs include decisions made from project-by-project status without dependency analysis, portfolio packs growing every quarter, identical dashboards used for every decision type, leaders discovering indirect impacts after approval, and important decisions routinely deferred because the meeting ran out of time.
A positive signal is that leaders can describe the few relationships that make a decision difficult before discussing the individual project statuses.
References
- Killen, C.P. 2013, 'Evaluation of project interdependency visualizations through decision scenario experimentation', International Journal of Project Management, vol. 31, no. 6, pp. 804–816.
Questions for the Leadership Team
- Which portfolio relationships are currently difficult to see in our standard reporting?
- Are our governance packs designed around decisions or around available data?
- Which indirect dependency could create the largest surprise if one initiative changes?
- Do major irreversible decisions receive enough interpretation time?
- What would the portfolio look like if we organised it by shared capability rather than by project?
- Which measures are included because they are easy to report rather than because they change a decision?
Closing Perspective
Executives do not make decisions on raw reality. They make decisions on representations of reality. That makes information design a governance responsibility. The strongest portfolio reporting system is not the one that contains the most data. It is the one that makes the material relationships visible early enough, clearly enough and quickly enough for leaders to choose differently when the system demands it.
About EraNorth Insights
EraNorth Insights publishes practical analysis on strategy, projects, operations, transformation and decision intelligence for professional and organisational use. About EraNorth.