Designing an Innovation Operating System Beyond a Temporary Initiative

Designing an Innovation Operating System Beyond a Temporary Initiative: A scarcity of ideas rarely hinders innovation within organisations; rather, it often falters due to a lack of a systematic approach to evaluate which ideas hold significance, how much organisational capacity can be allocated to bring those ideas to life, when to test them, and at what point to cease investment in a particular initiative.

To run a successful innovation endeavour, organisations need more than sporadic challenges, ad-hoc idea portals, or temporary project teams. What is essential is an innovation operating system: a structured, repeatable framework with clearly defined goals, decision-making rules, designated roles, committed resources, regular review meetings, and established metrics. This framework ensures that innovation becomes an integral aspect of the organisational culture.

The core principle underlying this approach is straightforward: Innovation stagnates without a consistent operating rhythm.

While a program might generate temporary excitement and engagement, an operational system ensures enduring commitment and consistency over time.

Transitioning from a Program to an Operating System

Typically, a program has a defined start and end. It might take the form of an innovation workshop, an employee idea-generation campaign, or a short-term accelerator designed to spur creativity. While these activities can ignite motivation and stimulate innovative thinking, they often fail to instigate lasting changes in the organisation’s underlying habits and practices.

Conversely, an innovation operating system works differently. It provides answers to critical, practical questions that persist throughout the year and beyond:

• What strategic challenges are we aiming to address? Identifying and agreeing upon the core problems that require innovative solutions is essential to guide efforts.
• Which opportunities warrant our attention? It’s vital to prioritise initiatives that align with overall business objectives and have the potential for significant impact.
• What evidence must a project yield before we consider additional funding? Clear criteria help ensure investment decisions are based on measurable outcomes rather than speculation.
• Who is accountable for each innovation endeavour? Defining ownership ensures responsibility and clarity, facilitating focused efforts on specific initiatives.
• How much time and capital are teams permitted to utilise? Allocating finite resources strategically helps prevent burnout and encourages efficient use of assets.
• When will leadership conduct progress reviews? Regular check-ins enable timely adjustments and accountability within the innovation efforts.
• What criteria justify the continuation, alteration, or termination of a project? Clear guidelines help teams make reasoned decisions based on project performance and potential.
• How can the organisation safeguard promising initiatives from being overshadowed by day-to-day operational pressures? Protecting innovative efforts from routine distractions is crucial to ensure they have the opportunity to develop.

This systematic approach frames innovation as a curated portfolio of investments rather than a sporadic collection of independent ideas. It distinguishes exploration activities, which typically involve learning, experimentation, and uncertainty reduction, from routine operational tasks that deliver immediate results. Organisations that assess every innovation experiment solely on short-term financial outcomes may prematurely abandon promising projects. At the same time, those that fail to demand substantial evidence may find themselves perpetually funding underperforming initiatives.

By adopting a portfolio-based model, organisations can effectively amalgamate clear decision-making authority, staged funding processes, cross-functional ownership, and regular portfolio assessments, ultimately fostering a culture of sustained innovation.

1. Establish Clear Innovation Objectives

Managing innovation successfully can be challenging for leaders, especially when they rely on vague, inspirational phrases like “think differently,” “create new ideas,” or “prepare for the future.” While these phrases can spark enthusiasm and motivation among employees, they fail to give teams clear direction or a framework for making critical decisions and trade-offs.

To reduce this confusion, start by defining a small set of specific innovation objectives that align directly with the organisation’s overarching strategy. These objectives should articulate the specific value the organisation intends to create and be grounded in tangible outcomes. For example, an organisation might set clearly defined goals such as:

• Develop a New Service for an Underserved Customer Segment: Identify an overlooked customer group and create tailored services to meet their unique needs.
• Reduce Time Required to Complete Key Customer Processes: Streamline processes customers frequently use to improve efficiency and satisfaction.
• Create a New Source of Recurring Revenue: Explore business models that generate consistent income to improve financial stability.
• Respond to New Technologies or Regulatory Changes: Stay ahead of industry shifts by proactively adapting to technological advancements or regulatory changes.
• Enhance Access, Affordability, Sustainability, or Customer Experience: Target specific improvements in these areas to meet evolving consumer expectations and societal demands.
• Build Necessary Capabilities for the Next Three Years: Identify the skills, technology, or infrastructure that will be pivotal for future success, and begin investing in developing them now.

