Ask about a change that was not chosen
Anyone can describe a change they wanted. A stronger question asks about a change that arrived from outside: a new priority, a lost supplier, a role that shifted, a plan that stopped working. The candidate cannot claim credit for the change, so the answer shows how they responded.
Ask for the moment before the response. What did the candidate know, what did they try first and what made them change course? That sequence is where adaptability becomes visible.
Probe the constraint
A problem-solving story without a constraint is hard to score. Ask what limited the options: time, budget, a policy, a missing skill or a disagreement. The constraint tells the reviewer whether the candidate made a trade-off or simply followed a familiar process.
Ask what the candidate decided not to do. A decision against an option shows the reasoning behind the choice. An answer that lists every action without a trade-off is a description, not a decision.
Write anchors for the answer
For each question, write what a strong answer contains, what a partial answer contains and what is missing. A strong answer names the change, the constraint, the action and the result. A partial answer names the change and the action but skips the constraint or the result.
An anchor can include a follow-up. If the candidate says the plan changed, ask who decided and what the candidate did next. The follow-up is part of the test, not an interruption.
Do not reward the performance
A confident delivery can make a thin example sound strong. A quiet delivery can make a solid example sound uncertain. The reviewer should score the content: the moment, the constraint, the decision and the result, not the style of the telling.
If the answer is polished but has no specific moment, mark it partial and use the follow-up. A prepared story is not a problem when the details hold up. A story without details is a problem even when it sounds smooth.
Use the same questions across candidates
Ask the same questions in the same order. If the role needs a different context for a different candidate, write the difference down and explain why. The comparison is only useful when the questions are comparable.
Keep the questions in the role file. A new interviewer can then use the same set and the same anchors. The role file becomes the memory of what the team decided to test.
Review the answers together
Ask each reviewer to score before the discussion and to bring the evidence. Compare the notes and the scores. If one reviewer found a constraint that another missed, read the passage again. The difference may point to a vague anchor or a missed detail.
The aim is a fair read of the evidence. Adaptability and problem-solving are visible in what the candidate noticed, what they chose and what happened next. A question that asks for those details gives the team something concrete to discuss.