What is Rule Number 70? Unpacking the Principles of Effective Communication and Decision-Making

What is Rule Number 70?

Rule number 70 isn’t a universally recognized law, a statutory regulation, or a scientific constant. Instead, it’s a concept that has emerged and gained traction in certain professional circles, particularly those focused on project management, team collaboration, and effective decision-making. At its core, **what is Rule Number 70?** It’s a guiding principle suggesting that achieving 70% of a desired outcome is often sufficient and more efficient than striving for an unattainable 100%, especially when faced with constraints like time, resources, or the inherent complexities of a situation. It’s about recognizing diminishing returns and prioritizing progress over perfection.

I remember a particularly challenging project early in my career. We were developing a new software feature, and the client was notoriously difficult to please, always pushing for “just one more tweak.” We spent weeks, then months, refining tiny details, chasing an elusive 100% perfect user experience. Meanwhile, competing features from other companies were already hitting the market. We ended up launching a product that was technically brilliant, but several months behind schedule and significantly over budget. The feedback? Customers were happy, but they would have been just as happy with a slightly less polished version that arrived on time. That experience hammered home the lesson that sometimes, “good enough” delivered promptly is far more valuable than “perfect” delivered late, or worse, never.

This is where the idea of Rule Number 70 begins to resonate. It’s a pragmatic approach, encouraging teams to identify the critical elements that deliver the most significant value and focus their energy there, rather than getting bogged down in marginal improvements that yield minimal additional benefit. It’s not an excuse for shoddy work, mind you, but rather a strategic lens through which to view project execution and decision-making. It advocates for a mindful allocation of resources, understanding that perfection can often be the enemy of progress.

The Genesis and Context of Rule Number 70

While there isn’t a singular historical figure or documented event that birthed Rule Number 70, its principles are deeply rooted in concepts like the Pareto principle (the 80/20 rule), satisficing theory, and agile methodologies. The Pareto principle, for instance, suggests that roughly 80% of effects come from 20% of causes. Applying this to our context, Rule Number 70 implies that roughly 70% of the desired value or impact can be achieved with a significant portion, but not necessarily all, of the potential effort or resources.

Satisficing, a term coined by Nobel laureate Herbert Simon, describes the tendency to make decisions that are “good enough” rather than perfectly optimal. In complex environments where information is incomplete and time is limited, finding the absolute best solution can be impossible or prohibitively costly. Rule Number 70 aligns perfectly with this, promoting a practical approach that prioritizes achieving a functional and valuable outcome within realistic constraints.

Agile development, with its iterative and incremental approach, also embodies the spirit of Rule Number 70. Instead of aiming for a monolithic, perfect product at the end of a long development cycle, agile teams deliver working software in short sprints, gathering feedback and adapting as they go. Each iteration represents a step towards the final goal, and while each step might not be 100% perfect, it delivers tangible value and moves the project forward efficiently. The emphasis is on continuous delivery and adaptation, rather than a single, grand, perfect launch.

In essence, understanding **what is Rule Number 70** involves grasping its philosophical underpinnings. It’s about embracing pragmatism, valuing efficiency, and making intelligent trade-offs. It’s a recognition that in the real world, perfection is often an illusion, and a substantial, valuable achievement is frequently more beneficial than a never-ending pursuit of an idealized state.

Why Strive for 70%? The Benefits of Practical Perfection

The immediate question that arises when discussing Rule Number 70 is, “Why settle for 70%?” This isn’t about lowering standards or accepting mediocrity. Instead, it’s about understanding the concept of **diminishing returns**. The effort required to go from 70% to 80% is often significantly greater than the effort to get from 0% to 70%. The marginal gains in quality, functionality, or completeness diminish as you approach perfection. By strategically aiming for that 70% mark, teams can often unlock substantial value much more quickly and cost-effectively.

Let’s break down the key benefits of adopting a “70% mindset”:

