Camp S.O.P.
Your Field Guide to SOPs for Busy Tech Teams
A companion resource to the live presentation by Pete Schweiss
You just sat through my talk (or stumbled here from the internet — welcome, friend). Either way, this page is your take-home guide to actually running your own Camp S.O.P. and getting your documentation house in order. No PowerPoint required.
Want the slides? Download the full presentation deck from AIIM.
Download Slides (PDF)What Even Is an SOP?
Your Recipe for Work
Before I got into technology, I spent years in professional kitchens. Every dish on every menu had a recipe — a precise, tested, documented set of steps. It didn't matter if the sous chef called in sick or the line cook was new; the recipe was the recipe. The guest got the same dish every time because the process was written down, trained to, and followed.
An SOP is just that — a recipe for a work process. Who does what, in what order, and what "done" looks like. It's not a policy document or a manifesto. It's a practical, repeatable guide that makes your team less dependent on the one person who "just knows how to do it."
The best kitchens don't rely on individual memory. They rely on documented process. Why should business operations be any different?
Why Bother?
Institutional knowledge walks out the door. Don't let it.
I worked with a nonprofit that had 45 years of donor and fundraising data sitting in a legacy system — and exactly three people who knew how to actually use it.
Then those three people left. Within months, no one could reliably pull reports, reconcile records, or replicate the workflows that had sustained the organization's fundraising engine for decades. Forty-five years of institutional knowledge — gone, because it only lived in people's heads.
If this story made you think of someone at your organization — that's the point.
Welcome to Camp S.O.P.
The Framework — Three Camp Rules
Make it Engaging, Hands-On, and Meaningful
A room full of coworkers is no different from a room full of teenagers — they both need a reason to care. Build sessions around doing, not watching. Keep energy high. Pizza helps.
Focus on Tangible Outcomes
Pick the stuff that actually matters right now — don't try to boil the ocean. Rome wasn't built in a day and neither is your SOP library. Start with three to five critical processes and call it a win.
Don't Scrutinize — Collaborate
People get defensive when you ask how they do their job. Reframe it: "I need to understand this so we can make it better together." You catch more flies with curiosity than with a clipboard.
How to Get Started
The AI Kickstart
You know you need SOPs, but where do you even start? The blank page is the hardest part. Here's the move: make AI do the heavy lifting on step one.
Open your favorite AI assistant — Claude, ChatGPT, whatever you have handy — and ask it:
Prompt
"I manage a busy [technology/Salesforce] team. What are the top 10 processes that teams like mine most commonly forget to document as SOPs?"
You'll get a list. Some of it will be obvious, some of it will make you go "oh no, we definitely don't have that." That list is your starting point. Now you have something to prioritize instead of a blank page.
Set Up a Claude Project as Your Camp Counselor
Use a Claude Project (or similar persistent AI workspace) to keep your SOP planning organized. Feed it your existing documentation, a brief about your team structure, and this system prompt from the talk:
Example System Prompt — Slide 13
You are a documentation specialist helping [Organization Name] build and maintain standard operating procedures for our [technology/Salesforce] team. You have been given context about our existing processes, team structure, and tools. When I describe a process, help me format it as a clear SOP with: an overview, any prerequisites, numbered step-by-step instructions, and tips or common pitfalls. Keep language plain and direct — written for someone doing the task for the first time.
Keep this project running. Add your SOPs as you write them. Let the AI help you identify gaps, suggest improvements, and draft new documentation when you describe a process out loud.
The SOP Toolkit
Create it. Share it. Embed it.
Create
Scribe, Tango, Guidde
Turn on the recorder, do the thing, documentation appears. That's it. TL;DR: turn Scribe on → do the process → documentation is created.
Share
Live links, embed codes, direct URLs
Export a live link, text it to your team — yes, you can literally text it to someone. If it's behind a login nobody will use it. Remove friction.
Embed
Salesforce Knowledge, Experience Cloud, SharePoint, Monday.com, WordPress
Meet people where they already work. An SOP in a folder nobody opens is just a really expensive thought experiment.
Scribe SOP Embed — Open Source
Want to embed Scribe SOPs directly into your own site or app? I published a lightweight, open-source tool that makes it dead simple. Drop it in, point it at your Scribe URL, done.
637-Digital/scribe-sop-embedCompliance & Finance Teams
Most screen-capture tools include auto-redaction for sensitive fields. Review your captures before publishing — especially if your processes touch financial data, PII, or credentials.
Accessibility Note
Add alt text to screenshots and images in your SOPs. Screen readers matter. A documented process is only useful if every team member can access it.
SOPs + User Adoption = ROI
You can spend $200k on Salesforce licenses. But if nobody uses them, you wasted $200k.
User adoption is the single most underrated success metric in enterprise software. And the most effective lever for adoption is removing friction — making it easy and obvious for people to do the right thing. Well-written, embedded SOPs do exactly that.
When users can find the answer in 30 seconds inside the tool they're already using, they stop sending the "how do I do this?" Slack message. They stop submitting the same help desk ticket every quarter. They stop recreating workarounds because nobody taught them the right way.
The Scribe Stat
Teams using screen-capture documentation tools like Scribe report answering how-to questions in roughly 3 minutes instead of the typical 10. That's per question, per person, every time it comes up. Multiply that across your team and you have a real number to put in front of leadership.
Your Camp S.O.P. Checklist
Ready to run your own camp? Here's what to actually do this week.
Ask AI for your top 10 undocumented processes
Pick 3–5 that matter most right now (don't boil the ocean)
Schedule a 2–3 hour session with pizza and a hard end time — make it an event
Set up a Scribe (or similar) account and record your first process
Pick ONE place to embed or share it where your users already live
Set a calendar reminder to revisit in 90 days
Want help mapping your tech stack?
If you're trying to figure out what apps you're even managing before you can document them, check out Stackium — it's a tool I built to help teams map and manage their application landscape.
Visit Stackium.techWant to bring this talk to your team or event?
I present Camp S.O.P. all over the country. If your group wants a live session — complete with the activity, the toolkit overview, and yes, ideally pizza — let's talk.
Get In Touch