90-day innovation framework (no operations disruption required)

SPECIAL ANNOUNCEMENT FOR EARLY SUPPORTERS

Want to read Innovation at Work before it hits the shelves?
​

I'm looking for a small group of innovation champions to join my official book launch team — the inner circle helping bring Innovation at Work into the world. You'll get:
​

✨ Early access to the complete book (mid-January)
📖 Exclusive bonus materials not available anywhere else
🎯 First look at all 52 micro-experiments before the world sees them
​

Your part is simple: Read (or skim the parts most relevant to your work), share your honest feedback, and post a short Amazon review once the Kindle version goes live.
​

The updated timeline:

• Jan 5 – 6: ARC delivery + launch-team access
• Jan 16: Kindle soft launch (time to post your Amazon review!)
• Early Feb: Official paperback release + virtual launch celebration 🎉
  ​

Want to be part of the inner circle? Join the Launch Team here​

​

Now, on to this week's topic...

Hey there, innovation champions!
​

"We need to become more innovative—but we can't afford to disrupt operations."
​

I hear this tension from leaders constantly. They know their teams need innovation capability, but they can't shut down production for culture transformation.
​

Here's the good news: You don't have to choose between innovation and operations.
​

Based on what I've learned from research on organizational change, feedback from workshop participants, and designing the systematic framework in Innovation at Work, the most successful transformations don't require dedicated "innovation time" or elaborate offsite retreats.
​

They happen through systematic integration—small experiments embedded into the work teams are already doing.
​

Let me show you the 90-day framework I've designed specifically for this challenge.
​

Why 90 Days?

First, why this specific timeframe?
​

Research on habit formation shows that meaningful behavioral change requires sustained practice over 8-12 weeks. Studies on organizational change suggest this is the minimum timeframe for new behaviors to feel natural rather than forced.
​

But here's what most transformation programs miss: You can't wait 90 days to see results.
​

Leaders need early wins to maintain commitment. Teams need quick proof that change is possible. Executives need visible progress to justify continued investment.
​

That's why this framework is designed for immediate impact that compounds over time.
​

The Three-Phase Transformation Model

Here's the strategic structure I've designed:

Phase 1: Foundation Building (Weeks 1-4)
​Build psychological safety and permission to experiment
​

Phase 2: Capability Building (Weeks 5-8)
​Accelerate learning cycles and generate breakthrough thinking
​

Phase 3: Culture Embedding (Weeks 9-12)
​Make innovation behaviors automatic, not optional
​

Notice what's NOT in this model: No "pause operations for training." No "dedicate resources to innovation projects." No "wait for perfect conditions."
​

Instead, experiments integrate into existing meetings, workflows, and processes.
​

Phase 1: Foundation Building (Weeks 1-4)

The biggest barrier to innovation isn't lack of ideas—it's perfectionism that prevents sharing imperfect ideas.
​

Week 1: Remove the Perfection Barrier

Start your next team meeting with Experiment #1 (Crappy First Draft Showcase)—15 minutes where everyone creates deliberately terrible solutions to a current challenge.
​

The principle is simple: When "crap" is the goal, people share ideas they'd normally self-censor. I saw this dynamic at work when I ran playful, experimental exercises with 125 project managers at PMI San Francisco Bay Area. As one attendee wrote: “I could see the breakthroughs happening—it was ELECTRIC!”
​

Week 2: Normalize Productive Failure

Integrate Experiment #50 (Celebrate the Attempt) into your retrospectives—5 minutes acknowledging bold experiments regardless of outcome.
​

This isn't "participation trophies." It's rewiring what teams pay attention to. When attempts get celebrated as much as successes, experimentation increases.
​

Week 3: Build Cross-Functional Empathy

Run Experiment #11 (Switch Seats, Switch Minds) during project discussions—15 minutes where team members literally argue from another role's perspective.
​

This systematically breaks down the silos that kill cross-functional innovation.
​

Week 4: Establish Permission Structures

Use Experiment #13 (Permission Slip Protocol) to explicitly grant permission for experimental behaviors—10 minutes identifying what the team needs permission to do.
​

Most teams know what they should do differently but wait for explicit permission. This experiment makes it explicit.
​

What research and participant feedback suggest happens by Week 4:

• Increased idea-sharing in meetings
• Reduced meeting time spent on "perfect" analysis before trying anything
• Visible improvement in cross-functional communication
• Explicit permission structures replacing implicit cultural barriers
  ​

Phase 2: Capability Building (Weeks 5-8)

Now that psychological safety exists, teams can practice harder skills.
​

Week 5: Stress-Test Assumptions

Integrate Experiment #23 (Inversion Day) into product reviews—15 minutes asking "How would we make this fail spectacularly?"
​

This reveals blind spots traditional analysis misses.
​

Week 6: Accelerate Prototype Speed

