How to Write Instructions Your Team (Or AI) Actually Follows
Vague instructions produce vague results. Here is how to write clear, repeatable protocols that get executed properly every time.
"Can you make sure we follow up with leads?"
This is not an instruction. It is a wish. And wishes do not get fulfilled. They get forgotten.
Whether you are managing humans, training AI, or documenting a process for yourself, the quality of the output depends entirely on the quality of the input. Vague instructions produce vague results. Specific instructions produce specific results.
The Anatomy of a Good Instruction
A good instruction has five parts:
1. The trigger. When does this happen? "When a new lead fills out the contact form" is a trigger. "When someone seems interested" is not.
2. The action. What exactly happens? Not "follow up." But "send email template A within 5 minutes, then email template B after 48 hours if no reply."
3. The owner. Who is responsible? Not "the team." Not "someone." A named person or role.
4. The standard. What does good look like? How do we know it was done correctly? A checklist, a template, or a screenshot of the expected outcome.
5. The exception. What do we do when things do not go to plan? Who decides? How do we escalate?
Why Most Instructions Fail
They assume context. "Handle it the way we usually do" assumes the person knows what "usually" means. They probably do not. Write it down.
They use jargon. "Enrich the lead and move it to the nurture sequence" means nothing to someone who has never used your CRM. Use plain language.
They skip the edge cases. What if the lead has no company name? What if they reply on a weekend? What if the calendar is fully booked? Answer the obvious questions before they become problems.
AI Makes This More Important, Not Less
As businesses use more AI, the quality of instructions matters more than ever. AI does exactly what you tell it. No more, no less. If your prompt is vague, the output will be vague. If your prompt is precise, the output will be precise.
The skill of writing clear instructions is now one of the most valuable skills in business. It applies to humans, software, and AI equally.
The Test
Before you publish any instruction, ask: could a new person follow this without asking questions? If not, rewrite it.
Clarity is not bureaucracy. It is respect for the person executing the work. And it is the fastest way to get consistent, high-quality results.
If your team constantly asks "what do you mean by that?" or your AI outputs are inconsistent, I can help you build clearer protocols.