“The users” is not a plan.
Adoption fails one role at a time, for reasons specific to that role. AdoptIFS starts from 20 named personas across 10 families, each mapped to the IFS surfaces they touch, the processes they run and the training they need, so the change plan is addressed to somebody rather than to everybody.
Read from the platform as this page loaded.
20 personas, by IFS pillar and family
These are the roles an organization running IFS Cloud actually has, grouped by the IFS pillar they work in. Open a family to see the roles in it, and what is attached to each one. The profile itself is what a license opens.
The change profile behind each name
A persona list is easy to write. What makes it useful is what is attached to each one.
What changes, and what they resist
20 profiles
For each persona: what is actually different about their day, the specific reason they will push back, and the objection they will voice in the room. Written down before the meeting rather than after it.
What is in it for them
20 value statements
The one thing that makes this worth their while, per persona, plus the channel that actually reaches them and how long you have their attention.
Readiness, weighted per persona
20 readiness profiles
Five dimensions (curriculum, assessment, simulation, engagement, sentiment), weighted differently for a technician than for a controller, with UAT and go-live thresholds per role.
The communications plan
39 templates
Templates across 4 program phases, anchored to real dates and addressed to a persona rather than to a distribution list.
Workshop material
71 questions
Structured workshop topics and the questions to ask in them, tied back to the processes under discussion.
Tied to the process model
103 curriculum links
Personas mapped to the training they need and the processes they run. This is the join that makes a change plan specific, and it only exists because the process library exists.
The last one is the point. Change management that knows which processes each role touches is a different activity from change management that does not, and that knowledge comes out of ModelIFS. It is why these are one platform and not three products.
Everything you can see here is real and current, the names, the structure and the counts come straight out of the AdoptIFS library and change as it grows. What sits behind the license is the worked-out content itself: the execution steps, the data each one needs, the configuration decisions, the KPIs, the integration points, the workshop questions and the diagrams. That is the part you would otherwise spend a program building from nothing.
Sign in to open it