Adaptability
performance review phrases

Consistently stays ahead of shifting project requirements, meeting deadlines despite external changes.

Displays remarkable resilience when faced with unexpected technical hurdles, often finding creative workarounds that benefit the entire team.

Has successfully transitioned to new digital workflows this year, showing a keenness to upskill and lead others through the change.

Maintains a positive and professional demeanour during periods of high ambiguity, serving as a stabilising influence for the department.

Quickly assesses new information and adjusts strategic priorities to keep our goals relevant in a changing market.

Volunteers for unfamiliar work rather than waiting to be asked, and treats new tools as an opportunity rather than a disruption.

Ready for a bigger change to run. Give them the next system migration end to end rather than a workstream inside it.

The instinct to bring others along is already there. Formalise it by pairing them with the next new starter through their first process change.

I have actively sought out training for [new software or methodology] to remain a versatile asset to the team.

I have successfully managed the transition to our new hybrid schedule, maintaining high output while supporting my colleagues' adjustment periods.

Helps colleagues adjust to new processes by sharing what they have learned rather than keeping workarounds to themselves.

Asks the right questions when direction changes, which surfaces problems early and helps the whole team recalibrate.

Acts as a steadying presence for newer team members during restructures and system changes.

Balances flexibility with follow-through, adapting plans without letting existing commitments slip.

Handles announced change well. The next step is seeing it coming, so bring them into planning conversations before decisions land.

Adjusts willingly once a direction is set. The harder version worth practising is forming a view while the direction is still open.

Copes with change in their own work. Widen it by asking them to think through what each change means for the people downstream.

I pride myself on staying calm and productive even when our primary objectives are reassessed at short notice.

When our priorities were reset in the second half, I re-planned my work within the week and flagged what would slip rather than letting it slide quietly.

Needs a firmer plan than the work usually allows. When scope shifts mid-cycle, the delivery date tends to move with it.

Raises objections to new processes after they are agreed rather than while they are being decided.

Reverts to the previous method once attention moves elsewhere, which leaves the team running two versions of the same process.

Waits for complete information before acting, and on this team that wait often costs more than an imperfect first move.

While technically proficient, there is an opportunity to improve responsiveness when project scopes are adjusted mid-cycle.

Encouraged to seek out new learning opportunities more frequently to stay ahead of changing industry standards.

We would like to see more confidence in making decisions when all the facts aren't yet available; embracing a degree of ambiguity will be key this year.

Could focus on developing a more flexible mindset when collaborating with teams that have different work styles.

Aims to reduce the time taken to recalibrate after a change in direction is announced by the leadership team.

I recognise that I sometimes prefer routine, but I have made a conscious effort this year to volunteer for pilot projects that require a flexible approach.

I tend to wait for certainty before committing to a direction. I am working on making the call with the information available and revising it openly when it changes.

Has not adopted the workflows introduced this year, despite training in March and two follow-up conversations since.

Continues to escalate routine changes as problems, which draws the team leader into work that should not need them.

Declined the transition support offered twice this year, and the capability gap has widened rather than closed.

This is now affecting the team's output, not only their own. We need a written plan with dates: which processes, what support, reviewed in six weeks.

Two separate things are worth pulling apart: whether the change is workable, and whether it is being worked. The first is a conversation I want to have. The second is not optional.

I have struggled with the changes introduced this year and did not ask for help early enough. I would like a structured plan with regular check-ins rather than waiting until review time.