The ProcOps Manifesto: Fast Process Operations

 Mission Statement

​We've seen too many organizations get stuck in endless process improvement cycles, drowning in documentation and frameworks while their actual work gets slower and more frustrating. There's a better way.
ProcOps is about making your processes faster through rapid iteration, not perfect planning.

Core Values

We value:

Working processes over perfect documentation - A process that works beats a perfectly documented process that doesn't.
Fast iteration over comprehensive planning - Change things quickly, measure what happens, change them again.
Getting things done over following frameworks - Results matter more than methodology compliance. Exception: follow standards for data collection - wrong data means wrong decisions.
Real data over opinions - Look at what actually happens, not what people think happens.
Ownership over committees - One person fixes it, everyone else gets out of the way.

The ProcOps Principles

Make It Fast:
1. Someone owns every changes - One person can change it and owns the results. For processes affecting multiple teams, they coordinate changes but don't need approval.
2. Change it this week - If a process sucks, fix it now. Don't wait for the next planning cycle.
3. Measure everything that matters - Track what actually affects your customers and your business. Ignore vanity metrics.
4. Kill broken processes - If it's not working after three attempts to fix it, delete it and try something completely different.

Learn Fast:
5. Watch what really happens - Sit with people doing the work. Your process documentation is probably wrong.
6. Try small changes first - Change one thing, see what happens, then change the next thing.
7. Automate the boring stuff - If people are doing the same thing over and over, a computer should do it instead.
8. Fix the biggest pain point first - Ask your team what's most frustrating. Start there.

Keep It Simple:
9. Less handoffs, more ownership - Every handoff is a place for things to break. Eliminate them.
10. Make problems visible - When something breaks, everyone should know immediately.
11. Document what's essential - Keep documentation minimal but don't skip it. Document decisions, key steps, and how to recover from failures.
12. Standard tools, custom solutions - Use boring technology that works. Get creative with how you use it.

Stay Focused:
13. Fix the work, not the people - Bad processes make good people look incompetent. Fix the process.
14. Everyone can suggest fixes - The person doing the work knows what's broken. Listen to them.
15. Ship improvements weekly - If you're not making your processes better every week, you're falling behind.

How to Start

Week 1: Find the Pain

• Ask your team what's most frustrating
• Pick the one thing that wastes the most time
• Watch someone actually do the work
• Write down what really happens (not what's supposed to happen)

Week 2: Fix Something Small

• Change one step in the process
• If it affects other teams, let them know what you're changing and why
• Measure if it helped

Week 3: Go Bigger

• If the small change worked, do more of it
• If it didn't work, try something different
• Start tracking how long things take
• Fix the next biggest pain point

Month 2: Build Momentum

• Get other people suggesting fixes
• Set up automatic tracking for key metrics
• Kill at least one stupid rule or approval step
• Start automating repetitive tasks

Month 3: Scale What Works

• Teach other teams how to fix their own processes
• Share what you've learned
• Focus on fixing problems that affect customers
• Keep measuring and iterating

What Good Looks Like

Your processes are working when:

• Things get done faster than they used to
• People complain less about bureaucracy
• New employees can figure out how to do things quickly
• You're fixing problems before customers notice them
• Your team suggests improvements instead of just complaining

Red flags that you're doing it wrong:

• You're spending more time documenting processes than improving them
• Changes take weeks or months to implement
• People are working around the official process
• You have more process managers than people doing actual work
• Your metrics look good but customers are still unhappy

Tools That Actually Help

For Small Teams (< 50 people)

• Shared documents for quick updates
• Simple project management tools
• Basic automation (scripts, webhooks)
• Direct communication channels

For Bigger Organizations

• Workflow automation platforms
• Real-time dashboards
• Process mining tools (to see what actually happens)
• API integrations between systems

Don't Overthink It

• Start with whatever tools you already have
• Upgrade only when current tools become the bottleneck
• Choose tools that non-technical people can use
• Avoid anything that requires training to use

Measuring Success

Track These Numbers:

• How long things actually take (not estimates)
• How often things break or get stuck
• Customer satisfaction with your processes
• How quickly you can implement changes
• How often people bypass the official process

Weekly Questions:

• What took longer than expected this week?
• What frustrated our team the most?
• What frustrated our customers the most?
• What one change would make next week better?

Monthly Questions:

• Are we getting faster or slower?
• Are we fixing problems before they affect customers?
• Are people working around our processes?
• What should we stop doing entirely?

Common Mistakes

Don't Do This:

• Spend months planning before changing anything
• Require committee approval for small changes
• Skip documentation entirely
• Try to fix everything at once
• Copy another company's processes exactly
• Wait for perfect data before making decisions
• Change cross-team processes without communication

Do This Instead:

• Change something small this week
• Let process owners make decisions quickly
• Document essential information concisely
• Fix the biggest problem first
• Build processes that fit your specific situation
• Make decisions with good enough data
• Coordinate changes that affect multiple teams

The Bottom Line

ProcOps isn't about following a methodology. It's about making your work faster and less frustrating through constant, rapid improvement.
If your processes aren't getting better every week, you're not doing ProcOps. You're just managing processes.

Start today:

1. Pick one thing that sucks
2. Try to fix it this week
3. Measure if it worked
4. Do it again next week

That's it. Everything else is just details.

Make it work. Make it fast. Make it better. Repeat.

This document is copyrighted Noah Liot - 2025 - It is free to use for any organisation, anywhere, forever. Quotes and derivative work must cite this original article as The ProcOps Manifesto: Fast Process Operations by Noah Liot