‘Twas the Night Before Launch Day

‘Twas the Night Before Launch Day

‘Twas the night before launch day, when throughout HQ,
Not a worker had left, there was too much to do;
The plans were laid out by the whiteboard with care,
While our Innovation Chief Sarah planned with great flair;

The team was all nestled all snug at their posts,
While visions of success inspired them the most;
And Sarah in her blazer, so sharp and so bright,
Had just settled in for a long working night,

When out in the hall there arose such a clatter,
She sprang from her desk to see what was the matter.
When what to her wondering eyes should appear,
But the CEO and board, spreading holiday cheer!

“Now, ARCHITECTURE!” they cried, “We need strategy and rules!
Now BEHAVIORS and CULTURE!” – these ABC tools.
“Tell us Sarah,” they said, “how you’ll lead us to glory,
Through bringing new value – tell us your story!”

She smiled as she stood, confidence in her stance,
“The ABCs of Innovation aren’t left up to chance.
Architecture’s our framework, our process and measure,
Our governance model not built at our leisure;

“The Behaviors we foster? Curiosity leads,
With courage and commitment to meet future needs.
And Culture,” she said, with a twinkle of pride,
“Is how innovation becomes our natural stride.”

Her cross-functional team gathered ’round with delight,
Each bringing their skills to help win this big fight:
“From concept to testing, from planning to more,
We’re ready to launch what we’ve worked toward before!”

The CEO beamed and the board gave a cheer,
“This is exactly the progress we’d hoped for this year!
With Architecture to guide us, and Behaviors so strong,
Plus Culture to fuel us – well, nothing could go wrong!”

Then Sarah exclaimed, as they turned out the light,
“Happy launching to all, and to all a good night!
For tomorrow we share what’s been worth all the wait,
Guided by ABCs, we’ll make something great!”

The 12 Killers of Innovation: A Corporate Carol About Why You’re Not Getting Results

The 12 Killers of Innovation: A Corporate Carol About Why You’re Not Getting Results

Last week, InnoLead published a collection of 11 articles describing the root causes and remedies for killers of innovation in large organizations.  Every single article is worth a read as they’re all written by experts and practitioners whose work I admire.

I was also inspired.

In the spirit of the hustle and bustle of the holiday season, I gave into temptation, added my own failure mode, and decided to have a bit of fun.

The 12 Killers of Innovation
(Inspired by the 12 Days of Christmas yet relevant year-round)

On the twelfth day of innovating, management gave to me:

12 leaders short-term planning

11 long projects dragging

10 cultures resisting

9 decisions made too quickly

8 competing visions

7 goals left unclear

6 startups mistrusted

5 poorly defined risks

4 rigid structures

3 funding black holes

2 teams under-staffed

And a bureaucracy too entrenched to change

Want to write a happier song?

Each of the innovation killers can be fended off with enough planning, collaboration, and commitment.  To learn how, check out the articles:

12 leaders short-term planning – Why Innovation is a Leadership Problem by Robyn Bolton, MileZero

11 long projects dragging – Failing Slow by Clay Maxwell, Peer Insight

10 cultures resisting – How to Innovate When Resistance is Everywhere by Trevor Anulewicz, NTT DATA

9 decisions made too quickly – Red Light, Green Light by Doug Williams, SmartOrg Inc.

8 competing visions – The Five Most Common Innovation Failure Modes by Parker Lee, Territory Global

7 goals left unclear – Mitigating Common Failure Modes by Jim Bodio, BRI Associates

6 startups mistrusted – Developing a New Corporate Innovation Model by Satish Rao, Newlab

5 poorly defined risks – Strategic Innovation is too Scary by Gina O’Connor, Babson College

4 rigid structures – Corporate Innovation is Dead by Ryan Larcom, High Alpha Innovation

3 funding black holes – Failure Modes by Jake Miller, The Engineered Innovation Group

2 teams under-staffed – Why Innovation Teams Fail by Jacob Dutton, Future Foundry

And a bureaucracy too entrenched to change – Building Resilient Teams by Frank Henningsen, HYPE Innovation

How are you going to make sure that you receive gifts and not coal this year for all your innovation work?

What are you afraid of?

What are you afraid of?

“We identified four opportunities for market expansion, all adjacent to our current business, and entry into any one of them is almost guaranteed to materially grow our business.   But no one is doing anything.”

I wanted to be surprised.  Instead, I sighed and asked the question I knew he couldn’t answer.

“What are your colleagues afraid of?”

The Four Horsemen of the Apocalypse

Most of the time, when opportunities are clear, but action is absent, it’s because one of the first three horsemen of the innovation apocalypse appeared:

  • Short-termism: “The CFO is worried we may miss the quarter, so we’re starting to make cuts.”
  • Size:  “We have a new President coming in who wants to put his stamp on things, so he’s cutting anything that won’t double out business in three years.”
  • Scarcity: “We’re implementing a new process, and this would just be one thing too many for people to handle.”

The business my client described has doubled in the past five years. After fifty years of steady, reliable, and predictable revenue, its top line suddenly became the mythical “hockey stick of growth.”  The technological driver of this change is more likely to be the “new normal” than a fad, so the business is expected to double again in the next five years.

