LGSDN

1. Start with a clear hypothesis, not a finished solution
 A prototype should test a specific assumption

(For example, “proactive outreach increases engagement” or “multidisciplinary triage improves outcomes”). Being explicit about what you are testing helps teams learn faster and prevents the pilot from becoming an unfocused service rollout.

2. Prototype the operating model, not just the touchpoints

Effective service prototypes test roles, workflows, governance, decision-making, and collaboration patterns, not only resident-facing interactions. Many implementation risks sit in operational details rather than user journeys.

3. Design the conditions that allow the prototype to work

Pilots succeed when enabling conditions are deliberately created: time for collaboration, leadership permission to experiment, flexibility in performance measures, and clear escalation routes. Without these, the prototype tests organisational constraints rather than the intended service model.

4. Capture learning continuously, not only at the end

Set up lightweight mechanisms (regular reflection sessions, simple learning logs, operational retrospectives) to capture insights while the prototype is running. This enables iterative adjustment and ensures that implementation learning is not lost.

5. Expect partial evidence and combine data types

Early-stage pilots often produce small quantitative samples, so combining quantitative indicators with qualitative insight (staff experience, resident stories, operational observations) gives a more complete understanding of impact.

6. Design for iteration from the start

Assume that the first version of the prototype will need adjustment. Build feedback loops into delivery so that processes, scripts, workflows, and collaboration practices can evolve as learning emerges.

7. Plan early for scaling or transition

Even at the start of a prototype, consider what would need to change if the service were expanded: governance, funding, staffing models, systems, and ownership. Early thinking about sustainability prevents pilots from stalling after initial success.

8. Make the prototype visible across the organisation

Communicating what the prototype is testing, what is being learned, and how colleagues can engage helps build legitimacy, attract collaborators, and prepare the organisation for potential adoption.

9. Protect space for professional judgement

Many service innovations depend on frontline discretion and relational work. Ensure the prototype allows staff sufficient autonomy to test new approaches rather than constraining them within existing procedural rules.

10. Treat the prototype as organisational learning infrastructure

The most valuable output of a service prototype is often not the service itself but the insight it generates about how the organisation operates, where barriers exist, and what systemic changes are needed for long-term implementation.