Lesson 6 of 6
Give Bad News Early and Keep the Customer's Trust
Tell the sponsor on the day you learn that a date will be missed, with the effect, the options, a recommendation and the decision you need, then record what was decided without rewriting the past, and know when to ask the sponsor to step in.
7 minForward Deployed Engineering
After this lesson you will be able to tell a customer that a date will be missed in a way that leaves them better able to decide, and with more confidence in you than before.
Last Friday's update asked the operations director to get a delivery date from the supplier of the practice system. On Monday 15 June they made the call, and it went into the log as action A11. On Wednesday 17 June, just after lunch, the answer arrives.
The news
Replace actions.csv with the log as it stands on Wednesday afternoon.
id,raised,side,owner,action,due,done,blocks
A01,2026-06-02,us,FDE,Send notes and actions from the discovery call,2026-06-02,2026-06-02,
A02,2026-06-02,customer,Practice manager,Send May's order history for the two pilot practices,2026-06-05,2026-06-04,
A03,2026-06-02,customer,Head nurse,List the items that must never be suggested for reorder,2026-06-08,2026-06-09,
A04,2026-06-02,customer,IT manager,Get a read-only key for the practice system from its supplier,2026-06-10,,Pilot start
A05,2026-06-02,us,FDE,Demo reorder suggestions on May's order history,2026-06-11,2026-06-11,
A06,2026-06-04,customer,Operations director,Confirm the start date with both practice managers,2026-06-09,2026-06-08,
A07,2026-06-11,us,FDE,Round every suggestion up to whole boxes,2026-06-16,2026-06-15,
A08,2026-06-11,customer,Head of clinical services,Decide who approves each order during the pilot,2026-06-15,2026-06-16,Pilot start
A09,2026-06-11,us,FDE,Write the one-page guide for the pilot practices,2026-06-18,,
A10,2026-06-11,customer,Practice manager,Book 30 minutes of training at each pilot practice,2026-06-17,2026-06-16,
A11,2026-06-15,customer,Operations director,Get a delivery date for the key from the supplier's account manager,2026-06-17,2026-06-17,python actions.py 2026-06-17Action log at the end of Wed 17 Jun 2026: 9 done, 2 open, 1 late
With Larchmont
A04 due Wed 10 Jun LATE 7d IT manager: Get a read-only key for the practice system from its supplier [blocks: Pilot start]
With us
A09 due Thu 18 Jun FDE: Write the one-page guide for the pilot practicesMuch has gone right this week. Suggestions now come in whole boxes. The head of clinical services has decided that the duty vet at each practice approves every order during the pilot. Training is booked. Nine actions are done and only two are open.
The one that matters is still open, and A11 has brought the reason. The supplier will issue the read-only key on Wednesday 24 June. The pilot is due to start on Monday 22 June. It cannot start on that date.
Tell them today
The next written update is due on Friday. It would be easy to hold the news until then, and by Friday you might have a tidier plan to present with it. Do not wait.
- The rhythm agreed in lesson 1 says urgent news is given on the day it is known. This is what that line was for.
- Two practices have booked training and told their staff a start date. Every day's delay in telling them makes the change more awkward for the operations director.
- The sponsor may have options you do not know about. They cannot use them until they know.
- If they hear it first from the IT manager or the supplier, they will wonder what else you have not told them.
Telephone the operations director first. News like this should not arrive as a surprise in an inbox, and a call lets them ask questions at once. Keep the call short: what has happened, what it means, and that a written note with options will follow within the hour. Then send the note, so that there is a record and something to forward.
The shape of a bad-news message
A bad-news message has five parts, in this order: what happened, the effect, the options, your recommendation, and the decision you need by a date.
Subject: Stock pilot: start date will move, decision needed by Thu
The supplier has confirmed that the read-only key will be issued
on Wed 24 June. The pilot was due to start on Mon 22 June and
cannot read the practice system without the key.
Options
A Start on 22 June with stock levels typed in by hand each
morning. Keeps the date. Adds daily work for the head nurses,
and tests a way of working that nobody will use afterwards.
B Move the start to Mon 29 June. Training goes ahead in the
week of 22 June as booked, on May's orders. The pilot ends
on Fri 24 July, one week later than planned.
I recommend B. It costs one week and keeps the pilot a fair test.
What I need: your choice by Thu 18 June, so that both practices
hear the new plan from you before the weekend.Each part has a job.
- What happened is a fact with its source, in one sentence. There is no apology in it and no story about how hard everyone tried.
- The effect is stated in the customer's terms: the start date, not the state of the integration.
- The options are real ones, each with what it costs. Option A is included although you do not recommend it, because the date may matter to the sponsor for reasons you cannot see.
- The recommendation is yours, with a reason in one line. A list of options with no recommendation hands your job to the customer.
- The decision is asked for by a date, with the reason for the date.
No blame, and no fog
Two failures are common in messages like this one, and they pull in opposite directions.
The first is blame. "The supplier has failed to deliver" and "IT did not chase" may both be arguable, and neither helps the reader decide anything. The message above says what the supplier confirmed and stops there.
The second is fog. "We are experiencing some challenges with third-party access which may have an impact on timelines" contains no date, no effect and no request. A reader has to telephone you to find out what it means. If the start date will move, write "the start date will move".
Record the decision without rewriting the past
On Thursday morning the operations director chooses option B and tells both practice managers. The pilot will now start on Monday 29 June.
It is tempting to tidy the log to match: change the due date on the key to 24 June, so that nothing shows as late. Do not do that. The key was due on 10 June, and that date was agreed in front of five people. If you overwrite it, the log no longer explains why the pilot moved, and the next person to read it will think everything ran to plan.
Leave the old row as it is and add the new plan beside it. The exercise does this: your own check of the connection becomes a new action, due on Friday 26 June, two days after the key and one working day before the new start. In the status update, the first line carries the decision and the day it was made.
When to ask the sponsor to step in
Look back at how the date was found out. For a week the key was "with the supplier", and nobody at your level could get an answer. One telephone call from the operations director produced a date in two days.
Asking a senior person to step in is called escalation, and new engineers often avoid it because it feels like admitting failure or going over somebody's head. It is neither, if you do it properly.
- Escalate when an action that blocks something is late and its owner cannot unblock it alone.
- Tell the owner first. The IT manager knew what Friday's update would ask before it was sent.
- Ask for one specific thing that the senior person is able to do and you are not.
- Do it early. The request went out when the key was two days late, not ten.
What you practised
Look back over the three weeks. You wrote down who the people were and what each needed. You ran a call in which the customer did most of the talking, played it back, and sent notes the same day. You kept every action in one log, with an owner and a date, including your own. You built a demo around one order that the head nurse remembered, and gained a fifth stakeholder and a decision the pilot needed. You wrote an update that said "at risk" in its first line while there was still time to act. And when the date slipped, the sponsor heard it from you, the same day, with a recommendation.
The pilot starts a week late. Larchmont's operations director knows why, chose the new date personally, and has seen every promise you made to them kept. A customer in that position gives the next piece of work to the same engineer.
Key takeaways
- Give bad news on the day you learn it, by voice first and then in writing.
- A bad-news message has five parts: what happened, the effect, the options, your recommendation, and the decision you need by a date.
- State facts without blame. The reader needs to know what to do, not whose fault it is.
- When a date moves, keep the old date in the log and add the new plan beside it.
- Asking the sponsor to step in is a normal part of the work. Do it early, with a specific request.
Try it
Record Thursday's decision and write Friday's update. In actions.csv, put 2026-06-18 in the done column of row A09, and add this row at the end: A12,2026-06-18,us,FDE,Connect with the key and check one day's suggestions against the shelf at Ashby Road,2026-06-26,,Pilot start. Run python status.py 2026-06-19. A good result lists five actions done this week, shows the key as 9 days late under "Needed from Larchmont", shows A12 due on Fri 26 Jun under "Our open actions", and still suggests "at risk". Then write the finished update. A good first line says that the start has moved from Mon 22 June to Mon 29 June by a decision of the operations director on 18 June, and that the new date holds if the key arrives on Wed 24 June. Notice that the script could not have written that line.
Official documentation
Written with AI and checked automatically. Nobody has run these steps by hand, and tools change, so a command may behave differently in the version you install. Spotted a mistake? Tell us.