You are working on a task agreed with your team when a message arrives: the result should look different, a new requirement has been added, or the priority has changed. Some of the work is already done, the deadline has not moved, and each colleague interprets the update a little differently. Should you carry on, start over, or wait for clarification?
In this situation, adaptability is about more than reacting quickly. It means understanding what has actually changed, what still stands, and who can decide what happens next. Without that clarity, even a genuine willingness to help can lead to repeated rework.
First, find out whether the goal changed or just the route
Not every new request means the brief has changed. Sometimes only the document format is different. In other cases, the audience, purpose of the project, or criteria for evaluating the result have changed. The distinction matters: a small adjustment may let you continue, while a change in purpose can make the original plan unusable.
Before reshuffling tasks, ask three questions: What should the result be now? Which parts of the original agreement still apply? What happens if we make the wrong call? If you cannot answer them, the problem may not be your lack of preparation; the brief may be incomplete.
For common workplace changes, it helps to distinguish between these situations:
| Type of change | What to check | Possible next step |
|---|---|---|
| The format of the deliverable changes | Are the content and purpose still the same? | Adjust the presentation, not the entire analysis. |
| The goal or audience changes | How will the result be assessed? | Reconsider the structure and priorities. |
| A new requirement is added | What should be dropped or postponed? | Agree on scope and capacity. |
| The deadline is brought forward | What must be completed first? | Propose a smaller, usable deliverable. |
| Conflicting instructions arrive | Who is authorized to confirm the direction? | Ask for one decision that the team can follow. |
Pause only the work that could be wasted
One of the costliest responses to a change is to discard everything in progress immediately. It is just as risky to continue with the original plan when it is unlikely to be needed. A brief review can help separate reusable work from decisions that remain uncertain.
You can sort work in progress into three groups:
- Keep: background material, data, findings, or technical solutions whose validity is unaffected by the new request.
- Review: work that depends on the audience, expected deliverable, or approval process.
- Hold off on: time-consuming or difficult-to-reverse steps that depend on an important confirmation.
The aim is not to stop the whole project. You may be able to finish checking the data or prepare shared materials while the final deliverable is clarified. Good adaptation protects work already done while preventing further investment in an unclear direction.
For example, if an internal presentation is now also intended for a customer, verified figures may still be useful. Explanations, sensitive information, and the level of detail may need to be reconsidered. Without confirmation of the new purpose, simply changing the title slide and carrying on is unwise.
Decide what you can do before every question is answered
It is not always possible to wait for complete information. There is a difference between a decision that is easy to revise and a step that would be costly to undo or disruptive to others. Let that difference guide how cautious you need to be.
- Low risk and easy to revise: prepare a working draft, state your assumptions, and leave room for changes.
- Moderate risk or a significant time cost: check the most important uncertainty with the responsible person before continuing.
- High risk, sensitive data, or an irreversible step: do not proceed without the required approval, even under time pressure.
A page layout draft can often be changed quickly. Sending information to an external partner, deleting source material, or introducing an operational change may require formal approval. In those situations, improvising on your own is not a sign of greater adaptability.
If you need confirmation, ask a specific question. Instead of the vague “So, what should I do?”, try: “Should we prioritize delivering a basic version quickly, or deliver the full scope later?” This makes the decision that needs to be made clear.
Discuss the impact of a change, not personal objections
“We can’t get this done on time” may be true, but it does not necessarily tell the other person what decision you need. Likewise, “You’ve changed the brief again” can shift the conversation away from the work and toward defending past decisions.
Instead, briefly connect four points: the original agreement, the new request, its impact, and the available options. This leaves room for compromise without pretending that the change comes at no cost.
For example: “We originally agreed to prepare three detailed materials by Friday. We now also need a competitor comparison. With the current capacity, we can deliver the three materials on Friday and the comparison on Monday, or prepare a shorter combined version by Friday. Which option better supports the current goal?”
When working together, also confirm what will stop once the new plan is agreed. If a new deliverable is added while every existing task remains unchanged, the team may not have a revised plan at all. It may simply have a longer to-do list.
A worked example of an unexpected project change
Imagine a team preparing an internal report on campaign results. Two people are processing the data, while a third is drafting the conclusions. The day before delivery, a new request arrives: the material will be used in a customer meeting and should include a recommendation for what to do next.
The seemingly quick response: everyone starts revising their section based on their own assumptions. One person changes the charts, another shortens the text, and a third adds recommendations. An hour later, the team discovers that the customer mainly needs to choose between two campaign options. Some of the revisions were unnecessary.
A more considered approach: the team first confirms what question the new meeting needs to answer. It then keeps the verified data, prepares a comparison of the two options, and moves internal technical details out of the main deliverable. The team also confirms who will approve the recommendation and when the revised version is due.
When two colleagues disagree about the new direction
Adaptability in a team is not just an individual skill. When people respond differently to a change, disagreements can arise even among colleagues who all want a good result. One person prioritizes a quick delivery, another wants completeness, and a third is waiting for precise information.
Before deciding who is right, separate the shared goal from differing assumptions. Check whether everyone agrees on the expected result, deadline, and quality criteria. Sometimes the conflict is not about willingness to cooperate, but about each person having received a different version of the brief.
If instructions come from two managers or several stakeholders, do not become the informal referee. Summarize the conflict briefly: “The latest message says to prioritize option A, while the original agreement says option B. We need to confirm one approach so we don’t continue working on both in parallel.” Identify the person authorized to decide and share the outcome with the whole team.
A simple change log prevents repeated explanations
When changes happen repeatedly, it is not enough for someone to remember what was said in a meeting. A short record in a place the team can access is enough; it does not need to become a separate administrative project.
Capture these points in a line or a brief note:
- What was agreed: the original result or scope.
- What is changing: the new deliverable or priority.
- What remains: usable material and unchanged commitments.
- What the impact is: additional work, a delay, or another task being dropped.
- Who decided and when: the responsible person and the date of confirmation.
This record also helps people who were not at the meeting. If someone asks a few days later why a particular part was not completed, the answer will not rely only on memory or impressions. For a small change in a two-person team, a few sentences in shared communication may be enough; a larger project may need a more formal process.
Being adaptable does not mean accepting every change without limits
Some teams change priorities because new information has emerged. In others, the brief keeps changing without explanation, decisions, or a reassessment of capacity. In the latter case, more individual flexibility training may not help. The problem may lie in how the work is managed.
Notice whether priorities change so often that nothing gets completed, whether you are held responsible for decisions you cannot influence, or whether you are regularly expected to work beyond agreed capacity. These are reasons to discuss how the work is organized, not automatically signs that you have failed to adapt.
If a change involves a safety risk, a serious breach of rules, or unreasonable work pressure, agreeing on a new deadline may not be enough. Depending on the issue, it is appropriate to involve the responsible manager, a relevant internal team, or other available professional support.
What to try the next time a brief changes unexpectedly
You do not need to introduce a whole new system the next time a surprise request arrives. Before making the first revision, write two sentences: “The new deliverable is…” and “The parts of the original plan that still apply are…” If you cannot complete them without guessing, you have a specific reason to ask for clarification.
After the task is complete, take a moment to identify where the most time was lost: getting information, reworking tasks, or waiting for a decision. Adjust one step next time. Adaptability is not about handling ever-increasing amounts of chaos; it is about being able to create a clear shared way forward more quickly when the next change comes.
