The Lightweight Creation Sprint: From Opportunity to Testable Proposal in Two to Four Weeks

Between the alignment workshop and the decision workshop, teams have a defined period — typically two to four weeks — to take a Big Opportunity and develop it into a concrete, testable proposal. The process is deliberately lean. Most team members are running this work alongside existing responsibilities, not as a dedicated sprint.

The goal is not a polished design. It is a specific output: an articulation of the problem, a proposed direction, an estimated impact, and a plan for the smallest possible experiment.

The Six-Step Process

Step 1: Rapid Ideation Begin with divergent thinking — Crazy 8s or an equivalent fast-sketch exercise that generates quantity before quality. The rule is simple: fill the space with options before evaluating any of them. This step exists to prevent the team from anchoring immediately on the first plausible idea.

Step 2: Shortlist and Flesh Out Select one or two ideas and develop them enough to evaluate: what are the key features, what moments in the customer journey does this affect, what impact do you expect on the experience score, and what are the early risks that could make this fail?

Step 3: Feasibility Check A short (fifteen-minute) conversation with development or operations to answer: what is technically straightforward, what is hard, what is unknown, and what blockers exist? This check happens early, while the concept is still flexible, not after the team has invested weeks in a direction that turns out to be blocked.

Step 4: Validate Against "What Needs to Be True" Check the proposal against the management gate criteria from the alignment workshop. Does the expected impact meet the threshold? Does the resource requirement stay within the constraint? Does the timeline fit the planning cycle? A proposal that fails these checks is not a failed idea — it needs to be reshaped or deferred to a future cycle.

Step 5: Define the Test Plan Before any full implementation, define the smallest possible experiment that could validate or invalidate the core assumption. What is the minimal version of this solution that could be shown to customers? How will its success be measured? What result would confirm the assumption, and what would refute it?

Step 6: Draft the Implementation Path If the test succeeds, what comes next? Outline the required teams, rough timeline, main risks, and dependency notes. This is not a full project plan — it is a sketch of the scale of commitment required if the test produces positive results.

"This is not a full design sprint, but a lightweight, sprint-inspired process aimed at multiplying the potential of several small initiatives by blending them into a coherent Big Solution."

What the Service Designer Offers During This Period

The service designer's role in the creation period is support, not direction. Teams own their Big Solutions. The designer offers:

Sparring sessions: Weekly thirty-to-forty-five minute check-ins for teams to pressure-test their thinking, surface blind spots, and ensure alignment with the journey insights that motivated the work.

Templates: Simple structured formats — Problem → Hypothesis → Test → Evidence → Next Step — that give all teams comparable outputs for the decision workshop, without creating bureaucratic overhead.

Fast-track to insights: When a team starts re-researching a problem that was already addressed in discovery, the designer redirects them to the relevant pains, needs, and pressures already on the map. This prevents the common waste of teams reinventing research that was done six weeks earlier.

Feasibility reality checks: Short conversations with technical or operational colleagues to surface blockers before teams invest too heavily in directions that cannot be implemented.