Accelerated Time-to-Market: In competitive landscapes, speed is often a critical differentiator. Releasing a product or solution that meets 70% of the ideal requirements earlier can capture market share, generate revenue, and provide valuable user feedback that can inform future iterations. The delay incurred in pursuing the final 30% could mean missing the market window entirely.
Optimized Resource Allocation: Human effort, financial capital, and time are finite resources. Rule Number 70 encourages focusing these resources on the highest-impact areas. Instead of spreading efforts thinly to achieve minor improvements across the board, it promotes concentrating on the core functionalities or aspects that deliver the most significant value. This prevents “resource drain” on tasks that offer little return.
Reduced Risk of Scope Creep: The pursuit of perfection can often lead to endless additions and modifications, known as scope creep. By setting a clear target of a high-value, yet attainable, outcome (e.g., 70%), teams can establish boundaries and resist the temptation to continuously add features or refine details beyond what is essential for initial success.
Enhanced Adaptability and Flexibility: A project that is “done enough” can be released and subjected to real-world testing and user feedback. This feedback is invaluable. It allows teams to pivot, refine, and improve based on actual usage rather than theoretical perfection. Striving for 100% upfront can lead to building something that, while perfect in design, might not meet actual user needs once deployed.
Increased Team Morale and Motivation: Constantly chasing an unattainable ideal can be demotivating for teams. Seeing tangible progress and achieving significant milestones (even if not “perfect”) can boost morale and create a sense of accomplishment. Rule Number 70 provides a more realistic and achievable target, fostering a more positive and productive work environment.
Mitigation of Analysis Paralysis: When the pressure is on to achieve absolute perfection, teams can fall into “analysis paralysis,” spending an inordinate amount of time gathering data, debating options, and refining plans without ever taking action. Rule Number 70 provides a clear directive to move forward once a substantial portion of the goal is met.

Consider a marketing campaign. Is it better to spend months agonizing over the perfect slogan, the ideal color palette, and the most statistically impactful ad placement, only to launch it six months late when the market has shifted? Or is it more effective to launch a strong, well-conceived campaign that hits 70% of its theoretical potential within a reasonable timeframe, allowing for real-time adjustments based on performance metrics? The latter often proves more fruitful.

My own experiences as a project manager have repeatedly validated this. I’ve seen projects stall indefinitely because the team was obsessed with a feature’s edge cases or a UI element’s subtle shading. When we shifted focus to delivering the core functionality and a solid user experience (the “70%”), we often found that users were delighted with the progress, and the remaining “enhancements” became less critical or were re-prioritized based on actual feedback. It’s a delicate balance, certainly, but one that can lead to more impactful outcomes.

When to Apply Rule Number 70: Identifying the Right Context

Understanding **what is Rule Number 70** is only half the battle; knowing *when* to apply it is crucial. It’s not a blanket rule to be applied indiscriminately to every task or project. Certain situations and environments lend themselves far better to this pragmatic approach than others.

High-Complexity, High-Uncertainty Environments

In fields like cutting-edge research, innovative product development, or complex system integration, the path to a perfect outcome is often unclear. There are many unknowns, and the requirements themselves may evolve as understanding deepens. In such scenarios, aiming for an exact 100% from the outset is often futile. Rule Number 70 encourages making significant progress, gathering data, and learning from the process, which then informs the next steps. It’s about navigating ambiguity with practical steps rather than trying to map out a flawless route in advance.

Projects with Strict Deadlines and Limited Resources

When faced with immovable deadlines or tight budgets, the luxury of pursuing perfection is often unavailable. Rule Number 70 becomes a necessity for survival. It forces a prioritization of what truly matters and what can be achieved within the given constraints. The question shifts from “Can we make it perfect?” to “What is the most valuable outcome we can deliver within these limitations?”

Iterative Development and Agile Methodologies

As mentioned earlier, agile frameworks are inherently aligned with the spirit of Rule Number 70. The very nature of sprints, incremental delivery, and continuous feedback loops means that each iteration aims to deliver a usable, valuable increment of the product. Each increment is “done enough” to be potentially releasable, contributing to the overall goal without necessarily being the final, perfect version.

Situations with Significant Diminishing Returns

There are many instances where the effort required to achieve the last few percentage points of quality or completeness yields a disproportionately small increase in value or usability. This is particularly true in software development, user interface design, and even certain manufacturing processes. Identifying these points of diminishing returns is key to knowing when to deem a deliverable “70% done” and move on.

When User Feedback is Critical for Refinement

For many products and services, especially in consumer markets, the ultimate measure of success is user satisfaction. Building a perfectly engineered product in isolation can be a risky endeavor. Releasing a product that meets the core needs (the 70%) and then refining it based on actual user behavior and feedback is often a more robust strategy than attempting to anticipate every user preference upfront.