Run Experiment #18 (Ugly Prototype Sprint) during design discussions—20 minutes building deliberately rough prototypes that test core assumptions.
​

The "ugly" requirement eliminates polish pressure and accelerates testing cycles.
​

Week 7: Inject Fresh Perspectives

Use Experiment #51 (Trade a Problem) when teams are stuck—12 minutes solving each other's challenges.
​

We're emotionally attached to our own problems. Solving someone else's creates psychological distance that unlocks breakthrough thinking.
​

Week 8: Right-Size Overwhelming Projects

Apply Experiment #32 (Make It Smaller) to complex initiatives—15 minutes identifying the smallest version that delivers value.
​

This experiment helps teams discover they've been overbuilding.
​

What the framework is designed to create by Week 8:

• Faster iteration cycles
• Better early detection of flawed assumptions
• Increased willingness to test "incomplete" ideas
• Systematic approach to managing overwhelming scope
  ​

Phase 3: Culture Embedding (Weeks 9-12)

Final phase makes innovation behaviors automatic.
​

Week 9: Build Systematic Reflection

Establish Experiment #28 (Emoji Retrospective) as standard practice—10 minutes using simple visual language to accelerate honest feedback.
​

Week 10: Create Innovation Rituals

Use Experiment #45 (Interrupt the Routine) to deliberately break patterns—5-minute setup establishing regular pattern disruptions.
​

Week 11: Connect to Purpose

Run Experiment #40 (Invisible Impact Map) to connect daily work to larger mission—20 minutes making abstract purpose tangible.
​

Week 12: Plan Systematic Capability Development

Close with Experiment #52 (Innovation Time Travel)—15 minutes planning next month's capability-building experiment.
​

This establishes ongoing practice rather than "we did innovation transformation, now we're done."
​

What the framework is designed to create by Week 12:

• Innovation behaviors that feel natural, not forced
• Teams automatically applying experimental thinking to new challenges
• Cross-functional collaboration happening without facilitation
• Systematic approach to building innovation muscle over time
  ​

The Integration Principle

Notice what makes this framework work: No experiment requires stopping operations.
​

They integrate into:

• Sprint planning sessions
• Daily standups
• Project reviews
• Retrospectives
• Product discussions
  ​

Your team is already in these meetings. This framework just changes how they approach them.
​

What I've Seen Work

When I work with teams using playful, experimental approaches—even in short sessions—I see immediate shifts.
​

At PMI San Francisco Bay Area Chapter's Professional Development Day last month, I ran interactive exercises with 125 project managers. Leaders told me afterward that participants were already planning to bring experimental thinking into their team meetings the following week. One participant shared that after our session, "it was much easier to connect with people for the rest of the day."
​

That immediate shift—from a single 45-minute session—showed me the power of removing perfection barriers and creating permission to experiment.
​

But here's the critical difference: One session creates a shift. Systematic practice over 90 days creates transformation.
​

The experiments in Innovation at Work are designed specifically for that systematic practice—so teams can experience similar shifts in Week 1, then compound them through consistent practice over 12 weeks.
​

The Implementation Reality

Let me be completely honest: I've designed this 90-day framework based on research on organizational change, participant feedback, and systematic practice principles.
​

I haven't yet guided an organization through the complete 90-day journey—but the framework is built on proven principles and real participant experiences with individual experiments.
​

The most successful transformation would combine:

1. The book = Your systematic practice guide (52 experiments)
2. Strategic workshops = Intensive skill-building at key milestones
3. Leadership coaching = Navigate resistance and embed cultural change
4. Ongoing facilitation = Ensure experiments get implemented, not just discussed
   ​

This is the comprehensive engagement model I'm building—and I'm looking for organizations ready to be early partners in proving this approach works at scale.
​

Your Next Step

If you're serious about building innovation capability—not just getting inspired by innovation concepts—here's what I recommend:

Start with the book to get the systematic practice framework and 52 experiments your team can integrate immediately.
​

For organizations ready to partner on comprehensive transformation, let's explore what a 90-day strategic engagement could look like for your specific challenges.
​

Ready to build lasting innovation capability? Join the book waitlist to get the 90-day systematic practice framework.

Next week, I'm tackling the question: "Your background is arts and creativity—how does that translate to our technical business?" Spoiler: It's your secret weapon, not a liability​
​

Creatively yours,
Melissa

​P.S. When you’re ready to build a culture of thriving innovation, so your team can Create the Impossible™, here are three ways I can help:

1) Download my FREE Innovation Culture Assessment to evaluate where your team stands

2) Download the first 50 pages of my book, The Creative Sandbox Way™, to reconnect with your creativity

3) Click here to schedule a complimentary Innovation Strategy Session

Did someone forward this email to you? If you'd like more articles like this right in your own inbox, click here to subscribe!​​