Making SOPs Accessible To Everyone

How I Wrote SOPs at Amazon (And Still Do Now) Early in my career, I thought an SOP was just… A document explaining how to do something. Then I watched a new team member follow one of my SOPs. They stopped every few minutes. Asked questions. Made assumptions. That’s when I realized: A great SOP isn’t written for the person who created the process. It’s written for the person who has never seen it before. That changed how I wrote them forever. 1/ I started with the “why” ↳ What is this process? ↳ When should someone use it? ↳ What problem does it solve? People follow processes better when they understand the purpose. 2/ I assumed zero prior knowledge ↳ No acronyms ↳ No tribal knowledge ↳ No “everyone knows this” If a new hire couldn’t follow it… It wasn’t finished. 3/ I wrote in the exact order someone would perform the work ↳ Step 1 ↳ Step 2 ↳ Step 3 Seems obvious. It’s amazing how many SOPs jump around. The reader shouldn’t have to think about the sequence. 4/ I included decision points…not just steps Instead of: ↳ “Review the request.” I’d write: ↳ “If the request is missing required information, return it to the requester. If complete, continue to Step 4.” Good SOPs remove ambiguity. 5/ I documented common mistakes This became my favorite section. ↳ Common failure points ↳ Frequent questions ↳ Things to double-check Example: ⚠️ Before submitting, verify the customer ID matches the request. This is the most common error. One sentence can prevent dozens of mistakes. 6/ I asked someone else to follow it Without me explaining anything. Every question they asked… Became an improvement to the SOP. If they got stuck, the document was wrong…not the person. 7/ I treated SOPs like living documents Processes change. Systems evolve. So should documentation. The best SOPs were updated continuously…not once a year. Amazon taught me something simple: A good SOP explains the process. A great SOP makes the process almost impossible to do incorrectly. That’s still the standard I use today. 📬 I write weekly about leadership, execution, and building systems that scale in The Weekly Sync: 👉 https://lnkd.in/e6qAwEFc What’s the best SOP you’ve ever used…and why did it work so well?

90% of SOPs die in Google Drive purgatory because they’re either too complicated, too basic, or written by someone who's never actually done the job. Here's the framework that actually works (written by someone who’s actually used it): 1. Do you even need an SOP? Only document when: The same questions keep coming up repeatedly Multiple team members need to execute consistently The task happens on a regular schedule The current process owner is leaving or scaling More than one person needs to know how to do it 2. Answer these 5 questions first What's the core objective? Who currently owns this process? Who else needs to execute it? How often does it happen? Where is it breaking down right now? 3. Match the detail level to the user For new team members: Step-by-step instructions with screenshots Basic terminology only Clear checkpoints throughout For experienced staff: Fewer checkpoints Technical language is fine Focus on efficiency, not handholding For leadership review: Technical enough to validate without drowning in details Clear success metrics High-level overview with essential specifics 4. Include these non-negotiable elements Every effective SOP must have: Time expectations (how long it should take) Clearly numbered steps Highlighted critical actions Validation checkpoints Common pitfalls and how to avoid them What success looks like 5. Validate with these 5 tests Not done until it passes these checks: Can leadership understand it? Can a new hire execute it without confusion? Does it solve the original problem? Are the time expectations realistic? Is there a clear path to completion? This will never change for how I'm creating or my team is creating SOP's but what will change is how the person uses it and has it evolve over time.

Writing SOPs is easy. Getting people to actually use them? That’s the real challenge. If you want your processes to live and breathe inside your business, not just sit in a digital folder, here’s how to operationalize them: Start with reality, not theory Don’t aim for the perfect process. Document what’s actually happening today, then improve from there. Break it down into roles Every SOP should answer: Who does what, when, and with what tools. If multiple people are involved, use a RACI matrix to align your team. Turn SOPs Into Checklists A checklist is what the team uses in real life. It should follow the flow of the SOP but be actionable, step-by-step, clear, and tied to the tools they use daily. Embed it where work happens If your team uses project management software, embed the checklist there. If they work from tablets in the field, build it into a form or app they already use. Don’t make them go hunting for the process. Train it. Review it. Reinforce It. Introduce it in a team meeting. Use real-world scenarios. Check in weekly or monthly to ask: → Is it being used? → What’s unclear? → Has anything changed? SOPs don’t create structure. Using them does.

