Hello Reader,

My product roadmap started with three clear phases. Then marketing requested one automation. Sales needed a dashboard feature. Operations wanted a process update. Leadership suggested an innovative integration.

Six months later, I was still in phase one. Nothing had shipped. My team was exhausted. I'd become a product therapist, managing expectations instead of executing the plan we all agreed on.

The problem wasn't that the requests were bad. It's that I never defined when to stop accepting them.

This happens everywhere—at work, in relationships, with time and commitments. You recognize the pattern: reasonable requests accumulate until progress stops. The issue isn't saying no more often. It's deciding boundaries before pressure arrives.

That's the Stop Rule, and most people miss what makes it powerful. It's not about saying no more often. It's about deciding your boundaries before the pressure starts, when you're thinking clearly instead of reacting to whoever just walked into your office.

This mental model is part of Re:Mind, my toolkit for clearer thinking in a world where other people's priorities constantly try to override yours. Understanding when to stop isn't about being rigid—it's about protecting your ability to finish what matters.

Why Use It

Stop Rules are pre-commitment devices that remove decisions from moments when you're least capable of making them clearly.

Without predetermined boundaries, you're vulnerable to what behavioral economists call boundary erosion—the gradual compromise of limits through small, individually reasonable concessions. The first feature request seems harmless. So does the second. By the tenth, your scope has doubled, and your ship date has vanished.

Gerald Loeb's clients survived the 1929 crash because of one Stop Rule: "Sell any investment that loses 10% of its value." Not 11%. Not "let's see if it recovers." Ten percent, then sell. No deliberation occurred when losses were mounting and emotions were at their highest.

Mountaineers use the same principle. If you haven't summited by 2 PM, you turn around—even if you're 100 meters from the top. In 1996, climbers on Everest broke this rule. They were so close. Just a little further. Eight people died because proximity to completion overrode their predetermined limit.

Technology teams face identical pressure. You're 80% through phase one. Just one more feature would make it complete. Then one more feature would make it really complete. The Stop Rule breaks this pattern by deciding the boundary before completion bias takes over.

When to Use It

Use Stop Rules whenever you're setting up work where scope creep is predictable—which is almost always.

You're planning any multi-phase initiative. Before starting, define what each phase includes and excludes. Your Stop Rule: "Phase one delivers X, Y, Z. Requests received during execution are assigned to phase two or three."

You notice you're spending more time negotiating scope than executing. That's the signal. You've become a boundary negotiator instead of a boundary enforcer. Time to set Stop Rules that remove negotiation from the equation.

Your team's service mentality is preventing delivery. Everyone wants to help. Everyone wants to accommodate. The intention is good. The outcome is that nothing ships well. Stop Rules define what "helpful" actually means: delivering what you committed to.

How to Use It

In 127 Hours, Aron Ralston's arm is trapped by a boulder in a remote canyon. He exhausts every option to free himself over five days—chipping at the rock, rigging pulleys, rationing water. When his resources hit critical levels, his predetermined survival rule activates: "If still trapped with less than a day's water remaining, cut the arm." The Stop Rule—set when he could think clearly about survival math—saves his life when he's least capable of rational deliberation.

Here's how to implement Stop Rules for work boundaries:

• Identify the decision you're making repeatedly. "Should we add this feature to the current phase?" "Should we extend the timeline to accommodate this request?" These recurring decisions signal where you need a Stop Rule.
• Create the rule before pressure arrives. Not during the meeting when someone is requesting the feature. Not when you're 90% done. Before phase one starts. "New feature requests received during a phase are automatically assigned to the next phase."
• Make it unconditional. No "unless it's really important" clauses. No "except for strategic initiatives" exceptions. Those caveats are where boundaries collapse. The rule holds or it doesn't exist.
• Distinguish boundaries from preferences. Non-negotiable Stop Rule: "This phase locks on [date] and nothing new enters." Negotiable guideline: "We prefer to avoid changes after kickoff but can accommodate critical items if we extend the timeline accordingly."
• Communicate the rule externally. Share it with stakeholders. Put it in the documentation. When requests arrive, you're not rejecting them personally—you're applying a rule everyone already knows exists.

Next Steps

Select one project that will start within the next month. Before it begins, write down your Stop Rule. Make it specific: "Phase one delivers [x] by [date]. Any changes after [date] will be evaluated for the next iteration."

Share the rule with your team, stakeholders, or just you. When the first request arrives that violates the boundary, apply the rule. Don't deliberate. Don't make exceptions. The decision was already made.

Where It Came From

Gerald Loeb's 10% rule protected investors during the 1929 crash: sell any investment that loses 10% of its value, without question. His Stop Rule removed emotion from the decision. Medical researchers adopted similar frameworks, ending trials based on predefined effects rather than continuing them indefinitely. Mountaineers formalized turnaround times after deadly consequences from summit fever. Kathleen Eisenhardt and Donald Sull documented these patterns in "Simple Rules," showing that predetermined boundaries outperform case-by-case deliberation under pressure. The framework works because it defeats the sunk-cost fallacy (the tendency to keep investing). After all, you've already invested so much.

Until next time, keep questioning. Your mind is the last territory you truly control.

Think Independently, JC

​Share or Join 👉

• Download the Re:Mind App.
• Get insights from me on Instagram or Linkedin.
• Share this newsletter with a friend.