Abstract
Organizations have become increasingly sophisticated at managing work after delivery begins, yet many consequential choices are still made before formal project, product, program, or portfolio controls are fully engaged. This paper defines the decision-readiness gap as the interval between the moment an idea or request attracts organizational attention and the moment leaders possess enough clarity, evidence, ownership, and governance context to make a defensible commitment. The paper argues that the gap is widening as artificial intelligence, low-code tooling, distributed technology ownership, and faster experimentation increase the number and speed of requests entering enterprise systems. Drawing on public research from NIST, McKinsey, Deloitte, Microsoft, IBM, and PMI, the analysis distinguishes demand capture from intake governance and proposes a public decision-readiness model that can be applied before delivery. The model is intentionally conceptual; it does not disclose the proprietary Lean Intake Analysis™ scoring method. The central proposition is that a disciplined upstream decision can improve traceability, clarify accountability, and reduce the amount of unresolved decision work transferred into delivery teams.
Keywords: enterprise intake, decision readiness, governance, portfolio management, artificial intelligence, PMO, operating model, demand management
1. The problem exists before the project starts
Many enterprises have mature practices for schedule management, delivery risk, product backlogs, architecture review, cybersecurity, financial controls, and post-implementation measurement. Those controls matter, but they often activate after a request has already accumulated political support, budget expectations, stakeholder commitments, or delivery momentum. At that point, the organization may be managing the consequences of an earlier decision rather than evaluating whether the decision was sufficiently formed in the first place.
Lean Intake Analysis™ treats this front end as a governance problem rather than a form-completion problem. The relevant question is not simply whether a request has been submitted correctly. The relevant question is whether the organization has enough information, alignment, and accountable ownership to decide what should happen next.
Demand capture records that someone wants something. Intake governance determines whether the enterprise has enough evidence and accountability to make a decision about that request.
This distinction aligns with broader governance practice. PMI describes governance as consequential to strategic initiatives, portfolios, programs, and projects, and its current PMBOK guidance emphasizes value delivery, accountability, risk, stakeholders, and governance as connected dimensions of modern project work. NIST makes the same upstream principle explicit for AI: after mapping context and risk, framework users should have enough contextual knowledge to inform an initial go/no-go decision about whether to design, develop, or deploy an AI system (NIST, 2023).
2. Why the decision-readiness gap is widening
The volume and velocity of enterprise demand are increasing faster than many operating models were designed to absorb. McKinsey reported that 88% of surveyed organizations used AI in at least one business function in 2025, while only 7% reported that AI had been fully scaled across the organization. The difference between broad use and enterprise-scale operating maturity is important: it suggests that organizations can generate and adopt new capabilities faster than they can standardize the systems that govern them (McKinsey & Company, 2025).
More recent 2026 research strengthens that interpretation. Deloitte found that nearly three quarters of surveyed technology executives expected their operating models to require change within 12 to 18 months to sustain AI progress, even though 81% said their organizations could deploy and govern AI at scale. Deloitte frames the scaling problem as an operating-model challenge involving decision rights, capital allocation, risk governance, accountability, and cross-functional coordination (Wilson et al., 2026).
Microsoft reached a related conclusion from a different evidence base. Its 2026 Work Trend Index found that organizational conditions—culture, manager support, talent practices, rules, and governance maturity—accounted for more reported AI impact than individual effort alone. Only 19% of surveyed AI users fell into Microsoft’s high-capability, high-readiness “Frontier” zone, while the remainder occupied blocked, stalled, unclaimed, or still-emerging conditions (Microsoft, 2026).
IBM’s 2026 C-suite study highlights the control consequence. Among 2,000 technology executives surveyed, 70% said business teams were deploying technology faster than IT could track, 77% said AI adoption was outpacing current governance capabilities, and only 11% believed they were fully prepared for the expected scale of AI agent deployment (IBM, 2026). These findings do not prove that enterprise intake is the cause of the scaling gap. They do show why the quality of upstream decisions is becoming materially more important.
3. A working definition of decision readiness
Decision readiness is the condition in which an organization has sufficient clarity, evidence, ownership, stakeholder context, and governance information to make an accountable decision about whether and how a request should advance. It is not the same as delivery readiness. A request can be decision-ready and still require substantial discovery, design, planning, or engineering before implementation begins.
The concept is deliberately threshold-based rather than perfection-based. The objective is not to eliminate uncertainty. The objective is to identify whether the remaining uncertainty is understood, owned, and acceptable for the decision being made.
| Public dimension | What it establishes |
|---|---|
| Problem clarity | The need, opportunity, or risk is expressed clearly enough to distinguish symptoms from the decision that must be made. |
| Strategic and value context | The request has an articulated relationship to organizational objectives, customer or stakeholder value, compliance, resilience, cost, growth, or another legitimate enterprise outcome. |
| Ownership and accountability | A business owner is identifiable and prepared to own the outcome, not merely sponsor the submission. |
| Stakeholder alignment | Materially affected functions and decision-makers have been identified; known conflicts or unresolved viewpoints are visible. |
| Evidence and assumptions | Material assumptions, known facts, unknowns, dependencies, and evidence gaps are explicit enough to support a decision. |
| Risk and constraint context | Relevant risk, security, regulatory, architectural, data, financial, operational, or capacity constraints are surfaced at the appropriate level. |
| Decision and governance conditions | The approving authority, decision state, conditions, required follow-up, and accountability for next actions are clear. |
These dimensions are a public representation of the methodology and are not the proprietary LIA readiness score. Their purpose is to create a shared vocabulary for evaluating whether a request is ready for a decision.
4. The intake sequence: from signal to commitment
An enterprise request often travels through several distinct states that are collapsed into a single word—“intake.” Separating those states makes governance clearer.
Signal → Request → Clarification → Readiness → Decision → Governance → Delivery
The sequence does not require a slow, stage-gate process. It requires the organization to recognize that capturing demand, clarifying it, evaluating readiness, and committing resources are different management acts.
A signal is an observation, idea, obligation, opportunity, or problem. A request gives the signal enough structure to enter an organizational system. Clarification develops the minimum context needed for evaluation. Readiness asks whether the decision can be made responsibly. The decision records what will happen. Governance establishes conditions, owners, and traceability. Delivery begins only after the organization has made—and can explain—the commitment.
5. A Hold is an active governance decision
One of the most important implications of decision readiness is that “not yet” is a legitimate outcome. A Hold does not have to mean indecision, delay, or process failure. When evidence is incomplete, ownership is unresolved, a dependency is material, or a required stakeholder has not been engaged, a documented Hold can be the most disciplined decision available.
Likewise, approval need not be unconditional. A request can advance with conditions when the organization understands the remaining uncertainty and explicitly assigns responsibility for resolving it. This is materially different from allowing missing information to follow the work informally into delivery.
6. Decision readiness in the age of AI and agents
AI increases the importance of upstream governance because the distance between idea and execution is shrinking. Low-code tools, copilots, agent frameworks, and vendor platforms can turn a concept into a working prototype before architecture, security, risk, finance, data governance, procurement, or operating leadership has established a shared view of the request. The organization can therefore become operationally committed before it becomes decision-ready.
NIST’s AI Risk Management Framework provides a useful external parallel. The framework’s Map function emphasizes understanding purpose, context, users, benefits, costs, assumptions, risks, and human oversight before proceeding. The Manage function explicitly calls for determining whether the system achieves its intended purpose and whether development or deployment should continue. These are decision-readiness behaviors even though NIST does not use the Lean Intake Analysis terminology (NIST, 2023).
Deloitte’s 2026 analysis also emphasizes that AI scaling requires clarity about who owns AI strategy, who governs risk, how business leaders participate, how funding adapts, and where human decision gates remain nonnegotiable. Those operating-model questions are difficult to answer after an initiative is already embedded in delivery (Wilson et al., 2026).
7. Organizational implications
Decision readiness changes the role of several enterprise functions. It does not replace them; it gives them an earlier and more coherent point of engagement.
- PMO / EPMO: shift from receiving approved work to improving the quality and traceability of the decisions that create work.
- Product and business leadership: separate discovery and opportunity shaping from an irreversible delivery commitment.
- Architecture and engineering: surface material constraints and options while there is still room to change the request.
- Risk, security, legal, and compliance: engage proportionately before decisions create avoidable exposure.
- Finance and portfolio leadership: connect investment decisions to explicit assumptions, evidence, conditions, and owners.
- Executives: establish decision rights so speed does not depend on bypassing accountability.
8. Research propositions for future LIA publications
The decision-readiness concept should be tested empirically rather than accepted as a self-validating methodology claim. Future LIA research should examine whether measurable upstream conditions correlate with delivery outcomes.
- Do initiatives with explicit decision owners show fewer late-stage sponsorship or priority reversals?
- Does documenting assumptions and unresolved conditions before commitment reduce rework or escalation during delivery?
- Which readiness dimensions are most strongly associated with cycle time, cancellation rate, budget variance, or benefit realization?
- How does decision-readiness performance differ across AI, regulatory, customer, infrastructure, and transformation demand?
- Can enterprises increase intake speed while also increasing decision traceability?
9. Conclusion
Organizations do not need more bureaucracy at the front door. They need a clearer distinction between receiving work and deciding about work. The decision-readiness gap names the management space in which ideas become enterprise commitments before the information, ownership, and governance supporting those commitments are sufficiently visible.
As AI and distributed technology accelerate enterprise demand, governing that space becomes more important. A disciplined intake model should help leaders answer three questions before delivery inherits the consequences:
What are we deciding? What evidence supports the decision? Who owns what happens next?
References
- IBM. (2026, June 8). New IBM study finds CIOs and CTOs face growing AI control gap as enterprise deployment scales. https://newsroom.ibm.com/2026-06-08-new-ibm-study-finds-cios-and-ctos-face-growing-ai-control-gap-as-enterprise-deployment-scales
- McKinsey & Company. (2025, December 10). AI at work but not at scale. https://www.mckinsey.com/featured-insights/charts/ai-at-work-but-not-at-scale
- Microsoft. (2026, May 5). 2026 Work Trend Index Annual Report: Agents, human agency, and the opportunity for every organization. https://www.microsoft.com/en-us/worklab/work-trend-index/agents-human-agency-and-the-opportunity-for-every-organization
- National Institute of Standards and Technology. (2023). Artificial Intelligence Risk Management Framework (AI RMF 1.0). https://nvlpubs.nist.gov/nistpubs/ai/nist.ai.100-1.pdf
- Project Management Institute. (2025). PMBOK Guide - Eighth Edition. https://www.pmi.org/standards/pmbok
- Wilson, M., Shaikh, A., Caplan, M., & Mahto, M. (2026, June 29). Rewiring the enterprise operating model for AI scale. Deloitte Insights. https://www.deloitte.com/us/en/insights/topics/technology-management/rewiring-ai-operating-model.html