2026 05 14 org failure modes project demand product it

Project-Based Demand Governance With Product-Structured IT Teams: Empirically Observed Organisational Failure Modes

Research Question

What failure modes have been empirically observed in organisations where demand is managed through a project-based model while information technology (IT) teams are structured and operated as product teams?

Scope

In scope:

Empirically documented failure modes arising from the mismatch between project-based demand governance, fixed scope, fixed budget, defined end date, and product-team operating models, persistent teams, continuous delivery, outcome-focused
Literature and case studies on dual funding tensions: project budgets cutting across product team capacity
Observable symptoms: funding gaps, priority conflicts, team instability, erosion of product ownership
Evidence from organisations in transition from project to product delivery
Frameworks such as the Project-to-Product transition and Team Topologies as analytical lenses

Out of scope:

Pure theoretical arguments without supporting empirical or case-study evidence
Failure modes unrelated to the project-vs-product structural mismatch
Prescriptive transformation roadmaps without evidence of effectiveness

Constraints:

Prefer empirical sources, surveys, case studies, retrospectives, and audit-style evidence, over unsupported consulting opinion
Every source must include a verifiable Uniform Resource Locator (URL)
Acronyms expanded on first use throughout

Context

[inference; source: https://info.planview.com/rs/456-QCH-520/images/Planview_2023-Project-to-Product-State-of-the-Industry-Report.pdf; https://itrevolution.com/articles/funding-model-the-seven-domains-of-transformation/; https://www.thoughtworks.com/insights/blog/leadership/funding-agility-moving-beyond-project-budgets] This item examines a common transitional state in which organisations keep annual project budgeting, project approval gates, and project reporting, while asking long-lived product teams to deliver continuous outcomes.
[inference; source: https://less.works/blog/2026/02/20/project-based-funding-in-product-development; https://www.cio.com/article/196208/creating-a-new-funding-model-for-product-based-it.html; https://github.com/davidamitchell/Research/blob/main/Research/completed/2026-05-14-org-failure-modes-accountability-gaps.md] The central risk is governance mismatch, because capacity, backlog authority, and accountability for long-term product health no longer sit in the same place.

Approach

Define the key distinguishing characteristics of project-based and product-based demand management, using public sources on project-to-product transitions and team design.
Search for empirical evidence, industry surveys, case studies, and practitioner retrospectives, of failure modes that emerge specifically when product teams remain under project funding or project governance.
Catalogue recurring failure modes, including over-commitment, backlog fragmentation, team instability, weak product ownership, and dependency bottlenecks.
Examine whether the severity of failure modes varies by industry, organisation size, or degree of product-operating-model maturity.
Identify empirically supported approaches for managing the transition period and mitigating failure.

Sources

Research Skill Output

(Full output from running the research skill - retained verbatim in the completed item. Sections 0-5 are the investigation; section 6 seeds the Findings section below.)

§0 Initialise

Question: identify empirically observed failure modes created when project-based demand governance controls funding, approval, or reporting, while delivery is expected from long-lived product teams.

Scope: in scope are recurrent failure modes, severity patterns, and evidence-backed mitigations from public surveys, case studies, and practitioner retrospectives; out of scope are pure theory and untested transformation playbooks.

Constraints: prefer public, citable sources; separate direct observation from structural inference; use completed repository items only as adjacent synthesis support, not as the sole basis for central domain terms.

Output: knowledge, specifically a structured synthesis with executive summary, key findings, evidence map, assumptions, analysis, risks, and open questions.

Mode: full.

[inference; source: https://github.com/davidamitchell/Research/blob/main/Research/completed/2026-05-14-org-failure-modes-accountability-gaps.md; https://github.com/davidamitchell/Research/blob/main/Research/completed/2026-05-14-org-failure-modes-cohort-demand-domain-it.md] Prior completed repository work already covers adjacent accountability ambiguity and boundary-mismatch queueing, so this item treats project-based demand as a specific governance mechanism that recreates those broader failure surfaces.
[assumption; source: https://info.planview.com/rs/456-QCH-520/images/Planview_2023-Project-to-Product-State-of-the-Industry-Report.pdf; https://itrevolution.com/articles/funding-model-the-seven-domains-of-transformation/] Public evidence is stronger for large-enterprise project-to-product transitions than for small firms, so enterprise cases are used as the main empirical base for this item.

§1 Question Decomposition

Root question: what failure modes appear when project demand governs long-lived product teams?
- A. Definitions
  - A1. What counts as project-based demand governance?
  - A2. What counts as a product-team operating model?
  - A3. What mechanisms connect the mismatch to observable failure?
- B. Direct failure modes
  - B1. What planning and capacity failures are observed?
  - B2. What backlog and prioritisation failures are observed?
  - B3. What ownership and accountability failures are observed?
  - B4. What delivery and release bottlenecks are observed?
  - B5. What team-stability and knowledge-retention failures are observed?
- C. Variation and context
  - C1. Does severity change with organisation scale or shared-service complexity?
  - C2. Does severity change with maturity of product management and funding reviews?
- D. Mitigations
  - D1. Which interventions have direct empirical support?
  - D2. Which recommendations remain inferential or practitioner-led?

§2 Investigation

2.1 Definitions and baseline

[fact; source: https://less.works/blog/2026/02/20/project-based-funding-in-product-development] Bas Vodde defines project-based development as work managed through projects with a goal, relatively fixed scope, expected timeline, and funding and prioritisation as one whole, after which new work requires a new project.
[fact; source: https://www.cio.com/article/196208/creating-a-new-funding-model-for-product-based-it.html; https://www.thoughtworks.com/insights/blog/leadership/funding-agility-moving-beyond-project-budgets] The accessible transition literature describes product-team funding as stable funding for standing cross-functional teams, with ongoing roadmap and backlog authority rather than a one-off project budget.
[fact; source: https://teamtopologies.com/key-concepts; https://teamtopologies.com/book] Team Topologies defines stream-aligned teams as long-lived teams aligned to a flow of work that own an end-to-end slice and reduce handoffs and dependencies.
[inference; source: https://less.works/blog/2026/02/20/project-based-funding-in-product-development; https://www.cio.com/article/196208/creating-a-new-funding-model-for-product-based-it.html; https://teamtopologies.com/key-concepts] The mismatch begins when a team is expected to behave like a product team, maintain a durable backlog, preserve architecture and operational health, and respond to new evidence, while the intake and budget model still behaves like a project portfolio.

2.2 Planning and capacity failure

[fact; source: https://info.planview.com/rs/456-QCH-520/images/Planview_2023-Project-to-Product-State-of-the-Industry-Report.pdf] The Planview 2023 Project to Product State of the Industry Report says 37 percent of respondents still use exclusively annual project budgets, while only 12 percent report a continuous, flexible funding model.
[fact; source: https://info.planview.com/rs/456-QCH-520/images/Planview_2023-Project-to-Product-State-of-the-Industry-Report.pdf] The same report says top-down annual project-based budgeting cycles create large batches of demand that outweigh delivery-team capacity, and reports systems data showing only 8 percent of what is planned by Agile teams gets delivered.
[fact; source: https://itrevolution.com/articles/funding-model-the-seven-domains-of-transformation/] IT Revolution's cross-enterprise interview synthesis says antiquated funding models create friction because they make it difficult to show business outcomes and value from product teams and are often the last transformation domain to change.
[inference; source: https://info.planview.com/rs/456-QCH-520/images/Planview_2023-Project-to-Product-State-of-the-Industry-Report.pdf; https://itrevolution.com/articles/funding-model-the-seven-domains-of-transformation/; https://www.thoughtworks.com/insights/blog/leadership/funding-agility-moving-beyond-project-budgets] Project-based demand systematically over-commits product teams because annual approvals and business cases create demand as large, pre-committed batches, while product teams can only absorb work through bounded ongoing capacity.

2.3 Backlog fragmentation and prioritisation conflict

[fact; source: https://less.works/blog/2026/02/20/project-based-funding-in-product-development] Vodde describes an interim model in which teams work from one Product Backlog, but each backlog item still carries a project identifier for funding and reporting, which preserves project accounting inside product development.
[fact; source: https://less.works/blog/2026/02/20/project-based-funding-in-product-development] The same article says keeping projects, even just for funding, causes lack of flexibility in development and unnecessary additional complexity.
[fact; source: https://itrevolution.com/articles/project-to-product-transformation-case-study-global-media-service-provider/] In the global media service provider case, leaders found that product managers focused on new features and struggled to incorporate incidents and other work types until the organisation standardised work types and made one backlog for all work.
[fact; source: https://teamtopologies.com/news-blogs-newsletters/2024/10/18/shifting-from-projects-to-products-insights-from-our-open-forum] Team Topologies' open forum reports that immature product management leaves teams behaving like feature factories and failing to balance feature work with defect fixing, risk mitigation, and technical debt reduction.
[inference; source: https://less.works/blog/2026/02/20/project-based-funding-in-product-development; https://itrevolution.com/articles/project-to-product-transformation-case-study-global-media-service-provider/; https://teamtopologies.com/news-blogs-newsletters/2024/10/18/shifting-from-projects-to-products-insights-from-our-open-forum] When project budgets remain the intake boundary, the product backlog stops being a single ranked expression of product value and becomes a negotiated merge of project claims, incidents, debt, and platform obligations.

2.4 Ownership erosion and matrix behaviour

[fact; source: https://www.cio.com/article/196208/creating-a-new-funding-model-for-product-based-it.html] The Chief Information Officer (CIO) article contrasts project mode, in which a business unit scopes a project and agrees a budget before requirements are understood, with perpetual team funding that gives end-to-end lifecycle accountability to dedicated teams.
[fact; source: https://itrevolution.com/articles/project-to-product-transformation-case-study-global-media-service-provider/] The global media service provider case says project managers were mission-focused and less interested in investment return on investment (ROI) or spend than product management, and that the organisation had to move project-management capability inside product groups.
[fact; source: https://less.works/blog/2026/02/20/project-based-funding-in-product-development] Vodde says the hybrid model only works if projects have no fixed people assigned to them, because otherwise managers try to secure dedicated resources for their own projects.
[inference; source: https://www.cio.com/article/196208/creating-a-new-funding-model-for-product-based-it.html; https://itrevolution.com/articles/project-to-product-transformation-case-study-global-media-service-provider/; https://less.works/blog/2026/02/20/project-based-funding-in-product-development; https://github.com/davidamitchell/Research/blob/main/Research/completed/2026-05-14-org-failure-modes-accountability-gaps.md] Project-demand governance recreates matrix behaviour inside product teams because the team nominally owns the product, but project sponsors, finance gates, and line managers still compete to direct the same capacity.

2.5 Delivery bottlenecks and slow feedback loops

[fact; source: https://teamtopologies.com/news-blogs-newsletters/2024/10/18/shifting-from-projects-to-products-insights-from-our-open-forum] The Team Topologies forum reports that release processes become bottlenecks when multiple teams work on the same product and coordination is pushed to the end of delivery.
[fact; source: https://dora.dev/capabilities/loosely-coupled-teams/] DevOps Research and Assessment says higher software-delivery performance requires teams to complete work, test, and deploy without fine-grained coordination with other teams.
[fact; source: https://teamtopologies.com/news-blogs-newsletters/2024/10/18/shifting-from-projects-to-products-insights-from-our-open-forum] The same forum reports customer-feedback loops stretching to as long as two months because internal silos and legacy systems prevent fast iteration.
[inference; source: https://teamtopologies.com/news-blogs-newsletters/2024/10/18/shifting-from-projects-to-products-insights-from-our-open-forum; https://dora.dev/capabilities/loosely-coupled-teams/; https://github.com/davidamitchell/Research/blob/main/Research/completed/2026-05-14-org-failure-modes-cohort-demand-domain-it.md] A project-governed product team inherits slow release and feedback loops when every meaningful change still has to satisfy project milestones, cross-team coordination, or end-stage governance gates before the team can learn from the market.

2.6 Team continuity, knowledge retention, and morale

[fact; source: https://www.cio.com/article/196208/creating-a-new-funding-model-for-product-based-it.html] The CIO article says team-based funding eliminates much of the ramp-up cost because cross-functional teams stay dedicated to a business domain instead of being built and disbanded around individual projects.
[fact; source: https://www.thoughtworks.com/insights/blog/leadership/funding-agility-moving-beyond-project-budgets] Thoughtworks says product planning requires dedicated standing product teams with explicit accountability cascades, iterative roadmaps, and authority to re-prioritise within quarterly and annual review cycles.
[fact; source: https://itrevolution.com/articles/project-to-product-transformation-case-study-fortune-100-retail-enterprise/] In the Fortune 100 retail case, the transformation replaced traditional project roles with product-team roles and identified role-transition failures, attrition, and frustration as concrete failure points during the shift.
[inference; source: https://www.cio.com/article/196208/creating-a-new-funding-model-for-product-based-it.html; https://www.thoughtworks.com/insights/blog/leadership/funding-agility-moving-beyond-project-budgets; https://itrevolution.com/articles/project-to-product-transformation-case-study-fortune-100-retail-enterprise/] Even when product teams formally exist, project-demand governance weakens continuity because it keeps teams exposed to stop-start funding, role ambiguity, and the expectation that capacity can be reshaped around the next approved project.

2.7 Variation by scale and maturity

[fact; source: https://info.planview.com/rs/456-QCH-520/images/Planview_2023-Project-to-Product-State-of-the-Industry-Report.pdf] Planview reports that only 8 percent of respondents have operationalised the shift at scale.
[fact; source: https://itrevolution.com/articles/funding-model-the-seven-domains-of-transformation/] IT Revolution says large enterprises often leave the funding model until late in the transformation because finance, capitalization, and accountability structures are hard to change politically.
[fact; source: https://itrevolution.com/articles/project-to-product-transformation-case-study-global-media-service-provider/] The global media case says 90 percent of spend was eventually aligned to products, but epics still competed for funding every two weeks and chargeback remained contentious.
[inference; source: https://info.planview.com/rs/456-QCH-520/images/Planview_2023-Project-to-Product-State-of-the-Industry-Report.pdf; https://itrevolution.com/articles/funding-model-the-seven-domains-of-transformation/; https://itrevolution.com/articles/project-to-product-transformation-case-study-global-media-service-provider/] Severity appears to increase with enterprise scale, shared services, and financial complexity, because hybrid project and product rules multiply approval points, backlog claimants, and dependency negotiations.

2.8 Mitigations and evidence quality

[fact; source: https://info.planview.com/rs/456-QCH-520/images/Planview_2023-Project-to-Product-State-of-the-Industry-Report.pdf] Planview identifies continuously funded build-and-run teams, mature product management, and flexible outcome-based funding review as the strongest markers of more mature product operating models.
[fact; source: https://www.thoughtworks.com/insights/blog/leadership/funding-agility-moving-beyond-project-budgets; https://www.cio.com/article/196208/creating-a-new-funding-model-for-product-based-it.html] Thoughtworks and CIO both recommend adapting annual and quarterly budget cycles so standing teams are funded for outcomes and can re-prioritise within their approved capacity.
[fact; source: https://itrevolution.com/articles/project-to-product-transformation-case-study-global-media-service-provider/] The global media case supports one visible backlog for all work and explicit capacity awareness across features, incidents, and epics to avoid overload.
[inference; source: https://info.planview.com/rs/456-QCH-520/images/Planview_2023-Project-to-Product-State-of-the-Industry-Report.pdf; https://www.thoughtworks.com/insights/blog/leadership/funding-agility-moving-beyond-project-budgets; https://www.cio.com/article/196208/creating-a-new-funding-model-for-product-based-it.html; https://itrevolution.com/articles/project-to-product-transformation-case-study-global-media-service-provider/] The strongest supported transition pattern keeps governance at the outcome and capacity-review level while leaving team-level prioritisation and backlog stewardship inside long-lived product teams.

§3 Reasoning

[inference; source: https://info.planview.com/rs/456-QCH-520/images/Planview_2023-Project-to-Product-State-of-the-Industry-Report.pdf; https://itrevolution.com/articles/funding-model-the-seven-domains-of-transformation/; https://itrevolution.com/articles/project-to-product-transformation-case-study-global-media-service-provider/] The strongest direct evidence comes from one survey-and-systems-data report and several public enterprise case studies that explicitly discuss funding-model friction during project-to-product transitions.
[inference; source: https://less.works/blog/2026/02/20/project-based-funding-in-product-development; https://www.cio.com/article/196208/creating-a-new-funding-model-for-product-based-it.html; https://www.thoughtworks.com/insights/blog/leadership/funding-agility-moving-beyond-project-budgets] The central causal mechanism is governance mismatch rather than a purely technical flaw, because the repeated symptom cluster appears where budget, approval, and reporting logic remain project-shaped after delivery has been reorganised into product teams.
[inference; source: https://teamtopologies.com/news-blogs-newsletters/2024/10/18/shifting-from-projects-to-products-insights-from-our-open-forum; https://dora.dev/capabilities/loosely-coupled-teams/; https://github.com/davidamitchell/Research/blob/main/Research/completed/2026-05-14-org-failure-modes-cohort-demand-domain-it.md] Delivery bottlenecks are not a separate failure class from backlog and ownership problems, because the same project-intake logic also increases dependency management, release batching, and slow feedback.
[assumption; source: https://info.planview.com/rs/456-QCH-520/images/Planview_2023-Project-to-Product-State-of-the-Industry-Report.pdf; https://itrevolution.com/articles/funding-model-the-seven-domains-of-transformation/] The absence of many controlled academic studies on the exact hybrid pattern means practitioner surveys and enterprise retrospectives are assumed to be the best accessible evidence family for this question.

§4 Consistency Check

[inference; source: https://info.planview.com/rs/456-QCH-520/images/Planview_2023-Project-to-Product-State-of-the-Industry-Report.pdf; https://itrevolution.com/articles/funding-model-the-seven-domains-of-transformation/] The evidence is consistent that funding-model change lags other product-operating-model changes and therefore acts as a persistent source of friction during transition.
[inference; source: https://less.works/blog/2026/02/20/project-based-funding-in-product-development; https://itrevolution.com/articles/project-to-product-transformation-case-study-global-media-service-provider/; https://www.cio.com/article/196208/creating-a-new-funding-model-for-product-based-it.html] No consulted source presents project funding as fully compatible with mature product-team behaviour without qualification; even transitional accommodations are described as compromises that preserve complexity or reduce flexibility.
[inference; source: https://itrevolution.com/articles/project-to-product-transformation-case-study-fortune-100-retail-enterprise/; https://itrevolution.com/articles/project-to-product-transformation-case-study-global-media-service-provider/; https://teamtopologies.com/news-blogs-newsletters/2024/10/18/shifting-from-projects-to-products-insights-from-our-open-forum] The main unresolved tension is that some organisations can operate hybridly for a period, but the evidence treats that state as transitional and high-friction rather than as a durable target model.
[inference; source: https://www.cio.com/article/196208/creating-a-new-funding-model-for-product-based-it.html; https://itrevolution.com/articles/project-to-product-transformation-case-study-fortune-100-retail-enterprise/; https://www.thoughtworks.com/insights/blog/leadership/funding-agility-moving-beyond-project-budgets] Alternative explanations such as role redesign failures, finance capability, or legacy architecture remain relevant, so project-based demand is best treated as a recurring amplifier and coordination failure rather than the sole cause of every bad outcome.

§5 Depth and Breadth Expansion

[inference; source: https://info.planview.com/rs/456-QCH-520/images/Planview_2023-Project-to-Product-State-of-the-Industry-Report.pdf; https://itrevolution.com/articles/funding-model-the-seven-domains-of-transformation/] Economic lens: annual project budgeting turns uncertainty into over-commitment, which then shows up as missed commitments, re-planning waste, and underused capacity models.
[inference; source: https://teamtopologies.com/news-blogs-newsletters/2024/10/18/shifting-from-projects-to-products-insights-from-our-open-forum; https://dora.dev/capabilities/loosely-coupled-teams/] Technical lens: the mismatch encourages large-batch releases and late coordination, which blocks the product-team goal of independent, continuous delivery.
[inference; source: https://www.cio.com/article/196208/creating-a-new-funding-model-for-product-based-it.html; https://itrevolution.com/articles/project-to-product-transformation-case-study-fortune-100-retail-enterprise/] Behavioural lens: when the funding model assumes temporary work, teams rationally optimise for delivery of the approved scope instead of long-term product health.
[inference; source: https://less.works/blog/2026/02/20/project-based-funding-in-product-development; https://github.com/davidamitchell/Research/blob/main/Research/completed/2026-05-14-org-failure-modes-accountability-gaps.md] Governance lens: project identifiers inside a shared backlog preserve decision-right ambiguity even if the team chart says "product team."
[inference; source: https://itrevolution.com/articles/funding-model-the-seven-domains-of-transformation/; https://info.planview.com/rs/456-QCH-520/images/Planview_2023-Project-to-Product-State-of-the-Industry-Report.pdf] Historical lens: the funding model repeatedly appears as one of the last structures to change in project-to-product transitions, which explains why hybrid failure modes persist even after teams and tooling have been renamed.

§6 Synthesis

Executive summary:

Project-based demand governance is repeatedly associated with over-commitment, backlog fragmentation, weak product ownership, and slow feedback loops when the same work is delivered by long-lived product teams. [inference; source: https://info.planview.com/rs/456-QCH-520/images/Planview_2023-Project-to-Product-State-of-the-Industry-Report.pdf; https://less.works/blog/2026/02/20/project-based-funding-in-product-development; https://itrevolution.com/articles/project-to-product-transformation-case-study-global-media-service-provider/]

The direct evidence is strongest for large-enterprise transition settings, where annual project budgets and project reporting survive after teams have been reorganised around products or long-lived work flows. [inference; source: https://info.planview.com/rs/456-QCH-520/images/Planview_2023-Project-to-Product-State-of-the-Industry-Report.pdf; https://itrevolution.com/articles/funding-model-the-seven-domains-of-transformation/]

The recurring mechanism is that project governance keeps budget, approval, and reporting attached to temporary initiatives, while product teams require stable capacity, one ranked backlog, and accountability for defects, risk, architecture, and operations over time. [inference; source: https://www.cio.com/article/196208/creating-a-new-funding-model-for-product-based-it.html; https://www.thoughtworks.com/insights/blog/leadership/funding-agility-moving-beyond-project-budgets; https://less.works/blog/2026/02/20/project-based-funding-in-product-development]

The strongest supported mitigation is continuously funded build-and-run teams with visible full-product backlog management and periodic outcome reviews, rather than project-by-project funding gates controlling day-to-day product priorities. [inference; source: https://info.planview.com/rs/456-QCH-520/images/Planview_2023-Project-to-Product-State-of-the-Industry-Report.pdf; https://itrevolution.com/articles/project-to-product-transformation-case-study-global-media-service-provider/; https://www.thoughtworks.com/insights/blog/leadership/funding-agility-moving-beyond-project-budgets]

Key findings:

Annual project budgeting creates a demand-capacity mismatch for product teams, because it approves work in large planned batches while stable teams can only absorb work through bounded ongoing capacity and re-prioritisation. ([inference]; high confidence; source: https://info.planview.com/rs/456-QCH-520/images/Planview_2023-Project-to-Product-State-of-the-Industry-Report.pdf; https://itrevolution.com/articles/funding-model-the-seven-domains-of-transformation/; https://www.thoughtworks.com/insights/blog/leadership/funding-agility-moving-beyond-project-budgets)
When project identifiers remain attached to backlog items, the product backlog becomes a negotiated merge of project claims, incidents, and technical debt instead of a single ranked view of product value. ([inference]; high confidence; source: https://less.works/blog/2026/02/20/project-based-funding-in-product-development; https://itrevolution.com/articles/project-to-product-transformation-case-study-global-media-service-provider/; https://teamtopologies.com/news-blogs-newsletters/2024/10/18/shifting-from-projects-to-products-insights-from-our-open-forum)
Project-governed product teams lose ownership quality because new-feature business cases crowd out defect fixing, incident reduction, risk work, and technical-debt reduction that long-lived product stewardship requires. ([inference]; high confidence; source: https://itrevolution.com/articles/project-to-product-transformation-case-study-global-media-service-provider/; https://teamtopologies.com/news-blogs-newsletters/2024/10/18/shifting-from-projects-to-products-insights-from-our-open-forum; https://www.cio.com/article/196208/creating-a-new-funding-model-for-product-based-it.html)
Hybrid project and product rules recreate matrix-style decision conflict, because project sponsors, finance gates, and line managers continue competing to direct the same team capacity that the product team is supposed to own. ([inference]; medium confidence; source: https://less.works/blog/2026/02/20/project-based-funding-in-product-development; https://www.cio.com/article/196208/creating-a-new-funding-model-for-product-based-it.html; https://github.com/davidamitchell/Research/blob/main/Research/completed/2026-05-14-org-failure-modes-accountability-gaps.md)
Release speed and customer feedback slow down under the mismatch, because project milestones and cross-team coordination preserve large-batch delivery and reduce the autonomy that high-performing product teams need. ([inference]; medium confidence; source: https://teamtopologies.com/news-blogs-newsletters/2024/10/18/shifting-from-projects-to-products-insights-from-our-open-forum; https://dora.dev/capabilities/loosely-coupled-teams/; https://github.com/davidamitchell/Research/blob/main/Research/completed/2026-05-14-org-failure-modes-cohort-demand-domain-it.md)
Team stability improves only partially when organisations rename teams as products, because project-based demand still encourages stop-start funding, role ambiguity, and pressure to reshape capacity around the next approved initiative. ([inference]; medium confidence; source: https://www.cio.com/article/196208/creating-a-new-funding-model-for-product-based-it.html; https://www.thoughtworks.com/insights/blog/leadership/funding-agility-moving-beyond-project-budgets; https://itrevolution.com/articles/project-to-product-transformation-case-study-fortune-100-retail-enterprise/)
The strongest evidenced mitigation is to move governance up to outcome and capacity review, keep one visible backlog for all work, and continuously fund build-and-run teams instead of funding temporary project slices. ([inference]; high confidence; source: https://info.planview.com/rs/456-QCH-520/images/Planview_2023-Project-to-Product-State-of-the-Industry-Report.pdf; https://itrevolution.com/articles/project-to-product-transformation-case-study-global-media-service-provider/; https://www.thoughtworks.com/insights/blog/leadership/funding-agility-moving-beyond-project-budgets; https://less.works/blog/2026/02/20/project-based-funding-in-product-development)

Evidence map:

Claim	Source	Confidence	Notes
[inference] Annual project budgeting over-commits product teams by creating approved demand that exceeds stable team capacity.	https://info.planview.com/rs/456-QCH-520/images/Planview_2023-Project-to-Product-State-of-the-Industry-Report.pdf; https://itrevolution.com/articles/funding-model-the-seven-domains-of-transformation/; https://www.thoughtworks.com/insights/blog/leadership/funding-agility-moving-beyond-project-budgets	high	batch-size mismatch
[inference] Project labels inside one backlog fragment prioritisation and reduce product flexibility.	https://less.works/blog/2026/02/20/project-based-funding-in-product-development; https://itrevolution.com/articles/project-to-product-transformation-case-study-global-media-service-provider/; https://teamtopologies.com/news-blogs-newsletters/2024/10/18/shifting-from-projects-to-products-insights-from-our-open-forum	high	multiple claims on one backlog
[inference] Product ownership erodes when feature business cases crowd out incidents, defects, risk, and technical debt.	https://itrevolution.com/articles/project-to-product-transformation-case-study-global-media-service-provider/; https://teamtopologies.com/news-blogs-newsletters/2024/10/18/shifting-from-projects-to-products-insights-from-our-open-forum; https://www.cio.com/article/196208/creating-a-new-funding-model-for-product-based-it.html	high	sustaining work loses priority
[inference] Hybrid project and product governance recreates matrix-style authority conflict over the same team capacity.	https://less.works/blog/2026/02/20/project-based-funding-in-product-development; https://www.cio.com/article/196208/creating-a-new-funding-model-for-product-based-it.html; https://github.com/davidamitchell/Research/blob/main/Research/completed/2026-05-14-org-failure-modes-accountability-gaps.md	medium	governance and accountability overlap
[inference] Release speed and customer feedback loops slow because project milestones preserve coordination-heavy, large-batch delivery.	https://teamtopologies.com/news-blogs-newsletters/2024/10/18/shifting-from-projects-to-products-insights-from-our-open-forum; https://dora.dev/capabilities/loosely-coupled-teams/; https://github.com/davidamitchell/Research/blob/main/Research/completed/2026-05-14-org-failure-modes-cohort-demand-domain-it.md	medium	dependency and gating effect
[inference] Team continuity remains fragile when funding still assumes temporary initiative slices rather than durable product capacity.	https://www.cio.com/article/196208/creating-a-new-funding-model-for-product-based-it.html; https://www.thoughtworks.com/insights/blog/leadership/funding-agility-moving-beyond-project-budgets; https://itrevolution.com/articles/project-to-product-transformation-case-study-fortune-100-retail-enterprise/	medium	continuity improved only partially
[inference] Continuously funded build-and-run teams, one visible backlog, and outcome reviews are the strongest supported mitigation package.	https://info.planview.com/rs/456-QCH-520/images/Planview_2023-Project-to-Product-State-of-the-Industry-Report.pdf; https://itrevolution.com/articles/project-to-product-transformation-case-study-global-media-service-provider/; https://www.thoughtworks.com/insights/blog/leadership/funding-agility-moving-beyond-project-budgets; https://less.works/blog/2026/02/20/project-based-funding-in-product-development	high	strongest repeated remedy

Assumptions:

[assumption; source: https://info.planview.com/rs/456-QCH-520/images/Planview_2023-Project-to-Product-State-of-the-Industry-Report.pdf; https://itrevolution.com/articles/funding-model-the-seven-domains-of-transformation/] Large-enterprise transition evidence is treated as directionally informative for other organisations, even though smaller firms may have fewer governance layers. Justification: the question concerns the structural mismatch, and that mismatch is most explicitly documented in large-enterprise cases.
[assumption; source: https://less.works/blog/2026/02/20/project-based-funding-in-product-development; https://www.cio.com/article/196208/creating-a-new-funding-model-for-product-based-it.html] Practitioner retrospectives are treated as valid evidence for transitional failure modes when they describe concrete operating patterns, even though they are weaker than controlled studies. Justification: the exact hybrid pattern is under-documented in academic literature.

Analysis:

The evidence weighs most heavily toward project-based demand as a governance amplifier of delivery friction rather than as a stand-alone technical flaw, because the strongest sources tie annual budgets, project gates, and funding logic directly to oversized demand, backlog distortion, and weak product stewardship. [inference; source: https://info.planview.com/rs/456-QCH-520/images/Planview_2023-Project-to-Product-State-of-the-Industry-Report.pdf; https://itrevolution.com/articles/funding-model-the-seven-domains-of-transformation/; https://less.works/blog/2026/02/20/project-based-funding-in-product-development]

The most persuasive direct observations concern planning and backlog behaviour, not team labels. Product teams fail to realise product-model benefits when approval and reporting still happen through project slices, because those slices keep reasserting priority claims inside the same team and backlog. [inference; source: https://less.works/blog/2026/02/20/project-based-funding-in-product-development; https://itrevolution.com/articles/project-to-product-transformation-case-study-global-media-service-provider/]

Alternative explanations remain important. Legacy architecture, weak product management, role-transition problems, and finance capability all affect outcomes, so the mismatch should be understood as a recurrent compounding mechanism that makes those other problems harder to correct. [inference; source: https://teamtopologies.com/news-blogs-newsletters/2024/10/18/shifting-from-projects-to-products-insights-from-our-open-forum; https://itrevolution.com/articles/project-to-product-transformation-case-study-fortune-100-retail-enterprise/; https://dora.dev/capabilities/loosely-coupled-teams/]

Rival remedies also exist, such as preserving project gates but staffing more programme-management capacity, or improving architecture without changing funding. The evidence here does not show those options as the preferred scaled pattern, because the consulted cases repeatedly move toward stable team funding, one backlog, and outcome reviews when they want to reduce overload and restore ownership. [inference; source: https://itrevolution.com/articles/funding-model-the-seven-domains-of-transformation/; https://itrevolution.com/articles/project-to-product-transformation-case-study-global-media-service-provider/; https://www.cio.com/article/196208/creating-a-new-funding-model-for-product-based-it.html]

Risks, gaps, uncertainties:

[inference; source: https://info.planview.com/rs/456-QCH-520/images/Planview_2023-Project-to-Product-State-of-the-Industry-Report.pdf; https://itrevolution.com/articles/funding-model-the-seven-domains-of-transformation/] Public evidence is stronger on large-enterprise transitions than on smaller firms or born-digital companies, so transfer beyond enterprise settings should be cautious.
[inference; source: https://www.cio.com/article/196208/creating-a-new-funding-model-for-product-based-it.html; https://less.works/blog/2026/02/20/project-based-funding-in-product-development] Several strong claims come from practitioner and transformation sources rather than peer-reviewed controlled studies, which lowers confidence for the exact causal weight of each failure mode.
[inference; source: https://teamtopologies.com/news-blogs-newsletters/2024/10/18/shifting-from-projects-to-products-insights-from-our-open-forum; https://dora.dev/capabilities/loosely-coupled-teams/] Some observed bottlenecks could also arise from architecture and dependency design even without project funding, so the mismatch should not be treated as the only explanatory factor.

Open questions:

Under what conditions can a hybrid project-funding and product-team model remain stable for more than a short transition period?
What finance and capitalization patterns best preserve one backlog while still satisfying external reporting obligations?
How much of the observed pain comes from the funding cycle itself versus from weak product-management capability during the transition?

§7 Recursive Review

Review result: pass
Acronym audit: Project Management Institute (PMI), DevOps Research and Assessment (DORA), Chief Information Officer (CIO), and return on investment (ROI) are expanded on first use; no other unexpanded central acronyms remain in the audited prose.
Claim audit: every substantive sentence in Research Skill Output sections 2-6 is labeled as fact, inference, or assumption; sections 0, 1, and 7 use metadata fragments or decomposition items.
Source audit: every cited claim uses a URL-backed source; the blocked Project Management Institute source is listed only as identified but not consulted.
Cross-item integration audit: adjacent completed items on accountability and boundary mismatch are cited where they sharpen the governance interpretation.
Parity audit: Findings below mirror this synthesis without adding new substantive claims.

Findings

(Populated from §6 Synthesis above.)

Executive Summary

Project-based demand governance is repeatedly associated with over-commitment, backlog fragmentation, weak product ownership, and slow feedback loops when the same work is delivered by long-lived product teams. [inference; source: https://info.planview.com/rs/456-QCH-520/images/Planview_2023-Project-to-Product-State-of-the-Industry-Report.pdf; https://less.works/blog/2026/02/20/project-based-funding-in-product-development; https://itrevolution.com/articles/project-to-product-transformation-case-study-global-media-service-provider/]

The direct evidence is strongest in large-enterprise transitions where annual project budgets and project reporting survive after teams have been reorganised around products or long-lived work flows. [inference; source: https://info.planview.com/rs/456-QCH-520/images/Planview_2023-Project-to-Product-State-of-the-Industry-Report.pdf; https://itrevolution.com/articles/funding-model-the-seven-domains-of-transformation/]

The recurring mechanism is that project governance keeps budget, approval, and reporting attached to temporary initiatives, while product teams require stable capacity, one ranked backlog, and accountability for defects, risk, architecture, and operations over time. [inference; source: https://www.cio.com/article/196208/creating-a-new-funding-model-for-product-based-it.html; https://www.thoughtworks.com/insights/blog/leadership/funding-agility-moving-beyond-project-budgets; https://less.works/blog/2026/02/20/project-based-funding-in-product-development]

The strongest supported mitigation is continuously funded build-and-run teams with visible full-product backlog management and periodic outcome reviews, rather than project-by-project funding gates controlling day-to-day product priorities. [inference; source: https://info.planview.com/rs/456-QCH-520/images/Planview_2023-Project-to-Product-State-of-the-Industry-Report.pdf; https://itrevolution.com/articles/project-to-product-transformation-case-study-global-media-service-provider/; https://www.thoughtworks.com/insights/blog/leadership/funding-agility-moving-beyond-project-budgets]

Key Findings

Annual project budgeting creates a demand-capacity mismatch for product teams, because it approves work in large planned batches while stable teams can only absorb work through bounded ongoing capacity and re-prioritisation. ([inference]; high confidence; source: https://info.planview.com/rs/456-QCH-520/images/Planview_2023-Project-to-Product-State-of-the-Industry-Report.pdf; https://itrevolution.com/articles/funding-model-the-seven-domains-of-transformation/; https://www.thoughtworks.com/insights/blog/leadership/funding-agility-moving-beyond-project-budgets)
When project identifiers remain attached to backlog items, the product backlog becomes a negotiated merge of project claims, incidents, and technical debt instead of a single ranked view of product value. ([inference]; high confidence; source: https://less.works/blog/2026/02/20/project-based-funding-in-product-development; https://itrevolution.com/articles/project-to-product-transformation-case-study-global-media-service-provider/; https://teamtopologies.com/news-blogs-newsletters/2024/10/18/shifting-from-projects-to-products-insights-from-our-open-forum)
Project-governed product teams lose ownership quality because new-feature business cases crowd out defect fixing, incident reduction, risk work, and technical-debt reduction that long-lived product stewardship requires. ([inference]; high confidence; source: https://itrevolution.com/articles/project-to-product-transformation-case-study-global-media-service-provider/; https://teamtopologies.com/news-blogs-newsletters/2024/10/18/shifting-from-projects-to-products-insights-from-our-open-forum; https://www.cio.com/article/196208/creating-a-new-funding-model-for-product-based-it.html)
Hybrid project and product rules recreate matrix-style decision conflict, because project sponsors, finance gates, and line managers continue competing to direct the same team capacity that the product team is supposed to own. ([inference]; medium confidence; source: https://less.works/blog/2026/02/20/project-based-funding-in-product-development; https://www.cio.com/article/196208/creating-a-new-funding-model-for-product-based-it.html; https://github.com/davidamitchell/Research/blob/main/Research/completed/2026-05-14-org-failure-modes-accountability-gaps.md)
Release speed and customer feedback slow down under the mismatch, because project milestones and cross-team coordination preserve large-batch delivery and reduce the autonomy that high-performing product teams need. ([inference]; medium confidence; source: https://teamtopologies.com/news-blogs-newsletters/2024/10/18/shifting-from-projects-to-products-insights-from-our-open-forum; https://dora.dev/capabilities/loosely-coupled-teams/; https://github.com/davidamitchell/Research/blob/main/Research/completed/2026-05-14-org-failure-modes-cohort-demand-domain-it.md)
Team stability improves only partially when organisations rename teams as products, because project-based demand still encourages stop-start funding, role ambiguity, and pressure to reshape capacity around the next approved initiative. ([inference]; medium confidence; source: https://www.cio.com/article/196208/creating-a-new-funding-model-for-product-based-it.html; https://www.thoughtworks.com/insights/blog/leadership/funding-agility-moving-beyond-project-budgets; https://itrevolution.com/articles/project-to-product-transformation-case-study-fortune-100-retail-enterprise/)
The strongest evidenced mitigation is to move governance up to outcome and capacity review, keep one visible backlog for all work, and continuously fund build-and-run teams instead of funding temporary project slices. ([inference]; high confidence; source: https://info.planview.com/rs/456-QCH-520/images/Planview_2023-Project-to-Product-State-of-the-Industry-Report.pdf; https://itrevolution.com/articles/project-to-product-transformation-case-study-global-media-service-provider/; https://www.thoughtworks.com/insights/blog/leadership/funding-agility-moving-beyond-project-budgets; https://less.works/blog/2026/02/20/project-based-funding-in-product-development)

Evidence Map

Claim	Source	Confidence	Notes
[inference] Annual project budgeting over-commits product teams by creating approved demand that exceeds stable team capacity.	https://info.planview.com/rs/456-QCH-520/images/Planview_2023-Project-to-Product-State-of-the-Industry-Report.pdf; https://itrevolution.com/articles/funding-model-the-seven-domains-of-transformation/; https://www.thoughtworks.com/insights/blog/leadership/funding-agility-moving-beyond-project-budgets	high	batch-size mismatch
[inference] Project labels inside one backlog fragment prioritisation and reduce product flexibility.	https://less.works/blog/2026/02/20/project-based-funding-in-product-development; https://itrevolution.com/articles/project-to-product-transformation-case-study-global-media-service-provider/; https://teamtopologies.com/news-blogs-newsletters/2024/10/18/shifting-from-projects-to-products-insights-from-our-open-forum	high	multiple claims on one backlog
[inference] Product ownership erodes when feature business cases crowd out incidents, defects, risk, and technical debt.	https://itrevolution.com/articles/project-to-product-transformation-case-study-global-media-service-provider/; https://teamtopologies.com/news-blogs-newsletters/2024/10/18/shifting-from-projects-to-products-insights-from-our-open-forum; https://www.cio.com/article/196208/creating-a-new-funding-model-for-product-based-it.html	high	sustaining work loses priority
[inference] Hybrid project and product governance recreates matrix-style authority conflict over the same team capacity.	https://less.works/blog/2026/02/20/project-based-funding-in-product-development; https://www.cio.com/article/196208/creating-a-new-funding-model-for-product-based-it.html; https://github.com/davidamitchell/Research/blob/main/Research/completed/2026-05-14-org-failure-modes-accountability-gaps.md	medium	governance and accountability overlap
[inference] Release speed and customer feedback loops slow because project milestones preserve coordination-heavy, large-batch delivery.	https://teamtopologies.com/news-blogs-newsletters/2024/10/18/shifting-from-projects-to-products-insights-from-our-open-forum; https://dora.dev/capabilities/loosely-coupled-teams/; https://github.com/davidamitchell/Research/blob/main/Research/completed/2026-05-14-org-failure-modes-cohort-demand-domain-it.md	medium	dependency and gating effect
[inference] Team continuity remains fragile when funding still assumes temporary initiative slices rather than durable product capacity.	https://www.cio.com/article/196208/creating-a-new-funding-model-for-product-based-it.html; https://www.thoughtworks.com/insights/blog/leadership/funding-agility-moving-beyond-project-budgets; https://itrevolution.com/articles/project-to-product-transformation-case-study-fortune-100-retail-enterprise/	medium	continuity improved only partially
[inference] Continuously funded build-and-run teams, one visible backlog, and outcome reviews are the strongest supported mitigation package.	https://info.planview.com/rs/456-QCH-520/images/Planview_2023-Project-to-Product-State-of-the-Industry-Report.pdf; https://itrevolution.com/articles/project-to-product-transformation-case-study-global-media-service-provider/; https://www.thoughtworks.com/insights/blog/leadership/funding-agility-moving-beyond-project-budgets; https://less.works/blog/2026/02/20/project-based-funding-in-product-development	high	strongest repeated remedy

Assumptions

[assumption; source: https://info.planview.com/rs/456-QCH-520/images/Planview_2023-Project-to-Product-State-of-the-Industry-Report.pdf; https://itrevolution.com/articles/funding-model-the-seven-domains-of-transformation/] Large-enterprise transition evidence is directionally informative for other organisations, even though smaller firms may have fewer governance layers. Justification: the question concerns the structural mismatch, and that mismatch is most explicitly documented in enterprise cases.
[assumption; source: https://less.works/blog/2026/02/20/project-based-funding-in-product-development; https://www.cio.com/article/196208/creating-a-new-funding-model-for-product-based-it.html] Practitioner retrospectives are valid evidence for transitional failure modes when they describe concrete operating patterns, even though they are weaker than controlled studies. Justification: the exact hybrid pattern is under-documented in academic literature.

Analysis

The evidence weighs most heavily toward project-based demand as a governance amplifier of delivery friction rather than as a stand-alone technical flaw, because the strongest sources tie annual budgets, project gates, and funding logic directly to oversized demand, backlog distortion, and weak product stewardship. [inference; source: https://info.planview.com/rs/456-QCH-520/images/Planview_2023-Project-to-Product-State-of-the-Industry-Report.pdf; https://itrevolution.com/articles/funding-model-the-seven-domains-of-transformation/; https://less.works/blog/2026/02/20/project-based-funding-in-product-development]

The most persuasive direct observations concern planning and backlog behaviour, not team labels. Product teams fail to realise product-model benefits when approval and reporting still happen through project slices, because those slices keep reasserting priority claims inside the same team and backlog. [inference; source: https://less.works/blog/2026/02/20/project-based-funding-in-product-development; https://itrevolution.com/articles/project-to-product-transformation-case-study-global-media-service-provider/]

Alternative explanations remain important. Legacy architecture, weak product management, role-transition problems, and finance capability all affect outcomes, so the mismatch should be understood as a recurrent compounding mechanism that makes those other problems harder to correct. [inference; source: https://teamtopologies.com/news-blogs-newsletters/2024/10/18/shifting-from-projects-to-products-insights-from-our-open-forum; https://itrevolution.com/articles/project-to-product-transformation-case-study-fortune-100-retail-enterprise/; https://dora.dev/capabilities/loosely-coupled-teams/]

Rival remedies also exist, such as preserving project gates but staffing more programme-management capacity, or improving architecture without changing funding. The evidence here does not show those options as the preferred scaled pattern, because the consulted cases repeatedly move toward stable team funding, one backlog, and outcome reviews when they want to reduce overload and restore ownership. [inference; source: https://itrevolution.com/articles/funding-model-the-seven-domains-of-transformation/; https://itrevolution.com/articles/project-to-product-transformation-case-study-global-media-service-provider/; https://www.cio.com/article/196208/creating-a-new-funding-model-for-product-based-it.html]

Risks, Gaps, and Uncertainties

[inference; source: https://info.planview.com/rs/456-QCH-520/images/Planview_2023-Project-to-Product-State-of-the-Industry-Report.pdf; https://itrevolution.com/articles/funding-model-the-seven-domains-of-transformation/] Public evidence is stronger on large-enterprise transitions than on smaller firms or born-digital companies, so transfer beyond enterprise settings should be cautious.
[inference; source: https://www.cio.com/article/196208/creating-a-new-funding-model-for-product-based-it.html; https://less.works/blog/2026/02/20/project-based-funding-in-product-development] Several strong claims come from practitioner and transformation sources rather than peer-reviewed controlled studies, which lowers confidence for the exact causal weight of each failure mode.
[inference; source: https://teamtopologies.com/news-blogs-newsletters/2024/10/18/shifting-from-projects-to-products-insights-from-our-open-forum; https://dora.dev/capabilities/loosely-coupled-teams/] Some observed bottlenecks could also arise from architecture and dependency design even without project funding, so the mismatch should not be treated as the only explanatory factor.

Open Questions

Under what conditions can a hybrid project-funding and product-team model remain stable for more than a short transition period?
What finance and capitalization patterns best preserve one backlog while still satisfying external reporting obligations?
How much of the observed pain comes from the funding cycle itself versus from weak product-management capability during the transition?

Output

Type: knowledge
Description: This item documents recurring failure modes when project-based demand governs long-lived product teams and identifies continuously funded build-and-run teams, one visible backlog, and outcome reviews as the strongest supported mitigation. [inference; source: https://info.planview.com/rs/456-QCH-520/images/Planview_2023-Project-to-Product-State-of-the-Industry-Report.pdf; https://itrevolution.com/articles/project-to-product-transformation-case-study-global-media-service-provider/; https://less.works/blog/2026/02/20/project-based-funding-in-product-development]
Links: