Strategy
Early intervention
Make it easier to seek help early for emerging anxiety and depression.
Internal concept walkthrough
A connected mental health system.
A safe, high-level concept for bringing digital access, human support, peer community, telehealth, referral pathways, outcomes measurement and service governance into one coordinated stepped-care model.
Early intervention strategy
Integrated stepped care
Human-supported digital service
Shared governance
Core story
Any entry point
Shared intake
Least intensive safe support
Step up or down
Measure and improve
Model
Integrated stepped care
Match people to the least intensive safe support and adjust as needs change.
Enabler
Service orchestration
Connect channels, people, data, governance and partners around one pathway.
01 · The opportunity
People experience pathways, not org charts.
The concept starts from a simple proposition: a person should be able to enter through web, phone, chat, forums or telehealth and still experience one connected service pathway.
The shift is from separate products and channels toward a governed early-intervention pathway that can assess need, route safely, support self-management, escalate when appropriate, and learn from outcomes over time.
From
Channel-led service delivery
Web, phone, chat, forums, telehealth and digital programs risk behaving as separate entry points with different operating rules.
To
Pathway-led service delivery
Each channel becomes part of one service journey with shared intake, routing, support, escalation and follow-up.
So that
The person does less navigation
The organisation holds the complexity of the system, rather than asking the person to work out where they fit.
02 · Future role
A national early-intervention pathway operator.
The future role is broader than operating digital channels. It is to coordinate access, safety, trust, service quality and system connection around an integrated stepped-care model.
Framing statement
Early Intervention is the strategy. Integrated stepped care is the operating model.
The app demonstrates how a national mental health charity could move from channel-led delivery to one connected, governed pathway across digital, human, peer and clinical support.
Role 01
Trusted front door
Simple, stigma-light access through multiple channels, with a consistent service promise behind each door.
Role 02
Pathway coordinator
Shared intake, routing, escalation and follow-up so people can move between levels of support safely.
Role 03
Trust and quality steward
Governance, measurement, assurance and lived-experience input embedded into service design and change.
03 · Stepped care
One pathway, multiple levels of support.
The service model should support self-management, brief support, guided low-intensity care, telehealth, and escalation or referral — without making the person restart at every step.
Service blueprint
The operating logic behind the person journey.
A simple blueprint connects user actions, frontstage service, backstage work, support systems and governance controls.
04 · Person journey
Design from need and pathway, not from incumbent channel.
The journeys are the centrepiece of the concept. They show how one connected service model can respond differently to different needs while staying aligned to stepped care, quality controls and a coherent technology backbone.
One front door
Least intensive safe response first
Review and step-up when needed
Journey demonstration
Select a person journey.
Lead with the lived pathway, then show how the service model, governance and technology line up behind it.
Journey persona
Select a journey
Journey summary appears here.
Pathway through the service
Each step shows how the person moves across access, assessment, matching, support and review without re-entering a fragmented system.
Designed outcome
What this proves
Journey storyboard
Three connected lenses for the same journey.
Use the storyboard to move from lived experience to operating logic and then to the enabling platform. Related architecture, governance and roadmap items are highlighted below.
Service model intersection
How the operating model shows up for the person.
The selected journey explains how shared intake, navigation, intervention and escalation work as one model.
Care framework alignment
Why the pathway fits stepped care and quality expectations.
The selected journey explains how least intensive safe support, review and step-up logic operate in practice.
Enabling technology
The platform that makes the experience feel connected.
The selected journey explains the orchestration, data and workflow capabilities needed behind the scenes.
Follow the technology storyTraceability
The selected storyboard lens highlights the platform capabilities, governance controls and roadmap moves it depends on.
05 · Operating model
Shift from channel ownership to capability ownership.
The outsource/insource decision should follow the capability model: what must the organisation own to safely operate the pathway, and what can be delivered through partners?
Operating model question
Which capabilities must be owned internally to protect trust, safety and pathway integrity?
Specialised delivery can still be internal, outsourced or partner-led. The critical distinction is whether the organisation keeps control over service definitions, pathway rules, governance, data standards, quality expectations and escalation logic.
06 · Technology backbone
Technology enables the pathway; it is not the pathway.
The target platform should orchestrate access, screening, routing, support, telehealth, community safety, referrals, outcomes and partner integration.
Capability map
Reusable platform capabilities.
Journey selections highlight the capabilities required behind the scenes.
07 · Governance and assurance
A connected pathway requires connected governance.
Clinical safety, community moderation, digital design, data use, privacy, cyber, service quality and partner performance need to be governed together.
08 · Transformation pathway
Start with model, governance and sequencing — not just technology replacement.
The roadmap is deliberately conceptual: align first, design foundations second, pilot integrated pathways third, then scale based on evidence.
09 · Discussion prompts
The app should create alignment, not pretend to be the final answer.
Use these prompts to support a mixed internal group discussion without forcing premature implementation decisions.
Strategic
What future role are we prepared to own?
Trusted front door, pathway operator, service provider, partner coordinator, evaluation engine — or some combination?
Operating model
What must be internally controlled?
Model of care, risk logic, service definitions, data standards, partner assurance, community safety and outcomes are likely ownership anchors.
Technology
What platform capabilities are genuinely shared?
Intake, identity, consent, workflow, referral, analytics and governance evidence should be treated as common services, not channel add-ons.
Source basis
Use as an internal concept artefact.
This walkthrough is based on the strategic framing paper, service catalogue, operating model notes and the current demo application repository. External references should be formalised before using the app as a published or board-pack artefact.