Areas Where “Good Enough” is Sufficient

Not every undertaking requires absolute perfection. Internal tools, prototypes for testing concepts, or solutions for non-critical processes might not warrant the expenditure of time and resources to reach an idealized state. In these cases, a functional solution that meets the primary requirements (70%) can be perfectly adequate and significantly more efficient to implement.

When Not to Apply Rule Number 70

It’s equally important to recognize situations where Rule Number 70 should *not* be the primary guiding principle:

Safety-Critical Systems: Applications where failure can lead to severe injury, loss of life, or catastrophic damage (e.g., medical devices, aircraft control systems, nuclear power plant software) demand the absolute highest standards of quality and rigor, often far exceeding 70%.
Legal and Regulatory Compliance: Situations requiring strict adherence to legal mandates or industry regulations typically leave little room for compromise. The “70% solution” might be non-compliant and carry significant legal or financial repercussions.
Foundational Infrastructure or Core Architecture: When building the fundamental components upon which much else will rely, the integrity and robustness of the initial build are paramount. Weak foundations (less than 70% of ideal) can lead to cascading problems later.
Situations with High Emotional or Reputational Stakes: For projects where public perception, brand reputation, or significant emotional impact is involved, the drive for excellence and near-perfection might be non-negotiable.

My role as a consultant has often involved advising teams on these very trade-offs. I’ve had to gently steer clients away from the “70% solution” when the consequences of even a minor failure were too high, and conversely, help them embrace it when the pursuit of perfection was a clear impediment to progress and value delivery.

Implementing Rule Number 70: A Practical Framework

So, if we’ve accepted that **what is Rule Number 70** and when it might be applicable, the next logical step is to understand how to implement it effectively. This isn’t about throwing caution to the wind; it requires careful planning, clear communication, and a disciplined approach. Here’s a practical framework:

Step 1: Define the “70% Outcome”

This is the most critical step. You need to clearly articulate what “70%” means in the context of your specific project or task. It’s not just a feeling; it needs to be a tangible definition.

Identify Core Value Drivers: What are the absolute essential features, functionalities, or aspects that will deliver the most significant value to the end-user or stakeholder? These are your “must-haves.”
Prioritize Ruthlessly: Use techniques like MoSCoW (Must have, Should have, Could have, Won’t have) or value-effort matrices to distinguish between essential components and desirable enhancements.
Quantify Where Possible: Can “70%” be translated into metrics? For example, “70% of core user workflows are functional,” or “70% of critical bugs are resolved.”
Establish Acceptance Criteria: Define what success looks like at the 70% level. What are the non-negotiables for this stage?

Step 2: Estimate the Effort and Identify Diminishing Returns

Once you know what “70%” looks like, you need to understand the effort involved in reaching it versus the effort to get to 100%.

Map the Effort Curve: For key tasks or features, try to estimate the effort required to achieve different levels of completion (e.g., 50%, 70%, 85%, 95%, 100%). Visualizing this can highlight where the effort spikes dramatically for small gains.
Benchmark and Learn: If possible, look at past projects or industry benchmarks to understand typical effort curves for similar tasks.
Consult Subject Matter Experts: Their experience can be invaluable in identifying where perfection becomes overly costly.

Step 3: Communicate and Gain Buy-In

Implementing Rule Number 70 requires transparency and agreement from all stakeholders.

Explain the Rationale: Clearly articulate why this approach is being taken – the benefits of speed, efficiency, and pragmatic value delivery. Address concerns about quality upfront.
Define the Scope of “70%”: Ensure everyone understands what the target outcome entails and what is being deliberately deferred or simplified.
Manage Expectations: Be clear that this is a strategic decision, not an excuse for poor quality. Reassure stakeholders that feedback loops will be in place for future improvements.

Step 4: Execute with Focus and Discipline

This is where the rubber meets the road. Stick to the defined 70% target.

Timeboxing: Set firm deadlines for achieving the 70% target.
Iterative Development: If applicable, break down the work into smaller cycles, aiming for 70% completion of each cycle’s goals.
Resist “Just One More Thing”: Empower the team to say no to scope creep that pushes beyond the 70% target, especially if it jeopardizes the deadline or core objectives.
Focus on Core Quality: While not aiming for 100%, ensure the 70% delivered is robust, functional, and meets the defined acceptance criteria. This isn’t about cutting corners on essentials.

