Standard Operating Procedure Optimization

I have a saying: a good SOP is like a good recipe. If only the chef understands the instructions, you’ll never eat the same dish twice. In a fermentation process, that’s where the trouble starts. An SOP (Standard Operating Procedure) is supposed to guarantee reproducibility: delivering the same results no matter the operator, the team, or the site. But when an SOP is poorly designed or ambiguous, it often ends up understood only by the person who wrote it. That’s when scale-up breaks down. You get variability, dependency on one key person, and undetected process deviations that can mean: → 40 hours per month lost in troubleshooting and onboarding → $800,000 worth of scrapped batches every year → Up to 15% annual revenue loss And beyond the cost, there’s the compliance risk. In GMP/ISO environments, you and I both know that’s unacceptable. At Cultiply, we apply a few simple principles to avoid these issues: — Have someone uninvolved in writing the SOP review it, and log any ambiguities during first use — Set a clear target: a new technician should be fully independent by their 3rd run — Always update after a scale change (a lab SOP ≠ a pilot SOP) For me, an SOP is a strategic tool for scaling up with confidence. That perspective has completely changed the way I approach processes.

If I had a dollar for every organization I've worked with where the SOPs were good, I wouldn't have a dollar. From my work with companies such as GSK, Novartis, and Pfizer, I hold that: 📋 SOPs must be functional above all else. Their purpose is to help people complete tasks successfully and safely, on time, with expected outcomes. ❌ But most SOPs fail because of: 1. Too Much Information • Every task 20+ steps • Information not concise or focused • Steps containing rationales (belongs in policy docs) • Poor titles that don't indicate task purpose Example of what NOT to do: "Please take a moment to review the testing documentation below." (It's not a favor—just write "Review the testing documentation") 2. Format & Language Issues ⚠️ • Walls of text without reading cues • No white space for visual breaks • Complex words where simple ones work ("utilize" vs "use") • Multiple actions crammed into single steps Real example of what NOT to do: "Remove one packet from the pouch and carefully add all contents to the water sample, swirl the sample until all the reagent dissolves into the solution." (That's 3 separate steps crammed into one!) 3. Structure Problems 🔍 • Steps not chronological • Sections bleeding into each other • Missing process mapping (critical for understanding flow) • Key information (like definitions) buried at the back ✅ The solution starts with three key principles: 1. Map Before Writing 🗺️Process mapping isn't optional; it's the foundation for any usable SOP (like your clinical trials, start with a protocol, not a prayer). 2. Write for Real Use ✍️One action per step, simple language (save the fluff for your cotton swabs). 3. Structure for Success 🎯Put key information where readers need it (hint: definitions belong up front, like your safety goggles). 💡 As I tell my pharma clients: "Will incorporating these concepts make your SOPs longer? Yes, sorry. Will it make them more usable? Yes, not sorry." ⚠️ Because in pharma, unusable SOPs aren't just inefficient—they're a compliance risk (or worse, accident) waiting to happen. Questions? AMA in the comments ⤵︎

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

The Secret to Scaling Your DSO Without Chaos As your DSO grows, inconsistency can creep in—different offices following different protocols, inefficiencies causing delays, and teams struggling to stay aligned. Without a standardized approach, growth becomes chaotic and frustrating. To scale successfully, your operations must be: ✔️ Standardized: Every location should follow the same core systems to ensure efficiency and quality. ✔️ Measurable: Clear KPIs should guide every team’s performance and highlight areas for improvement. ✔️ Adaptive: Processes should be structured but flexible enough to evolve as the organization grows. Ways to create operational consistency: 🔹 Develop clear Standard Operating Procedures (SOPs) and ensure all teams adhere to them. 🔹 Leverage technology to automate and streamline workflows, reducing manual errors and inefficiencies. 🔹 Hold quarterly process reviews to refine and optimize efficiency, ensuring that best practices are always followed. 🔹 Create a centralized training system so all team members receive consistent onboarding and ongoing development. Growth doesn’t have to mean chaos. With the right systems in place, your DSO can scale efficiently while maintaining quality and profitability. What’s your biggest challenge in standardizing operations? #DentalOperations #ProcessOptimization #Scalability

📢 "Our QMS should serve us, not the other way around!" 📢 This was a key message in our All Hands Meeting yesterday as we kicked off a company-wide initiative to revitalise our processes. As an ISO 13485 certified manufacturer, we know robust processes are vital in meeting quality objectives - but they need to work for the teams using them. Otherwise the fundamental purpose of a QMS - a set of processes and procedures that ensure a business consistently meets customer requirements and delivers quality products and services - is undermined. ❤️ I might have pushed the boat out a little too far when I suggested that it might even be possible to love an SOP but we live in hope. ⚠️ Here are 5️⃣ warning signs your SOPs might need a refresh (and how to fix them): 1️⃣ The "Optional" Perception When teams view SOPs as optional guidelines rather than essential tools, it often signals a disconnect between process and purpose. Make the link explicit between SOPs and quality outcomes. Attaching meaningful metrics to SOPs can further strengthen this link - does the SOP do what it’s meant to do? 2️⃣ The Knowledge Gap If your team doesn't know SOPs exist or where to find them, centralisation is key. In SaMD development, tribal knowledge isn't enough - we need consistent, accessible, controlled documentation. 3️⃣ The Utility Problem SOPs should be written by and for the people doing the work. In SaMD development, this means ensuring procedures reflect actual workflows while meeting regulatory requirements. A good test for whether a process is useful: does anyone want to own it?! 4️⃣ The Trust Issue  Outdated or incorrect SOPs erode confidence. Create clear paths for updates and feedback - quality systems should evolve with processes. 5️⃣ The Perfectionist Trap An SOP needs to be practical yet comprehensive - a difficult balance to strike! Too much can be as problematic as too little. Make SOPs skimmable with clear checklists for validation. 🎯 The goal isn't bureaucracy - it's enabling consistent, high-quality outputs while meeting regulatory requirements. An effective QMS should feel like a helpful framework rather than a constraining box. 💡 Consider providing TL;DRs for each SOP. Make it clear when an SOP applies and when it doesn’t, not too dissimilar to indications for use. Cater for different types of information absorption: written, graphics, audio and, dare I say it, videos. What's your experience? How do you balance regulatory compliance with practical usability in your SOPs?

Agile Operating Procedures (AOPs) Standard Operating Procedures (SOPs) have great value across industries. In the military, they promote discipline and repeatability. In healthcare, they reduce risk and improve patient outcomes. In Agile software development, SOPs must balance consistency with adaptability. SOPs in Agile Agile thrives on flexibility, not chaos. SOPs provide structure, and that consistency benefits teams: Definition of Done (DoD): Reduces risk of teams pushing unfinished work. Branching and Merging: Expect chaos if every developer pushes code however they want. Incident Management: A structured response process is critical when issues arise in Prod. Code Review: Quality improves when peer reviews follow a repeatable process. Sprint Planning, Reviews, and Retros: Even Agile events need clear expectations to avoid wasted time. These SOPs establish a shared understanding of key activities in high-velocity environments, improving effectiveness, quality, and collaboration. SOP Evolution Agile SOPs should adapt based on experience and empiricism. Top-Down Adaptations: Leadership refines SOPs based on strategy, tooling, or regulations. Bottom-Up Adaptations: Developers propose adjustments based on what works (or doesn’t) on the ground. For example, a team might realize strict branch policies slow them down without improving quality. Leadership should empower and encourage them to suggest changes instead of demanding rigid adherence. The best Agile organizations create feedback loops where frontline teams influence SOP improvements. SOPs Can Go Too Far Over-standardization can stifle innovation. When every action is prescribed, teams lose the autonomy to experiment. The key is identifying where freedom adds value and where structure prevents failure. SOP Value Spectrum High-Value SOPs: CI/CD pipelines, security, compliance. Moderate-Value SOPs: Coding style guides, sprint formats, documentation. Low-Value SOPs: Standup and retro formats. Jira administrativia. Rigidity pushes teams toward cargo cult Agile, where process adherence matters more than value delivery. Smart SOPs guide but don’t constrain. The U-Shaped Curve of SOP Effectiveness Too few SOPs, and teams waste time reinventing the wheel. Too many, and they may fail to adapt. The ideal state sits in the middle, where essential procedures provide guardrails but leave space for innovation. Performance improves with some standardization but drops if it becomes excessive. Agile SOPs SOPs are appropriate for Agile teams, but only when they're not static, and foster agility. The most effective teams refine SOPs based on performance, balancing structure and flexibility. Teams should be (and feel) empowered to shape these processes, recognizing that the best improvements come from the people doing the work. Agile isn’t about rigid adherence to SOPs. It’s about delivering value. The right SOPs - and taking an agile approach to SOPs - help teams do just that.