Executives ask me the same question every time: “How long will this take?” They want a number. A milestone. A date they can put in a board presentation. The honest answer is uncomfortable: orthodoxy-smashing timelines depend entirely on what you’re challenging and how entrenched it is.
Orthodoxy-smashing timelines range from 30 days for operational quick wins to 365+ days for fundamental business model transformations. The timeline depends on orthodoxy type, organizational complexity, and whether you’re challenging internal assumptions or industry-wide beliefs.
After leading transformations at Berkshire Hathaway, Illinois Tool Works, and Whirlpool Corporation, I developed The 30-90-365 Timeline Model to help leaders set realistic expectations and sequence initiatives appropriately.
What Can You Achieve in 30 Days?
In 30 days, you can identify and challenge operational orthodoxies—internal assumptions about processes, approvals, and resource allocation that exist because “we’ve always done it this way.” These quick wins build momentum and demonstrate that orthodoxy-smashing produces results.
Operational orthodoxies are the lowest-hanging fruit. They don’t require customer buy-in, competitive repositioning, or technology investment. They only require leadership permission and organizational willingness to stop doing things that don’t make sense.
Examples of 30-day wins include eliminating approval layers that add time but not value, stopping reports nobody reads, canceling meetings that produce nothing, and removing process steps that exist only from habit. According to Harvard Business Review research, organizations waste significant resources on activities nobody would design if starting fresh.
The 30-day timeline works because these orthodoxies have no external dependencies. You’re not waiting for customers to accept new approaches or markets to shift. You’re simply stopping organizational dysfunction. The only barrier is internal willingness.
What Can You Achieve in 90 Days?
In 90 days, you can challenge customer-facing orthodoxies through rapid experimentation—testing whether assumptions about what customers want, how they buy, and what they’ll accept are actually true. This phase validates or invalidates beliefs before major investment.
The 90-day timeline allows for proper customer research, prototype development, pilot testing, and iteration based on feedback. It’s long enough to generate meaningful data but short enough to maintain organizational focus and prevent scope creep.
McKinsey research on rapid experimentation shows that 90-day cycles produce better innovation outcomes than longer planning horizons. The constraint forces prioritization and prevents analysis paralysis.
Examples of 90-day initiatives include testing new pricing models with willing customers, piloting service delivery alternatives, experimenting with channel approaches, and validating product simplification hypotheses. Each test challenges a specific customer assumption with real market data.
What Requires 365 Days or More?
Business model transformations and industry-wide orthodoxy challenges require 365 days or more to implement fully. These initiatives involve repositioning value propositions, building new capabilities, and changing how markets perceive your organization—none of which happens quickly.
The extended timeline reflects external dependencies. Customers need time to understand and accept new approaches. Sales forces need retraining. Systems need rebuilding. Partners need renegotiation. Each dependency adds weeks or months to total timeline.
According to MIT Sloan research on business model innovation, successful transformations typically show results in 18-36 months. Promises of faster transformation usually reflect either limited scope or unrealistic expectations.
The 365-day timeline isn’t a single initiative—it’s a sequence of 30-day and 90-day initiatives that compound into transformation. Quick wins build credibility. Medium-term wins demonstrate market traction. Together they create the organizational confidence and capability required for fundamental change.
How Do You Sequence Initiatives Across Timelines?
Effective sequencing starts with 30-day quick wins to build momentum, uses 90-day experiments to validate strategic hypotheses, and reserves organizational energy for 365-day transformations only after shorter initiatives prove the approach works.
The sequencing matters because organizations have limited change capacity. Launching a major transformation without quick wins to point to invites skepticism and resistance. The 30-day wins demonstrate that orthodoxy-smashing produces results. The 90-day experiments validate strategic direction. Only then does the organization have confidence for sustained transformation effort.
| Timeline | Orthodoxy Type | Expected Outcome |
|---|---|---|
| 30 days | Operational/Internal | Process improvements, cost savings |
| 90 days | Customer/Product | Validated hypotheses, pilot results |
| 365+ days | Business Model/Industry | Market repositioning, competitive advantage |
Don’t skip phases. Leaders eager for transformation often want to jump straight to 365-day initiatives. Without the foundation of quick wins and validated experiments, these initiatives fail from organizational resistance or strategic misdirection.
What Factors Extend Orthodoxy-Smashing Timelines?
Three factors consistently extend orthodoxy-smashing timelines: organizational complexity, stakeholder alignment challenges, and capability gaps requiring new hires or technology investments. Each factor can double or triple baseline estimates.
Large organizations move slower than small ones. Multiple business units, global footprints, and matrix structures require more coordination and create more resistance points. What a 500-person company achieves in 90 days may take a 50,000-person company six months.
Stakeholder alignment challenges arise when orthodoxy-smashing threatens powerful constituencies. Sales organizations protecting commission structures. Manufacturing protecting capital investments. Finance protecting budgeting approaches. Each constituency must be either converted or circumvented—both take time.
Capability gaps appear when orthodoxy-smashing requires skills your organization doesn’t have. If challenging your orthodoxy requires data science you don’t possess or technology you haven’t built, add the capability-building timeline to your transformation timeline.
Frequently Asked Questions
Can you accelerate orthodoxy-smashing timelines?
Dedicated resources, executive commitment, and organizational urgency can compress timelines by 20-30%. But fundamental constraints—customer adoption cycles, capability building, organizational change capacity—set floor timelines that can’t be rushed without risking failure.
What’s the biggest timeline mistake organizations make?
Underestimating the time required for adoption, not implementation. Organizations plan for building new capabilities but underestimate how long customers, partners, and internal teams need to embrace new approaches.
Should you communicate timelines publicly?
Communicate ranges, not specific dates. We expect initial results in Q2 and significant impact by year-end” creates appropriate accountability without setting up failure if timelines slip for valid reasons.
About the Author
Todd Hagopian is the author of The Unfair Advantage: Weaponizing the Hypomanic Toolbox and founder of the Stagnation Intelligence Agency. He has transformed businesses at Berkshire Hathaway, Illinois Tool Works, and Whirlpool Corporation, generating over $2 billion in shareholder value. His methodologies have been published on SSRN and featured in Forbes, Fox Business, The Washington Post, and NPR. Connect with Todd on LinkedIn or Twitter.
—
**EXTERNAL LINKS USED:**
1. Harvard Business Review research on meeting waste → https://hbr.org/2017/07/stop-the-meeting-madness
2. McKinsey research on rapid experimentation → https://www.mckinsey.com/capabilities/mckinsey-digital/our-insights/the-case-for-digital-reinvention
3. MIT Sloan research on business model innovation → https://sloanreview.mit.edu/article/the-hard-truth-about-business-model-innovation/