Designed for your needs. Grounded in best practices.
Changible by Design is our consulting methodology for defining the conditions for change success, designing the preparation and vendor requirements, validating readiness, and advising progression. We begin while the business case is taking shape and revisit the conditions at critical project milestones. The method is tailored to your needs while maintaining change management best practices.
Early planning connects the magnitude of change with the business case, impact heat map, and roadmap. Preparation then becomes part of the project’s change-management work.
ONE METHOD. FOUR CONNECTED STAGES.
Define. Design. Validate. Advance.
Each stage produces a practical output for decisions and delivery. Apply the method early, then revisit it as scope, vendors, people, timing, and readiness needs evolve.
01
OUTPUT: SUCCESS CONDITIONS BRIEF
Define success.
Clarify the business outcomes, people and processes affected, magnitude of change, and the key success factors. Make the assumptions, prerequisites, dependencies, and measures visible while the business case is being shaped.
02
OUTPUT: CHANGE REQUIREMENTS PLAN
Design the conditions.
Translate success factors into prerequisite work, owners, resources, timing, and acceptance criteria. Connect the business case, impact heat map, and roadmap, and build a clear list of change deliverables for vendors and internal teams.
03
OUTPUT: READINESS EVIDENCE REVIEW
Validate readiness.
Review evidence against the agreed conditions at critical milestones. Check what is ready, what is missing, and what needs action—such as data quality, process ownership, basic technology skills, learning, or operational support.
04
OUTPUT: PROGRESSION RECOMMENDATION
Advance with evidence.
Give leaders a clear recommendation: proceed, proceed with defined actions, or address gaps before advancing. Follow the agreed actions, vendor commitments, and success factors through delivery, readiness reviews, and adoption.
PLAN THE RIGHT CHANGE WORK WITH YOUR VENDORS
Clear expectations. Connected plans.
We support your organisation in vendor discussions so change requirements are considered early and translated into practical delivery commitments. Make the vendor’s contribution and your internal preparation explicit before plans and responsibilities are finalised.
01
Make the change elements explicit.
Build a clear list of change deliverables for stakeholder engagement, communication, role-based learning, readiness, adoption, and handover. Define scope, owners, effort, timing, dependencies, and acceptance criteria, connected with the prerequisites and success factors identified in the business case.
02
Agree ownership. Follow it through.
Clarify what the vendor will provide, what your organisation owns, and which dependencies need joint attention. Carry those commitments into the project plan, governance discussions, and readiness reviews, revisiting them when scope or timing changes.
MAKE THE MAGNITUDE VISIBLE
A heat map that helps you plan the work.
Map impacts by affected group and area of change. Discuss readiness alongside the map, then use the priorities to inform effort, ownership, investment, and sequencing.
Illustrative planning example · Relative change impact
Affected group
Process
Data
Technology
Skills
Readiness priority
Data owners
Moderate
High
Moderate
Low
Data quality & validation
Frontline teams
High
Moderate
High
High
Basic digital skills & process practice
Managers
Moderate
Low
Moderate
Moderate
Role clarity & reinforcement
These are sample planning assumptions. Build the actual map with affected teams and refresh it as the project develops.
WHAT EARLY PREPARATION LOOKS LIKE
Make the early work part of the plan.
A move from manual processes to technology can involve groundwork that comes before system training. Two examples show how assessing this early changes the roadmap.
01 /
Clean the data before it needs to move.
A new platform will use information currently held in paper files, spreadsheets, or legacy systems.
See how this shapes the plan +
Spot it early
Check for missing fields, duplicates, inconsistent formats, and unclear data ownership.
Include it in the case and heat map
Make data-owner effort, capacity, validation, and migration dependencies visible in scope, timing, and resourcing.
Prepare before the milestone
Agree owners and quality rules. Schedule cleanup and validation before the migration and testing activities that depend on the data.
Carry it into the project
Connect the cleanup plan with testing, process changes, user guidance, and ongoing data ownership.
We start with the work already in motion. Together, we review the business-case assumptions, prerequisite work, vendor plans, and success factors to identify what needs attention next.
Clarify ownership and refresh the change commitments with your team and vendors. Fit the remaining preparation, communication, learning, and support into current milestones and capacity, then follow progress through delivery.
