Writing Down How Your Business Runs

Understanding Brain-Dumping and SOPs

Standard Operating Procedures, or SOPs, are the repeatable instructions your managed IT company uses to deliver work the same way every time. They are the playbooks for onboarding a new client, responding to a high-priority ticket, deploying a workstation, restoring a backup, or closing a terminated user account.

The goal is not to create paperwork for its own sake. The goal is for a capable new technician to complete a common task at about 80% effectiveness by following the documented process and asking only a few questions. If every client onboarding depends on the owner remembering hidden steps, the company cannot grow safely. If the process is clear, another technician can follow it while the owner focuses on sales, vendor relationships, or service quality.

The Importance of Brain-Dumping

Brain-dumping means moving the knowledge in your head into a format the team can use. In a managed IT business, this knowledge often includes small but important details: which monitoring agent to install first, how to name a new Microsoft 365 tenant, where client credentials are stored, when to escalate a security alert, and how to document a change in the ticket.

Real-World Example: You may know exactly how to onboard a 25-user Microsoft 365 client because you have done it dozens of times. You know to verify domain ownership, create groups, apply baseline security settings, enroll devices, test conditional access, and confirm the backup job. If that sequence stays only in your head, a technician may skip a step when you are away. Record the process once, then turn it into a usable SOP.

Creating Effective SOPs

1. Why: Explain why the task matters and what risk it controls. For example, proper offboarding protects client data and prevents former users from accessing company systems.
2. What: List the exact steps in the order they should happen. Include required tools, approval points, screenshots, ticket fields, and escalation rules. Avoid phrases such as "handle it normally" or "use your judgment" unless you explain what that means.
3. Outcome: Define what successful completion looks like. A completed new-user setup might require a working login, enrolled device, tested email, assigned license, security training, and ticket notes showing who approved the access.

Real-World Example: An SOP for a critical server alert should explain why fast response matters, how the technician checks monitoring data, when to call the client, which changes are allowed without approval, and what evidence must be attached to the ticket before closure.

Organizing Your SOPs

Store SOPs in one searchable location that every authorized team member can reach. A managed IT company may use Hudu, IT Glue, Confluence, or a well-structured SharePoint site. Organize the library by work type, such as Service Desk, Client Onboarding, Security, Backup and Disaster Recovery, Projects, Sales Handoffs, and Offboarding.

Each SOP should have an owner, a review date, a version number, and a clear title. Link client-specific details to the correct client documentation rather than placing passwords or private information inside a general SOP. The team should be able to find "New Microsoft 365 User Setup" in under one minute.

The Loom-First Approach

Start with a screen recording instead of trying to write a perfect document. Open a test client or training tenant, talk through the task, and record the clicks, decisions, checks, and common mistakes. Loom is useful for showing how to configure a firewall rule, create a ticket, or verify a backup restore.

After recording, have a technician turn the video into a short written checklist. The video captures the real work; the written version makes the process searchable and easier to audit. Never record live passwords, recovery codes, or sensitive client information. Use a test account or pause the recording when secrets appear.

Building a Culture of Self-Reliance

Train technicians to check the SOP library before asking how a routine task works. This does not mean refusing help. It means the team uses the same source of truth and improves it when something is unclear.

When a technician asks how to add a new user, respond with, "Check the New User Setup SOP, then tell me which step is unclear." If the SOP is wrong or missing a step, update it after the ticket is complete. Over time, repeated questions become documented improvements instead of repeated interruptions.

By brain-dumping critical knowledge, recording real workflows, and reviewing SOPs after incidents, your managed IT company becomes less dependent on one senior engineer. Work becomes more consistent, onboarding gets faster, and clients receive the same standard of service even when the owner is not available.