Experimentation at Small Scale: The 5-Day Innovation Sprint

Experimentation at Small Scale: The 5-Day Innovation Sprint. Innovation often begins not with elaborate strategy sessions, significant financial investments, or groundbreaking ideas, but with a simple yet profound question: “What might happen if we tried this?” The most effective and innovative teams are not necessarily those with the largest resources; instead, they are made up of individuals who cultivate a culture of experimentation—where testing, learning, adapting, and iterating become part of their daily routine.

Small-scale experimentation lets organisations explore Innovation in a way that feels safer and more practical. Rather than requiring immediate commitment to an expansive and often uncertain initiative, this approach encourages teams to conduct modest tests that can yield valuable insights. These small experiments could include various initiatives, such as trying out a new method of communicating with customers to enhance engagement, streamlining a particular internal process to improve efficiency, altering the format of a team meeting to foster better discussions, piloting a new service feature with a limited group of users to gather feedback, or creating a rough prototype of an idea to gauge reactions from peers.

Importantly, these small-scale experiments aim not to achieve perfection on the first try but to build momentum and create learning opportunities. Each experiment provides a wealth of information: what worked, what fell short, what unexpected outcomes emerged, and what areas warrant further exploration. As individuals witness that experimentation is manageable and can lead to constructive outcomes, they become more inclined to share ideas and take careful, thoughtful actions. Confidence in the process builds through experience, rather than waiting for all uncertainties to be resolved.

One structured approach to integrating experimentation into daily work routines is through the 5-Day Innovation Sprint. This framework is a short, focused cycle that guides individuals or teams from initial curiosity to practical, real-world learning within a single workweek. The design intentionally keeps the experiment’s scope small, which minimises the temptation to overanalyse and helps maintain a concentrated focus on actionable outcomes. This approach also builds a repeatable learning practice, ensuring teams can iterate and improve their ideas consistently.

Through initiatives like the 5-Day Innovation Sprint, organisations can cultivate a dynamic environment where experimentation is embraced, leading to ongoing Innovation and growth.

The Purpose of the Sprint

The 5-Day Innovation Sprint is designed to normalise experimentation. It helps people shift from saying, “We need a perfect plan,” to asking, “What is the smallest useful test we could run?”

This distinction matters. A perfect plan can take weeks or months to develop, and it is often built on assumptions that haven’t been tested yet. A small experiment brings assumptions to light. It allows a team to learn before investing more time, money, energy, or reputation in a larger solution.

For example, a team may believe that customers want a new information resource, a different booking process, a shorter report, or a more personalised follow-up. Rather than spending months building the complete version, the team can test the underlying idea first. They might create a simple draft, show it to several users, trial it with one customer segment, or run a temporary manual version of the process. The feedback may confirm the idea, improve it, or reveal that another problem matters more.

All three outcomes are valuable. Innovation is not only about finding evidence that an idea will work. It is also about learning early when an idea needs to change.

The Week Rhythm: A Detailed Approach to Enhancing Curiosity and Experimentation

Monday: Start With Curiosity

As you start a new week, dedicate Monday to cultivating curiosity and framing questions that spark deeper exploration of challenges your team or organisation may face. This day isn’t for immediate solutions; it’s for digging into the nuances of the problems at hand.

Frame the Exploration

Start by brainstorming questions that highlight different aspects of your work environment. These could include inquiries such as:

• Customer Frustrations: What specific issues are causing dissatisfaction among our customers, colleagues, or the community at large? Identifying common pain points can reveal potential areas for improvement.
• Inefficiencies: In what processes are individuals spending unnecessary time or effort? Understanding where energy is being misallocated helps to streamline operations.
• Assumptions Without Evidence: Are there beliefs we hold about our processes or customers that lack a solid basis? Challenging these assumptions can lead to enlightening discoveries.
• Complexities in Work: Are there tasks or procedures that seem more complicated than they should be? Simplifying these elements can greatly enhance productivity and satisfaction.
• Recurrent Requests or Challenges: What do our customers or team members often request, struggle with, or tend to avoid? Spotting these patterns can guide us toward meaningful enhancements.
• Untapped Opportunities: Have we noticed small opportunities for improvement that we haven’t explored yet? These often-overlooked areas can lead to impactful changes.

Narrow Down the Focus

