How to communicate with a Beacon
Getting the bad news early from somebody who reports it as a finished fact.
They said no to your request inside the first minute. Not a maybe, not a let me look at my week. A flat no, with a reason attached, and you spent the walk back to your desk deciding whether you had been snubbed.
Then the thing they did agree to arrived on the day they said it would, during a month you later found out was rough for them. They mentioned none of that. You are not dealing with coldness. You are dealing with somebody who thinks the delivery was the message.
What is actually happening
This pattern commits to a concrete outcome and executes it without much need for company or commentary. What it says is a plan rather than a hope. That is why the early no is so abrupt. Declining clearly is treated as the kinder option, because a soft maybe would have left you planning around something that was never coming.
The strain shows up as silence. Under pressure this pattern goes quiet, so the first visible sign that anything is wrong is the missed date itself. There was no warning phase you failed to notice. There was a warning phase that was conducted entirely in private, and by the time it surfaced the decision had already been made.
The other half of it is ambiguity. A vague brief is the one input this pattern handles badly, because the response to an unclear goal is to pick the most literal reading and deliver that. If the goal quietly changed while the work was running, the old goal gets delivered anyway, perfectly, on time.
What it costs, and who pays it
The cost lands on whoever is downstream of the date. You get no early signal, so you cannot re-plan, and the first thing you learn is that a thing you were counting on is not coming. A week of warning would have cost one sentence. You did not get the sentence.
The second cost lands on the colleague who missed one commitment. This pattern measures a person by their delivery record and stops there, and a single miss can move somebody into a permanent lower category. They will not be told. They will notice, over months, that they stopped being asked to do anything that mattered.
What to do differently
Say what done looks like before anybody starts.
Ambiguity is the specific input this pattern handles worst, and the failure is invisible until delivery. Name the finished state in concrete terms and the work will match it. Leave it loose and you will get a competent version of something you did not ask for, argued for correctly.
SayDone means the report is in Sarah's inbox and she has signed it off. Not drafted. Signed off.
Ask about the hard part, not about how it is going.
The general question gets a general answer here, and the answer will be fine. That is not evasion; it is an accurate summary of a situation the other person considers handled. Name the specific piece you are worried about and you get a real report, because there is now something concrete to report on.
SayHow is the data migration piece going? That is the bit I would expect to be ugly.
Announce the change in goal out loud, on the day it changes.
A plan agreed in March will be delivered in June exactly as agreed, because keeping your word is the baseline assumption rather than a virtue being displayed. Nobody will check whether the goal still holds. If you do not say it changed, you will get the old thing, finished, and it will be your fault.
SayThe goal moved last week. Stop building against the old spec. Here is the new one.
Ask for the halfway flag, and say you want it.
The reading names flagging slippage at the halfway point as the growth edge, which means it is not happening yet. Requesting it explicitly turns a confession into a deliverable, and this pattern delivers what it agreed to. Without the request you get silence until the deadline, every time.
SayAt the halfway mark I want one sentence on whether this is on track. Even if the sentence is yes.
When this goes wrong
The one it gets confused with
Both are undramatic, self-contained and hard to read from a distance, and both will give you a short answer that is exactly what they think. The difference is whether a promise exists. A Beacon has committed to an outcome and a date, and the commitment is the thing it will not break. A Signal has not committed and will not be talked into it by the mood of a room. If you are waiting on a delivery and it arrives when they said, you were dealing with a Beacon.
The full description of this pattern, including what it looks like at its best and what it costs under pressure, is on the Beacon page.
All of that is the outside view. It is written from where you stand, watching somebody finish things, and inferring the reasoning from the record.
The part this page cannot do
All of that is the outside view. It is written from where you stand, watching somebody finish things, and inferring the reasoning from the record.
The hard part is that a low-commentary pattern gives you very little to work from. You are inferring load from the absence of complaint, and the reading is explicit that those two are not the same. Worth noticing: somebody is currently reading your quiet months the same way, and they will not tell you what they decided.
Start the interviewIt takes about fifteen minutes and it is free. The $29 Portrait is only charged after five people finish and the evidence clears.