Download

Service and CX design

Walk the journey before your customers do.

Your blueprint shows the journey you designed. Subjourney shows the one people actually get, by sending simulated personas through every channel, handoff and policy your service depends on.

Run your first journey
  • Service designers who need the blueprint to match what's actually written down at every touchpoint.
  • CX leads who want to catch the friction before it turns into complaints and churn.
  • Journey owners responsible for an end-to-end experience they don't fully control.
  • Research teams who want their personas used, not just presented.

The map is not the service.

The journey map looks clean on the wall. But the real service lives in a dozen other places: the website copy, the call-centre script, the eligibility policy, the email templates. Nobody has walked all of them together.

So the first time the full journey gets tested end to end is when a customer tries it. And the first you hear of it is a complaint.

What a run catches

  • Missing

    The broken handoff.

    The web flow says “we'll call you within two days”. The contact-centre SOP has no step for it.

  • Missing

    The persona you didn't design for.

    The carer applying on someone else's behalf, who the form assumes doesn't exist.

  • Contradictory

    The channel contradiction.

    The app says one thing, the policy says another, and the customer can't tell which to trust.

  • Dead end

    The dead end.

    A path where the only next step is “contact us”, and contacting us leads back to the start.

Everything behind every touchpoint.

  • Service blueprints and journey maps.
  • Website and app copy for each step customers see.
  • Contact-centre scripts and knowledge articles.
  • Eligibility rules, policies and terms the service applies.
  • Email, letter and SMS templates customers receive along the way.

The map shows intent. A run shows what people get.

  • Journey validation

    Today
    Workshops and walkthroughs on the wall
    With Subjourney
    Personas walk every touchpoint against the real docs

  • Edge-case customers

    Today
    Covered if someone in the room remembers them
    With Subjourney
    Run as personas, every time

  • Cross-team handoffs

    Today
    Discovered when a customer falls through
    With Subjourney
    Each broken handoff named, with the doc on each side

  • Research personas

    Today
    Presented once, then shelved
    With Subjourney
    Run against every change to the service

  • After launch

    Today
    Complaints tell you what broke
    With Subjourney
    Re-runs tell you before customers do

A loop, because services keep changing.

  1. 1Bring your blueprint or journey map, plus the docs behind each touchpoint.
  2. 2Run personas from your research: the edge cases, not just the primary user.
  3. 3See every stall pinned to the touchpoint and the document behind it.
  4. 4Take findings to the teams that own each doc, with evidence attached.
  5. 5Re-run after changes, so the service you designed stays the service you deliver.

In practice

A service design team imports a benefits application journey: the web form, the eligibility policy and the call-centre script. A persona who recently changed jobs stalls at income verification. The policy asks for “current income”, the form asks for last year's, and the script tells staff to accept either. Three docs, one fix, found before launch instead of in the complaints log.

A run, step by step

One service, three teams' docs, one hidden conflict.

  1. 01Import.

    The team brings the online application form copy, the eligibility policy, and the contact-centre script for application queries.

  2. 02Model.

    Subjourney builds the journey.

    Apply for support
    Check eligibility
    Start application
    Verify income
    Submit
    Call for statusFlagged
    Decision letter

    It flags that Call for status has no step for applications still in verification.

  3. 03Run.

    Four simulated personas set off. Choose one to see what they want and what gets in their way.

    CarerAuthorised representative

    Applying on behalf of a parent.

    Motivation
    Get Mum's support sorted without taking another day off work.
    Frustration
    Being told only the applicant can speak to the call centre.
    Need
    A way to apply on someone's behalf, said plainly up front.
    • Age52
    • Income$54,000
    • EducationHigh School Diploma
    • EmploymentMid Career
    • Communication styleBusiness Casual
    • Social engagementActive Contributor
    • Risk appetiteSafe
    • Eco awarenessActive Concern
    • Work-life balanceWorking Late
    • Brand loyaltyHabitual
    • Price sensitivityValue Seeker
    • Tech adoptionResistant
    • Tech literacyBasic

  4. 04Findings.

    MissingStalled at: Start application

    Carer applying for a parent

    No doc covers applying on someone else's behalf. The form assumes the applicant is the account holder.

    Open in sourceSend to owner
    ContradictoryStalled at: Verify income

    Changed jobs two months ago

    The policy asks for current income (Section 3.1). The form asks for last financial year. The script tells staff to accept either.

    Open in sourceSend to owner
    Dead endStalled at: Call for status

    Calls mid-way to check progress

    The script covers submitted and decided applications only. In-verification callers have no next step.

    Open in sourceSend to owner

  5. 05Fix and re-run.

    Policy, digital and contact-centre owners each get the finding for their doc. After the fixes, all four personas reach a decision.

    Three teams, three docs, one journey that finally lines up.

Personas to start with

Run the customers your service finds hardest.

  • The primary customer.The journey you designed for, start to finish.
  • The proxy.A carer, parent or advocate acting for someone else.
  • The channel-switcher.Starts online, calls halfway, finishes in person.
  • The changed circumstance.New job, new address, new household, mid-journey.
  • The low-confidence customer.Reads every word literally and takes no shortcuts.

Questions

Does this replace customer research?

No. It makes research go further. Run your research personas against every version of the service, and save real sessions for what only real people can tell you.

Our service spans lots of teams and documents. Can it handle that?

That's where it's most useful. Bring the docs from each team, and a run shows where they don't line up.

Do I need a finished blueprint?

No. Start with the docs behind the service. Subjourney builds the journey from them, and the gaps show you what the blueprint is missing.

How do I share findings with other teams?

Each finding names the step, the persona and the paragraph. Send it to whoever owns that doc, with the evidence attached.

Bring your blueprint. Watch someone walk it.

Download Subjourney