The Red Ball Method
A High-Velocity, Question-Driven Innovation Protocol for Interdisciplinary Teams
Author: Gunnar Øyvin Jystad Fredrikson
Version: Draft for professional and academic review
Abstract
The Red Ball Method is a high-velocity innovation protocol designed to compress both effort-time and calendar-time from problem framing to minimum-value delivery. Unlike many innovation approaches that prioritize structured ideation or controlled failure, the Red Ball Method optimizes for rapid forward momentum by combining interdisciplinary equality, question-driven exploration, and immediate build-to-answer cycles.
Rather than treating convergence as the primary objective, the method treats convergence as a byproduct of accelerated insight generation and minimum value delivery. It can operate independently or function as a protocol embedded within larger frameworks such as Design Thinking, Dual Track Agile, and Lean Startup.
This document formalizes the method, articulates its positioning and novelty, defines boundary conditions, and proposes falsifiable hypotheses for future empirical validation.
1. Positioning and Core Thesis
Most innovation frameworks optimize for one of three things:
- Quality of exploration
- Quality of validation
- Quality of execution
The Red Ball Method optimizes for velocity toward usable value, without structurally sacrificing interdisciplinary equality or learning.
Its central thesis:
Innovation velocity increases when interdisciplinary teams are allowed to own questions, explore them in parallel, and build minimum value artefacts that answer those questions while delivering real value.
Velocity is defined along two dimensions:
- Effort velocity — minimizing unnecessary meetings, permission loops, and idea filtering
- Calendar velocity — minimizing time to something real that stakeholders can use
2. The Shift: From Idea-Led to Question-Led Innovation
Traditional brainstorming is idea-led.
The Red Ball Method is question-led.
A Red Ball is not merely an idea. It is:
A question with enough shape to explore through action, and enough potential to become a minimum value product.
This shift has structural implications:
- Questions reduce ego attachment
- Questions invite exploration rather than defense
- Questions expose unknowns explicitly
- Questions enable build-to-answer cycles
Where some methods promote “fail fast,” the Red Ball Method promotes:
Advance fast toward anything that can work.
Failure is not eliminated. It is de-prioritized in favour of credible forward motion.
3. Core Design Principles
3.1 Velocity as a Primary Metric
The method explicitly optimizes:
- Time from question to build
- Time from build to stakeholder exposure
- Total effort spent per iteration
3.2 Distributed Ownership as Structural Rule
Every participant:
- Selects one Red Ball
- May adapt or reframe any ball
- Cannot cancel another’s ball — only add to it
Equality is designed, not assumed.
3.3 Interdisciplinary Team as Latent Toolbox
Teams are treated as dynamic toolboxes.
The full capability of the team is not known at the outset.
It reveals itself through exploration.
This is a critical departure from role-based models.
3.4 Minimum Value Product (MVP 2.0)
A Minimum Value Product must:
- Be usable by a real stakeholder
- Deliver measurable value
- Answer at least one key innovation question
- Enable forward movement
This differs from many MVP interpretations that focus solely on hypothesis testing.
4. The Red Ball Velocity Loop
Step 1 — Assemble a Small Interdisciplinary Team
Maximum seven including facilitator.
Step 2 — Frame the Strategic Question Space
Define what we know, what we do not know, and what must become true.
Step 3 — Generate Question-Balls
Each participant selects one question worth pursuing.
Step 4 — Parallel Exploration
Participants explore independently through rapid builds, reframing, and critique.
Step 5 — Build-to-Answer
Each ball must produce something tangible.
Step 6 — Momentum Selection
The team selects the ball with the strongest forward momentum.
Step 7 — Minimum Value Delivery
The selected ball becomes a usable artefact.
Step 8 — Continue or Release
Evidence determines scaling, adaptation, or archive.
Convergence is present, but velocity is the driver.
5. Embedding Inside Other Frameworks
The Red Ball Method is best understood as a high-velocity upstream protocol.
Inside Design Thinking
Design Thinking emphasizes empathy, problem framing, and iterative prototyping.
Red Ball can replace or compress:
- Early ideation workshops
- Extended brainstorming phases
It accelerates the move from empathy insights to tangible artefacts.
Inside Dual Track Agile
Dual Track separates discovery and delivery.
Red Ball can serve as:
- The discovery engine within the discovery track
- A bridge between discovery and backlog-ready delivery
Inside Lean Startup
Lean assumes hypotheses are clear.
Red Ball operates before hypotheses are stable.
It generates testable hypotheses through action rather than speculation.
6. Comparison with Adjacent Frameworks
| Framework | Primary Focus | Speed Orientation | Ownership Structure | Question-Driven? | Minimum Value Focus? | Red Ball Differentiator |
| Design Thinking | Empathy & divergence | Moderate | Collective | Partially | Iterative | Faster divergence-to-build |
| Google Sprint | Time-boxed validation | High (fixed) | Centralized decision | Limited | Prototype validation | More flexible, parallel ownership |
| Lean Startup | Hypothesis testing | Iterative | Founder-led | Yes | MVP | Operates before hypotheses stabilize |
| Agile/Scrum | Delivery | Iterative | Role-based | No | Incremental delivery | Upstream velocity engine |
| Dual Track Agile | Continuous discovery | Continuous | Mixed | Yes | Backlog ready | Stronger parallel exploration |
| Lean UX | Collaborative UX | Moderate | Shared | Partially | Prototype feedback | Structured equality rule |
| Double Diamond | Divergence/convergence | Moderate | Phase-based | Partially | Not explicit | Velocity prioritization |
| Jobs To Be Done | Customer need framing | Slow/moderate | Analytical | Yes | Not build-centric | Build-to-answer emphasis |
| TRIZ | Structured problem solving | Analytical | Expert-driven | Yes | No | Hands-on interdisciplinary builds |
| Effectuation | Entrepreneurial logic | Adaptive | Founder-centric | Yes | Action-based | Formalized team equality |
| Stage-Gate | Governance control | Slow | Hierarchical | No | Formal validation | Radically higher velocity |
| Continuous Discovery | Ongoing testing | Continuous | Product-led | Yes | Yes | Explicit parallel ownership |
| Cynefin-based experimentation | Context classification | Contextual | Expert-led | Yes | Varies | Less analytical, more build-driven |
| Theory of Constraints (innovation flow) | Bottleneck removal | Flow-based | System-level | No | No | Micro-level question velocity |
7. Strengths Emerging from This Reframing
- Structural velocity as measurable outcome
- Distributed agency embedded in process rules
- Question-driven exploration reduces ego defence
- Build-first mentality compresses theory-to-practice gap
- Flexible insertion into other frameworks
8. Boundary Conditions and Safety Constraints
The method is not ideal when:
- Regulatory validation must precede exploration
- Strategic direction is fully defined and stable
- Hierarchical decision control cannot be relaxed
- Psychological safety cannot be reasonably established
Safety rule:
Ideas violating legal, ethical, or safety standards are filtered before exploration.
9. Falsifiable Hypotheses for Validation
H1: Teams using parallel question-balls will reach usable artefacts faster than teams using serial ideation.
H2: Explicit distributed ownership increases engagement and iteration throughput.
H3: Question-led framing reduces defensive behaviour compared to idea-led brainstorming.
H4: Minimum Value Products produced under velocity constraints will produce comparable learning outcomes to traditional MVP cycles but in shorter time.
10. Is This Novel or a Remix?
The Red Ball Method is not a rejection of existing frameworks.
It is a recombination with a different center of gravity.
Its novel contribution lies in:
- Making velocity the primary design constraint
- Treating distributed ownership as structural rule
- Replacing brainstorming with question-driven build cycles
- Formalizing minimum value delivery as both learning and value instrument
- Operating as a bridge protocol across frameworks
If future validation shows it is merely a variant of existing discovery practices, it may be best positioned as:
The Red Ball Protocol: A velocity loop for interdisciplinary innovation teams.
Closing Statement
The Red Ball Method is an attempt to formalize a practice observed across multiple innovation contexts over a decade: interdisciplinary teams move fastest when they are equal, question-driven, and building immediately toward value.
This document is an invitation for critique, testing, and refinement.
Beyond Competitive Advantage: Strategic Continuity in the Infinite Business Landscape
Modern strategy literature is saturated with the language of advantage: competitive advantage, first-mover advantage, sustainable advantage. Yet the historical record suggests something more sobering: advantages erode.
Technologies decay.
Markets reorganize.
Institutions mutate.
From a Darwinian perspective, survival is not secured by dominance, but by adaptation. From a thermodynamic perspective, systems naturally move toward entropy unless energy is continuously applied. From a game-theoretic perspective, equilibrium is rarely permanent. If we accept that business operates in a dynamic, non-equilibrium environment, then perhaps the central strategic task is not to win — but to remain viable.
This article proposes a structured model for what I call strategic continuity: the capacity of an organization to survive the death of its own services while remaining coherent in identity and direction.
The Infinite Game as Structural Premise
The distinction between finite and infinite games, articulated in philosophy and later applied to organizational theory, offers a useful lens.
• A finite game has known players, fixed rules, and a defined endpoint.
• An infinite game has shifting participants, evolving rules, and no terminal victory condition.
Most individual services are finite games. They launch, compete, generate returns, and eventually decline. But the organization itself participates in an infinite game. There is no final win-state. There is only continued participation or exit.
Game theory formalized by John Nash demonstrates that equilibrium conditions depend on player expectations and strategic interaction. In real markets, players continuously enter and exit, altering the payoff matrix. Stability is provisional.
From evolutionary biology to dynamic systems theory, the pattern repeats: systems that survive are those capable of adaptation under changing constraints. The question therefore becomes:
How do we design organizations structurally capable of continuity in an infinite landscape?
The Infinite Service Continuity Model
To answer this, I propose a layered model. Imagine the organization as a structured system composed of four concentric layers.
- Infinite Vision (Core Identity)
At the center lies Infinite Vision: purpose, identity lock points, moral anchors, and sustainability commitments. In philosophy, identity persists through change if core properties remain stable. In constitutional law, enduring principles anchor evolving interpretation. In finance, long-term value presumes consistent underlying thesis. Vision must survive product cycles. If a company’s identity collapses when a service fails, the service was mistaken for the organization. - Endless Strategy (Governance and Continuity Logic)
Surrounding the core is Endless Strategy: governance structures, cultural norms, legal compliance, and value systems. Ronald Coase demonstrated that firms exist to reduce transaction costs within markets. Governance, therefore, is not administrative overhead; it is structural logic. In legal theory, durable institutions balance flexibility with rule-based constraint. Endless Strategy defines how the organization moves without dissolving its identity. It is the stabilizing field around the core. - The Time Spectrum (Strategic Awareness Across Horizons)
Strategy is often collapsed into annual plans. Yet time itself is multi-layered.
The Time Spectrum includes:
• Reflective – Institutional memory and post-mortem learning
• Actual – Present operations
• Focus – Immediate directional prioritization
• Tomorrow – Forecast based on available evidence
• Future – Scenario exploration beyond current models
• Endless – Long-arc existential positioning
Physics reminds us that systems are path-dependent. Economics shows that expectations shape behavior. Psychology, particularly Daniel Kahneman’s work on cognitive bias, demonstrates that short-term focus often overrides long-term reasoning.
The Time Spectrum corrects for temporal blindness by institutionalizing multiple horizons simultaneously. - Finite Services (Orbiting Activations)
Beyond the strategic ring are finite services. Each service is an activation:
• It has a birth.
• It generates value.
• It accumulates entropy.
• It eventually declines.
Joseph Schumpeter’s concept of creative destruction captures this dynamic: innovation dismantles previous structures. In finance, portfolio theory (Markowitz) spreads risk precisely because individual assets are volatile. Services are not identity. They are portfolio elements. An organization that understands this can allow services to die without existential panic. - The Ecosystem Layer (Experience and Data)
Surrounding everything is the ecosystem:
People.
Processes.
Market structures.
Regulation.
Technology.
Data.
Claude Shannon’s information theory reminds us that data is not meaning, it is signal. Meaning arises through interpretation. Data precedes technology. It may exist as archival documents, lived experience, or mathematical models. Technology, including artificial intelligence, is a retrieval and transformation mechanism.
Within this model, AI systems – including systems that simulate “personalities” – function as advanced tools for engaging with data. They are not identities. They are structured interfaces for navigating complexity, enabling interdisciplinary teams to interrogate archives, simulate scenarios, and detect patterns at scale. Used correctly, AI becomes a cognitive amplifier within the ecosystem layer. Used incorrectly, it becomes a distraction from structural design.
Finite Innovation Inside Infinite Structure
Continuity requires renewal. High-velocity innovation frameworks for rapid convergence and scalable outcomes operationalizes innovation as a finite, repeatable cycle within the infinite structure. Small interdisciplinary teams pursue ideas in parallel. Psychological ownership is given and preserved to ensure process momentum. Convergence is structured. Key concepts advance to scalable testing; others remain archived.
This resembles scientific hypothesis testing: multiple models compete, one survives provisional validation, but none claim final truth. Thomas Kuhn’s work on paradigm shifts reminds us that even dominant frameworks eventually yield. Innovation methods that allows organizations to generate new service orbits continuously, at low cost and high velocity, without destabilizing the core are critical to keep evolving and adapting into an ever changing business ecosystem.
Cross-Disciplinary Foundations
This model can draw implicitly from multiple enduring fields such as:
• Natural Sciences: Evolutionary adaptation and entropy.
• Mathematics: Game theory and equilibrium instability.
• Psychology: Bounded rationality and cognitive bias.
• Finance: Portfolio diversification and risk distribution.
• Law: Institutional continuity through rule structures.
• Philosophy: Identity persistence through structured change.
• Marketing: Brand coherence amid tactical variability.
None of these fields alone explain continuity. Together, they converge on one insight:
Stable systems are those that separate core identity from adaptive components.
Who This Framework Serves
This architecture is not optimized for early-stage startups struggling for viability. In the earliest phase, focus must dominate. The Infinite Service Continuity Model becomes relevant when an organization already occupies space in the landscape – when it is already playing the game.
It is particularly relevant for:
• Established technology firms navigating platform transitions
• Media institutions adapting to digital ecosystems
• Public agencies balancing regulation and innovation
• Mature organizations managing multiple service portfolios
These entities face a different problem than survival through growth. They face survival through transformation.
Beyond Advantage
Competitive advantage is a finite concept. Strategic continuity is infinite.
Advantage may secure temporary dominance. Continuity secures participation across generations of services, technologies, and market structures. In the infinite business landscape, the objective is not to defeat competitors permanently. It is to design an organization capable of replacing itself, repeatedly, without losing itself. The only true failure is structural inability to adapt. And that, unlike market fluctuations, is a choice.
Memory, Context & Consistency – Building an Agent That Remembers
One of the trickiest challenges in modelling AI agents isn’t logic or response generation, it’s continuity. Ensuring that an AI not only answers now, but remembers later. That it can return to a thread without losing its identity. Because there is nothing more disorienting than having a conversation with an agent that shifts personality mid-stream, kinda like speaking to a friend who suddenly wakes up as a completely different person.
In most human-machine interaction, a stable memory framework is essential. This includes:
- Short-term memory; retaining conversational objects and references
- Long-term memory; maintaining personal identity, commitments, and preferences across time
- Persona integrity models; preventing unexpected character drift
In agent identity modelling, all three are working together to prevent the “Dr. Jekyll and Mr. Hyde” problem: agents that oscillate between roles, tone, and mental models from interaction to interaction. If your AI forgets it’s the medical advisor and randomly re-emerges as the local plumber, trust collapses immediately. And in default mode, large models often behave like dissociated personalities because they lack grounded, internalized identity and every new prompt can potentially reshape their personality. Each conversation can trigger a reset.
To avoid this, an intentional design strategy is needed:
- Map the intended personality
- Map what the agent is allowed to remember
- Test whether it remains internally consistent over time
One external reference that explores this theme is the paper:
Evolution and Alignment in Multi-Agent Systems – Managing Shift, Drift and Tool Confusion
https://medium.com/%40shashanka_b_r/evolution-and-alignment-in-multi-agent-systems-managing-shift-drift-and-tool-confusion-04c6ce42af5a
This work highlights how agent identity can mutate over time if not anchored to explicit constraints.
This issue, the continuity of mind, is also beautifully illustrated in science fiction (like so many predictions and observations about the future). In Star Trek: The Next Generation, Season 3, Episode 16 (“The Offspring”), the android Data creates a child named Lal who begins to develop her own personality traits through lived experience and memory accumulation. When Lal’s emotional and cognitive system becomes overwhelmed by conflicting identity signals, Data desperately attempts to preserve continuity of self. The entire episode is a meditation on the importance of stable internal identity structures and this goes even for artificial beings. Even if this does not reflect our reality today, it could quickly become an issue we get thrown into in the near future.
Designing AI that “stays itself” over time is essentially about preventing identity fragmentation. And this concern isn’t just philosophical, it absolutely has real-world consequences with trust, predictability and responsibility.
As Steven Pinker wrote in How the Mind Works (1997), page 60:
“Memory is not a mere repository of facts but a mechanism that shapes and constrains our sense of identity. What we remember defines who we have been, and guides who we become.”
This applies directly to AI agents:
- What the agent remembers determines who it is allowed to be.
- What is forgotten dissolves identity.
- What is stable forms personality.
Looking ahead, I believe AI must evolve from stateless engines to persistent collaborators and equipped with structured memory frameworks and internally coherent personalities. Agents can and should accumulate self-consistency over time rather than reinvent themselves each prompt. One can even argue that its a good idea to have an agent be part of a team and allowing the team members to discuss and apply critical thinking and feedback to each other.
Because ultimately, an AI that remembers itself can potentially become someone and not just something.