Step 5: Gather Feedback and Iterate

Once the 70% outcome is achieved, the work isn’t necessarily over, but the approach changes.

Deploy and Observe: Get the product or solution into the hands of users or stakeholders.
Collect Feedback Systematically: Implement mechanisms for gathering structured feedback on what’s working, what’s missing, and what could be improved.
Prioritize Next Steps: Based on feedback and evolving business needs, prioritize what to tackle next. This might involve addressing some of the deferred 30% or refining the initial 70%.

I once guided a startup through the launch of their initial product. They were burning through cash and facing immense pressure. We collectively defined the “minimum viable product” as their “70% solution.” It had the core features, a functional interface, and addressed the primary user pain point. We launched it within their funding runway. The market reaction was positive, and the feedback they received was instrumental in shaping their next development sprints, allowing them to build precisely what their users needed, rather than what they *thought* they needed in a vacuum. It was a classic demonstration of Rule Number 70 in action.

Rule Number 70 vs. Other Efficiency Principles

It’s helpful to contextualize Rule Number 70 by comparing it to other well-known principles of efficiency and quality.

Rule Number 70 vs. The Pareto Principle (80/20 Rule)

The Pareto principle states that roughly 80% of effects come from 20% of causes. Rule Number 70 can be seen as a practical application or extension of this. If 80% of the value comes from 20% of the effort, then perhaps achieving 70% of the total desired outcome is a realistic and efficient target, focusing on that high-leverage 20% of effort to get a substantial chunk of the value. While Pareto focuses on the *inputs* (causes) and their impact, Rule Number 70 focuses more on the *output* (outcome) and what level of completion is practically valuable.

Rule Number 70 vs. Minimum Viable Product (MVP)

The concept of an MVP, popularized by Lean Startup methodology, is very closely aligned with Rule Number 70. An MVP is the version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort. It’s about building just enough to test a core hypothesis and gather feedback. Often, an MVP represents the “70% solution” that can be released to learn and iterate. The key difference might be in emphasis: MVP is heavily focused on *learning and validation*, while Rule Number 70 is more broadly about *efficient value delivery* which can encompass learning but also timely completion in non-startup contexts.

Rule Number 70 vs. Satisficing

Satisficing, as mentioned earlier, is about finding a solution that is “good enough” rather than the absolute best. Rule Number 70 provides a potential heuristic for satisficing. Instead of searching exhaustively for the “best” solution, one might aim for a “70% solution” that meets the most critical criteria and is achievable within constraints. It’s a practical decision-making strategy to avoid perpetual optimization.

Rule Number 70 vs. “Perfection is the Enemy of Good”

This adage directly encapsulates the essence of Rule Number 70. It warns that the relentless pursuit of perfection can prevent us from achieving something that is already good and functional. Rule Number 70 operationalizes this by suggesting a specific, albeit flexible, target (70%) that represents a “good” outcome, encouraging us to stop before perfection becomes counterproductive.

I’ve found that understanding these connections helps teams embrace the concept. It’s not a radical new idea, but rather a distillation of effective practices that have been around for a while. It’s about giving a name and a framework to something many experienced professionals intuitively do.

Common Pitfalls and How to Avoid Them

While the logic behind Rule Number 70 is sound, its application can be fraught with challenges. Being aware of these potential pitfalls can help teams navigate them successfully.

Misinterpreting “70%” as “Low Quality”: This is perhaps the most common and damaging misinterpretation. Rule Number 70 is not an invitation to be sloppy. The delivered 70% must be functional, reliable within its scope, and meet the defined acceptance criteria. The effort saved is in perfecting the edges, not in compromising the core.

Mitigation: Rigorous definition of the 70% outcome, clear acceptance criteria, and a focus on core quality assurance for the delivered components.

Scope Creep Beyond 70%: Once a project reaches the defined 70% target, the temptation to add “just a few more things” can be strong, especially if stakeholders see the progress. This negates the efficiency gains.

Mitigation: Strict change control processes, clear communication about what the 70% entails, and a disciplined project management approach.

Inadequate Definition of “70%”: If the target is vague, teams may struggle to know when they’ve reached it, leading to continued overwork or an incomplete delivery.

