Business & Organizational Transformation

If the process is not changed, the agent becomes another system nobody opens on Monday morning. This is the work that determines adoption — and it is the work most projects skip.

Who it is forCIO, CTO, IT and architecture leadership
EngagementProject-based, scoped after assessment
Works withYour existing partners and platform estate

The system works. The organisation does not use it.

Technically sound, deployed correctly, and adopted by nine people out of four hundred. The pilot team champions it; the rest of the organisation has no reason to change how they work, and no clarity on what changes for them.

This is not a training problem. When an agent takes over part of someone's judgement, the organisation has to decide who now owns that judgement, what the escalation path is, how performance is measured, and what happens when the agent is wrong. Those are design decisions, not comms ones.

Who this is for

Three audiences, and what each of them actually needs to know

Transformation executives

Accountable for whether capability changes performance.

Operations and line management

Who must actually adopt the new way of working.

HR, L&D and OD partners

Who turn role redesign into capability.

Risk, legal and audit

Who need the decision rights and evidence to be defensible.

What Origin does

The work, in the order we do it

01

Process redesign

Map the process as it actually runs, including the workarounds people have invented, then redesign it around what the agent can now do. The workarounds are usually where the real process is.

02

Human–AI workflow design

Where the agent stops and a person resumes, what the person is given when they resume, and how much authority they have at that point.

03

Role redesign and human–machine capital

What the role becomes when the routine judgement is automated: what is left, what is new, what training that requires, and how the organisation keeps that capability.

04

Governance and decision rights

Who approves, who is accountable, what is logged, and what the escalation path is. Written down, and enforced in the system rather than in a policy PDF.

05

Adoption and change

The unglamorous part: who has to change, what they are afraid of, what they get, and the sequence that makes the change survivable.

06

Measurement

How you will know it worked — decided before launch, because afterwards everyone agrees the numbers are fine.

Scope and deliverables

Deliverable
01As-is process map including informal workarounds
02Target process and human–AI workflow design
03Role and capability impact assessment
04Governance, decision rights and escalation model
05Adoption and change plan
06Measurement framework agreed before launch
07Execution support through the first operating period

Prerequisites

What we need from you

  • Executive sponsorship with authority to change the process, not only the tooling.
  • Line management genuinely willing to have their process changed.
  • Agreement on what is measured and when it is judged.
  • Honesty about which roles and volumes are genuinely affected.
A practical example

Who owns the judgement now?

An agent drafts, checks and schedules renewal reviews. The account manager's role changes: less assembly of data, more judgement on the exceptions, and a named responsibility for approving what the agent recommends.

That is a role redesign, not a training course. It affects how performance is measured, what happens when the agent's assessment is wrong, and whether the person approving has enough information to decide. If the approval is a rubber stamp, the control is decorative — and everyone in the room knows it.

Composite scenarios drawn from the kinds of constraints we work with. They are not customer case studies and no outcome figures are claimed.

See it working

Demonstrations and method

Boundaries — what we will not claim

These are the limits we hold ourselves to, stated up front so you can hold us to them.

  • We do not deliver a transformation roadmap and leave. The work is not done until the organisation is operating differently.
  • We do not claim a cultural or adoption outcome we cannot influence — we can design the conditions and measure the result.
  • We do not use AI as the justification for a change the organisation had already been avoiding for unrelated reasons, though we will name it if that is what it is.
Next step

Work out whether the organisation will actually change

A conversation with the transformation and operations leadership together is usually the most useful first hour we can spend with you.