Each objective must include a clear strategic rationale. Instead of a general wish for “more digital innovation,” leaders can articulate the goal more specifically: “We aim to test digital services designed to reduce customer waiting times and increase the availability of self-service options.” Such a statement not only communicates a clear direction for teams but also helps leaders evaluate and eliminate ideas that, while perhaps intriguing, do not address a meaningful organisational priority.

2. Utilise Strategic Boundaries

While setting clear objectives is essential, it does not mean leaders should dictate the exact means by which teams achieve those objectives. Instead, leaders should create a detailed framework that outlines the problem, opportunity, customer segment, or desired outcome while giving teams the latitude to explore a range of innovative approaches.

A practical and effective innovation brief should encompass the following elements:

• The Strategic Challenge: Clearly define the issue or opportunity that needs to be addressed.
• Target Customers or Stakeholders: Identify the specific customer groups or stakeholders that the innovation efforts will impact.
• Desired Outcome: Specify the precise outcome the organisation seeks to improve or achieve through innovation.
• Constraints to be Respected: Outline any limitations or constraints that teams must adhere to during the innovation process.
• Justification Evidence: Identify the metrics or evidence that would validate the need for further investment in the proposed innovation.
• Timeframe for Discovery and Experimentation: Establish a timeline that delineates the period available for preliminary testing and exploration of ideas.

For instance, an innovation brief could state: “Within the next quarter, we will test various methods to assist first-time customers in comprehending and completing our onboarding process with minimal external support. Teams are encouraged to explore potential solutions that may be digital, human-driven, or a combination of both. A successful experiment will need to demonstrate improvements in the completion rates, a decrease in customer confusion, or an increase in customer confidence.”

This structured approach keeps the focus while preserving the creative freedom needed for effective innovation. By clearly outlining the parameters within which teams can operate, organisations foster an environment where creativity and strategic alignment can flourish simultaneously.

2. Publish Visible Resource Criteria

Effective innovation decisions often stall when funding criteria are buried in executive discussions. When teams lack clarity on how leaders allocate resources, they may resort to political maneuvering, persistence, or personal influence instead of using concrete evidence. This lack of transparency can detract from sound decision-making and stifle genuine innovation.

To prevent this, organisations should publish clear, accessible criteria that outline how initiatives will be evaluated for attention, time investment, funding, and access to specialised support. By demystifying these processes, organisations can foster a more collaborative and evidence-based approach to innovation.

Visible Criteria for Evaluation

The criteria that should be made visible might encompass a variety of factors, such as:

• Strategic Relevance: How well does the initiative align with the organisation’s overarching goals and strategy?
• Customer Problem Size and Importance: What is the scale and significance of the problem the initiative aims to address from the customer’s perspective?
• Strength of Customer Evidence: Is there robust, qualitative or quantitative data supporting the existence and urgency of the customer need?
• Potential Economic or Social Value: What kind of value—financial, social, or otherwise—can the initiative potentially deliver to both the organisation and its customers?
• Distinctiveness of Proposed Approach: How innovative or unique is the solution compared to existing alternatives in the market?
• Feasibility within Organisational Capabilities: Does the organisation have the necessary resources, skills, and technology to execute the initiative successfully?
• Regulatory, Ethical, Operational, or Reputational Risks: What potential risks could affect the initiative’s success, and how are they likely to be managed?
• Learning potential: What opportunities does this initiative present for learning and development within the organisation?
• Speed and Cost of Next Experiment: How quickly can the next phase of experimentation be executed, and what will it cost?
• Evidence of Adoption or Willingness to Pay: Is there data indicating that potential customers will adopt the solution or are willing to pay for it?
• Ability to Scale if Experiment Succeeds: If the initiative proves successful, what plans are in place for scaling and broader implementation?

