When a coworker changes the plan, ask what must still ship, what can move, who decides, and when everyone needs an answer. Open with the shared commitment: “Let’s keep Friday’s deadline. What can we swap out if we add this?” Use MBTI Judging/Perceiving to think of questions about settling plans or leaving room for new information.
Four questions to ask when a plan changes
- Commitment. What deadline and deliverable did we promise? Who is waiting on them?
- Flexibility. If the deadline holds, what can we shrink, defer, or make optional?
- Decision. What information are we waiting for? When is the latest we can decide, and who decides?
- Communication. Who records and shares the new scope? Who needs to acknowledge it?
Message you can send: “Let's confirm what stays in Friday's release. If the new work displaces something, let's decide what to replace by 4 p.m. today. I'll update the version and tell everyone affected. If your work depends on it, please confirm.”
A practice scenario before a launch
This example is fictional. The team agreed to release a new event page by Friday noon. On Wednesday afternoon, an operations colleague asks for three location-specific variations after seeing new feedback. Design has started the handoff, and engineering has yet to confirm whether the product can identify location. Insisting on the old plan can miss a real reason to change it. Starting first and deciding later can leave the Friday commitment unclear.
Confirm that the general page needs to go live Friday at noon because promotion has been scheduled. Ask whether regional changes can follow later and whether there is an option that leaves the existing interface between systems intact. Record the trade-off, the decision time, and who will notify people.
| Item | Updated agreement |
|---|---|
| Fixed milestone | Launch the general page Friday at noon with the existing sign-up flow |
| Flexible scope | No advance promise of regional content. By Thursday at 11 a.m., if data, copy checks, and sign-off ownership are ready and engineering confirms location detection and time within the test window, the release owner decides whether to add one regional example |
| Default decision | If anything is missing at the checkpoint, release the general page and defer regional content. The release owner confirms the plan and informs operations and QA |
| Record and confirm | Log additions and exclusions in the request. Operations confirms the external messaging. QA acknowledges the revised scope before proceeding |
The hours are examples. Reuse the fields for commitment, flexibility, the decision conditions, and who gets notified. At the checkpoint, update the status.
If teams disagree, start with what you observed, then ask what should change. An MBTI thinking/feeling feedback example
How can J/P help a work conversation?
In the Myers & Briggs Foundation framework, J/P describes preferences in approaching the outside world. One end tends toward closure. The other tends to leave options open for new information. Use both perspectives to check a single plan. Myers & Briggs Foundation on preferences
| What to check | Sample question | Output |
|---|---|---|
| What needs to be settled? | What must we decide today so someone else can start tomorrow? | Commitments and dependencies |
| What should stay open? | What new information would justify changing the plan? | Conditions, deadline, and fallback |
Ask both questions regardless of your coworkers' test results. QA might ask to lock the items for sign-off because only one test environment will be available. Operations may want to wait because regional data arrives later. Ask what drives the request so the team can make a workable plan. MBTI basics
When you cannot approve the change: send the owner the original promise, the requested change, and the trade-off. Name the last time the team can decide without missing its planned checks. Hold off on confirming the new commitment until the owner responds.
Which changes need a decision and which can you try?
Check impact on commitments, coworkers, and costs you can't reverse. If you only change the order of an internal discussion and everyone affected agrees, try it for one work cycle. When adding a module would take time from an agreed testing window, ask the person who can change scope, timing, or staffing to decide. Use the same record for both cases and adjust the level of approval and follow-up.
Atlassian's trade-off exercise starts by agreeing which conditions can move before discussing the cost of a change. Adapt this example to your team's decision rights. If no decision maker is clear yet, mark the new work pending and continue tasks you can finish without rework. Atlassian project trade-offs
Did the conversation help?
After delivery, spend two minutes checking if you met the milestone, if anyone started from the old scope, and if a signal that should have triggered a change was missed. For example, if QA used the old acceptance checklist, version each change next time and have the QA owner acknowledge which version they received. Record what you can observe if you want to examine your own planning habits. Use any preference insights as prompts while keeping team decisions tied to responsibilities and facts. Two-week planning experiment · FermatMind MBTI assessment
Frequently asked questions
What if no one knows who can approve the change? Record the new request as unapproved, continue work that remains valid under either option, and ask the person accountable for the deadline to name a decision owner.
How do you send an update people can act on when a deadline is close and someone's unavailable?
Suppose a client needs to preview an event page by 5 p.m. At 3 p.m., someone learns that the client wants to replace the registration instructions. The teammate who can approve the copy won't be online until 4 p.m., and the layout designer has two other pages to finish. In the project chat, say which preview needs to go out, which work can continue now, and where to look for confirmation. People who are waiting get a time to check, and those who can start know which version to use.
You could write this.
The 5 p.m. preview is still on. Please keep laying out the rest of the page and use the registration instructions approved this morning. At 4 p.m., operations will check the client's requested changes. If we have copy ready to use by 4:10 p.m., the layout lead will reply with an estimated completion time, then we'll decide whether to swap it in. If the text still needs approval at 4:10, I'll use the morning version for the preview and carry the feedback into the next version. Testing team, please reply with the file version you received. I'll post the decision in this thread.
If someone says, “Let's leave room for it. We'll have time,” ask whether leaving room will change the overall page height and whether the content below needs to be checked again. If the change takes up one line and there's time to proofread, the layout designer can suggest making an internal sample for the person in charge. If it cuts into pre-preview checks, list the extra work and ask the person in charge to choose between adjusting the scope and confirming the change later. Keep the discussion on what changes on the page, when it gets confirmed, and who does the work. Team members can raise different questions based on their roles.
Sometimes a key person is already offline. Check whether the change affects their work. If opening the old file tomorrow could lead to rework, put a note at the top of the project record naming the current version, the fallback version, and the difference between them. Flag what you need the person to confirm. If their approval is required, continue the existing work within the approved scope and put the new item on the to-do list. The person can answer a specific question when they return, and the team has work it can keep doing.
Follow through when the decision time arrives. If the copy hasn't come in by 4:10 p.m., for example, the person who sent the update can post, “We'll use the version approved this morning for the 5 p.m. preview. The new instructions are with operations for review. I'll post another update when the text arrives.” Then ask the people who need the file to reply with the version they actually received. If a later change only affects wording, use the same record to say when the next version will replace the current one. After delivery, see whether anyone did the same work twice because a time or version was missing. Add that detail to the original message next time.
Teams sometimes debate whether the first message should include a fallback plan. Ask the person who relies most on the delivery to read it and say what they'd do now, when they'd check back, and when they'd stop. If they can answer all three, the message is usually specific enough. If you still need a meeting, use it to decide the work trade-offs that need approval.


