The Innovation Loop
A lightweight framework for discovering and delivering AI-enabled products and services.
AI makes building easier.
Does it make innovation better?
An impressive AI demo answers “Can we build this?” Innovation asks a harder question: “Should this become a product, and what would persuade us otherwise?” The difference is a repeatable way to turn curiosity into testable claims, and testable claims into accountable investment.
The opportunity is substantial, but conditional. In a randomized experiment with 453 professionals, ChatGPT reduced time on specified writing tasks by 40% and increased rated output quality by 18%; those results concern bounded writing tasks, not enterprise-wide productivity or profit. (Noy & Zhang, 2023) In a published field study of 5,172 customer-support agents, an AI assistant increased issues resolved per hour by 15% on average, with substantial differences by worker experience and skill; the staggered-rollout study was not a randomized trial. (Brynjolfsson et al., 2025)
There is an equally important counterweight. A meta-analysis of 106 experimental studies found that human-AI teams performed somewhat worse, on average, than whichever was better alone: the human or the AI. Because the studies measured different tasks, the authors report the gap in standard deviations rather than percentages: Hedges’ g = −0.23, a small effect, with a 95% confidence interval of −0.39 to −0.07. The whole interval sits below zero, so the shortfall is modest but unlikely to be zero; it is not a 23% productivity decline. (Vaccaro et al., 2024) A 2026 reanalysis of 74 relevant studies identified feedback and human learning as promising moderators, but explicitly called for experiments before drawing stronger causal conclusions. (Berger et al., 2026)
Less time on specified writing tasks; rated quality increased 18%. Randomized experiment, 453 professionals.
Noy & Zhang, 2023More issues resolved per hour in a support-agent field study. Staggered rollout, 5,172 agents.
Brynjolfsson et al., 2025Human-AI teams vs. the better of human or AI alone: a small shortfall of 0.23 standard deviations, not 23%. 95% confidence interval −0.39 to −0.07.
Vaccaro et al., 2024The Innovation Loop turns that tension into four practical movements:
- Frame together: Select a consequential user problem, name its eventual owner, and compare AI with the current workflow and a credible simpler alternative.
- Test the uncertainty: Write down what success and failure mean before prototyping. Test the riskiest assumption, not just the easiest capability to demonstrate.
- Commit and deliver: Make an explicit stop, revise, pilot, or scale decision. Transfer operational responsibility through shared work and acceptance, not a presentation alone.
- Learn and compound: Measure actual use, quality, cost, and harm. Feed failures into evaluations and teach the method using evidence, including stopped bets.
The aim is not to maximize ideas, demos, approvals, or even launches. It is to make better decisions about which AI-enabled experiences deserve users, resources, and continued operation.
This is not an argument for more committees. It is a proposal for four movements, three living records, and five rules, usable by a small team and extensible to enterprise governance. The practical invitation is to try one bounded opportunity, preserve the evidence, and evaluate the framework itself rather than assuming the framework works.
Increase commitment as evidence improves and keep ownership continuous from discovery to real use.
The framework has four parts:
- The movements the work passes through
- The rules that hold throughout
- The people accountable for it
- The records that carry the evidence
Four movements, not four departments
Together, the four movements form the loop: "Learn and compound" feeds back into "Frame together", and work can return to an earlier movement whenever evidence changes the problem, solution, or investment case. Tidd and Bessant likewise describe innovation as a repeated cycle rather than a neatly linear event. (Tidd & Bessant, 2024, ch. 3)
Frame together
Is this a problem worth testing?
Minimum evidence to move forwardNamed user and owner, observable problem, baseline, riskiest assumption, authorized experiment
How to run it
Purpose: Find an important uncertainty worth paying to reduce. Begin with the product or service owner, not with a finished concept looking for a home.
- Discover the work: Observe users, examine workflow data and existing complaints, identify workarounds, and distinguish the expressed request from the underlying task. Record access limits and whose perspective is missing.
- Form alternatives: Generate candidate approaches independently before pooling them; include a process change, a deterministic solution, or an existing product when plausible. Use AI to widen and challenge the set, not to create a false impression of independent agreement.
- Define the test: Select a primary user outcome, a baseline, a credible comparator, a failure condition, and the cheapest ethical test of the highest-consequence assumption. Establish authorized data use and the boundaries of the experiment.
The independent-ideation suggestion is a design precaution, not a proven optimal workshop format. It responds to an experiment in short-story writing where AI assistance improved individual evaluations but made the stories more similar to each other; that finding does not establish that AI reduces product-innovation diversity in every setting. (Doshi & Hauser, 2024)
Exit decision: The outcome owner and delegated investment authority authorize a bounded experiment, revise the opportunity, or stop. The opportunity card should be understandable without a slide deck.
Test the uncertainty
Does the proposed solution merit exposure to users?
Minimum evidence to move forwardPrototype evidence against predefined criteria, cost range, failure analysis, bounded pilot plan
How to run it
Purpose: Produce evidence that can change the decision. Refine the proposal and build the prototype together rather than requiring a detailed business case before learning anything.
- Write the evaluation contract: Define the population, unit of analysis, current workflow, comparator, primary measure, meaningful improvement, guardrails, sample rationale, and analysis/stopping plan. Separate qualitative discovery from confirmatory claims.
- Build the smallest useful test: Use a mock-up, concierge workflow, offline model comparison, retrieval experiment, or bounded working prototype according to the uncertainty. Avoid unnecessary agents, integrations, or model training.
- Evaluate the whole experience: Test task completion, human correction effort, unacceptable errors, latency, and total cost, not just model output. Where appropriate and safe, compare human-only, AI-only, and human-AI performance on the same task.
- Challenge the result: Use representative cases and an untouched final test set; examine relevant user and task slices. For temporal predictions, respect time ordering and prevent leakage; for generative systems, include groundedness, abstention, and adversarial cases.
- Update the investment case: Show downside, base, and upside scenarios, with assumptions for adoption, integration, review, inference, maintenance, and error costs. Distinguish a forecast from an observed benefit.
Application-specific evaluation, factual consistency, cost, and latency are explicit concerns in Huyen’s AI engineering treatment; NIST also cautions that laboratory and benchmark performance may not extrapolate to real use. (Huyen, 2025, ch. 4, NIST, 2024) The statistical-learning textbook provides the methodological foundation for model assessment, resampling, and multiple testing, rather than a universal sample size for this framework. (James et al., 2023)
Exit decision: Stop, revise, or authorize a bounded pilot. An inconclusive result calls for an explicit choice about whether more information is worth its cost, not an automatic declaration of success or failure.
Commit and deliver
Can we responsibly own this in use?
Minimum evidence to move forwardExplicit investment decision, accepted ownership, risk review, monitoring and rollback
How to run it
Purpose: Turn a supported proposition into an owned, controlled product or service. A good demo alone is not evidence that the organization can operate it.
- Present the decision, not the theater: State the problem, alternatives, strongest evidence and counterevidence, uncertainty, economics, risks, and precise resource request. Use an existing product review; require an executive presentation only when the decision exceeds delegated authority.
- Pilot with controls: Define who is exposed, what the system may do, the monitoring owner, incident route, and conditions for pause or rollback. Use shadow evaluation or controlled release where appropriate; shadow mode does not test every user-interaction effect.
- Accept together: The owner, builders, and relevant reviewers walk through the code or prototype, data rights and lineage, prompts/model versions, evaluations, known failures, instrumentation, support, and dependencies.
- Commit to delivery capacity: Name the delivery team and funded roadmap or backlog commitment. If another team will continue the work, require explicit acceptance and overlap; a handoff is not complete because a document was sent.
For agentic services, restrict tool permissions, isolate tests, log actions, and require appropriate human authorization for consequential actions. These are risk controls informed by NIST’s treatment of security, prompt injection, monitoring, and human-AI configurations, not a claim that a checklist can guarantee safety. (NIST, 2024)
Exit decision: The owner accepts the bounded service; the investment authority approves the relevant commitment; required risk reviewers approve within their remit. Unknowns stay visible on the ownership card, with an owner and next review.
Learn and compound
Did value survive real use?
Minimum evidence to move forwardMeasured outcomes, adverse effects, operating cost, next decision, reusable learning
How to run it
Purpose: Establish whether the proposition produces durable value in use, and improve both the service and the method. Delivery is a beginning of measurement, not the end of innovation.
- Measure in use: Compare outcomes with the baseline or a suitable control; distinguish availability, exposure, trial, repeat use, and successful task completion. Treat clicks, edits, and satisfaction as signals requiring interpretation, not direct proof of value.
- Watch degradation: Monitor outcome quality, cost, latency, data changes, incidents, and user workarounds. Re-evaluate after changes to data, models, prompts, retrieval, or tools; versioning and continuous monitoring are core MLOps concerns. (Kreuzberger et al., 2023)
- Retrospect privately and together: Offer confidential one-to-one feedback as well as a team discussion. Select one or two changes to the next iteration and assign an owner; do not turn the retrospective into a mandatory ritual without an improvement decision.
- Teach with evidence: Use a roadshow containing a successful case, a stopped case, costs, limitations, and reusable evaluations. For train-the-trainer adoption, progress from observation to co-facilitation to independently facilitated work reviewed against the same record requirements.
- Govern a portfolio only when needed: Review strategic fit, evidence strength, shared dependencies, cumulative exposure, operating burden, and resources across bets. Compare within appropriate maturity and risk categories; do not rank an exploratory option against a mature product using a single ROI score.
Exit decision: Continue, change, expand, retire, or return to discovery. Keep a subsequent value-review date even when the next facilitation cycle has already begun.
Worked example: the four movements applied to an AI research brief
Consider a hypothetical service that helps a product manager prepare a source-grounded research brief. The following is an illustration, not a claim about any company’s roadmap, internal practices, data, or achievable results.
- Frame: Users need a defensible answer to a bounded research question. Compare the current search-and-writing workflow with a structured non-generative template and the AI-assisted proposal; nominate an owner.
- Test: Define success as answering the question with correct, relevant, traceable evidence under a blinded rubric. Measure total time, verification and correction effort, unsupported claims, citation support, latency, and cost per successful brief.
- Commit: Only if the prespecified quality and risk criteria are met, run a bounded pilot with consenting users, clear limits, and an incident route. Do not allow unverified external messages or autonomous consequential actions.
- Learn: Assess repeat use alongside completed, acceptable briefs; return corrections and retrieval failures to the evaluation set. A faster first draft that increases total verification effort may fail the product’s goal.
No numerical target is supplied because baseline difficulty, risk tolerance, and sample requirements are unknown. Set those before exposure rather than borrowing an impressive number from an unrelated study.
Five rules
- Start with an outcome, not an AI requirement: State whose task should improve, against what alternative, and why AI might be necessary. “No AI” remains an acceptable answer.
- Make claims falsifiable: Record the hypothesis, comparison, success criteria, guardrails, and stop conditions before reviewing results. Label later exploratory findings as exploratory.
- Match permission to risk: Do not treat approval to explore as approval to expose private data, affect users, or deploy autonomous actions.
- Keep an owner from beginning to end: Name the product or service owner during framing; that owner accepts delivery and remains accountable for outcomes after launch.
- Preserve decisions and counterevidence: Record stopped ideas, negative findings, limitations, and disagreements alongside successes.
The rationale for explicit hypotheses comes partly from four randomized trials involving 759 firms: training in a scientific approach increased project termination by 9.8 percentage points in the pooled analysis, rather than simply encouraging more persistence. (Camuffo et al., 2024) That supports treating evidence-led stopping as legitimate; it does not establish a desirable termination rate for corporate AI projects.
Four accountabilities, not four new job titles
- Outcome owner: Represents user and business needs, sets acceptance criteria with the team, owns the outcome measure, and accepts the service into its product roadmap.
- Builders: Provide the design, domain, data, software, and ML capabilities needed to test and deliver the use case. Invite security, privacy, accessibility, legal, and operations specialists when the use case requires them.
- Facilitator: Protects inquiry, enables cross-functional access, keeps the evidence legible, and runs the retrospective. The facilitator is not the sole owner of the invention or its delivery.
- Sponsor or investment authority: Authorizes resources and risk within delegated limits, resolves cross-functional constraints, and decides larger commitments.
A small team may combine accountabilities; higher-risk decisions should receive independent review. As a starting configuration, try four to seven active contributors with named specialist access, then adjust to the work rather than treating headcount as a success condition.
Recruit volunteers for interest where useful, but obtain explicit manager agreement on protected capacity, availability, and replacement coverage. Include different functional expertise and direct access to affected users; do not assume that nominal diversity, volunteer enthusiasm, or membership in a data science function automatically provides AI product delivery capability.
This cross-functional emphasis is consistent with MLOps research identifying business, data science, data engineering, software, and operations roles, together with collaboration and continuous feedback. (Kreuzberger et al., 2023)
Three living records
Use existing tools. These are information requirements, not mandatory documents, software purchases, or additional approval forms.
Opportunity cardOpened in Frame together; it authorizes the first experiment.
- User and task: Who is trying to do what, in which context?
- Observed problem: What evidence indicates a meaningful unmet need?
- Baseline and alternatives: Current workflow; credible non-AI or simpler approach.
- Outcome and hypothesis: What should improve, for whom, and why?
- People and authority: Outcome owner; builders; facilitator; investment authority.
- Constraints: Capacity, authorized data, rights, dependencies, risk boundaries.
- Next test: Riskiest assumption; test cost cap; date of decision.
Evidence logKept through Test the uncertainty; it ends in a dated decision.
- Evaluation contract: Population, unit, comparator, primary measure, minimum worthwhile effect, guardrails, sample rationale, stopping rule.
- Reproducibility: Data provenance/splits, model, prompt, tool and code versions.
- Results: Denominators, estimates, uncertainty, subgroup results, correction effort.
- Counterevidence: Failures, user objections, missing perspectives, validity limits.
- Economics: Assumptions, scenario range, implementation and operating costs.
- Decision: Stop/revise/pilot/scale; rationale, approver, next learning question.
Ownership cardOpened in Commit and deliver; reviewed through Learn and compound.
- Acceptance: Product/service owner, delivery team, accepted scope, funded capacity.
- Operations: Dependencies, access, monitoring, service expectations, support.
- Safety: Risk owner, authorized actions, incident response, pause/rollback.
- Value review: Outcome dashboard, adoption denominator, review date.
- Open items: Unresolved risks, accountable people, deadlines.
To start your first loop, copy these into the tools you already use.
Adopt it without adding meetings
Start with one opportunity, the three records, and the four accountabilities. Reuse sprint planning, product reviews, and existing engineering controls; the Scrum Guide is a model of a deliberately incomplete framework, not evidence for copying its exact events or team size into innovation work. (Schwaber & Sutherland, 2020)
For a volunteer cohort, negotiate protected capacity and record both activity time and elapsed calendar time. For a product team, embed the loop in existing sprints; for an enterprise, run recurring intake and portfolio reviews while preserving delegated decisions and delivery ownership.
Cadence is a configuration, not a promise. Quarterly cohorts, sprint-level exploration, and ad hoc work may all fit; none substitutes for sufficient observation time to evaluate the specific outcome.
Evaluate the framework itself across repeated cohorts: compare decision time, effort, evidence quality, and realized outcomes with an appropriate prior or concurrent process, recording differences in project mix. That is a proposed validation program, not evidence that this version already improves innovation speed or success.
The goal is not more AI projects. It is better decisions about which ones deserve to exist.
Measure the experience.
Not the demo.
Choose one primary outcome, a small number of guardrails, and a decision date. The definitions below are proposed operationalizations of concerns in the literature, not a standardized or validated scorecard; thresholds must be set locally before testing.
| Measure | Operational definition and use | Evidence connection |
|---|---|---|
| User outcome | Successful eligible tasks ÷ all eligible tasks under the assigned workflow; compare with control and report absolute difference, sample size, and uncertainty. Define success in advance. | Issues resolved/hour is a real field-study productivity outcome, not a universal KPI. (Brynjolfsson et al., 2025) |
| Time and quality together | End-to-end time per task including correction; independent rubric-based quality where possible. Report both rather than rewarding speed at the expense of correctness. | Writing time and rated quality were separate outcomes in a randomized experiment. (Noy & Zhang, 2023) |
| Human-AI complementarity | In a safe, comparable evaluation, assess whether the combined workflow beats human-only and AI-only performance on the same prespecified measure. | Synergy uses the better-alone baseline; beating only humans is a weaker claim. (Vaccaro et al., 2024) |
| Predictive-ML quality | Select precision, recall, calibration, and error costs for the intervention; report the threshold and relevant slices. Prediction quality is not evidence that acting on the prediction improves outcomes. | Classification and model assessment are textbook topics. (James et al., 2023) |
| Generative/agent quality | Measure rubric-based task success, verified support for audited factual claims, invalid or unauthorized tool actions, and escalation/abstention quality. Define denominators and label human-audit coverage. | Context-specific evaluation, factual consistency, and verification are explicit concerns. (Huyen, 2025, NIST, 2024) |
| Economics and service | Total operating cost ÷ successful tasks, including failed attempts, review, retries, and inference; also tail latency and service failures. Keep build costs separate in the investment case. | Cost and latency are AI evaluation criteria; operations include system and infrastructure monitoring. (Huyen, 2025, Kreuzberger et al., 2023) |
| Harm and reliability | Severity-weighted incident counts and rates with exposure denominators; slice-specific quality and critical error counts. Zero observed failures is not proof of zero risk. | NIST calls for contextual risk assessment, varied testing, and post-deployment monitoring. (NIST, 2024) |
| Innovation-system learning | Track elapsed time and person-hours to a recorded decision, evidence completeness, stopped/revised/piloted bets, and realized versus forecast value by cohort. Do not prescribe a target kill rate. | Scientific decision training changed termination behavior; it did not validate these proposed process KPIs. (Camuffo et al., 2024) |
Use randomized product experiments when feasible and ethical for causal impact claims. If using observational before/after comparisons, identify seasonality, selection, workflow changes, and other rival explanations; do not relabel correlation as incremental value.
For the financial case, use a transparent scenario model: eligible volume × adoption × incremental contribution per adopted task, minus incremental operating and implementation costs. This is a proposed planning identity, not a literature-derived effect estimate; avoid double-counting benefits and do not book released capacity as cash savings unless spending actually changes.
Striking results.
Visible boundaries.
Writing assistance: 453 professionals; randomized online experiment; 40% less time and 18% higher rated quality on occupation-specific writing tasks. That’s a time saving on specific tasks, not 40% more enterprise productivity or profit. (Noy & Zhang, 2023)
Customer support: 5,172 agents; staggered-rollout field study; 15% more issues resolved/hour on average, with a 30% increase for less-skilled and less-experienced workers. The published 2025 result is used here, not the earlier working-paper headline of approximately 14%. (Brynjolfsson et al., 2025)
Product ideation: A 2026 Organization Science article reports a preregistered experiment with 791 Procter & Gamble professionals; individual AI users improved proposal performance by 0.37 standard deviations over unaided individuals, described by the authors as approximately 9.6%. Outcomes were expert-rated product proposals, not launched products, customer adoption, revenue, or ROI. The 0.37 is in standard deviations, not percent. (Dell’Acqua et al., 2026)
Complementarity: 106 studies and 370 effect sizes. On average, human-AI teams fell short of whichever was better alone, the human or the AI, by 0.23 standard deviations: a small effect, with a 95% confidence interval of −0.39 to −0.07. The same analysis found that teams often did outperform humans working alone, so “human plus AI never works” would be false. (Vaccaro et al., 2024)
Learning matters, provisionally: A 2026 reanalysis examined 74 relevant studies and found feedback plus explanations associated with positive synergy, while explanations without feedback were associated with negative synergy. This is a moderator finding, not randomized proof that adding feedback will create synergy. (Berger et al., 2026)
Scientific stopping: Four trials, 759 firms; pooled termination effect +9.8 percentage points. It is not a 9.8% increase in innovation success, a universal kill-rate target, or a test of this framework. (Camuffo et al., 2024)
Bibliography
13 references · Source types made explicitBerger, J., Burton, J. W., Hertwig, R., Kosch, T., Kurvers, R. H. J. M., Kurzenberger, B., Lazik, C., Onnasch, L., Rieger, T., Thoma, A. I., Wulff, D. U., & Herzog, S. M. (2026).Meta-analytic reanalysis
Berger, J., Burton, J. W., Hertwig, R., Kosch, T., Kurvers, R. H. J. M., Kurzenberger, B., Lazik, C., Onnasch, L., Rieger, T., Thoma, A. I., Wulff, D. U., & Herzog, S. M. (2026). Human learning is an understudied but promising lever for boosting human-AI synergy. Proceedings of the National Academy of Sciences, 123(39), e2536100123. Meta-analytic reanalysis. PubMed record and abstract.
Brynjolfsson, E., Li, D., & Raymond, L. (2025).Field study
Brynjolfsson, E., Li, D., & Raymond, L. (2025). Generative AI at work. The Quarterly Journal of Economics, 140(2), 889–942. Field study. Published article.
Camuffo, A., Gambardella, A., Messinese, D., Novelli, E., Paolucci, E., & Spina, C. (2024).Randomized trials
Camuffo, A., Gambardella, A., Messinese, D., Novelli, E., Paolucci, E., & Spina, C. (2024). A scientific approach to entrepreneurial decision-making: Large-scale replication and extension. Strategic Management Journal, 45(6), 1209–1237. Randomized trials. Repository record and full text.
Dell’Acqua, F., Ayoubi, C., Lifshitz, H., Sadun, R., Mollick, E., Mollick, L., Han, Y., Goldman, J., Nair, H., Taub, S., & Lakhani, K. R. (2026).Preregistered field experiment
Dell’Acqua, F., Ayoubi, C., Lifshitz, H., Sadun, R., Mollick, E., Mollick, L., Han, Y., Goldman, J., Nair, H., Taub, S., & Lakhani, K. R. (2026). The cybernetic teammate: A field experiment on generative AI and teamwork. Organization Science, 37(4), 1217–1242. Published online June 12, 2026. Preregistered field experiment. Published article.
Doshi, A. R., & Hauser, O. P. (2024).Randomized experiment
Doshi, A. R., & Hauser, O. P. (2024). Generative AI enhances individual creativity but reduces the collective diversity of novel content. Science Advances, 10(28), eadn5290. Randomized experiment. Open full text.
Huyen, C. (2025).Professional engineering reference
Huyen, C. (2025). AI engineering: Building applications with foundation models. O’Reilly Media. Professional engineering reference, not a peer-reviewed study; the publisher’s online release is dated December 2024. Publisher contents and overview; chapter 4 preview.
James, G., Witten, D., Hastie, T., Tibshirani, R., & Taylor, J. (2023).Academic textbook
James, G., Witten, D., Hastie, T., Tibshirani, R., & Taylor, J. (2023). An introduction to statistical learning: With applications in Python. Springer Texts in Statistics. Springer Nature. Academic textbook; chapters 2, 4, 5, and 13 cover model assessment, classification, resampling, and multiple testing. Publisher record; authors’ resource site.
Kreuzberger, D., Kühl, N., & Hirschl, S. (2023).Mixed-method research synthesis
Kreuzberger, D., Kühl, N., & Hirschl, S. (2023). Machine learning operations (MLOps): Overview, definition, and architecture. IEEE Access, 11, 31866–31879. Mixed-method research synthesis. Published-version repository record; accessible manuscript.
National Institute of Standards and Technology. (2024).Government technical guidance
National Institute of Standards and Technology. (2024). Artificial intelligence risk management framework: Generative artificial intelligence profile. NIST AI 600-1. Government technical guidance, not a causal effectiveness study. Publication record; full report.
Noy, S., & Zhang, W. (2023).Randomized online experiment
Noy, S., & Zhang, W. (2023). Experimental evidence on the productivity effects of generative artificial intelligence. Science, 381(6654), 187–192. Preregistered randomized online experiment. Published article.
Schwaber, K., & Sutherland, J. (2020).Framework specification
Schwaber, K., & Sutherland, J. (2020). The Scrum Guide: The definitive guide to Scrum: The rules of the game. Framework specification, used here as an example of lightweight design rather than as validation evidence. Official guide.
Tidd, J., & Bessant, J. R. (2024).Academic textbook
Tidd, J., & Bessant, J. R. (2024). Managing innovation: Integrating technological, market and organizational change (8th ed.). Wiley. Academic textbook; chapter 3 covers innovation process models. Publisher record.
Vaccaro, M., Almaatouq, A., & Malone, T. (2024).Systematic review and meta-analysis
Vaccaro, M., Almaatouq, A., & Malone, T. (2024). When combinations of humans and AI are useful: A systematic review and meta-analysis. Nature Human Behaviour, 8(12), 2293–2303. Systematic review and meta-analysis. Published article.
Practice origins: H&R Block and what changed
I developed and applied an earlier facilitated framework across several all-volunteer teams within H&R Block’s Data Science & Analytics function, outside design, product, and engineering. The work therefore required cross-functional collaboration, and an iteration involved approximately nine activity days spread across several weeks alongside normal workloads.
This revision preserves facilitated teams, discovery, proposals, prototypes, sponsorship, handoff, retrospectives, and distributed facilitation. It brings the owner and sponsor into framing, makes the prototype/proposal cycle iterative, ties approval to incremental commitment and risk, and extends accountability into delivery and observed value.
These are provenance statements based on my own experience, not scholarly evidence or independent validation. The research supports components and cautions; only future application can establish how well this particular synthesis works.
Research method and limitations
This is a targeted evidence synthesis, not a systematic review or a claim of exhaustive coverage. Research prioritized recent peer-reviewed studies and 2023–2024 academic textbooks, with the foundational 2020 Scrum Guide and a 2025 professional engineering book clearly distinguished from empirical research.
Published versions take precedence over earlier working-paper headlines. Numerical results retain their population, measure, design, and limitations; original framework prescriptions are explicitly separated from findings.