Download

Policy and operations

Find the gap before an auditor, or a customer, does.

Policies and procedures only work if people can follow them. Subjourney sends simulated staff and customers through your policies step by step, and shows you exactly which clause they couldn't act on.

Run your first policy
  • Policy owners who need their policy to be followable, not just defensible.
  • Operations leads turning policy into procedures that frontline teams can run.
  • Risk and compliance teams who'd rather find the gap in review than in an incident.
  • Learning and enablement teams writing the guides staff actually work from.

“It's in the policy” isn't the same as “it works”.

Your policies were written carefully, reviewed by legal and signed off. Then they meet a real situation: an exception nobody listed, a term defined two ways, a step that assumes a system people don't have access to.

That's when policy turns into a judgement call made under pressure, differently by every person who makes it. Inconsistent outcomes, avoidable escalations, and audit findings all start there.

What a run catches

  • Missing

    The undefined exception.

    The refund policy covers 30 days and says nothing about day 31.

  • Ambiguous

    The term used two ways.

    “Eligible customer” means one thing in section 2 and another in the appendix.

  • Dead end

    The impossible step.

    The procedure asks frontline staff to approve something only a manager's system role allows.

  • Contradictory

    The cross-document conflict.

    The SOP and the customer-facing terms promise different timeframes.

The policy, and everything that puts it into practice.

  • Policies and standards, internal or customer-facing.
  • SOPs and work instructions for the teams who apply them.
  • Decision trees and escalation matrices.
  • Customer terms, letters and notices.
  • Training guides and onboarding material for staff.

Approved isn't the same as tested.

  • Policy review

    Today
    Legal and stakeholder sign-off on the wording
    With Subjourney
    Staff and customer personas try to follow it

  • Exceptions

    Today
    Handled case by case, inconsistently
    With Subjourney
    Surfaced before launch and written in

  • Policy vs procedure

    Today
    Drift apart quietly over time
    With Subjourney
    Conflicts flagged by clause on every run

  • Changes

    Today
    Updated doc, unknown knock-on effects
    With Subjourney
    Re-run shows what the change broke

  • Evidence

    Today
    A sign-off record
    With Subjourney
    A sign-off record, plus runs showing it was walked

Through the policy's whole life.

  1. 1Import the policy, plus the SOPs and scripts that put it into practice.
  2. 2Run personas on both sides: the customer it applies to and the staff member applying it.
  3. 3Get every stall tied to the clause responsible, or the clause that's missing.
  4. 4Fix the wording before the policy goes live, or before the next review cycle.
  5. 5Keep a record of runs as evidence the policy was tested, not just approved.

In practice

An operations lead runs an updated hardship policy before rollout. A frontline staff persona stalls on the first case: the policy says to “assess eligibility” but never says against what. A customer persona stalls later, when the confirmation letter references a review period the policy doesn't define. Two clauses rewritten, re-run clean, rollout on schedule.

A run, step by step

One policy, both sides of the counter.

  1. 01Import.

    The ops lead brings the updated hardship policy, the frontline SOP for hardship requests, and the customer confirmation letter template.

  2. 02Model.

    Subjourney builds the journey.

    Customer
    Request help
    Provide details
    Receive decision
    Arrangement starts
    ReviewFlagged
    Staff
    Receive request
    Assess eligibility
    Approve or escalate
    Send confirmation

    It flags that Review has no owner on the staff side.

  3. 03Run.

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

    New frontline staffHardship officer

    Week one, following the procedure.

    Motivation
    Handle a first hardship call by the book, without escalating it.
    Frustration
    A procedure that says “assess eligibility” but never against what.
    Need
    The criteria, written down, at the step that asks for them.
    • Age23
    • Income$34,000
    • EducationBachelors Degree
    • EmploymentEarly Career
    • Communication styleCasual
    • Social engagementActive Contributor
    • Risk appetiteRisk-Tolerant
    • Eco awarenessEco-Conscious
    • Work-life balance9 to 5
    • Brand loyaltyNone
    • Price sensitivityValue Oriented
    • Tech adoptionEarly Adopter
    • Tech literacyAdvanced

  4. 04Findings.

    AmbiguousStalled at: Assess eligibility

    New frontline staff member

    The policy says to “assess eligibility” (Section 2.3) but doesn't say against which criteria. The SOP points back to the policy.

    Open in sourceSend to owner
    MissingStalled at: Receive decision

    Customer just above the income threshold

    No clause covers discretion near the threshold. Staff have no basis to approve or decline.

    Open in sourceSend to owner
    ContradictoryStalled at: Review

    Customer three months into an arrangement

    The letter promises a review “after 90 days”. The policy never defines a review period, and the SOP has no review step.

    Open in sourceSend to owner

  5. 05Fix and re-run.

    Two clauses rewritten, one added, and a review step added to the SOP. Re-run: all four personas reach the outcome.

    Rollout on schedule, with fewer judgement calls left to the frontline.

Personas to start with

Run both sides of the policy.

  • The new frontline staff member.Week one, following the procedure to the letter.
  • The experienced staff member.Knows the shortcuts. Does the policy still hold?
  • The straightforward customer.Clearly in scope, should sail through.
  • The edge-case customer.Just outside a threshold, or in two categories at once.
  • The escalation.The case that has to go up the chain. Does the policy say where?

Questions

Is this a compliance tool?

No. It doesn't tell you whether a policy meets regulation. It tells you whether people can follow it, which is where most policy failures actually happen.

Our policies are long and formal. Does that matter?

No. Subjourney reads them as written. Long, formal policies are often where the most stalls hide.

Can we run policy and procedure together?

Yes, and you should. Most gaps sit between the policy and the SOP that's meant to put it into practice.

Run the policy before people have to.

Download Subjourney