🙄 It's not uncommon for new employees to feel overwhelmed by the myriad of SOPs governing their daily tasks. This meme captures a moment we've all likely witnessed, but it also underscores a vital truth in our industry. Adhering to SOPs is not just a regulatory requirement; it's a commitment to quality, safety, and consistency. **So how can we ensure SOPs are used and followed?** 🤩 Make them usable: I cannot count how many times an SOP was created or updated and could not be followed as written. Not because people didn't want to, but the expectations within were not clearly stated or the tools/materials needed were not available. Why, you say, why then was it approved?! Possibly to rectify metrics or release a batch, or a number of other reasons. If SOPs are being generated without input from those using it, and are not being created or redlined while observing the process take place, then there will always be problems. 🏫 Training & Education: R/U is not it. Especially for the complex SOPs that are used to guide people through critical tasks. There should be a risk-based approach, with a thorough understanding of how the SOP will be used (information use, reference use, or continuous use), and then subsequent training. Any time there is a new process or change to an existing process, remember habits take ~30 days to become engrained. This leaves a window where the likelihood for error is higher, and thus oversight should be as well. 👁️🗨️ Accessibility: Make sure SOPs are easily accessible. Seems like common sense but in this digital age, and especially in cleanrooms, service can be spotty. If people need to get the job done but can't find a way to access the SOP, they will go off memory. Having hard copies available at the start of a shift during system downtimes is very important to building the right habits. By following their own memory or what they see instead of a standardized document, bad habits form and propagate. 🔊 Monitoring & Feedback: Regular audits and constructive feedback help identify areas for improvement and reinforce the importance of compliance. They are perfect for praising those exhibiting the right behaviors, as well as coaching and correcting those who need it. It also allows management to recognize the pain points of those operating that may have fallen on deaf ears. 🤗 Fostering a Culture of Compliance: Encourage a workplace culture where adherence to SOPs is valued and rewarded. Don't slack on this. Remember, SOPs are more than just a set of rules; they are a reflection of our commitment to excellence. Let's embrace them not as a burden but as a pathway to success in delivering top-notch biotech products. #biotech #manufacturing #quality #compliance #SOPs

“I can't wait to curl up with a good SOP tonight.” Said no one, ever. But in pharma, SOPs can mean the difference between life and death. You want a shared truth that serves as the foundation for safe, efficient, and repeatable workflows. So here’s my advice (having helped companies such as Pfizer and GSK with their documentation) on how to craft your SOPs so your team follows them consistently and successfully: 1️⃣ Know Your Cast of Characters 🎭 • Analyze roles: From lab techs to QA managers, everyone's got a part to play • Understand each role's specific needs (A chemist and a compliance officer walk into a lab...) • Consider how different roles will access and use the SOP A one-size-fits-all approach fits no one well in the pharma world. 2️⃣ Keep It Simple, Scientist 📝 • Short sentences are your friends • Active voice is your superpower ("Add reagent," not "Reagent should be added by you, maybe, if you feel like it") • Consistent terms (Pick a word and stick to it. This isn't a thesaurus contest) Nobody wants to decode War and Peace while handling active ingredients. 3️⃣ Format for the Skimmers (i.e., Everyone) 👀 • Embrace white space (it's not wasted space, it's breathing room) • Clear headings are your roadmap • One step, one action (multitasking = multierrors) A well-formatted SOP is less likely to be used as an impromptu pillow. 4️⃣ Picture This: Understanding 🖼️ • Diagrams and flowcharts (Worth a thousand words, especially when those words are "complex procedural steps") • Visuals that clarify, not confuse (no abstract art, please) • Callouts for the "Don't mess this up" bits Sometimes, showing is better than telling (and retelling, and explaining again). 5️⃣ Sections That Make Sense 📋 • Clear, logical sections (Introduction, Prerequisites, Steps, Troubleshooting, "What Not To Do Unless You Want An Exciting Day") • Keep it relevant (Save your weekend plans for the water cooler) • Include only the must-knows A well-organized SOP is like a well-organized lab: Everything has its place, and you can find what you need without a search party. Because in pharma, SOPs aren't just documents. They're the guardrails keeping us from chaos, contamination, and some very awkward conversations with regulators.