From your brainstorming session, choose one targeted question for the week. This question shouldn’t be overly broad. Instead of tackling something expansive like, “How can we improve customer experience?” focus on a specific aspect. For example, consider a question like, “Would customers find a one-page onboarding checklist more helpful than our current welcome email?” This question is specific enough to support focused investigation.

Define the Experiment Clearly

The objective on Monday is to clarify your chosen question, so your team shares a common understanding. Write out the experiment’s framework in straightforward language.

For instance, you could articulate your hypothesis like this:

“We want to learn whether implementing a one-page onboarding checklist will help new customers understand their first three actions more easily than the current welcome email does.”

This clear statement should encapsulate three critical components:

• Audience: Who will be impacted or involved in the experiment? In this case, it’s the new customers.
• Proposed Change: What specific adjustment or intervention are you proposing? Here, it’s shifting to a one-page onboarding checklist.
• Learning Goal: What outcome are you trying to determine? This experiment aims to determine whether customers find the checklist more effective at improving their understanding.

If your team struggles to explain the experiment, it’s a strong indicator that your question or objective might still be too broad or needs further refinement. Clarity at this stage lays the foundation for effective experimentation and learning throughout the week.

Tuesday: Build a 3-Minute Prototype

On Tuesday, create the smallest, most essential version of your idea within a strict time limit—consider setting it to just three minutes. The goal is to resist the temptation to refine and polish your creation during this initial phase.

A prototype at this stage does not need to resemble a final product in any way. Instead, it can take various forms such as a simple sketch, an informal script, a draft email, a paper mockup, a bare-bones slide deck, a straightforward workflow diagram, a mock customer conversation to illustrate interactions, or even a basic landing page layout. The main objective is to make your idea tangible enough so others can engage with it and provide constructive feedback.

The three-minute time constraint serves a crucial purpose: it helps to break the cycle of perfectionism. Many individuals and teams postpone testing their ideas, mistakenly believing they must first produce something complete, polished, and free of risk. However, obtaining early feedback is far more valuable than striving for initial elegance.

For example, if a team is developing a new onboarding checklist for new employees, they might put together a rudimentary document that contains just three sections: “Start Here,” “Your First Task,” and “Where to Get Help.” This document may lack final branding, ideal wording, or a meticulously designed layout, and that’s perfectly acceptable. At this stage, what matters most is verifying that the structure and content serve a clear purpose and are useful, rather than focusing on aesthetics or formatting.

Once you have this initial rough version, the next step is to make incremental improvements just enough to improve understanding and usability for testing. Continually ask yourself: What is the minimum viable version of this prototype that can help us gather meaningful insights? Keep this inquiry at the forefront to stay focused on learning rather than perfecting.

Wednesday: Borrow and Remix  

Innovation isn’t solely about coming up with brand-new ideas; often, it’s about leveraging existing ones in creative ways. On Wednesday, shift your focus beyond your immediate team or industry. Take time to investigate how others have effectively tackled similar challenges. The goal is to borrow the underlying principles from their solutions and adapt them to your unique context.

Start by observing different departments within your organisation. For instance, how does a neighbouring team conduct their meetings to foster creativity? What methods do they utilise to streamline communication? You might also explore other organisations entirely. Analyse how they have simplified a process that you are currently struggling with, or consider how a particular app enhances user experience for first-time users. Even diverse industries can provide valuable insights; for example, how does a retail business gather and utilise customer feedback effectively?

Your goal isn’t merely to imitate these approaches; it’s to engage in intelligent remixing. For instance, you might find that a library’s customer onboarding model serves as an excellent template for structuring your user engagement process. Similarly, a hospitality business may excel at creating warm and welcoming environments for new clients, while a school could communicate complex information in an easily digestible format. A software company might have a feedback prompt that effectively encourages user interaction. Reflect on these diverse influences and ask yourself: What can we learn from their approaches, and how might we adapt them to improve our situation?

By borrowing ideas and strategies, you can broaden your spectrum of potential solutions, alleviating the pressure to craft an “original” concept from scratch. In fact, most practical Innovation arises from combining, simplifying, adapting, or improving pre-existing ideas.

By the end of Wednesday, refine your prototype by integrating one or two of these external insights. However, be mindful not to let your research turn into a form of procrastination. The goal isn’t to conduct an exhaustive review of all available options, but to pinpoint a few useful ideas you can apply quickly and meaningfully.

Thursday: Talk to One Real Human 

Thursday serves as a critical reality check in your innovation process. It’s the day to present your prototype to a real person who can represent the interests of those affected by the problem you’re trying to solve. This individual could be a customer, colleague, supplier, stakeholder, team member, or even a member of your local community.

A single, focused conversation may not make a comprehensive research program, but it is far more beneficial than relying solely on internal assumptions. The person you engage with doesn’t need to validate your final solution; rather, their honest reactions will provide invaluable insights that help you learn and pivot as necessary.

When discussing your prototype, pose open-ended, practical questions that encourage thoughtful responses, such as:  

• What do you perceive this prototype to be designed for?  
• If you were to use this first, what action would you take?  
• What aspects of this design feel clear or confusing to you?  
• How could this be made more valuable or useful from your perspective?  
• What problem does this prototype address for you, if at all?  
• Are there any barriers that would prevent you from using it?  
• If you were given the chance to change one aspect, what would it be?

Be cautious to avoid leading questions, such as “Do you like this?” People might instinctively respond politely, and those responses don’t always yield constructive insights. Instead, encourage them to articulate their observations, their initial actions, and where they feel perplexed.

Pay close attention to their reactions, particularly any signs of hesitation, uncertainty, or unexpected comments. Note any discrepancies between what they verbalise and their likely actions. For example, someone might express positive sentiment about an idea but still show reluctance or difficulty using it. This feedback can be more enlightening than simple praise, as it offers critical insights into how your prototype performs in the real world. Ultimately, the most valuable feedback reveals not just what people think, but how they might realistically interact with your proposition.

Friday: Reflect and Plan for the Next Experiment

Friday offers a crucial opportunity to turn activity into meaningful team learning. Reflection is essential because, without it, a team might run many experiments yet fail to derive valuable organisational knowledge from them. Thus, the final segment of the sprint goes beyond merely reviewing outcomes; it involves a systematic approach to capturing insights gained and determining the next steps for testing.

During this reflective process, the team should engage in a series of guided questions designed to foster deep analysis and consideration:

What did we initially expect to occur?

Reflect on the hypotheses that guided the experiment’s design. Consider the assumptions made and the goals set before the experiment began.

What actually transpired?

Review the results and activities that unfolded during the experiment, paying close attention to the discrepancies between expectations and outcomes.

What evidence did we gather?

Compile and examine the data collected throughout the experiment. This can include quantitative measurements, qualitative feedback, or observational insights.

What aspects of the experiment took us by surprise?

Identify unexpected results or observations that could indicate underlying issues or new opportunities.

Which assumptions have become weaker or stronger based on our findings?

Assess the validity of the initial assumptions in light of the evidence. This can help inform future experiments and decision-making.

What actions should we cease, initiate, continue, simplify, or explore further?

Create a list of actionable items based on the findings. This list will guide what changes or new directions to pursue moving forward.

What is the smallest next step we can implement?

Identify a manageable, low-risk action that can be taken to test a new idea or hypothesis without overcommitting resources.

Once the team has generated these insights, it must formulate a “next-step bet.” A bet is a clear, well-defined, and testable proposition regarding what the team believes is valuable to attempt next. It commits the team to learning through action, not just hopeful assertion.

For example, the team might conclude that, based on their reflections, “We believe that new customers will complete their first task more quickly if we replace our long, detailed welcome email with a simplified one-page checklist and follow it up with a brief message.” Next, they could trial this approach with five new customers next week, carefully monitoring where they face challenges during the process.

It’s crucial to note that making a bet does not guarantee success; instead, it shows a team’s dedication to learning from experience and adjusting based on what they learn with each experimental iteration. This mindset promotes continuous improvement and Innovation within the organisation.

The Rules That Make It Work

To ensure a sprint’s success, teams must follow several foundational rules that streamline the process and amplify results.

1. Prioritise Clarity Over Speed: The purpose of a five-day sprint is not to accelerate the workload but to build the clearest possible understanding of the challenge at hand. Teams must remember that the objective is not to churn out deliverables quickly but to produce valuable insights from focused inquiry. When teams rush through experiments without a well-defined objective, they often end up in a haze of confusion and lose sight of the primary goals. In contrast, even a small-scale, meticulously structured experiment can lead to meaningful learning and breakthroughs. Therefore, teams should dedicate time to clarify their questions and objectives, ensuring that they remain the central focus throughout the sprint.
2. Treat Past Innovation Attempts as Valuable Data: Throughout the journey of Innovation, many teams have encountered roadblocks, facing setbacks with new ideas that seemed promising but ultimately did not yield the desired outcomes. It is vital to shift the perspective on these past endeavours; they should not be viewed merely as failures or indicators that Innovation is prohibitively challenging. Instead, teams should analyse what each previous attempt can teach them. Consider factors such as timing—were they trying to introduce a solution in a market that wasn’t ready? Did they misidentify the target audience, or was their understanding of the problem incomplete? Additionally, did the experiment’s scale exceed their capacity to manage it effectively? By viewing past initiatives as a source of insight rather than mere success or failure, teams can glean critical information to inform and improve future tests.
3. Tighten Feedback Loops: Delays in feedback can lead teams down paths built on false assumptions, further complicating progress. To combat this, it’s imperative to seek feedback as early as possible, in manageable doses, and specifically from individuals who are directly connected to the core issue being addressed. A brief discussion on a Thursday can save countless hours of misguided effort later in the sprint by aligning the team’s direction with stakeholders’ actual needs and expectations. Furthermore, prompt feedback strengthens the connection between teams and the people they aim to serve, leading to a more adaptive and responsive approach. Rather than getting lost in lengthy debates about customer preferences or stakeholder needs, teams can run small-scale tests and engage directly with their audience for real-time insights and validation.

By instilling these principles into their sprint methodology, teams can strengthen their capacity for Innovation and gain a deeper understanding of their objectives, ultimately delivering more impactful, effective outcomes.

The Key Outputs of a Sprint

Each sprint is designed to produce two essential, practical outputs that drive our learning and experimentation forward.

One-Page Learning Memo

The first output is a concise one-page learning memo. This document serves as a straightforward record of the hypotheses we tested and the insights we gained during the sprint. It doesn’t need to follow a formal structure or be overly elaborate; its value lies in encapsulating and sharing our learning in a clear, accessible format.

A robust learning memo should cover several crucial elements:

• The Question We Explored: A clear statement of the central question that guided our testing. This sets the context for the learning we derived.
• The Assumption We Tested: An articulation of the underlying belief we were examining. This is key in understanding what we hoped to validate or disprove.
• The Small Prototype or Action We Created: A description of the tangible small-scale solution or initiative we developed as part of our exploration. This may include mockups, materials, or processes designed to test our assumption.
• Who We Spoke With or What Evidence We Gathered: Information about the stakeholders or test subjects we engaged with, alongside any qualitative or quantitative data collected during the sprint.
• What Happened: A summary of the outcomes of our testing. Include both successes and challenges encountered during the process.
• What Surprised Us: Insights into unexpected results or learnings that emerged from the sprint. This reflects the nuanced nature of user interaction and behaviour.
• What We Learned: A reflective account of the key takeaways from the experiment, summarising how the results inform our understanding of the initial question and assumptions.
• What We Will Do Next: A forward-looking statement outlining the next steps based on our findings. This could involve further testing, prototype adjustments, or entirely new avenues of inquiry.

Example of a One-Page Learning Memo

• Question: Would a one-page onboarding checklist help new customers take their first action more confidently?
• Assumption: Customers feel overwhelmed by our current lengthy welcome email.
• Prototype: A simplified, one-page checklist detailing three clear initial steps for new users.
• Feedback: Insights indicated that one new customer quickly grasped the checklist but requested a more explicit support contact option for additional questions.
• Learning: Streamlined information appears beneficial; however, users still need a clear way to seek support
• Next Step: Conduct a revised test of the checklist with five new customers the following week and measure whether they complete their first action within 48 hours.

Next-Step Bet

The second output is what we call the next-step bet. This component is crucial as it ensures that the momentum of experimentation continues beyond the week’s end. The next-step bet prevents the reflections and insights gathered on Friday from becoming a terminal point in our learning cycle. Instead, it encourages us to devise another small, informed test based on the previous sprint’s discoveries.

In essence, this structure fosters a continuous improvement approach, where each learning cycle naturally transitions into the next phase of exploration, allowing us to build on previous insights while keeping the pace of Innovation brisk and responsive to user needs.

The Manager’s Role in Fostering Innovation

In any organisation, managers play a crucial role in shaping an environment conducive to Innovation. They are pivotal in ensuring that small experiments are not only safe but also meaningful and repeatable. Importantly, their responsibility is not to scrutinise every detail or require absolute certainty before authorising an experiment. Instead, they should focus on supporting their teams as they explore, learn, and test ideas responsibly.

Three Key Supports a Manager Provides During Sprints

Removing Blockers: One of a manager’s primary functions is to eliminate barriers that impede progress. Teams engaged in experimentation often need access to various resources, whether that’s direct contact with a customer, a few hours of focused time, vital information, simple tools, or the authority to trial a new approach. When managers proactively remove these obstacles, they enable teams to run experiments without unnecessary delays. If a lengthy approval process hinders each small experiment, the team may revert to familiar routines, stifling creativity and experimentation.

Celebrating Learning Opportunities: Managers should celebrate not just successful outcomes, but the learning that happens throughout the experimentation process. If team members feel judged solely on the immediate success of their ideas, they may gravitate toward safe, predictable projects rather than exploring innovative solutions. Managers can foster a more open-minded environment by acknowledging thoughtful questions, sensible testing approaches, honest reflections, and useful insights gleaned during the process. By focusing on the question, “What did we learn?” rather than “Did it work?”, they encourage a culture of exploration and continuous improvement.

Funding the Next Small Test: Supporting experimentation doesn’t always mean allocating substantial financial resources; instead, it might involve dedicating a small amount of team time for deep focus, granting access to a relevant customer group, or sanctioning a modest trial budget for new initiatives. The core idea is to maintain momentum for learning and Innovation while keeping the costs and risks of change low. By investing in small tests, managers can help sustain a culture of continuous experimentation.

When managers actively support small-scale experiments, Innovation becomes less reliant on individual confidence or sporadic bursts of creativity. Instead, it becomes part of the team’s operational routine, reinforcing a consistent approach to improvement and exploration.

A Practical Example of the Innovation Process

Consider a scenario where a team recognises that their weekly staff update is excessively lengthy and often overlooked. Rather than investing months into redesigning the entire internal communication system, the team opts for a more nimble approach by conducting a 5-Day Innovation Sprint.

• Monday: The team asks, “Would a more concise weekly update with a focus on three priorities enhance staff engagement?”
• Tuesday: They draft a preliminary version of the update condensed into a one-page format, organised under three clear headings: “What matters this week,” “What is changing,” and “What actions are needed.”
• Wednesday: To gather insights, the team researches how other organisations utilise short newsletters, visual snapshots, or brief video messages. They adopt the strategy of leading with one clear call to action based on their findings.
• Thursday: The team shares the draft with a selected staff member and asks for feedback on its clarity, impact, and anything that may seem superfluous. The staff member suggests that while the shorter format is effective, adding a deadline for each action would improve usability.
• Friday: Leveraging the feedback, the team documents what they have learned. It formulates their next hypothesis: “We believe that staff engagement will increase if each update focuses on no more than three priorities, with each requested action accompanied by a clear deadline.” They plan to test this new format with one department the following week and measure response rates to validate their assumptions.

This example illustrates Innovation at a meaningful scale. The team has not committed to sweeping changes but has moved beyond conversations, gathering evidence to inform next steps.

Take Action: Run Your Sprint Next Week

You do not need a comprehensive or polished innovation program to get started. All you need is one genuine question that matters, a small prototype to test, a fresh idea from external sources, an open and honest conversation, and a clear plan for your next experiment.

The 5-Day Innovation Sprint is a practical framework for turning curiosity into actionable insights. It reduces the fear of failure by keeping tests small, clarifying what you’ve learned, and allowing flexibility in subsequent steps. Over time, these iterative cycles help build a team that is more perceptive, confident, adaptable, and willing to optimise its working methods.

Prepare to implement the 5-Day Innovation Sprint with your team next week. Start with one significant question, design a test manageable within that timeframe, listen attentively to feedback from reality, and use the lessons learned by Friday to inform a smarter, more strategic next move.

This Post is 12/20. Tomorrow’s post will be: Decision Architecture: Making Resource Allocation Visible