Not every project must score highly across all these criteria. For instance, a high-risk, transformational project might yield negligible short-term revenue but could be deemed strategically vital. In contrast, a process improvement initiative might lack unique innovation but delivers quantifiable benefits rapidly.

The primary aim of publishing these criteria is not to create a rigid mathematical model that stifles creativity, but to foster a transparent, consistent decision-making process that improves innovation effectiveness.

Fund Evidence in Stages

A common pitfall in funding innovation initiatives involves providing a complete project budget at the outset. A more prudent approach is to allocate resources incrementally, increasing investment only when projects generate compelling evidence to justify further funding.

A Staged Funding Model May Include the Following Phases

• Explore: Provide a limited amount of time and budget to understand the problem, the customer’s needs, and the assumptions underpinning the initiative.
• Test: Allocate resources for targeted experiments designed to interrogate the most uncertain and critical assumptions surrounding the project.
• Pilot: Once initial testing proves successful, offer additional funding and resources to trial the solution in a controlled, realistic environment to gauge its performance.
• Scale: Only after confirming evidence of adoption, favourable economics, operational readiness, and a strong strategic fit, should the organisation commit to broader implementation efforts.

This staged approach helps mitigate two common errors in innovation funding. The first mistake is allocating excessive resources to unproven ideas too early. The second is the pressure to develop a fully-fledged business case before the team has gathered sufficient, meaningful evidence.

Moreover, innovation budgets should remain adaptable. Quarterly resource reallocations allow leaders to pivot and direct funding toward more promising opportunities as they arise, rather than adhering strictly to annual budgets that reflect past priorities. This flexibility encourages responsiveness to changing circumstances, enhancing the organisation’s overall capacity for innovation.

3. Safeguarding Strategic Innovation Initiatives

In organisations, even when leaders endorse innovation initiatives, the demands of daily operations can overshadow the human and time resources allocated to innovation efforts. Often, teams are granted permission to pursue innovative ideas, but they lack robust protection from competing priorities that may jeopardise these initiatives. Consequently, innovation can morph into unpaid overtime or tasks employees undertake only after fulfilling their other operational responsibilities.

To ensure strategic innovation is genuinely prioritised, organisations must establish explicit protection mechanisms. These mechanisms safeguard innovation work against the incessant pull of daily operations. They might encompass:

• Reserved Team Capacity for Innovation: Allocate specific personnel and time dedicated solely to innovation tasks, ensuring these resources are not diverted to other operational duties.
• A Designated Innovation Budget: Create a separate budget earmarked for innovation projects, preventing everyday operational constraints from stifling innovation.
• Time-Boxed Experiments: Set a structured timeframe for experimentation to encourage swift iterations and learning without the risk of indefinite project expansion.
• Dedicated Access to Customers and Data: Ensure that innovation teams have direct and prioritised access to customer feedback, market insights, and relevant data, essential for validating innovative ideas.
• Accelerated Support from Legal, Finance, Technology, or Procurement: Establish streamlined processes that allow innovation teams to obtain necessary approvals and resources quickly without being bogged down by routine bureaucratic hurdles.
• Leadership Endorsement for Unexpected Outcomes: Ensure leaders support teams when experiments yield unforeseen results, emphasising that learning and adjustment are part of the innovation process.
• Clear Restrictions on Additional Operational Work: Enforce policies that prevent excessive operational tasks from being added to innovation teams, ensuring they can focus on their core objectives without distraction.
• Separate Review Processes for Early-Stage Initiatives: Develop distinct review mechanisms to evaluate new initiatives early, allowing more flexibility and creative exploration without the constraints of established operational review processes.
• Designation of an Executive Sponsor: Appoint a senior leader to champion innovation efforts, tasked with identifying and eliminating barriers that may inhibit progress.

Protecting innovation does not mean granting unfettered freedom or sheltering projects with poor performance metrics. Rather, it entails shielding strategic work from the disruptive influence of routine operational demands, allowing the organisation the opportunity to validate its innovation hypotheses.

Prioritising Process Over Individual Ideas

