How I Manage Expectations Throughout a Delivery

No Client Should Ever Be Surprised by Bad News: How I Manage Expectations Throughout a Delivery

By Maria Duncan | Technical Project Delivery & Service Delivery Leader

No client should ever be surprised by bad news. Ever.

That is not just a preference. It is a professional standard I hold myself to on every engagement I lead. And in my experience, the delivery teams that live by it are the ones clients actually trust, as opposed to the ones clients simply tolerate.

As a Technical Project Manager and Service Delivery Lead, some of my most important work has nothing to do with timelines or budgets. It has everything to do with communication, and more specifically, with making sure clients always know where they stand.

Here is how I approach it.

Start With Clarity Before the First Task Kicks Off

Before a single task begins, I align with the client on how updates will be delivered and how often. Not in a vague, “we will keep you posted” kind of way. In a specific, agreed-upon way: what format status updates will take, how frequently they will come, and who is responsible for communicating what.

This conversation sounds simple, but most teams skip it. They assume communication will work itself out as the project progresses. It rarely does. Ambiguity about how a project will be communicated creates almost as many problems as ambiguity about what will be delivered.

Setting that expectation upfront removes the guesswork for everyone and gives clients a reliable rhythm they can plan around.

Surface Issues Early, Always With a Plan

The moment a risk appears on my radar, the client hears about it. Not after I have spent a week quietly trying to fix it. Not at the next scheduled status meeting. Early, and always paired with a proposed path forward.

This is a discipline that takes practice. There is a natural instinct to want to bring solutions before you bring problems. But waiting until you have a solution means waiting too long. Clients are stakeholders, not passive recipients of good news. They deserve to be part of the conversation while there is still time to influence the outcome.

Bad news does not get better with time. The longer a risk sits unshared, the fewer options everyone has, and the more trust erodes when it finally surfaces.

I have found that clients respond far better to early, honest communication about a problem than to a polished update that arrives too late to act on.

Define “Done” Before You Start

Ambiguity at the end of a project is almost always the result of assumptions made at the beginning.

I confirm acceptance criteria explicitly at the start of every engagement. Not buried in a project document that no one reads again, but as an active conversation: what does success look like? What are we measuring against? What would make you say this delivery fell short?

That conversation is sometimes uncomfortable to have upfront. It forces specificity when people often prefer to stay flexible. But it is far less uncomfortable than a disagreement at go-live about whether the solution met expectations.

Clear acceptance criteria protects everyone. It protects the client from a delivery that misses the mark. And it protects the delivery team from a moving target.

Proactive Communication Is What Builds Trust

Delivering on time and on budget matters. But it is not what makes clients trust you.

Clients trust delivery teams that keep them informed, treat them as partners, and never let them be caught off guard. They trust teams that surface problems honestly and come with options, not just bad news. They trust teams that do what they said they would do, communicated the way they said they would communicate it.

Proactive communication is not an extra layer of effort on top of the work. It is the work. It is what separates a delivery that goes smoothly from one that succeeds technically but damages the relationship.

The goal is not just to deliver. It is to make the client feel confident every step of the way.

 __________________

Maria Duncan is a Technical Project Manager and Service Delivery Leader based in New York, with over 15 years of experience delivering complex technology programs across financial services, healthcare technology, and enterprise IT.