Service 02

Change & operations

Help work move more smoothly — from planning and capacity through handovers, delivery and improvement.

Brand illustration of an office with gold data lines showing movement and change.
YJ ConsultingChange & operations

Typical areas of support

How can YJ Consulting improve business operations?

We look at how demand, capacity, information, handovers and delivery connect. That helps the business improve the whole flow instead of shifting a problem from one team to another.

Useful when: Growth has outpaced the way the business operates, too much depends on individual knowledge, or work keeps getting stuck between people or teams.

Select an area to explore how we could help.

Operating model and workflow mapping

Find the friction between a customer request and a completed job. When people are busy but work is still waiting, the problem may sit between teams rather than within any one role.

How YJ Consulting could help

YJ Consulting can work with your team to trace a real job from enquiry through delivery, invoicing and follow-up. We can compare the documented process with everyday practice, identify repeated entry, unclear decisions and avoidable queues, and agree which bottleneck deserves attention first.

What we could develop together

  • A current-state map showing owners, systems, decisions and handovers.
  • A prioritised improvement plan, with a proposed future workflow and measures such as elapsed time, rework and overdue work.
  • A practical view of what can be simplified now, and what would need better data or specialist implementation.

Research into practice

An emerging method: follow connected work, not isolated tasks

Casciani and colleagues (2026) explore conversational analysis of object-centric event logs: records that connect several business objects, such as orders and invoices. Their research framework was evaluated using a SAP procure-to-pay benchmark, not a general trial of SME performance.

Our practical application would start with a data-readiness review: can the same job be traced across your systems? Where reliable records exist, we can help scope evidence-led analysis. Where they do not, interviews and a sample of real jobs may be the better starting point. AI-generated explanations would need checking against source records; new software is not the default answer.

Where does work slow down in your business?

Discuss your workflow

Change planning and implementation support

Turn a good idea into a change people can actually use. A new system or process needs more than a launch date: it needs a clear purpose, realistic capacity and a way to learn what is working.

How YJ Consulting could help

YJ Consulting can help define the problem, identify the people affected and break implementation into manageable stages. Together, we can map dependencies, assign decision owners, prepare communications and training, and create a feedback rhythm that brings practical concerns into the plan early.

What we could develop together

  • A scoped change roadmap with responsibilities, dependencies and decision points.
  • A pilot plan with baseline measures, success criteria and a clear decision to adapt, stop or expand.
  • Staff-facing guidance, an issues log and an adoption review that considers workload as well as uptake.

Research into practice

A more useful rollout: test the workflow, not just the tool

Dillon and colleagues' 2025 working paper reports a randomised field experiment across 66 firms. AI access changed some individual work patterns, but the researchers did not detect a change in the quantity or composition of tasks. The findings concern a particular workplace tool and context, not a promise of organisation-wide transformation.

Our inference is that adoption should be tested alongside the work design. We could help one team trial a revised process, record quality and turnaround alongside staff feedback, and compare the results with a baseline. Any AI pilot would require agreed data boundaries and review responsibilities. The next decision should follow the evidence, not simply the number of licences activated.

Have a change in mind, but need a workable first step?

Plan a focused change

Roles, controls and handover documentation

Make the next step clear, even when the usual person is away. Reliable operations depend on knowing who owns the work, what a complete handover includes and when an exception needs attention.

How YJ Consulting could help

YJ Consulting can help turn informal know-how into proportionate, usable documentation. We can clarify who prepares, checks and approves work; define the information needed at each transfer; and walk through real scenarios with the people who will use the process.

What we could develop together

  • A responsibility and decision-rights map, including escalation routes and cover arrangements.
  • Short operating guides and handover checklists with clear acceptance criteria and exception handling.
  • A document register with named owners, version dates and review triggers, supported by a practical walkthrough.

Research into practice

Design the human check, rather than assuming it works

Vaccaro, Almaatouq and Malone's 2024 meta-analysis found that human-AI combinations did not, on average, outperform whichever performed better alone; results varied by task. NIST's 2024 generative-AI guidance also emphasises defined responsibilities and oversight. It is voluntary US guidance, not a New Zealand legal requirement or certification.

For an AI-assisted or automated step, we could help specify what must be checked, by whom, against which evidence and before which action. A rehearsal using an incomplete job, an absent approver or a disputed output can reveal gaps that a flowchart misses. These are proposed design choices, not a claim that a checklist guarantees accuracy or compliance.

Which handover depends too much on one person?

Strengthen your handovers

The right approach depends on your priorities, systems and available evidence. Scope and deliverables would be agreed before work begins.

The supply-chain lens

Follow the work from demand to learning.

Supply-chain thinking is useful beyond physical products. It makes the full chain of commitments, information, decisions and delivery visible.

  1. 01

    Demand

    Customer needs, service commitments, pipeline and uncertainty.

  2. 02

    Plan

    Priorities, capacity, dependencies and the chosen operating scenario.

  3. 03

    Source

    People, suppliers, information, approvals and other inputs.

  4. 04

    Deliver

    Handoffs, flow, quality, exceptions and customer outcomes.

  5. 05

    Learn

    Measures, feedback, decision records and the next improvement.

Five practical methods

Improve the way work moves through the business.

We choose the methods that fit the business. Each one produces something useful — a map, decision, handover guide or working routine — with a clear owner.

  1. 01

    Map the end-to-end flow

    Follow work from the first demand signal to delivery and learning. This exposes queues, rework and local fixes that move pressure elsewhere.

    Current process map · problems to fix · named owner
  2. 02

    Reconcile demand and capacity

    Bring customer commitments, pipeline, people, suppliers, backlog and change activity into one shared view.

    Demand–capacity view · scenarios · decisions
  3. 03

    Work on the constraint

    Prioritise the point limiting the whole system, rather than asking every function to optimise its own activity at once.

    Constraint statement · focused test · measures
  4. 04

    Design the handover

    Define the trigger, entry criteria, receiving owner, status, exception path and feedback loop where work changes hands.

    Handover standard · decision rights · escalation path
  5. 05

    Set the operating rhythm

    Use a simple, S&OP-inspired planning meeting to review what changed, choose trade-offs and record when decisions will be revisited.

    Operating review · action log · review date

How the engagement works

Map. Decide. Test. Review.

We build a shared view of how work moves now, choose a focused change, test it and learn from what happens.

  1. 01

    Map demand and current flow

    Start with the customer promise, then trace how work, information and decisions move through the real operating system.

  2. 02

    Find the constraint

    Compare demand with capacity and evidence to identify the point currently limiting end-to-end performance.

  3. 03

    Test a focused change

    Define the planned handover, owner, measures and exception path, then test it with representative work.

  4. 04

    Make the change stick

    Record decisions, monitor adoption and revisit the plan as demand, supply or operating conditions change.

Start a conversation

Tell us what you are working through. We will help identify a useful first step.

Get in touch