Leadership should focus on safeguarding the processes and capacity that enable innovation rather than protecting every single idea proposed by teams. This essential distinction allows teams to terminate less viable projects without undermining the organisation’s overall commitment to innovation. A project may not succeed, but the operating system can thrive if teams learn swiftly from their experiences, avoid unnecessary costs, and shift their efforts toward more promising opportunities.

A powerful message to communicate to teams is:

“We will protect your chance to assess and test this idea; however, we do not guarantee perpetual funding for any single concept.”

This approach fosters psychological safety, encouraging team members to explore bold ideas without fear of failure, while ensuring accountability and strategic alignment within the broader organisational context.

Establishing a Quarterly Operating Rhythm for Innovation

Innovation thrives on structure and frequency; establishing a predictable operating rhythm is essential to sustain momentum and make informed decisions. Without such a system, organisations can struggle with irregular decision-making, prolonged project timelines, and diminished team energy due to uncertainty around approvals and direction.

The Importance of a Quarterly Rhythm

A structured quarterly rhythm serves as a framework for aligning innovation efforts with the organisation’s strategic objectives. It creates a cycle for setting priorities, validating assumptions, assessing evidence, and reallocating resources as needed. By integrating innovation into the overall organisational cadence, the process becomes more systematic and results-oriented.

Suggested Quarterly Cycle

• Quarterly Kickoff: At the beginning of each quarter, organisational leaders gather to reaffirm the company’s strategic objectives and discern which challenges or opportunities merit innovative solutions. This involves a comprehensive analysis of the market landscape, identifying pain points and emerging trends that could impact the organisation’s direction. During this phase, leaders also communicate available project capacity, define funding limits, and establish clear decision-making criteria to guide evaluations throughout the quarter.
• Innovative Pursuits: During the quarter, dedicated cross-functional squads with diverse expertise engage in hands-on experimentation. These teams actively gather insights by engaging with customers, developing prototypes, and iterating on their ideas based on real-world feedback. The emphasis here is on practical learning, so leaders are encouraged to facilitate progress without imposing excessive reporting burdens, allowing teams to focus on their creative processes and learning.
• End-of-Quarter Review: As the quarter draws to a close, each initiative prepares to present its findings and insights. This presentation should encompass a comprehensive overview of the evidence gathered, lessons learned, associated risks, resource requirements, and actionable recommendations for the next steps. This review focuses on strategic decisions rather than polished presentations, keeping discussions centred on value and progress.
• Quarterly Portfolio Review: In the concluding phase of the quarterly cycle, leaders convene for a portfolio review meeting. This crucial session involves deciding the fate of various projects: whether to continue, pivot, pause, scale, or terminate them based on the evidence presented. By using the insights gained, leaders can redirect released resources back into the organisation’s strategic priorities, ensuring investments align with the most promising avenues for growth.

Conclusion

This structured quarterly rhythm not only connects innovation endeavours to the organisation’s broader strategic planning framework but also allows ample time for experimentation to yield actionable evidence. This cycle cultivates an environment where innovation is continually assessed and aligned with organisational goals, fostering a culture of agility and responsiveness in a fast-paced business landscape.

5. Establish Routine “Stop-Doing” Reviews

In many organisations, there’s a clear pathway for approving new projects and initiatives; however, discontinuing ongoing work is often a significant challenge. This creates a continuous buildup of responsibilities, where new priorities are layered onto existing workloads, causing older projects to drain both human resources and financial capital without reevaluation.

A “stop-doing” review counters this pattern by encouraging leaders and teams to assess current commitments and identify tasks that no longer warrant the support and resources they receive. This review should not only target innovation projects. It should also cover a wide range of operational initiatives, ongoing reporting obligations, recurring meetings, product features, and other commitments that consume valuable capacity within the organisation.

During the review, teams should ask a series of critical questions to evaluate their projects rigorously. These inquiries might include:

