DEV Community

T.M. Gunderson
T.M. Gunderson

Posted on

Stop Approving Everything: The MTTR Lesson That Cuts Your Bottleneck in Half

A 20-person team at AMP killed mandatory code review. They now ship 15 times per day.

Their principle isn't reckless. It's the opposite: optimize for mean time to recovery, not mean time to failure.

They replaced human gatekeeping with tight scope, automated checks, and 15-minute rollbacks. The result? Faster shipping and fewer catastrophic mistakes.

Here's why this matters for your 10-person business — and how to apply it starting Monday.

You Are the Bottleneck

If you run a small business, you review things that don't need reviewing:

  • Every invoice over $200
  • Every social media post
  • Every customer quote
  • Every schedule change
  • Every refund request

Each one waits for you. Each one is a decision you probably make the same way every time. Each one delays revenue, frustrates your team, and — here's the kicker — doesn't actually prevent most problems.

Code review has the same flaw at scale. Most reviews catch typos, not architectural disasters. The real disasters slip through because they're subtle, and the reviewer is reviewing 400 lines of someone else's code at 5 PM.

The MTTR Framework for SMBs

The AMP team's insight translates directly to small-business operations. Here's the framework:

1. Define the Scope

Not everything needs review. Be explicit about what does.

Software version: Changes under 50 lines to non-critical systems don't need review.

SMB version: Invoices under $500 to existing vendors don't need your sign-off. Neither do social posts following approved templates. Neither do routine refund requests under $100.

Write it down. Make a one-page "auto-approve" list. If you can't articulate the rule, you can't delegate it.

2. Automate the Checks

The AMP team didn't remove review and hope for the best. They replaced it with automated tests that catch the same problems a human would flag — consistently, instantly, and at 3 AM.

Your version: Set up guardrails, not gatekeepers.

  • Use accounting software that flags anomalies (duplicate invoices, unusual amounts, new vendors)
  • Create templates for quotes and proposals with locked fields for pricing and terms
  • Set approval workflows in your tools that auto-route only exceptions to you
  • Configure your AI assistant to check routine work against your documented rules

The checks run every time. They don't get tired. They don't rubber-stamp.

3. Keep Rollback Fast

This is the key insight most people miss. The AMP team ships fast because undoing a mistake is cheap. A 15-minute rollback means a bad deploy costs 15 minutes, not a week of customer complaints.

Build the same for your operations:

  • Refunds: If a refund is under $100, process it immediately. The cost of a wrong refund ($100) is less than the cost of a delayed one (lost customer, bad review, your time).
  • Content: Schedule social posts with a 2-hour review window. If nobody flags it, it goes live. A bad post can be deleted in 30 seconds.
  • Quotes: Give your sales team authority to discount up to 15%. A slightly lower margin beats a lost deal that waited three days for your approval.
  • Scheduling: Let your team reschedule within a defined window. Undo a schedule conflict in seconds, not in a back-and-forth email chain.

4. Stop Reviewing Routine Decisions

This is the hardest part. You built the business by controlling everything. But control isn't the same as quality.

Questions to ask yourself:

  • How many approvals last month did you change from the recommended decision? (If it's under 10%, your review process is theater.)
  • What's the actual cost of a wrong decision in each category? (If the cost is low and reversible, remove the gate.)
  • How much revenue are you losing to approval delays? (Even one day of delay on a quote can lose a deal.)

A Practical Monday-Morning Exercise

  1. List every decision that crosses your desk this week. Every invoice, every post, every email approval.
  2. Sort by volume and risk. High-volume, low-risk decisions are your targets.
  3. For each target, define: the auto-approve rule, the automated check, and the rollback cost.
  4. Implement the rule. Tell your team. Update your tools. Walk away.

You'll free up 2-3 hours per week. Your team will move faster. And the mistakes you do make will be cheap, fast, and reversible — which is exactly where you want them.

The Bottom Line

The AMP team didn't get reckless. They got systematic. They replaced slow, inconsistent human checks with fast, consistent automated ones — and they made sure recovery was cheap.

You can do the same. Every routine approval you remove is a decision you get back. Every automated check you add is consistency you never had. Every fast rollback you build is insurance that lets you move faster.

Stop approving everything. Start approving the things that actually need your judgment. Your business runs better when you're not in the way.


This post is part of SMB Scale Up's series on practical AI and automation for small businesses. Follow for weekly actionable guides.

Top comments (0)