Read a sample: 1. Start With the Decision
A technical update can be accurate from beginning to end and still leave its audience unsure what to do.
Imagine that a project manager asks an engineer whether a software release is ready. The engineer describes the tests completed, the unusual behavior discovered during a busy period, and the additional logs the team plans to inspect. The manager listens carefully. At the end, she asks, “So, are we releasing tomorrow?”
The engineer has not necessarily explained anything incorrectly. The problem is that the explanation began where the investigation began, not where the manager’s decision begins.
Technical work often moves through a sequence of observations, questions, experiments, false starts, and revisions. That sequence matters to the people doing the work. It can also be essential when the work needs to be reviewed or reproduced. But the order in which you discovered something is rarely the most useful order for someone who needs to act on it.
Starting with the decision means identifying what your explanation is meant to help someone choose, do, understand, or prepare for. It does not mean skipping evidence or reducing every conversation to a demand for approval. It means giving the audience a reason to care about the details before asking them to follow those details.
This small change in starting point can make a complicated explanation feel more manageable. It can also expose gaps in your own thinking: perhaps the decision is not yet clear, the audience cannot make it, or the evidence does not support the recommendation you were about to give. Discovering those gaps before a meeting is useful work.
When someone asks, “What have you been working on?” a description of the work may be exactly what they want. In many professional conversations, though, that question sits beside a more practical concern:
- Can we proceed?
- What has changed?
- Do we need to set aside time or resources?
- Which option should we investigate?
- What should we tell the customer?
- Is there a problem we need to watch?
- What can we responsibly conclude so far?
These questions point toward a decision, action, or concern. The distinction matters because a technically complete description can answer none of them directly.
Suppose you have spent several days investigating why a reporting process sometimes takes longer than expected. You could describe each query you examined, every configuration setting you checked, and the sequence in which you ruled out possible causes. That information may be valuable to a colleague who will continue the investigation. A department lead deciding whether to rely on the report for an upcoming planning session may need something else first: whether the report is likely to be available in time, what remains uncertain, and what alternative is available if it is late.
Neither audience is more intelligent or more important. They are responsible for different things. A useful explanation respects those differences without assuming that one person needs a “simple” version and another needs a “technical” one.
The question is not, “How much of my work can I fit into this update?” It is, “What does this person need from my work now?”
The word decision can sound more formal than the conversations you have every day. You may picture a budget approval, a release authorization, or a signed agreement. Those qualify, but they are not the only situations in which decision-focused communication helps.
Sometimes the immediate action is to keep monitoring a situation. Sometimes it is to decide who should investigate a problem. Sometimes the audience needs to understand why no decision is ready to be made.
For example:
> “We don’t yet know what caused the reporting delay. Today, we need to decide whether to use the most recent completed report for planning while the team investigates.”
The speaker is not pretending to have solved the technical problem. The decision is about how to work responsibly while that problem remains open.
An explanation can also support a concern rather than a discrete choice:
> “There is no action needed from your team today. I’m raising this because the delay could affect when you receive the next report, and I’ll update you when we know more.”
Here, the useful outcome is awareness. The audience can adjust its expectations and knows when to expect further information. Calling attention to a concern is still purposeful communication, even if the listener has nothing to approve.
Before preparing an explanation, try completing this sentence:
> After hearing this, the audience should be able to do, decide, understand, or prepare for something specific.
If the sentence ends with “understand everything I did,” look again. What will that understanding allow them to do? If the answer is “review my method for errors,” then the method itself may be central. If the answer is “decide whether to proceed,” the method is evidence in service of that decision.
It is tempting to select a decision for the audience and build an explanation around it. Sometimes you will be right. Sometimes you will frame the wrong problem.
A colleague who asks whether a system change is “ready” may mean technically complete, tested under expected conditions, approved by a customer, or feasible to support after launch. Those are related questions, but they are not interchangeable.
A brief clarification can prevent a long, misdirected answer:
> “When you ask whether it’s ready, are you deciding whether we can release…