The impact of AI on simplifying Standard Operating Procedures (SOPs) is paramount. Recently, I collaborated with a client to streamline their SOPs, a critical endeavor for any organization. AI plays a crucial role in expediting this simplification process, and we leveraged a variety of tools to achieve remarkable outcomes. - **Enhancing Readability:** Tools like OpenAI GPT and Grammarly are invaluable for refining text to enhance clarity. By tailoring the content to the education level or reading age of the audience, these tools effortlessly enhance comprehension. - **Efficient SOP Management:** Platforms such as Veeva and Docugami excel in content management, ensuring adherence to regulations, and automating updates, thereby boosting the efficiency of SOP procedures. - **Interactive Training:** AI-driven solutions like Docebo and Synthesia are transforming SOP training by creating video-based modules, replacing traditional methods with engaging and interactive content. - **Instant Support:** AI chatbots provide real-time assistance, ensuring compliance during tasks and offering valuable guidance to users. Within a mere three days, we significantly reduced SOP content by an average of 50%, greatly improving the clarity and user-friendliness of the SOPs. Embracing AI tools has proven to be a game-changer in simplifying processes and enhancing operational efficiency. #AI #SOPs #Automation

How to make your SOPs work for you, not against you: (a 3-step guide to simplify your processes) It’s not about creating more SOPs. It’s about making the ones you have useful. This step-by-step guide will help you create SOPs that actually help. 1. Look at what’s missing: Most SOPs fail because they’re incomplete. Do they cover the most critical tasks? Are they too long or confusing? Would someone new know exactly what to do? A good SOP is like a recipe. Clear. Simple. Easy to follow. 2. Keep it short and focused: Nobody reads 20-page SOPs. Focus on the key steps: What’s the goal? What’s step 1, step 2, step 3? What’s the expected outcome? Use templates or tools to make them user-friendly. Keep testing them until they’re good. 3. Treat SOPs as living documents: Your business evolves. So should your processes. Review SOPs regularly. Get feedback from the person using them. Update them when needed—don’t let them collect dust. Every “bad” SOP is a chance to create clarity. Keep simplifying, improving, and adapting. PS: To make the process easier for you, I've got a free SOP Template, lemme know if you want it and I'll send it over.

Most SOPs fail before they even get written Why? Because they’re written for the boss, not the team. A lot of small business owners treat SOPs (Standard Operating Procedures) like a rulebook. Long. Rigid. Complicated. But real documentation isn’t about control. It’s about CLARITY. One client came to me after her VA kept missing steps in the onboarding process. She had a Google Doc. It was 7 pages long. No one used it. So we rebuilt it, together. ↳ We started by identifying just the three core workflows she needed help with most. ↳ Then we simplified. ↳ Created a step-by-step checklist for each task. ↳ Added visuals to show exactly how things should look. ↳ Recorded short Loom videos (each under 3 minutes) to walk her VA through the process. The result? ✅ Her VA stopped asking the same questions. ✅ Tasks were completed on time. ✅ She finally stopped waking up to Slack messages at 6 a.m. Here’s the truth most people miss: Good systems don’t live in your head…. They live where your team can find and use them. And when your team has access to simple, repeatable SOPs, they stop waiting, guessing, or spiraling. They just do the work. Struggling to get your team to actually USE the SOPs you’ve created? I created a free guide to help you build simple, streamlined SOPs your team will follow, without extra meetings, micromanagement, or overwhelm. Link is in the comment section below. This is exactly what I help small business owners do: Turn over complicated processes into clear, practical systems that actually get used So your team runs smoother, and you stay focused on growth. #systems #leadership #business #strategy #ProcessImprovement

SOPs are not just documents. But many still view them as static paperwork. [or just a Loom] Imagine your business as being ten times the size it is now. What roles would exist? How would you hire & train everyone? Would you have someone taking care of the things you hate? How I modernize SOPs in 3 steps: → Build a workspace for real-time updates → Use interactive elements for user engagement → Include feedback mechanisms to continually refine So they can help you: → Streamline training and onboarding → Adapt and improve processes over time → Maintain high standards and consistency → Create a culture of continuous improvement. → Enhance efficiency and responsiveness to change → Empower you + your team with clearer, actionable guidance Building a 1-best way mentality. But remember - Your SOPs should evolve with your business. Why? Because the way your business functions needs a strategy, too. Less time in operations. More on what you love. ↓ And if you want more posts like this in your feed... - Follow Adam Judeh 🛠️ - Repost ♻️ to your network