• What have we learned since our last review? This allows teams to reflect on progress made, or the lack thereof, since the last evaluation.
• Which assumptions did the evidence support? Identifying supported assumptions helps determine which project elements remain valid.
• Which assumptions did the evidence weaken or disprove? Acknowledging incorrect assumptions is crucial for adapting strategies and resource allocation.
• Has the customer problem proved important enough to pursue? Understanding the relevance of the problem ensures resources align with market needs.
• Has the project demonstrated meaningful adoption or demand? It’s vital to assess whether the solution is being embraced by its intended users.
• Has the strategic context changed? Market and organisational conditions can shift rapidly, requiring a reevaluation of priorities.
• What would we choose to fund today if we were starting from scratch? This helps identify projects we would start today versus those we continue out of inertia.
• What work should we consider stopping, pausing, reducing, or transferring? This focuses on prudent resource management and prioritisation.
• What resources will be freed up by stopping this project? Identifying available resources allows for strategic reallocation.
• Which new priority should receive those released resources? Ensuring that freed-up resources are directed toward high-value projects maximises overall productivity.

The overarching goal of a stop-doing review is not to penalise teams for project failures; rather, it is to liberate resources from low-value commitments and redirect them into more productive avenues.

Implement Explicit Exit Criteria

Before launching any project, agree on explicit exit criteria—clear conditions under which a project may be deemed unworthy of continuation. These criteria could encompass:

• The target customer does not experience a significant problem. If the primary issue is not impactful for the customer, it’s a clear indicator to halt the project.
• Users do not adopt the proposed solution after repeated testing. Low user engagement despite multiple tests strongly suggests the solution may not meet their needs effectively.
• The economics cannot support a viable business or service model. If financial viability is in question, it is prudent to reassess the project investment.
• The project poses unacceptable legal, ethical, safety, or reputational risks. Projects that raise these concerns should be prioritised for discontinuation.
• The solution does not align with current strategic objectives. Any project that diverts from the organisation’s strategic goals may need reevaluation.
• The team cannot access the capabilities or infrastructure required to scale the project. Without the necessary resources or infrastructure, projects may be stymied.
• The project fails to produce meaningful learning within the agreed timeframe or budget. A lack of learning can signal that the investment is no longer justifiable.

Explicit exit rules help prevent teams from clinging to projects simply because of prior investments in time and resources. They provide a framework that makes difficult decisions less personal and more objective.

At the end of a stop-doing review, document the decisions made, assign a named owner to any follow-up actions, and determine resource allocation. Responses such as “We will keep monitoring it” should not be considered an acceptable outcome, as they can lead to indecision and continued waste of resources.

6. Clarify the Essential Roles

To create a successful innovation operating system, it is imperative to establish clear accountability structures. If all employees share responsibility for innovation, it can lead to a lack of ownership when it comes to making the tough decisions that drive projects forward. A robust framework can be built upon three critical roles: the executive sponsor, the innovation owner, and the cross-functional squad.

Executive Sponsor

The executive sponsor serves as a crucial link between the innovation portfolio and the overall organisational strategy. While this person is not involved in the day-to-day management of experiments, their active support is vital to protecting initiatives and enabling timely decision-making.

Key Responsibilities: – Define or reinforce the strategic priorities that guide innovation efforts, ensuring alignment with the broader organisational goals.

• Secure commitment from senior leadership, fostering a culture that values and supports innovative pursuits.
• Protect the innovation budget and maintain the team capacity needed throughout the project lifecycle.
• Identify and dismantle organisational barriers that may impede progress, providing a clear path for initiatives to advance.
• Resolve conflicts that may arise between different departments, ensuring that varying perspectives are harmonised in a way that fosters collaboration.
• Make or escalate portfolio decisions, weighing various factors to determine the best course of action for the organisation’s innovation strategy.
• Uphold evidence-based experimentation principles, especially during times of budget constraints, advocating for the scientific method in decision-making processes.
• Ensure that successful innovations can transition smoothly into the mainstream organisation, facilitating integration and scalability.

A sponsor who participates only at the initial launch meeting will provide insufficient support for the project’s ongoing needs. Effective sponsorship requires regular involvement at critical decision points, consistent advocacy for the operating rhythm, and reinforcement of the strategic importance of the work.

Innovation Owner

The innovation owner is accountable for driving the initiative forward day-to-day. This role may be filled by a product leader, business lead, service designer, project owner, or anyone with the authority and commitment to see the project through to success.

Key Responsibilities:

Clearly define the primary problem the initiative seeks to resolve, along with the underlying assumptions that must be tested.

• Maintain an experiment backlog outlining ongoing tasks and priorities, ensuring a transparent project roadmap.
• Coordinate customer research and testing efforts, utilising feedback to refine the innovation and better meet user needs.
• Track evidence and decisions made throughout the project, documenting insights that inform future activities.
• Manage the project’s capacity and budget efficiently, ensuring resources are allocated effectively.
• Provide honest progress reports, including obstacles faced and pivots needed to adapt to changing circumstances.
• Recommend whether to continue, pivot, pause, or halt the initiative based on evidence collected and strategic alignment.
• Prepare the initiative for handover or scaling when it reaches maturity, enabling a seamless transition to broader organisational integration.

The innovation owner must wield sufficient authority to act decisively. Assigning responsibility without corresponding decision-making power can cause unintended delays and frustration within the project team.

Cross-Functional Squad

The cross-functional squad is a diverse team that brings together the necessary skills and perspectives required to drive learning and execution. Depending on the initiative, the squad might include people from customer experience, operations, technology, finance, marketing, legal, data analysis, design, and frontline service teams.

Key Responsibilities

• Work collaboratively as an integrated team, rather than as separate departments, to streamline the innovation process. When one department develops an idea, it should flow seamlessly to the next, avoiding bottlenecks that can occur when different functions operate in isolation.
• Maintain agility by keeping squads small and including the right decision-makers and specialists needed for rapid progress. While the squad does not require permanent representation from every functional area, access to the essential expertise needed for each phase of the experiment is critical.
• Foster open communication and collaboration among team members to leverage each individual’s strengths, ultimately enhancing the innovative potential of the project.

In summary, clarifying these roles establishes a solid foundation for an effective innovation operating system, enabling teams to navigate the complexities of innovation with clarity and purpose. By empowering each role with the authority and resources needed, organisations can strengthen their innovation capacity and adapt better to the evolving market landscape.

7. Measuring Activity and Business Impact in Innovation

Innovation metrics play a crucial role in helping leaders make informed decisions about the direction of their initiatives. These metrics should not become a heavy reporting burden or incentivise teams to focus on superficial activities that do not yield substantial results. To achieve this, organisations should use a balanced scorecard approach that integrates both leading and lagging indicators.

Importance of Leading and Lagging Indicators

Leading indicators are particularly valuable during early stages of innovation, such as discovery and experimentation, when actual revenue may not yet be realised. These indicators provide early insights into the organisation’s learning capacity and its ability to progress effectively.

Leading Indicators

• Number of Experiments Conducted: Reflects engagement in testing new ideas.
• Percentage of Experiments Completed On Schedule: Indicates execution efficiency.
• Cycle Time from Idea to First Test: Measures the agility of the innovation process.
• Cycle Time from Experiment Decision to Launch: Measures how quickly the team brings validated ideas to market.
• Number of Customer Conversations Completed: Measures direct engagement with users to gather insights.
• Number of Assumptions Tested: Shows the rigour of the validation process.
• Number of Hypotheses Validated or Disproved: Indicates the quality of learning achieved.
• Time Between Learning and Decision: Measures responsiveness to new insights.
• Prototype or Pilot Completion Rate: Demonstrates progress in bringing concepts to tangible forms.
• Customer Engagement with Early Versions: Gauges initial user interaction and interest.
• Number of Projects Receiving Timely Decisions: Reflects the organisational speed in decision-making.
• Percentage of Innovation Capacity Actually Protected and Used: Ensures that resources earmarked for innovation efforts are being dedicated to active projects.
• Diversity of Ideas Across Customer Groups, Markets, and Strategic Themes: Encourages a wide range of thought, which can lead to innovative solutions.

Among these metrics, two particularly important measures are experiment velocity and cycle time. Experiment velocity tracks how often teams can test significant hypotheses, while cycle time focuses on how quickly the organisation moves from generating ideas to gathering evidence. Innovation scorecards often use additional metrics, such as the time from idea conception to assessment and the number of hypothesis-driven experiments executed over a given timeframe.

