Change management
in five steps.

Visualise

Start with the final state.

Before anything moves, the organisation describes the destination: how the changed work will look, how it will feel to the people inside it, and how it will operate day to day. The end goal is agreed before the route is planned.

Questions we answer

• How will the work look once the change is complete?
• How will it feel for the people doing it every day?
• How will decisions, handoffs and reporting operate in the final state?
• What must the final state protect, and what does success look like from the outside?

Activities

• Final-state design sessions with leadership and the people doing the work
• Walkthroughs of the future process, roles and interactions
• Success measures agreed before the change begins
• Priorities confirmed on what the final state must preserve

Delete

See the work as it is. Remove what does not belong.

Make the current state visible, then retire the steps, approvals, reports and meetings that will not survive into the final state. Automating waste only makes it faster and harder to see.

Questions we answer

• How does this work actually get done, not how is it documented?
• What would stop being missed if it stopped tomorrow?
• Which approvals protect the organisation, and which protect habit?
• What capacity does removal free before any tool arrives?

Activities

• Process and decision mapping with the people doing the work
• Value test on every step, approval and report
• Deletion decisions agreed openly with named owners
• Retiring legacy reporting and duplicate controls

Implement

Change the way work is done.

Introduce the new process, tools and technology support with role clarity, manager capability and honest communication around them.

Questions we answer

• What changes in each specific role, and what stays human?
• Who decides, who oversees and who escalates?
• What is the honest answer on job security?
• What support exists within arm's reach of the work?

Activities

• Role-level change design and practical guidance
• Manager enablement and champion support in each area
• Boundaries, oversight and escalation defined up front
• Staged rollout with visible leadership sponsorship

Optimise

Tune the bond between the organisation and the machine.

Optimisation is where Relationship Intelligence and the Method meet. The organisation and the technology are one running system: people, leadership, culture and ethics on one side, tools, data and automation on the other. We tune the relationship between them so both parts run at the same speed.

Questions we answer

• What kind of bond have people formed with the technology: trust, avoidance or dependence?
• Where is the machine running faster than the people, or the people faster than the machine?
• Is judgement still held by humans where it matters most?
• Which part of the engine is dragging the rest of the system?

Activities

• Relationship Intelligence review of how people and technology work together
• Method reading of every part of the organisation, not one team at a time
• Tuning speed and load so no part of the business is left behind
• Checking power, accountability and ethical boundaries still hold under real use

Feedback loop

The cycle continues.

Evidence from optimisation re-opens the view of the work, so change becomes a standing organisational capability rather than a finished project.

Questions we answer

• What did this cycle teach us about how the work really runs?
• Is feedback safe to give, and visibly used?
• What is the next thing to visualise?
• Who owns the cycle when the engagement ends?

Activities

• Structured listening channels that stay open
• Feeding evidence from Optimise back into Visualise
• Internal ownership handover
• Setting the cadence for the next cycle