Mitigation: Invest significant time in Step 1 of the implementation framework – defining the 70% outcome with clear, measurable criteria.

Applying to Inappropriate Situations: Using Rule Number 70 in contexts like safety-critical systems or strict regulatory environments can have severe consequences.

Mitigation: Thoroughly assess the project’s nature, risks, and requirements before deciding if Rule Number 70 is an appropriate guiding principle.

Lack of Stakeholder Buy-In: Without proper communication and agreement, stakeholders may feel that the team is cutting corners or not delivering a complete solution, leading to dissatisfaction and distrust.

Mitigation: Proactive and transparent communication, emphasizing the strategic benefits and clearly outlining the phased approach.

Difficulty in Identifying Diminishing Returns: It can be challenging to accurately predict when further effort yields diminishing returns, especially in novel projects.

Mitigation: Leverage historical data, expert opinions, and an iterative approach where feedback helps calibrate the understanding of diminishing returns.

In my experience, the most successful applications of Rule Number 70 involve a strong project manager or team lead who champions the principle, educates the team and stakeholders, and enforces the boundaries. It requires a culture that values pragmatism and results alongside quality.

Real-World Examples and Case Studies

To further illustrate **what is Rule Number 70**, let’s look at some hypothetical, yet illustrative, real-world scenarios:

Scenario 1: Software Feature Development

Project: A company is developing a new feature for its popular mobile application. The marketing team wants it launched before a major holiday season to capitalize on increased user engagement.

The Challenge: The engineering team estimates that achieving 100% of the originally envisioned polish, including extensive edge-case handling and a highly nuanced user interface animation, would push the launch date three weeks past the holiday window.

Applying Rule Number 70: The team defines the “70% outcome” as delivering the core functionality of the feature, ensuring it’s stable, intuitive for 90% of common use cases, and meets all critical user paths. The remaining 30% might involve perfecting the animations, adding support for obscure device settings, or implementing a niche accessibility feature that a small subset of users might need.

Outcome: The feature is launched in time for the holiday season, meeting the marketing objectives. Early user feedback confirms that the core functionality is well-received. The team then uses the feedback to prioritize the remaining 30% for subsequent updates, potentially discovering that some initially planned refinements were not as important as other emerging user needs.

Scenario 2: Product Launch in a Competitive Market

Company: A startup is launching a new smart home device. A major competitor is expected to release a similar product around the same time.

The Challenge: The startup’s product has undergone extensive internal testing and boasts a level of feature integration that, while impressive, took considerable time to develop. Achieving full certification from all international bodies and perfecting the packaging design for every global market would delay the launch by two months.

Applying Rule Number 70: The “70% outcome” is defined as achieving core product functionality, passing essential safety and performance certifications for the primary target market (e.g., North America), and having a clean, functional packaging design. The deferred 30% might include certifications for secondary markets, minor aesthetic tweaks to the packaging based on subjective feedback, or advanced integration with a few less common third-party smart home ecosystems.

Outcome: The startup launches its product concurrently with or even slightly ahead of the competitor. They capture initial market share and gather valuable data on customer adoption and preferences. They can then use this momentum and learning to pursue further certifications and market expansions more strategically.

Scenario 3: Internal Process Improvement

Organization: A large corporation is looking to streamline its internal expense reporting process.

The Challenge: The IT department has identified several potential software solutions, but achieving a perfectly integrated system that accommodates every single legacy exception and department-specific quirk would require a year-long project with significant custom development.

Applying Rule Number 70: The “70% solution” is to implement a standard, off-the-shelf expense reporting system that handles 70-80% of all typical expense submissions efficiently. This includes standard reimbursement, common approval workflows, and integration with the main HR system. The deferred 30% might include highly specialized workflows for international travel, rare expense categories, or direct integration with niche accounting software used by a single department.

Outcome: The new system is implemented within six months, significantly reducing processing time and errors for the majority of employees. The organization benefits from the efficiency gains immediately. The IT department can then address the remaining 30% of exceptions in subsequent phases, prioritizing based on actual user requests and business impact, rather than trying to build a perfect, all-encompassing system from day one.

These examples highlight how Rule Number 70 encourages a focus on delivering substantial value quickly, recognizing that further refinement can often be done more effectively once the core is established and validated.

Frequently Asked Questions about Rule Number 70

