A roofing company owner sends a short email to three people on a Tuesday morning. A customer called in about a callback on a job from two weeks ago, and the shingles are lifting again. The email says: “Get ahead of this one. Handle it and let me know where it lands.”
Four words to the owner. Perfectly clear. He wrote it in ninety seconds between two other things and moved on.
By Thursday, three different things had happened.
The service manager pulled the crew off a scheduled job to send someone out same day, worried that “get ahead of this one” meant the owner was about to lose the account. The office manager drafted a formal response letter and sat on it, waiting for the owner to review the wording before anything went to the customer, because “let me know where it lands” sounded like he wanted final approval. The install lead did nothing for two days, assuming someone else already had it, because the email didn’t say his name and he read “handle it” as a general instruction to the team rather than a task assigned to him.
None of them ignored the email. None of them misread a single word in it. They read the same four sentences and produced three different responses, and by the time the owner found out, the customer had already called back twice.
What actually happened in that email
No one dropped the ball here. One message reached three people who are wired to process directness, urgency, and ownership differently, and nothing in the business told them how to resolve that difference.
The service manager reads urgency as a signal to act immediately and visibly. Speed is how he shows he’s on top of things, so an ambiguous instruction gets treated as a green light to move fast and sort out the details later.
The office manager reads the same tone as a request for precision. To her, “let me know where it lands” means don’t finalize anything without a check-in, because the cost of getting the wording wrong on a customer-facing letter feels higher than the cost of moving slowly.
The install lead reads instructions literally, and an email that doesn’t name him by name doesn’t feel like an assignment. He’s not being careless. He’s applying the same logic he applies to every group email that goes out, and most of those aren’t meant for him personally.
Three reasonable interpretations. Three different actions. One email that felt completely clear to the person who wrote it.
The cost shows up somewhere else entirely
This is the part that makes the problem hard to catch. The gap between what the owner meant and what the team did rarely traces back to the email itself. It shows up three steps downstream, and by then it looks like a different problem.
The crew got pulled off a paying job to handle something that could have waited until the next day, which pushed that job’s completion date and irritated a different customer. The formal letter sat in a draft folder for two days while the original customer called in twice, each time more frustrated than the last, because nobody had told her anything was happening. The install lead found out on Thursday that the callback was still open, and by then the shingles had lifted further and the repair had gotten more expensive.
The owner, watching all this unfold, sees a customer complaint that got worse, a schedule that got disrupted, and a team that seemed slow to respond. His read is that people aren’t taking initiative, or that communication in general “needs work.” So the next email is more detailed, more urgent, sometimes sharper in tone, and the pattern repeats with a new set of instructions and the same three interpretations.
What looks like a communication problem is usually an execution gap that keeps re-forming, because nothing was ever defined at the seat level about who owns the decision when an instruction is ambiguous.
The one thing that was actually missing
It wasn’t tone. Brian’s email wasn’t rude, and none of the three people misread his intent as hostile or careless. It wasn’t a personality clash either. All three are competent people doing what they believe the job requires.
What was missing was decision authority at the seat level: a shared understanding of who owns the call when a message doesn’t spell out every step. The service manager didn’t know whether “handle it” meant he had authority to pull a crew off a job without checking first. The office manager didn’t know whether her seat included final say on customer letters or just drafting them. The install lead didn’t know whether an unnamed group email created a personal obligation to act.
Each of them filled that gap with their own default, because their own default was the only standard available. That’s what communication style differences actually do in a business. They don’t create the ambiguity. They fill it, in whatever direction each person is wired to fill it, when the seat itself never defined what belongs to that seat in the first place.
A clearly defined seat would have made the tone of the email almost irrelevant. If the service manager’s seat already specifies that customer callbacks inside a certain dollar range are his to schedule without approval, “get ahead of this one” reads as confirmation, not a new grant of authority. If the office manager’s seat specifies that customer-facing letters under a certain threshold don’t require owner sign-off, she sends it the same day. If the install lead’s seat specifies that any email naming a customer he’s worked with is his to flag or claim within 24 hours, silence isn’t an option he has.
What to look at before writing the next instruction
Most owners respond to a moment like this by trying to write a better email. Slower down, more explicit, more steps spelled out. That helps a little, and it also doesn’t scale. An owner cannot write a fully detailed instruction set every time something comes up, and the people relying on him for that level of detail will always need him for the next ambiguous situation too.
The more durable fix starts with the seat, not the sentence. For each role that touched this problem, there’s a question worth answering in writing, not just in the owner’s head: when a message from me is unclear, what decision belongs to this seat by default, and what does this person do when it doesn’t?
That’s not the same as writing a longer job description. Most job descriptions list tasks. This is about naming the decisions a seat owns, the dollar or time thresholds where that ownership applies, and what the person in that seat should do in the gap between instructions, before checking back in. Once that’s written down and confirmed with the person in the seat, the same short email lands the same way every time, regardless of how directly or diplomatically it was written.
This matters most in the moments that feel small. A short email on a Tuesday morning is a small moment. It only becomes expensive because three people filled the same gap three different ways, and the business paid for all three responses at once.
Where Trueseat fits
Trueseat is built around this exact gap: the space between what a seat is supposed to own and what actually gets written down about it. The process is designed to help an owner define what a seat owns, what decisions belong to it, and what success looks like early in the role, so instructions don’t have to carry the full weight of clarity every single time they’re sent.
It doesn’t rewrite how people communicate. It gives the seat a standard that communication can lean on, so a short email from a busy owner means the same thing to everyone who reads it.
If you’re dealing with this right now
If you’ve noticed the same instruction getting read three different ways by three different people, or you’ve caught yourself writing longer and longer emails to try to close a gap that keeps reopening, that’s usually not a tone problem. It’s a sign that a seat’s decision authority was never clearly defined.
A Trueseat call is a working conversation about the seat itself: what it should own, what decisions belong to the person in it, and what needs to be true before the next instruction goes out. If you have a seat where this keeps happening, book a call at https://calendly.com/trueseat and bring the situation with you.