Project qualification and change rollout
A good idea is not enough. You have to check whether it makes sense, and then guide the team through the change. This set of methods answers both questions.
This article collects methods that help assess a project before it starts and carry it through so that people actually use it. Each answers a different question — together they form a complete set.
RICKS — is the project worth starting at all
RICKS is a set of four conditions a problem must meet to deserve a solution.
- Relevant — important for strategic goals.
- Impactful — the benefit is measurable.
- Grounded in data — based on data, not impressions.
- Compatible — consistent with what the company already uses.
If any condition is not met, the project is postponed or narrowed. It is the cheapest way to avoid work that will bring no result.
ADKAR — how to guide people through change
ADKAR describes five stages every person goes through when adopting a new tool. Skipping any of them ends with a return to old habits.
- Awareness — understanding why the change is needed.
- Desire — willingness to take part in it.
- Knowledge — knowing how it works.
- Ability — practical skill.
- Reinforcement — making the new habit stick.
Lewin's model — unfreeze, change, refreeze
The oldest and simplest model of change. First you weaken old habits, then you introduce the new solution, and finally you stabilise it so it does not fall apart.
- Unfreeze — show what is no longer working.
- Change — introduce the new solution in small steps.
- Refreeze — settle the habit into daily work.
Three-level SWOT
The classic strengths and weaknesses analysis gains value when run at three levels at once.
- Micro level — a specific task, e.g. time spent on routine work.
- Team level — people's concerns and readiness to change.
- Macro level — the company's market position and competitive edge.
Day in the Life — where to look for improvements
The method has the team describe a typical working day in detail: the activities, their order and duration. Repetitive, time-consuming tasks surface on their own.
RFM — segmenting the customer base
RFM orders customers by three criteria. Each receives a score, which allows grouping them into segments with similar behaviour.
- Recency — how recently they bought.
- Frequency — how often they buy.
- Monetary — how much they spend.
FUTURE — standards for safety and trust
FUTURE is a set of principles worth writing into every rollout. They ensure the solution is fair, predictable and understandable for the user.
- Fairness — fairness towards all groups.
- Universality — availability and universality.
- Traceability — the ability to trace decisions.
- Usability — usefulness in daily work.
- Robustness — resilience to errors and load.
- Explainability — explainability of behaviour.
How to use these methods in a prompt
Each method can be turned into part of an instruction. The agent then runs the qualification conversation exactly according to the chosen scheme.
- Instruct it to collect data according to RICKS before proposing a solution.
- Ask it to identify the ADKAR stage the team is at.
- Add a prohibition on proposing solutions without data.
A prompt built this way goes into ePersona, where you can test how the agent runs qualification and organises the enquiry in a real conversation.
Frequently asked questions
Which method should I start with?
RICKS. It answers whether the project makes sense before you commit time and budget.
Do these methods work in a small company?
Yes. In a small team ADKAR and Day in the Life work even faster, because information travels a shorter distance.
How does three-level SWOT differ from the classic one?
The classic looks at the company as a whole. The three-level version splits conclusions into task, team and market, so they do not blur together.