Service design that gets implemented

Salt Grain is a service design agency Australia teams hire when customer experience has outgrown how the organisation is set up. Mid-market operators, agencies and government services teams who feel the friction after the customer shows up.

Fit signals:

• Demand is healthy; delivery and support create the pain
• Multiple functions touch the same customer; nobody owns the whole journey
• Leadership wants better CX but the backstage is spreadsheet hell
• You’ve had journey maps before — nothing changed in the systems

Service design that stops at a workshop is decoration. Real friction lives in handoffs, policies, queues, tools and unclear ownership.

We tackle:

• Broken end-to-end journeys (enquire → fulfil → support)
• Frontstage promises the backstage can’t keep
• Siloed teams optimising local metrics
• “CX initiatives” with no path into process and technology change

We redesign frontstage and backstage together — then implement.

Specialist CX boutiques often stop at insight. System integrators skip the human journey. We sit in the gap.

• Strategy-linked — service changes tied to business outcomes and trade-offs
• Journey + operating model — blueprints that name owners and policies, not only personas
• Systems follow design — ERP, CRM, portals, automation and web are configured to the service, not the other way around
• Implementation partner mindset — we stay through pilots and rollout via project delivery

Design → operate → measure. That is the wedge.

• Listen — Research with customers and staff. Current-state journeys and failure points. No generic persona packs.
• Shape — Future-state blueprint, service principles, prioritised moments that matter, change implications.
• Build — Prototypes, process redesign, and the tech/web changes required. Pilot before big-bang where it reduces risk.
• Deliver — Rollout, training, measurement. Adjust with real volume — not a launch party and a forgotten KPI.

A charming frontstage with a chaotic backstage trains customers to distrust you. We insist on designing both:

• Frontstage — channels, scripts, digital steps, moments of truth
• Backstage — queues, handoffs, policies, tools, SLAs, ownership

Blueprints name the systems that must change — CRM stages, ERP order flows, knowledge bases, portals — so technology solutions and web & digital experience are not separate science projects.

We pilot where risk is high. We measure after rollout. If a KPI was vanity, we replace it. Service design without operational metrics is just storytelling.

Typical artefacts we leave behind are useful, not decorative: research synthesis leadership will read, a service blueprint with owners, a prioritised change backlog, and a measurement set tied to real journeys.

Then the work moves into delivery — process change, training, and systems configuration. That is why we sit next to project delivery and technology partners instead of ending at a playback workshop.

Australian organisations often juggle legacy policy, fragmented tooling and thin change capacity. We design for that constraint set. Beautiful journeys that need a headcount you do not have are not honest design.

We still run workshops — timed, decision-oriented, with the right people in the room. The difference is what happens next week: owners, backlog, and build. If your last “service design” ended as a mural photo in Slack, you have met the problem we exist to fix.

Public-sector-adjacent and regulated environments get extra attention on policy constraints early, so we do not design a journey your organisation cannot lawfully or practically run.