The Client Who Changed the Brief Twice

Sara: Omar, I think we need to pause for a second. I just got the updated message from the client, and the brief has changed again. This is not the same priority list we prepared this morning.

Omar: Right, let’s stay grounded. If the brief has changed, we should clarify exactly what shifted before we react. Otherwise, we may spend time solving the wrong problem.

Sara: Agreed. From what I can see, they want the homepage refreshed, but now they are also asking for three new deliverables. I am not sure which part is essential and which part is optional.

Omar: That is the key question. We could ask, what exactly has changed, which deliverable is the top priority, and whether they want a full revision or just a targeted adjustment. Those questions should narrow the scope.

Sara: Yes, and we should keep the tone non-defensive. Something like, as I understand it, the scope has expanded, so we want to make sure we are aligned before we confirm the next step.

Omar: That sounds professional. We might also ask who the main stakeholder is on their side, because if several people are giving input, the expectations can easily drift in different directions.

Sara: Good point. I also want to know whether they still expect the original deadline. If the deliverables have doubled, the timeline may no longer be feasible without reducing the scope or extending the deadline.

Omar: Exactly. We should be honest but diplomatic. We can say, from our side, we can meet the revised brief, but only if we either adjust the timeline or agree on a smaller first phase. That keeps the discussion solution-oriented.

Sara: And if they push back, we can soften it with something like, perhaps a phased approach would work better. That way we are not refusing the request; we are offering an alternative that protects quality.

Omar: Yes, and we should be precise about deliverables. If they want a revision, we need to confirm what counts as a revision, how many rounds of feedback they expect, and whether new content is included or not.

Sara: I will draft the follow-up email with those questions. I want to avoid vague language, because vague approval often becomes vague responsibility later. Clear expectations now will save us from confusion at the final stage.

Omar: That is wise. In the meeting, we can say, to make sure we are fully aligned, could you walk us through the updated priorities in order? That invites clarity without sounding challenging.

Sara: And after that, we should summarize what we heard. For example, the top priority is the homepage refresh, the extra deliverables are still under review, and the client will confirm whether the deadline can move.

Omar: Exactly. Summarizing helps everyone hear the same version. Then we can confirm next steps, assign owners, and set a time for follow-up so nothing stays ambiguous.

Sara: So our action plan is: clarify the changed brief, ask focused questions about scope and priorities, propose a realistic timeline, and document the agreed version immediately after the meeting.

Omar: Yes, and the language matters as much as the plan. Could, might, and would help us sound polite; if we do this first, then we can do that next keeps the negotiation structured and calm.

Sara: I like that. We are not saying no; we are making the request workable. That is usually the difference between sounding resistant and sounding reliable.

Omar: Exactly. Let’s go in with one clear goal: leave the room with alignment, a realistic deadline, and a shared understanding of who is doing what.