What are the biggest risks associated with implementing Rule Number 70?

The biggest risks revolve around misinterpretation and the potential for a genuine decline in quality or user satisfaction. If “70%” is understood as “barely functional” or “rushed,” the project could fail. Another significant risk is scope creep; once the initial 70% is achieved, stakeholders might still push for more without a clear plan for subsequent phases, essentially turning a planned 70% delivery into an incomplete 100% that was never properly defined. Furthermore, if the identified “70%” doesn’t actually capture the most critical aspects of value, then achieving it won’t be very impactful.

There’s also the risk of organizational inertia. If a company culture is deeply ingrained with a “perfectionist” mindset, introducing Rule Number 70 might be met with resistance or suspicion. Teams might fear reprimand for not delivering “100%,” even if the 70% target was agreed upon. This requires strong leadership and consistent communication to overcome. Finally, for complex projects, accurately identifying the point of diminishing returns can be challenging, leading teams to either stop too early or continue too long, missing the intended efficiency.

How can I ensure that the “70% solution” is still high-quality?

Ensuring high quality at the 70% level is paramount. It begins with a very clear and precise definition of what “70%” means in terms of functionality, performance, and user experience. This involves:

Defining Core Value: Clearly identifying the essential features and functionalities that deliver the most significant value to the user or business. The 70% must encompass these.
Establishing Robust Acceptance Criteria: Just because you’re aiming for 70% doesn’t mean you skip quality checks. Define rigorous acceptance criteria for the core components that must be met. This includes functionality, usability, performance, and security for the delivered scope.
Prioritizing Essential Testing: Focus testing efforts on the core functionalities and critical user paths. Ensure that the elements making up the 70% are thoroughly tested and stable.
Using Proven Practices: Employ sound engineering and design principles. Even if you’re not perfecting every minute detail, the fundamental architecture, code quality, and user flow should be sound.
Seeking Expert Review: Have subject matter experts review the 70% delivered solution to ensure it meets the essential requirements and is built on a solid foundation.

The goal is not to deliver a buggy or incomplete product, but a complete and functional solution that addresses the primary needs, leaving the less critical enhancements or perfect polish for later stages. It’s about smart trade-offs, not cutting corners on the essentials.

Is Rule Number 70 only applicable to software development or tech projects?

Absolutely not. While the principles of Rule Number 70 often find a natural home in agile software development due to its iterative nature, its applicability extends far beyond the tech industry. Think about:

Product Design and Manufacturing: A consumer electronics company might aim to get 70% of its new product’s features and performance to market on time, deferring some advanced, less critical functionalities or aesthetic refinements for a later version 1.1 release.
Construction and Engineering: In large infrastructure projects, completing 70% of the core structural work and essential utilities to a functional standard might allow for earlier occupancy or use, even if final landscaping or aesthetic finishes are phased in later.
Marketing Campaigns: A marketing team might launch a campaign with its primary messaging and channels (70% effectiveness) to test the market, rather than waiting months to perfect every single advertisement and social media post.
Research and Development: Scientists might publish preliminary findings or a proof-of-concept that demonstrates 70% of their hypothesis is supported, rather than waiting years to achieve absolute certainty or explore every possible variable.
Event Planning: For a large conference, having 70% of the keynotes, venue logistics, and core attendee experience confirmed and functional allows for ticket sales and marketing to begin, even if the final breakout session speakers or minor amenities are still being finalized.

Essentially, any project or endeavor that faces constraints of time, budget, or complexity, and where incremental value delivery is beneficial, can potentially benefit from the strategic application of Rule Number 70.

How do you communicate the concept of Rule Number 70 to stakeholders who expect 100%?

Communicating Rule Number 70 effectively requires tact, clarity, and a focus on benefits. Here’s a breakdown of strategies:

1. Frame it as a Strategic Decision, Not a Compromise: Instead of saying “We can only deliver 70%,” explain it as “To deliver maximum value by [deadline/budget], we will focus on achieving the critical 70% of outcomes first, which will provide [specific benefits like faster market entry, immediate cost savings, etc.].” Emphasize that this is a deliberate choice for efficiency and impact.