Leadership isn’t worried about delivering the next quarter, year, or five years. They know that they have the resources they need and can access more when the time is right.  They’re confident that the opportunities identified are feasible and meaningful.

Yet, they will not act.

I’m not afraid.  I’m biased!

Behavioral economists, psychologists, and sociologists explain situations like the above by pointing out our “cognitive biases”—the “irrational errors that are programmed into our brains.”  For example, the first three horsemen could be known as Present Bias, the hard-easy effect, and Loss Aversion

As of 2024, over 150 cognitive biases have been identified.

While it’s comforting to blame programming bugs beyond our awareness and control for our “irrational errors,” this approach lets us off the hook a bit too easily.

I’m not biased.  I’m afraid!

Fear is at the root of most, if not all, of these biases because emotions, not programming bugs in our brains, drive our decisions. 

The study of how our emotions impact decision-making didn’t take off until the early 2000s. It really accelerated in 2015 when professors from Harvard, UC Riverside, Claremont McKenna College, and Carnegie Mellon published a meta-study on the topic and declared:

The research reveals that emotions constitute potent, pervasive, predictable, sometimes harmful and sometimes beneficial drivers of decision making. Across different domains, important regularities appear in the mechanisms through which emotions influence judgments and choices.

Bottom line – we decide with our hearts and justify with our heads.

Our hearts are afraid that we’ll lose the respect of our peers and loved ones, the reputations we’ve worked decades to build, the physical goods and intangible experiences that project our societal status, or the financial safety of a regular paycheck.

And, as my brilliant and kind sister told me, “These feelings we feel, these feelings are real.”

I’m afraid and biased and brave!

Next time you see someone (maybe you?) do something “irrational,”  get curious and ask:

  • What cognitive bias are they falling prey to? 
  • What is the fear that’s driving that bias? 
  • How can you help them to be brave, live with the fear, and move forward?

I’m curious…when was the last time you were afraid, biased, and brave?

If You Want to Be Happy, Ignore Your Customers

If You Want to Be Happy, Ignore Your Customers

“Now I know why our researchers are so sad.”

Teaching at The Massachusetts College of Art and Design (MassArt) offers a unique perspective. By day, I engage with seasoned business professionals. By night, I interact with budding designers and artists, each group bringing vastly different experiences to the table.

Customer-centricity is the hill I will die on…

In my Product Innovation Lab course, students learn the innovation process and work in small teams to apply those lessons to the products they create.

We spend the first quarter of the course to problem-finding.  It’s excruciating for everyone.  Like their counterparts in business and engineering, they’re bursting with ideas, and they hate being slowed down.  Despite data proving that poor product-market fit a leading cause of start-up failure and that 54% of innovations launched by big companies fail to reach $1M in sales (a paltry number given the scale of surveyed companies), they’re convinced their ideas are flawless.

We spend two weeks exploring Jobs to be Done and practicing interviewing techniques.  But their first  conversations sound more like interrogations than anything we did in class.

They return from their interviews and share what they learned.  After each insight, I ask, “Why is that?” or “Why is that important?

Amazingly, they have answers.

While their first conversations were interrogations, once the nervousness fades, they remember their training, engage in conversations, and discover surprising and wonderful answers.

Yet the still prioritize the answers to “What” over answers to “Why?”

…Because it’s the hill that will kill me.

Every year, this cycle repeats.  This year, I finally asked why, after weeks of learning that the answers to What questions are almost always wrong and Why questions are the only path to the right answers (and differentiated solutions with a sustainable competitive advantage), why do they still prioritize the What answers?

The answer was a dagger to my heart.

“That’s what the boss wants to know,” a student explained.  “Bosses just want to know what we need to build so they can tell engineering what to make.  They don’t care why we should make it or whether it’s different.  In fact, it’s better if it’s not different.”

I tried to stay professional, but there was definitely a sarcastic tone when I asked how that was working.

“We haven’t launched anything in 18 months because no one likes what we build.  We spend months on prototypes, show them to users, and they hate it.  Then, when we ask the researchers to do more research because their last insights were wrong, they get all cra….OOOOHHHHHHHH…..”

(insert clouds parting, beams of sunlight shining down, and a choir of angels here)

“That’s why the researchers are so sad all the time!  They always try to tell us the “Whys” behind the “Whats” but no one wants to hear it.  We just want to know what to build to get to work.  But we could create something people love if we understood why today’s things don’t work!”

Honestly, I didn’t know whether to drop the mic in triumph or flip the table in rage.

Ignorance may be bliss but obsolesce is not

It’s easy to ignore customers. 

To send them surveys with pre-approved answers choices that can be quickly analyzed and neatly presented to management.  To build exactly what customers tell you to build, even though you’re the expert on what’s possible and they only know what’s needed.

It’s easy to point to the surveys and prototypes and claim you are customer-centric. If only the customers would cooperate.

It’s much harder to listen to customers.  To ask questions, listen to answers you don’t want to hear, and repeat those answers to more powerful people who want to hear them even less.  To have the courage to share rough prototypes and to take the time to be curious when customers call them ugly.

So, if you want to be happy, keep pretending to care about your customers. 

Pretty soon, you won’t have any left to bother you.