So here's a weird little concept that's been bouncing around productivity circles for a while. The 70 rule basically says you should quit working on something when you're about 70% done. Sounds crazy, right? But the thinking goes that that last 30% of effort usually gives you almost nothing in return - it's just you futzing around with tiny details that nobody cares about. The whole point is to stop trying to make everything perfect and just get stuff done. Honestly? It's kind of liberating once you try it. Look, we've all been there. You spend hours tweaking a presentation slide that already looks fine. Or rewriting the same paragraph five times. The 70 rule just cuts through that nonsense. When you force yourself to stop at 70%, you suddenly have all this mental space for actually doing new things instead of obsessing over old ones. It's like magic for people who juggle a million different projects at once - knowledge workers, creatives, startup types, you know the drill. Here's what you actually get out of it: You can pretty much throw this rule at anything. Project management? Ship it when it's 70% done and let people give feedback. Writing? Get your draft to 70% and then edit like crazy. Software people already do this with MVPs - they ship the bare bones instead of waiting for perfection. Some real-world examples: People mix these up all the time. The Pareto principle - that whole 80/20 thing - is about how most effects come from a few causes. Like 80% of your sales from 20% of customers. The 70 rule is more like a cousin to that idea. It's saying you get most of the value from a task in the first 70% of effort, and after that you're just spinning your wheels. The Pareto principle describes how the world works. The 70 rule tells you when to stop working. Comparison table: Look, this isn't going to happen overnight. You've got to retrain your brain a bit. Start by noticing what tasks you tend to over-polish - we all have them. Then set yourself a timer or a checkpoint at roughly 70% of what you'd normally spend. When you hit that point, just stop. Send it. Share it. Move on. It feels terrible at first, honestly. But eventually you get used to it and realize the world doesn't end when you submit something that's not perfect. Here's your little cheat sheet: Okay so this isn't a magic bullet. Don't use it for brain surgery or flying planes or anything where 70% means someone dies. Same goes for legal contracts, medical stuff, financial reporting - places where mistakes actually matter. The rule works great for creative work, analysis, admin tasks - anywhere the last little bit of polish doesn't add much. But if you need precision, forget it. "The 70 rule is a tool for overcoming perfectionism, not a license for sloppy work. Use it wisely." Yeah, but tread carefully. In teams it helps avoid over-engineering and gets things moving faster. But you need to be super clear about quality expectations or people will get confused. Works best in agile environments where you're constantly iterating anyway. Not really, no. It's more of a practical rule of thumb that people figured out from experience. It lines up with stuff like diminishing returns and the Pareto principle, but nobody's done a proper study on it. That said, lots of smart people swear by it. You get better at estimating over time. Break tasks into steps - if it's 10 steps, step 7 is your cutoff. Or use time - if something usually takes 10 hours, stop at 7. Eventually you just develop a feel for it. Honestly? This is where it shines. Creative people are the worst about over-polishing. Stop when the main idea comes across. That last 30% of tweaking? Your audience won't even notice. Then don't tell them you're using the 70 rule. Just use it internally - get your draft to 70% before reviewing it, or apply it to personal stuff. Some workplaces just demand perfection and you have to work around that.What is the 70 rule of productivity
How does the 70 rule improve efficiency?
What are the practical applications of the 70 rule?
What is the difference between the 70 rule and the Pareto principle?
Aspect
70 Rule
Pareto Principle (80/20)
Focus
When to stop working on a single task
Identifying the most impactful inputs
Application
Time management, task completion
Resource allocation, strategy
Threshold
70% completion point
80% of results from 20% of efforts
Goal
Increase output volume
Increase efficiency and focus
How can I implement the 70 rule in my daily routine?
What are the risks of the 70 rule?
Frequently Asked Questions
Can the 70 rule be used for team projects?
Is the 70 rule based on scientific research?
How do I know when I have reached 70%?
Does the 70 rule apply to creative work?
What if my boss expects 100%?
Short Summary