2. Clearly Define the “70%” and the “Remaining 30%”: Be explicit about what constitutes the 70% outcome. What core features will be delivered? What problems will be solved? Equally important, articulate what is being deferred (the 30%) and why. This transparency builds trust and manages expectations. For example, “This initial release will include the core reporting engine and user management (our 70%), which addresses 80% of our users’ immediate needs. The advanced analytics dashboard and third-party integrations will be part of Phase 2.”

3. Highlight the Benefits: Focus on the tangible advantages of this approach:

Speed to Market: “Launching sooner allows us to capture early adopters and gain a competitive edge.”
Cost Efficiency: “By focusing resources on the core, we avoid unnecessary expenditure on features that might not be highly valued.”
Risk Mitigation: “Getting a functional product out allows us to gather real-world feedback, reducing the risk of building the ‘wrong’ 100%.”
Iterative Improvement: “This phased approach enables us to continuously improve based on actual user data.”

4. Use Analogies: Relate it to concepts they might already understand, like the MVP in startups or the idea of building a house with essential utilities before the final cosmetic touches.

5. Establish a Clear Roadmap for the “Remaining 30%”: Assure stakeholders that the deferred items are not forgotten. Provide a clear roadmap or backlog for future iterations, outlining how and when the remaining value will be delivered. This demonstrates a commitment to completeness, albeit in phases.

6. Listen and Address Concerns: Be prepared for questions and concerns about quality. Actively listen to their perspective and address any doubts by reiterating the quality standards for the 70% delivered scope and the benefits of the phased approach.

By framing Rule Number 70 as a strategic, benefit-driven approach rather than a compromise on quality, you can effectively gain stakeholder buy-in and ensure successful implementation.

What is the difference between Rule Number 70 and simply cutting corners?

The fundamental difference lies in intent, planning, and scope definition. Cutting corners is often a reactive, unplanned decision driven by a desire to save time or money without a clear understanding of the consequences. It can involve skipping necessary steps, using substandard materials, or neglecting essential quality checks, leading to a product or outcome that is genuinely flawed and potentially unreliable.

Rule Number 70, on the other hand, is a *strategic* approach. It is characterized by:

Deliberate Planning: The “70%” is carefully defined. The team identifies the core value drivers and decides, with full awareness, which aspects can be deferred or simplified.
Focus on Core Value: The “70%” delivered is designed to be fully functional and valuable in its own right, addressing the most critical needs. It’s not about delivering a partial solution, but a complete solution to a defined set of core requirements.
Awareness of Diminishing Returns: The decision to stop at 70% is often based on the understanding that the effort required to reach 100% yields disproportionately small additional benefits.
Phased Approach: Rule Number 70 implies a plan for future enhancements or completion. The “remaining 30%” is acknowledged and often planned for in subsequent phases, based on feedback and evolving priorities.
Quality Control: While not aiming for absolute perfection, the 70% delivered must meet defined quality standards for its scope. Essential quality assurance steps are not skipped; they are applied to the core components.

In essence, cutting corners often leads to a compromised and potentially failed outcome. Rule Number 70, when implemented correctly, leads to a functional, valuable outcome delivered efficiently, with a clear path for future development. It’s the difference between strategically aiming for a significant milestone and haphazardly rushing to the finish line.

Conclusion: Embracing Pragmatic Progress

Understanding **what is Rule Number 70** is about embracing a powerful philosophy: pragmatism in the face of complexity. It’s a recognition that in many real-world scenarios, the pursuit of an unattainable 100% perfection can be a significant impediment to progress, efficiency, and ultimate success. By strategically aiming for and delivering a substantial portion of the desired outcome – that “70%” – teams can accelerate delivery, optimize resource allocation, mitigate risks, and foster adaptability.

It’s crucial to remember that Rule Number 70 is not an endorsement of mediocrity or a license to be careless. Instead, it’s a call for intelligent prioritization, a keen understanding of diminishing returns, and disciplined execution. When applied thoughtfully, with clear definitions, robust communication, and a focus on core value, this principle can unlock significant advantages, allowing individuals and organizations to move forward with impactful solutions, rather than remaining stalled in the pursuit of an often-elusive ideal.

My own journey through various projects has continually reinforced the wisdom of this approach. The lessons learned from striving for perfection and then learning to embrace “progress over perfection” have been invaluable. Rule Number 70 provides a framework for making those difficult, yet often necessary, trade-offs, paving the way for more effective, efficient, and ultimately, more successful outcomes.