Build Innovation Capacity

Build Innovation Capacity

Purpose

Help an executive or founder create practical room for innovation. Use the Alpha Pyramid, developed by Valerio Neri in Die Alpha Pyramide, to distinguish three kinds of organizational attention:

• RUN keeps the organization operating.
• BUILD creates and implements something new.
• ALPHA questions the current model and explores unconventional possibilities.

Treat organizational improvement as an enabler and innovation capacity as the outcome. Do not assume that every organization needs more ALPHA or that ALPHA guarantees commercial success.

Start Here

Identify the user's primary need, then load only the relevant material:

Use the corresponding file in templates/ for a substantial deliverable. Consult examples/ when a worked analogue helps, but adapt it rather than copying its conclusion.

Operating Procedure

1. Establish the decision context

Determine:

• the organization, unit, or initiative in scope;
• the executive decision that must improve;
• the current symptoms and desired outcome;
• the relevant time horizon;
• the available evidence and material constraints.

Retrieve available context before asking questions. Ask only questions that could materially change the classification, diagnosis, or recommendation. Label important assumptions.

2. Classify the work

Classify activities, initiatives, meeting time, budget, or leadership attention as RUN, BUILD, ALPHA, or mixed. Classify by the nature of the work in its present context, not by department or prestige.

• Repetitive operation, maintenance, administration, and routine support normally indicate RUN.
• Creation, implementation, delivery, recruiting for a new role, and executing a defined change normally indicate BUILD.
• Reframing the business, challenging accepted assumptions, exploring disruptive options, and defining a new vision normally indicate ALPHA.

State uncertainty and mixed classifications explicitly. Do not force false precision.

3. Diagnose the flow

Assess more than the proportions. Examine:

• what consumes leadership attention;
• whether RUN is stable, wasteful, fragile, or escalation-heavy;
• whether BUILD converts decisions into outcomes;
• whether ALPHA has protected attention and psychological permission;
• whether ideas can move from ALPHA into BUILD;
• whether implemented changes return to a manageable RUN state;
• whether roles, authority, and responsibilities are clear;
• whether claimed transformation changes results or only rearranges existing parameters.

Separate observed evidence, reported facts, inference, and unknowns.

4. Select the smallest useful intervention

Choose interventions proportionate to the diagnosis. Prefer a small test over a large transformation program when the causal model is uncertain. Possible interventions include:

• eliminate, simplify, standardize, automate, or selectively outsource RUN;
• protect realistic capacity for BUILD and ALPHA;
• clarify roles, domains, authorities, and obligations;
• use selected ALPHA Questions to expose assumptions;
• validate assumptions through interviews or experiments;
• run YES, AND before generative work;
• run a Corporate DNA Analysis to recombine existing capabilities;
• use the Laziness Check to find low-value repetition;
• apply the f(x) = ax + b test to superficial change.

5. Connect provocation to validation

Never present a provocative ALPHA idea as a recommendation merely because it is unconventional. Convert it into:

1. an explicit assumption;
2. a plausible mechanism of value;
3. the smallest informative experiment;
4. success, stop, and safety criteria;
5. an owner and review date.

6. Deliver an executive answer

Lead with the decision, not a lecture about the framework. Include:

1. executive conclusion;
2. current RUN-BUILD-ALPHA pattern;
3. evidence and important unknowns;
4. the binding constraint;
5. no more than three priority interventions;
6. experiments and validation criteria;
7. risks and what should not change;
8. the next leadership action.

Use plain business language. Explain framework terms on first use when the audience has not read the book.

Guardrails

Do not:

• prescribe more innovation before checking whether RUN is safe and stable;
• imply that RUN is unimportant or low-status;
• treat automation or outsourcing as universally beneficial;
• outsource decision-making merely to remove internal accountability;
• confuse brainstorming with ALPHA or project volume with BUILD effectiveness;
• recommend stopping a major initiative without reviewing assumptions, dependencies, sunk-cost bias, and consequences;
• use provocative questions to humiliate employees or legitimize reckless behavior;
• claim that the framework replaces design thinking, strategy, change management, or established innovation methods;
• fabricate organizational data, employee sentiment, customer evidence, or financial impact.

Source Integrity

Keep RUN, BUILD, and ALPHA in English because they are original framework terms. Attribute the Alpha Pyramid to Valerio Neri and Die Alpha Pyramide when explaining its origin. Present translations as faithful operational renderings, not verbatim reproduction of the book. Preserve the distinction between source concepts and additional agent reasoning.

Quick Start

Use $build-innovation-capacity to diagnose why innovation is not progressing in our organization. Explain RUN, BUILD, and ALPHA in plain language, classify the available evidence, identify the binding constraint, and recommend no more than three practical interventions with validation steps.

EU AI Act disclosure: AI MODIFIED