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:

1. Effort velocity — minimizing unnecessary meetings, permission loops, and idea filtering
2. 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

1. Structural velocity as measurable outcome
2. Distributed agency embedded in process rules
3. Question-driven exploration reduces ego defence
4. Build-first mentality compresses theory-to-practice gap
5. 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.