Updated:
Published:
February 24, 2023
•
•
6 min
Maybe that’s exactly what you needed—a clear and concise definition of policy vs procedure.
If so—great! We’re glad you got what you came for. (And we hope you’ll swing by again soon.)
But maybe you’re looking for more. Maybe you want to do a deeper dive on policies and procedures. Maybe you want to see some policy and procedure examples. Maybe you want to understand their benefits—and if the juice is worth the squeeze. Maybe you have a few frequently asked questions. Or maybe you’d just like to document way more, in way less time.
In any of those cases—you should stick around.
Policy vs procedure—it’s a valid question. 🤔
While policies often inform procedures, the reverse is less common. How come? Because guidelines determined by decision makers influence the way things get done. But even the best step-by-step instructions don’t usually result in brand new, business wide philosophies.
Raise your hand if definitions are 👍🏽, but contextualized examples are 👍🏽👍🏽. This section is for you!
Think about a vacation policy. It’s probably full of general guidelines:
Those questions answer the what—and establish effective parameters for fast and fair decision-making. A *great* vacation policy may also include your company’s overall philosophy about time off—and explain why the policy is what it is.
A PTO-related procedure, on the other hand, might explain exactly how to submit your request. If your company has a strong culture of documentation (as it should 🕺), you might be able to use a step-by-step guide or checklist to speed up the process.
A universally accepted set of instructions for how to do things—and when to do them—should make following the overarching vacation policy easy.
Policies don’t necessarily need to be written down—or related to work. Here are a few examples of personal policies:
Workplace policies might include:
Examples of procedures are everywhere you look.
If you’ve ever assembled a piece of Ikea furniture (💪🏼), applied for a driver’s license, painted your toenails, followed a recipe, conducted a scientific experiment, or evacuated a building for a fire drill, chances are you’ve followed a procedure to a certain extent.
Well-documented procedures provide a clear roadmap for what to do, when. Here’s an example of how to make tea, in 10 steps:
The same logic applies at work.
You might rely on some pre-established procedures to make your job easier. Or you may be tasked with inventing them on your own. That’s the fun part, if you ask us!
If part of your success hinges on helping others adopt something you’ve discovered or built, you probably already know how important knowledge-sharing is. And you probably already know how tedious, time-consuming, and underappreciated process documentation can be. But it doesn’t have to be. 🤩
If you teach people to use software, there’s a better way to share everything you know. Generating how-to guides automatically, as you work, makes process documentation:
If you’ve worked for a company that doesn’t have a policy and procedure manual in place yet, we don’t need to tell you there are some obvious upsides to having that kind of clarity. But! There are also some less obvious, equally important advantages.
Let’s look at those in more detail.
Process powers teams and empowers individuals.
Understanding policy vs procedure is the first step towards creating guidelines and tutorials that land well.
Learning how to document processes (while you work!) is the first step towards making documentation easy, fast, and fun. 💃🏿
There’s one big reason to keep policy separate from procedure. We often make updates to how we do things. (Ideally by streamlining our processes!) While procedures are frequently in flux, overarching policies shouldn’t change quite as much. Approaching the two separately might make it easier to communicate what’s changing and what’s staying the same. The flip side is—policy and procedure should be closely aligned. Having related documentation can make it easier for everyone to follow the rules of the road, on a macro and micro level.
If you ask us—policies should come before procedures. It makes more sense for high-level guardrails (covering what and why) to inform step-by-step instructions (detailing how and when), doesn’t it?
Personal policy examples might include a savings policy, a healthy living policy, and a social media policy. Workplace policy examples might include a drug and alcohol policy, a travel policy, and an anti-discrimination and harassment policy.
Everyday procedure examples might include applying for a driver’s license, painting your toenails, and assembling a piece of furniture. Work-related procedure examples might include how to create a new project in Asana, a new sequence in HubSpot, or a weekly opportunities report in Salesforce.
While policies work toward long-term goals, they don't detail the exact steps for how to get there. Instead of focusing on step-by-step instructions, policies provide general guardrails for more specific standard operating procedures (and reinforce them).
Policies and procedures are important for obvious reasons like increased efficiency, faster decision-making, better onboarding experiences, and improved compliance and consistency. They also have underrated advantages. Think: operational excellence, employee empowerment, increased autonomy, fewer interruptions, and less knowledge-hoarding and more knowledge sharing.
We'll never show up
empty-handed (how rude!).