Someone asks you to commit to a plan. You ask what the requirements are. They tell you. Verbally. No document, no email, no written brief. Words in a meeting room that will evaporate the moment something goes wrong. You’re now expected to deliver against inputs that no one will remember the same way twice. This is how accountability gets manufactured from nothing and assigned to whoever builds first.
In March 2026, I wrote about being in a vibing position. This one is about passing vibes down to you, dressed up as briefings.
The pattern has a name
I call it the verbal mandate. A stakeholder describes what they want in a conversation. You take notes, maybe. They don’t review your notes. No one signs off on shared understanding. You go build. Three months later, the outcome doesn’t match their expectation. It has shifted because unwritten expectations always shift. The question lands on you: “Why didn’t you deliver what we agreed?”
You didn’t agree on anything. You received a verbal signal and treated it as a foundation. Hearsay is cheap to produce. As a foundation for product commitments, hearsay is expensive.
This pattern is distinct from the broader documentation problems I’ve written about before. This isn’t about teams failing to maintain specs or leaders hoarding institutional knowledge. This is about the specific moment when someone hands you spoken input and expects a written output: a plan, a commitment, a timeline, a strategy. That conversion, from their words to your accountability, is where the trap lives.
Why verbal inputs persist
Verbal directives aren’t accidents. They serve the person giving them.
Flexibility without fingerprints. A requirement that was never written down can be reinterpreted later. “That’s not what I meant” is only possible when there’s no artifact to check against. The person who gives verbal input retains the option to redefine success after the fact.
Speed as justification. “We don’t have time to write it all down” sounds reasonable in the moment. But the time saved on documentation gets spent three times over in clarification meetings, rework, and post-mortems where everyone remembers a different conversation.
Implicit authority preservation. Written inputs can be questioned, compared against evidence, evaluated by others. Verbal inputs exist only between speaker and listener, which keeps the power asymmetry intact. You can’t escalate a hallway conversation. You can’t audit a feeling.
None of this requires bad intent. Most people giving verbal mandates aren’t scheming. They’re operating in a system that doesn’t penalize vagueness at the point of input. It only penalizes failure at the point of output. And you’re at the point of output.
The cost structure
When you accept verbal inputs as the basis for commitments, you absorb several risks that belong elsewhere.
Interpretation risk. You become the translator between what was said and what gets built. Every translation decision is yours to defend.
Scope risk. Without written boundaries, scope isn’t undefined. It’s defined by whoever has the most authority at the moment of disagreement. That person is rarely you.
Accountability risk. When the outcome is questioned, the burden of proof falls on whoever made the concrete artifact. That’s your roadmap, your sprint plan, your spec. The verbal input that shaped all of it? Gone.
Audit risk. In regulated environments, or in any organization where decisions eventually get reviewed, verbal inputs create gaps that look like your gaps. Compliance teams don’t audit conversations. They audit documents. If the input isn’t documented, the decision trail starts with you, making you the de facto decision-maker for a decision you didn’t make.
The detection skill
Detecting a verbal mandate before it becomes your problem requires paying attention to a specific signal: someone is asking you for a commitment while offering you nothing written in return.
Watch for these patterns:
- A meeting ends with action items for you but no documented decisions from them.
- You’re asked to “put together a plan” based on a conversation, not a brief.
- Requirements arrive as opinions in Slack threads or hallway conversations that never get consolidated into an artifact.
- Feedback on your written work comes verbally, creating a layer of unwritten amendments on top of your documented proposal.
The moment you notice the asymmetry (they speak, you write, you own) you’ve detected the pattern.
The rejection protocol
Rejecting verbal mandates doesn’t mean refusing to work. It means refusing to be the only person who converts intent into artifact. Here’s how to do it without becoming the person who “blocks progress with process.”
Reflect the input back in writing before you act on it. Send an email or message summarizing what you understood from the conversation. Be specific. Include what you believe the requirements are, what you believe is out of scope, and what you believe the success criteria are. Ask for written confirmation. This isn’t bureaucracy. It’s a basic control against future reinterpretation.
Name the conversion explicitly. When someone asks you to produce a plan from a verbal briefing, say so plainly: “I want to make sure we’re aligned before I commit the team’s time. Can you confirm these inputs in writing so we’re working from the same foundation?” Most reasonable stakeholders will agree. The ones who resist are telling you something important about how they intend to operate when things go sideways.
Set a conditional commitment. “I can draft a proposal based on today’s conversation, but I’ll need written confirmation of requirements before we commit to timelines.” This separates exploration from commitment. It also protects your team from building against inputs and claims which don’ have a formal owner.
Treat silence as a finding. If you send a written summary and get no response, don’t assume agreement. Document the silence. “Sent summary on [date], no confirmation received. Proceeding based on my interpretation, subject to revision when written confirmation arrives.” This creates a traceable record that shows you tried to establish shared understanding and the other party chose not to engage.
What this doesn’t solve
This protocol protects you from one specific failure mode: being held accountable for outcomes built on inputs no one will stand behind. It doesn’t solve the deeper problem of organizations that are culturally allergic to written commitment at every level.
If you find yourself repeatedly asking for written inputs and repeatedly getting verbal responses, you’re not facing an individual communication preference. You’re facing a system that runs on ambiguity because ambiguity protects the people above you from owning their own decisions. At that point, the question shifts from “How do I get this in writing?” to “What does it mean that they won’t put it in writing?”
The absence of a written input isn’t neutral. It’s a decision. Treat it like one.