However, high experimental activity does not inherently indicate success. Teams may run numerous low-quality experiments that provide little valuable learning. Therefore, complement activity metrics with a focus on the quality of evidence gathered, customer reactions, and the speed of decision-making.

Lagging Indicators

Once the initial phases of innovation development are complete and some level of adoption has occurred, lagging indicators come into play. These metrics confirm whether innovation efforts have generated meaningful results tied to the organisation’s strategic goals. Potential lagging indicators include:

• Revenue from New Products or Services: Provides direct insight into financial impact.
• Percentage of Revenue Generated by Recent Offerings: Tracks the contribution of new initiatives to the overall revenue stream.
• Customer Retention or Acquisition from New Offerings: Highlights market response and customer loyalty.
• Adoption and Repeat Usage Rates: Offers a view of how consistently customers engage with new products.
• Cost Savings Achieved from Innovative Processes: Reflects efficiencies gained through innovation.
• Improvements in Service Quality: Indicates how innovation has influenced customer experience.
• Increased Market Share: A clear sign of competitive advantage gained.
• Customer Satisfaction or Effort Scores: Measures client perceptions and ease of use.
• Social, Environmental, or Community Impact: Even beyond financials, this addresses broader implications of innovation efforts.
• Return on Innovation Investment (ROI): Offers a concise measure of the value generated against the resources invested.
• Percentage of Pilots Transitioning to Sustainable Operations: Tracks the viability of experiments after initial testing.

While revenue from new offerings can serve as a useful long-term metric, leaders should clearly define what constitutes “new” for their purposes. This could mean tracking revenue from products or services that have launched within the past 24 to 36 months.

Importantly, relying solely on lagging indicators to evaluate early-stage work is not advisable. A discovery project may hold significant value if it successfully disproves a costly assumption, saving the organisation from potential investment losses. Similarly, while strong activity metrics may seem promising, they do not guarantee eventual commercial success.

Keeping the Dashboard Concise

To stay effective, start with a manageable set of metrics. A smaller dashboard might include:

• Experiments Completed: To provide a clear picture of sampling breadth.
• Time from Idea to Market Test: To gauge acceleration in moving to real-world testing.
• Evidence Strength or Key Assumption Validated: To assure quality in hypotheses tested.
• Customer Adoption or Engagement Levels: To monitor initial market response.
• Revenue from New Offerings: To track financial outcomes over time.

Review and refine the selected measures quarterly. Remove any metric that does not support timely, meaningful decision-making. Ultimately, a well-designed dashboard should help leaders decide which initiatives to continue, modify, halt, or fund, rather than merely increasing the volume of available information. The goal is to provide clear insights that drive strategic action.

8. Transforming Reviews into Strategic Decisions

A meeting can be integrated into an organisation’s operating framework only if it leads to well-defined actions that drive projects forward. For every project discussed in the review, it is essential to arrive at a specific decision. This decision should fall into one of the following categories:

• Continue: This conclusion indicates the project has enough evidence and momentum to move to the next agreed-upon step. The data collected thus far supports further investment and development, suggesting confidence in moving forward.
• Pivot: This option signifies that while the underlying problem remains pertinent, the initial solution or the target customer needs to be reassessed or altered. It reflects a willingness to adapt to new insights without abandoning the objective.
• Pause: Choosing to pause the project suggests potential for success, but the current circumstances do not warrant additional investment at this time. This allows for a reassessment of resources and conditions before proceeding.
• Stop: This decision indicates that the organisation will terminate the project because it lacks viability or alignment with strategic goals. The organisation will reassign remaining resources to more promising initiatives, ensuring optimal use of its capabilities.
• Scale: Choose this option when the project has demonstrated significant value and is ready to receive expanded investment to support broader implementation. The findings justify a larger commitment of resources and energy to fully realise the project’s potential.

Each decision made during these reviews should clearly identify the following components:

• Decision Owner: The individual responsible for overseeing the decision and subsequent actions.
• Evidence Supporting the Decision: A clear delineation of the data and insights that led to the conclusion, which bolsters transparency and accountability.
• Approved Resources: Documentation of any resources allocated to the next phase of the project or to further exploration.
• Next Milestone: A concrete goal that the team aims to achieve before the next review, helping maintain focus and accountability.
• Date of Next Review: This establishes a timeline for reevaluation, ensuring regular check-ins, and facilitating ongoing feedback.
• Conditions Affecting the Decision: Clarifies the circumstances or criteria that may prompt a future reassessment, fostering adaptability and responsiveness.

Implementing this disciplined approach prevents innovation reviews from devolving into mere ceremonial updates. It instils a culture where teams understand that honest learning and assessments yield tangible consequences.

A Practical Operating Model for Innovation

To cultivate a productive environment for innovation, an organisation can adopt a straightforward and effective framework rather than creating a convoluted governance structure that may hinder agility. This model can be organised into a rhythm of activities that occur at different intervals—monthly, quarterly, and annually.

Monthly Activities

• Innovation Owners Update Experiment Progress: Individuals leading the projects provide updates on their initiatives, sharing insights on what is working and what is not.
• Squad Reviews: Teams assess their assumptions, evaluate the evidence collected, identify risks, and determine the next tests to run based on their findings.
• Leadership Support: Executives and leaders focus on removing any immediate barriers that teams face, enabling fluid progress on innovative projects.

Quarterly Activities

• Executive Reviews of Strategic Priorities: Senior leadership comes together to evaluate the organisation’s strategic goals and priorities, ensuring alignment across projects and initiatives.
• Presentation of Evidence: Teams are encouraged to present evidence of outcomes rather than activity summaries, enabling meaningful discussions about progress and challenges.
• Stop-Doing Reviews: Leaders assess initiatives no longer deserving investment, prioritising efforts aligned with strategic priorities.
• Decision-Making on Projects: Teams receive clear directives—continue, pivot, pause, stop, or scale—based on the evidence presented during the reviews.
• Funding and Resource Allocation: Resources and funding are redirected towards projects that demonstrate stronger potential and alignment with strategic objectives.
• Publication of Updated Criteria and Resource Allocations: Clear communication of the updated criteria and the rationale behind resource allocation decisions reinforces transparency.

Annual Activities

• Review of the Innovation Portfolio: Leaders assess the innovation portfolio’s overall strategic contribution to the organisation. This includes reviewing revenue impact, user adoption rates, capability development, and the lessons learned throughout the year.
• Portfolio Balance Adjustments: Executives adjust resource allocation across initiatives, weighing core improvements against adjacent opportunities and transformational projects.
• Operating System Revisions: Teams assess what worked well and what hindered innovation over the past year, updating their operating framework to strengthen future efforts.

The frequency of these reviews may vary according to the organisation’s nature and pace. For a rapidly evolving digital enterprise, monthly reviews are imperative; however, more traditional or heavily regulated organisations might necessitate longer validation cycles. The key is to establish a review rhythm that is frequent enough to prevent stagnation while practical enough to support meaningful learning.

Taking Initial Steps: Start with Two Actions

Rather than waiting for the elusive perfect innovation framework to emerge, organisations should take two immediate, actionable steps to lay the groundwork for an effective innovation process.

• First: Schedule your next stop-doing review. Give leaders and teams enough time to evaluate their current projects candidly. This review should identify initiatives that no longer warrant investment, freeing up resources to redirect to more viable projects.
• Second: Publicise your funding criteria. Clearly outline how the organisation will assess strategic relevance, customer evidence, learning value, feasibility, risk levels, adoption potential, and anticipated impact. By making this information accessible, stakeholders can align their efforts with organisational priorities based on evidence rather than influence.

These two actions convey a powerful message: innovation should not be treated as an occasional program that vies for attention, but as a core organisational capability characterised by clear priorities, visible guidelines, protected resources, accountable roles, and a consistent decision-making rhythm.

When stopping becomes routine, teams gain the capacity to pursue what truly matters. When funding criteria are transparent, individuals can concentrate on providing sound evidence rather than relying on persuasion. Establishing a consistent operational rhythm turns innovation from aspiration into practice, ultimately propelling the organisation toward its strategic goals.

2/20 Yesterday’s Post. From Controller to Coach: The Supermanager Playbook