Change management
Put a change into practice. See who and what it affects.
Connect the affected processes, owners and instructions. Ask Meridi AI to draft updates, then plan and review the change with your team.
5 processes free. No credit card. Includes 1,000 AI credits for your first 30 days.
The problem
The process changed. The documents didn’t.
A decision in a meeting can affect several teams. Working out which steps, owners and instructions need to change takes time, and an old version can stay in use.
- 10
- planned enterprise changes the average employee went through in 2022, up from two in 2016.Gartner, via Harvard Business Review, 2023
See how the work moves. Four kinds of change, the same tools.
Follow a change from the affected work to updated processes and guidance. Choose an example below.
Operating model
See what it touches
Open the system in the operating model to see its linked processes, departments and people.
Who acts: Your team decides
Meridi AI
Draft the switch
Ask Meridi AI to propose the system replacement and updated steps. Review and apply the changes you accept.
Who acts: Meridi AI helps
Review status
Flag each changed process
Applied changes flag the affected processes for review. Process Home brings them together for their owners to check.
Who acts: Meridi flags it
ProcessesSOPs and documents
Verify and update the SOPs
Owners verify the processes against the new system, then review and update the flagged SOPs so the guidance matches.
Who acts: Your team decides
SOPs and documentsReview status
Attach the policy
Attach the new policy document to the processes it governs. Meridi flags each one for review.
Who acts: Your team decides
Meridi AIProcesses
Draft the new way of working
Ask Meridi AI to propose new steps beside today’s process. Use that proposal to test the handoffs before adopting it.
Who acts: Meridi AI helps
Operating modelMeridi AI
Test the new handoffs
Try the proposed flow on a copy of the operating model. Ask Meridi AI to check the handoffs for gaps and loops.
Who acts: Meridi AI helps
ProcessesSOPs and documents
Adopt it and update the guidance
Update the steps and have the owner verify the process. Review and update the linked SOPs to match.
Who acts: Your team decides
Meridi AIReview status
Find the gaps
Ask Meridi which processes have no owner. Each one is marked Missing owner on Process Home.
Who acts: Meridi AI helps
Stakeholders
Hand over
Hand each process to a named owner or role, and make the responsibilities clear.
Who acts: Your team decides
Review status
Back to review
The ownership change flags the process for review, giving the new owner a clear place to start.
Who acts: Meridi flags it
ProcessesSOPs and documents
Check the work and guidance
New owners check and verify their processes. Review any flagged SOPs and update the people and responsibilities they describe.
Who acts: Your team decides
Project plans
Compare with the original plan
Meridi shows how far each process has moved from the baseline, and flags a plan that outgrows its baseline or its contract. You decide whether to cut scope or revise the baseline.
Who acts: Your team decides
Project plans
Plan the milestones
Set rollout milestones tied to the processes they change, with acceptance criteria for what counts as done.
Who acts: Your team decides
Risks and status
Log risks and decisions
Record risks, issues and decisions against the processes they affect, each with an owner and a due date.
Who acts: Your team decides
Initiatives
Plan the adoption check
On the initiative, name the behavior change, how adoption will be measured and when to review it.
Who acts: Your team decides
Risks and statusMeridi AI
Report progress
Ask Meridi to draft a status update from what changed since the last one, then edit it and post it.
Who acts: Meridi AI helps
Meridi flags recorded changes. Ask Meridi AI for help; review and apply its proposals. Your team updates, approves and verifies the work.
The tools behind it
Explore the tools.
See what each tool contributes and which plan includes it.
Process changes on Meridi Base, $29 a month · Meridi Delivery, $149 a month, adds project plans and milestones
Compare every feature- Base
Review status and change signals
A changed process is flagged for review, and Process Home lists what needs attention.
Explore Processes - Base
Processes and human verification
Compare the proposed process with today’s, adopt the change and have someone with edit access verify it.
Explore Processes - Base
Operating model and systems
See every process, department and person a system touches, and test new handoffs on a copy first.
Explore Operating model - Base
Stakeholders and organization chart
Assign responsibility to a person or a role, without leaving a process unassigned.
Explore Stakeholders - Base
SOPs, documents and action items
SOPs written from changed steps are flagged for their owners, and an update is drafted when you ask.
Explore SOPs and documents - Base
Meridi AI
Shows what a process touches, finds processes without an owner and drafts each change for your approval.
Explore Meridi AI
Meridi Delivery adds
- Delivery
Project plans and milestones
See how far the plan has moved from its baseline, and plan rollout milestones.
Explore Projects and plans - Delivery
Contracts, budgets, risks and issues, status updates
Risks and decisions linked to the processes they affect, and status updates drafted from what changed.
Explore Risks and status updates - Delivery
Milestone library and initiatives
The behavior change behind an initiative, and how its adoption will be checked.
Explore Initiatives
What your team can do next.
For operations leaders and process owners who change how work runs, and need the people and instructions affected to change with it.
Changes checked by your team
Recorded changes flag the process for review. Someone with edit access checks it, and the record shows who verified it and when.
No process left unassigned
Processes without an owner are marked Missing owner, and someone who still owns processes can’t be removed until they’re handed over.
SOPs that follow the steps
Owners can see which SOPs a change affects, then review and update the instructions from the process.
One version to run on
Teams and SOPs read the same process, not copies of it. On Delivery, projects run on it too.