That sentence is usually uttered as tough-love advice to a friend who can’t seem to let go of a guy that’s clearly let go of her. A few weeks ago, it was tough love advice to one of my friends who couldn’t understand why customers weren’t swooning over his company’s newest product.
They didn’t hate.
But most didn’t like it enough to buy it.
It wasn’t rejection that was killing the business. It was apathy.
It was painful to witness.
It is also solvable.
Breeding apathy
I’m a baseball fan. I’m also the first to admit that baseball breeds apathy amongst its fans.
4-hour games. At-bats that feel like 4 hours. Fan involvement that is limited mainly to the Wave and the 7th Inning Stretch. It’s boring.
Unless you’re in Savannah, GA.
If you’re in Savannah to see baseball, you show up 2 hours before the game starts. When the gates open, you rush to your seats because you don’t want to miss a moment of the pre-game festivities. During the game, you bounce in and out of your seat so much that it counts as a workout. After the game, you spend another hour dancing and singing with the band and the team. By the time you get home, your voice is hoarse, your head is spinning, and you swear you never knew a baseball game could be so fun.
How does a collegiate summer baseball team sell out every game since 2016 and routinely attract people from around the world?
More importantly, what can you (and my friend) learn from them?
1. Do Your (customers’) Job (to be Done).
Most people go to baseball games to have fun and make memories. Most MLB franchises are focused on making a profit and winning trophies. Not a whole lot of overlap there.
The Bananas promise “to provide an electric atmosphere at all of our games! Our fans come first, and we’re dedicated to entertaining you!” There’s a complete overlap between what the fans want – have fun and make memories – and what the Bananas offer.
2. Deliver an end-to-end experience
For most businesses, designing and delivering an end-to-end experience is about investing in technology to make buying their products “frictionless” and training customer service to be more “helpful.”
The Bananas invest in delivering delight. Here’s what happened after I spent a whopping $50 to buy two tickets:
I received an email telling me I had just made the “best decision of my life” and sharing a video of the “live” view of their offices when my order came in (dancing and chaos)
Three days later, Carson called to thank me for buying tickets
Two weeks before the game, they emailed to help me “mentally prepare” for the experience.
One week before the game, they sent a permission slip to give to my boss to get out of work early.
On gameday, they emailed a Spotify playlist so we could prepare for the game
The day after, they emailed a handwritten thank you note from the owners
A week after the game, they emailed a video montage of the game we attended
3. Be human
Most companies “run lean” and use technology to improve efficiencies because humans are expensive.
The Bananas are human. Carson emailed the permission slip. She also called to thank me for buying tickets. Nick sent the gameday email. He also gave me the wristband required to get to our seats. The owner, Jesse Cole, spent the night running around in a yellow tuxedo hyping up the crowd. His wife wrote a thank you letter.
4. Give thanks. No strings attached
We’ve all received the “Thank You for Your Purchase” email after an online transaction. We also know that the email will ask for something more – track your package, write a review, post on social media, buy another product.
The Bananas say, “Thank You,” then give you something more – a funny video, a permission slip, a Spotify playlist, a handwritten thank you note. They don’t ask you to buy merchandise or post about your experience on social media, or leave them a review.
5.Care
If you don’t care about your product, no one else will.
In a world of baseballs, be a banana.
There are dozens of other things the Savannah Bananas do that make them unique and delightful that your business (and MLB) would struggle to copy.
But there are at least five things you can copy to stave off customer apathy and inspire die-hard, life-long, “tell all your friends” loyalty.
What did I miss? What have YOU experienced or done to be a banana?
In Part 1, you learned the What, Why, and How of 5 popular Innovation Frameworks – Human-Centered Design (also known as Design Thinking), Systemic Design, User-Centered Design, Lean Start-up, and Agile.
But as anyone who grew up in the 1980s and watched G.I. Joe will tell you, knowing is half the battle.
The other half is doing. More specifically, doing the right thing at the right time.
This brings us to Part 2 – the When of our 5 Innovation frameworks.
The Innovation Process
Before we get into the specifics of when to use each framework, let’s get clear on the activities that need to happen and the order in which they need to happen. In other words, we need to define an Innovation Process.
I know that sounds like an oxymoron. After all, you know that innovation is not a linear process. At best, it’s iterative. Usually, it looks and feels like this:
But you also know that this image doesn’t inspire confidence in senior leaders because it looks like chaos and doesn’t haven’t a timescale.
So to make the process more palatable to the powers that be, the Innovation Process is often shown as linear. Something like this:
Of course, that means that we, the innovators, must explain that the work isn’t, it’s an infinite loop with exit points at each step, and not every project can or should complete all the steps. It’s not perfect, but it serves its purpose (reassure senior leaders that we have a plan), so we’ll use it to help guide us to when to use each Innovation Framework.
Frameworks in the process
Now that we know the basic order in which activities should occur, we can return to our frameworks to determine which ones will best serve us in each step of the process.
“But wait!” some of you may exclaim. “Can’t we use them all?”
You can, but you don’t need to. Human-Centered Design and User-Centered Design are incredibly similar, and trying to use them both is more likely to confuse than clarify the work to be done.
“I knew it!” others will laugh, “that’s why I only use (fill in the framework).”
You can, but you shouldn’t. Every innovation has its strengths and weaknesses. The most successful innovators pull the best approaches and tools from each framework into their process.
Here’s how I think things fit together:
How to Interpret: The thicker the colored band in a column, the better suited the Innovation Framework is for the phase in the process. For example, Human-Centered Design is excellent for Diagnose, Design, and Develop phases, useful in De-Risk, and ok in Deliver. In contrast, Agile is not at all suited for Diagnose and Design but is excellent for De-Risk and Deliver.
In Diagnose and Design, lean heavily on Human-Centered Design because it keeps you open to all the types of people involved in the problem and the solution (not just users). If you’re operating in a complex environment, like healthcare or education, being in Systemic Thinking to make sure you don’t miss non-human elements like regulation, technology, or geopolitical dynamics that could also have a significant effect on the problem and eventual solution
In Develop, start weaving in elements of Lean Startup, especially its focus on building business models and not just individual products or services. Tools like the Business Model Canvas are a huge help here and reveal critical but non-product/service assumptions that need to be tested.
In De-Risk, Lean Startup and Agile become (relatively) interchangeable, so use the language that best resonates within your organization. The key here is to apply the Scientific Method to your solution through rapid prototyping and testing.
In Deliver, you’ve launched your solution, and the goal is to scale. Agile is designed for this, but it’s essential to keep the human/user at the center of continuous improvement efforts.
Popular “Innovation” Frameworks: Now What?
You’re now even more of an expert on five popular innovation frameworks, ready to talk the talk and walk the walk with the best of ’em. Right?
Maybe.
This is all the opinion of one person in a world of experts who think and who do. So what did I miss? What did I get wrong? Drop a comment, and you’ll make us all smarter!
Click here to automatically download the What, Why, How, and When Cheat Sheet
On April 26, 1937, Nazi warplanes, at the request of Franco’s Spanish nationalists, bombed Guernica, a town in northern Spain’s Basque Country. Bombs rained down on the city center for two hours, killing hundreds of people, primarily women and children.
On May 1, Pablo Picasso read an eyewitness account of the bombing and immediately began sketching. Over ten days, he created more than 50 sketches – some barely more than scribbles, others with crisp and clear pencil lines forming tragic and horrifying figures, and yet others in bold hues of yellow, purple, and blue.
On May 11, Picasso stretched and prepared a canvas so massive that it could not stand upright in his studio.
In July 1937, Guernica was unveiled at the Spanish Pavilion at the Paris International Exposition. At approximately 11.5 feet tall and 25.5 feet wide, the grey, black, and white oil painting with images showing the horrors of war was met with mixed reviews.
Today, it is regarded as one of the most moving and powerful anti-war paintings ever created and hangs in a custom-built gallery at Madrid’s Museo Reina Sofia.
What does this have to do with innovation?
Look again at the timeline above. In only ten days, Picasso learned about Guernica’s bombing, was inspired to create something in response to it, drew initial sketches, and started work on the final product.
To translate this into a (somewhat poor) analogy for innovation, in only ten days, Picasso went from identifying a need (respond to the terrorist act) to brainstorming a solution (make a painting), to developing prototypes (sketches), to preparing to launch (stretching the canvas).
Ten days.
Of which almost all were spent prototyping.
How does that compare to your innovation process?
How much time do you spend identifying a need? Brainstorming solutions? Developing prototypes?
If you’re like most companies, you probably have a 10/80/10 split – 10% of your time understanding customer needs, 80% of your time in brainstorming, and 10% of your time developing and testing prototypes.
Why?
If innovation is all about solving problems and the number one reason startups and products fail is lack of product-market fit, why do you spend most of your time coming up with ideas instead of making sure they’re the right ideas?
(Don’t) Go Big or Go Home
You know that listening to your customers is crucial because they ultimately decide the fate of your innovation. You know that prototyping is essential because all ideas are initially more wrong than right.
Yet, most companies adopt a “Go Big or Go Home” philosophy. They push innovation teams to stop worrying about the “details” and “fail fast” by getting to market (and revenue) ASAP.
But this approach puts the project and the company at risk by increasing the likelihood that money, people, and reputations will be spent on projects that do not solve a pressing customer need and, as a result, fail in the market.
(Do) Go Small to Go Big
A better approach, one more likely to lead to market success, is to “Go Small to Go Big.” Instead of a 10/80/10 split, spend 40% of your time finding the problem, 10% ideating, and 50% refining your idea through prototypes.
After all, if Picasso wasn’t willing to start painting until he first did some sketches, why are you willing to spend hundreds of millions of dollars to launch something you never prototyped?
Looking back, I realize that much of my childhood was also about embracing the AND.
Mom AND Dad
Nursery School Teacher AND Computer Engineer
Finger paint AND Calculus
A few years ago, I wrote about my mom, the OG (Original Gangster) of Innovation. She was what most people imagine of an “innovator” – creative, curious, deeply empathetic, and more focused on what could be than what actually is.
With Father’s Day approaching, I’ve also been thinking about my dad, and how he is the essential other-side of innovation – analytical, practical, thoughtful, and more focused on what should be than what actually is.
In the spirit of Father’s Day, here are three of the biggest lessons I learned from Dad, the unexpected innovator
Managers would rather live with a problem they understand than a solution they don’t.
When Dad dropped this truth bomb one night during dinner a few years ago, my head nearly exploded. Like him, I always believed that if you can fix a problem, you should. And, if you can fix a problem and you don’t, then you’re either lazy, not very smart, or something far worse. Not the most charitable view of things but perhaps the most logical.
But this changed things.
If you’ve lived with a problem long enough, you’re used to it. You’ve developed workarounds, and you know what to expect. In a world of uncertainty, it is something that is known. It’s comfortable
Fixing a problem requires change and change is not comfortable. Very few people are willing to sacrifice comfort and certainty for the promise of something better.
What this means for innovators is that it is not enough to identify, understand, and convince people of a problem. In order to make progress, we need to also identify, understand, and convince people that the solution is a better option. When people agree there is a problem but refuse our solution, it’s not because they’re lazy, dumb, or something worse. It’s because we haven’t given them a solution they understand. We have more work to do.
Pick Yourself up.
Dust yourself off.
Start all over again
My dad had an office job doing office stuff. We never really knew what he did, to the point that when True Lies came out, we (my mom, sister, and I) just started telling people that he was a spy.
Like everyone who has office jobs doing office things, Dad had lots of meetings and projects which means he also had some frustrating days. As I stepped out into the world, he knew I would have some frustrating days, too. So he gave me this Ziggy cartoon with a little note: “Keep things in perspective – it’s always a new day and a new opportunity for a fresh start.”
Not an easy thing for an impatient perfectionist to remember.
And isn’t that what innovators are? We’re impatient, we believe things can (and should) be better, and we don’t always react that well when other people don’t see what we believe is blindingly obvious. Sometimes we handle it well but sometimes we fall down (lose our tempers, yell at people, etc.).
Innovation, especially innovation within an existing company is hard. We will fall down because we’re trying to do something that’s really hard, drive change. But we can’t stay down. We need to pick ourselves up, dust ourselves off, and try again.
Sometimes a good THPPFT can help you get through a rough day
Mom was the silly one. Dad was the serious one. So it was a bit surprising when I received this card from Dad a few days before Finals.
He was right.
It’s important to remember that a good THPPFT, or burst of laughter, or *&%$#, or 30-second dance party can get you through a rough day. It breaks up the intensity and the self-imposed seriousness of whatever is happening.
Innovation, especially Design Thinking, is rooted in child-like wonder – curiosity, creativity, surprise, and joy. As innovators, if we get mired in the seriousness and stress of work, we will lose the joy and humor required to create and change. We need a good THPPFT to stay effective innovators.
One final nugget
In previous blog, I’ve mentioned a poem that Dad gave me, probably in HS, that I think about regularly. I am quite sure that there were times he deeply regretted sharing this with his head-strong, opinionated, and slightly anti-authoritarian daughter, as evidenced by the hand-written note on the paper version – “don’t think you’ll always be right.”
While I was right that I would never use calculus (or physics or chemistry) after school, he was right to share this with me. And now I share it with you:
A few weeks ago, I wrote a post using quotes from “Moneyball” (the movie, not the book) to describe the experience of trying to innovate within a corporate setting.
It was great fun to write, I received tons of feedback, and had many fascinating conversations (plus a fact check on the year the Red Sox broke the Curse of the Bambino), so I started searching for other movies that inadvertently but accurately describe the journey of corporate innovators.
The Princess Bride
If you have not seen The Princess Bride, stop reading and immediately go watch it. Seriously, there is nothing more important for you to do right now than to crawl out from the cultural rock you’ve been under since 1987 and watch this movie.
If you’re reading this, you’ve clearly watched the movie and know that it is packed with life lessons and quotable quotes. It also captures the reality of innovation within the walls of large companies
The Beginning
“You keep using that word. I don’t think it means what you think it means.” – Inigo Montoya
A company’s focus on Innovation usually begins the moment a senior executive, usually the CEO, declares it to be a key strategic priority and promises Wall Street analysts that significant investments will be made.
It then trickles down to business units and functions, with each subsequent layer told to “be more innovative” and “come up with more innovation.”
Then, one day, the responsibility for innovation lands in someone’s lap and stays there. To be honest, it’s usually an exciting day for the person because they’ve been asking questions, suggesting ideas, and pushing for innovation for a long time, and now the powers that be have permitted them to do something about it. They may even have been given a title and budget specific for innovation.
But “innovation” was never defined.
The CEO may think it is an entirely new business, something flashy and new that rivals anything coming out of Silicon Valley.
The Business Unit and Functional Heads may think it’s a new product or technology, something just different enough from the current business to be newsworthy but not so different that it changes how things are done.
And the new Innovation owner thinks it’s new ideas, lots of brainstorming sessions, and networking with entrepreneurs and startups.
Without alignment as to what “innovation” means and what it needs to deliver, the stage is set for misalignment, frustration, and ultimately failure. Al because that word, “Innovation,” does not mean what you think it means.
The Middle
“We’ll never survive.” – Buttercup, the Princess Bride
“Nonsense, you’re only saying that because nobody ever has.” – Westley
Let’s imagine for a moment that a common definition and set of expectations for innovation is established and everyone up and down the corporate hierarchy is in agreement (this actually does happen, but it takes effort).
The innovation owner has a clear mandate and is hard at work building an innovation pipeline – they’re having lots of qualitative interviews to build customer empathy, they’re facilitating brainstorming sessions to get ideas, they’re building prototypes to get customer feedback. Most importantly, they’re sharing their work with anyone who will listen, asking for feedback, and building supporters and champions.
And then, the chorus begins.
“This will never work”
“You’ll never get approval for that”
“If we do that, we’ll lose customers”
“If you do that, you’ll be fired.”
In these moments, the dark seeds of doubt are planted. The innovation owner must dig deep, reminding themselves that people are only saying those things because it hasn’t worked yet, no one got approval yet, customers haven’t yet weighed in, and you haven’t tried to do that yet.
After all, just because something has never been done, doesn’t mean that it can’t be done.
The End
“Thank you so much for bringing up such a painful subject. While you’re at it, why don’t you give me a nice paper cut and pour lemon juice on it.” – Buttercup, the Princess Bride
Let’s be honest, most corporate innovation efforts don’t result in the world-changing, life-affirming successes we hop for. Innovators are, by nature and necessity, an optimistic bunch so when things don’t work out as we hope, it hurts. It hurts as much as a paper cut with lemon juice poured on it.
But there is one truth that cuts across all attempts at corporate innovation, no matter whether the journey ends with wild success in the form of massive business growth, happy success in the form of new products and revenue streams, satisfying success in the form of improvements and greater efficiencies, or bitter disappointment because nothing changes and everyone goes on to old or new jobs.
“I supposed you think you’re brave, don’t you?” – Vizzini
“Only compared to some.” – Buttercup, the Princess Bride
Those who took on the work and responsibility of innovation are brave.
Not only compared to some but compared to most.
It takes guts to try something new. To ask questions. To challenge the status quo. To continue seeking a yes amongst a thousand no’s. To put your reputation, your bonus, and maybe even your job on the line.
And that’s what corporate innovators need to remember – that whatever happens, they were brave. They worked hard, they battled the odds, they did make change happen. Even if it was only how they see and understand the world. Even if it only to get smarter and stronger and prepare for the next time they are called upon to drive change.
Because in that moment, innovators must be ready to say “As you wish.”
After months of tests, quizzes, career counseling sessions, and peer support groups, I was sitting in the expansive wood-paneled office of Harvard Business School’s Head of Career Services, eagerly anticipating learning what my ideal career would be. I did not expect to be told that I was a fish.
“You are only happy when you are rebelling against something. You are a salmon. Whatever you choose to do, you must swim upstream.”
This did not sound like a recipe for the peaceful, easy, frictionless career that I envisioned. This sounded like a career of frustration, struggle, and just generally being annoyed most of the time.
It was 100% accurate.
Innovators are salmon
Quick tutorial on salmon – they hatch in freshwater, swim out to the ocean and live in the saltwater before returning to freshwater to spawn and die (assuming the don’t get caught by a bear or fisherman first).
Quick tutorial on innovators – they are born (like everyone else) with creativity and a sense of unlimited possibility, they go out into the world and face the sting of reality before returning to their natural creative state to ask questions, challenge the status quo, drive growth, and (like everyone else) die.
Swimming upstream is exhausting for fish and for people. That’s why most don’t do it. That’s why most fish and people make the sensible choice to go with the flow, work within the system, and find better ways to do the same things.
But innovators, like salmon, instinctively know that to create, they must follow a different and much harder path. Instead of going with the flow, they must question the status quo. Instead of finding a better way to do the same things, they question whether those things even need to be done and create new ways to do new things.
Companies recognize that they need innovators. They need people who think differently and aren’t afraid to take smart risks because these are the people that will create new revenue streams and drive companies’ long-term growth. But, like the river, the company can’t change how it operates.
Companies need salmon ladders
Quick tutorial on salmon ladders – they are structures on or around natural barriers like waterfalls and dams, that have a high enough water velocity to attract the fish but not so much as to exhaust them, and often have very low steps that the salmon can leap up to get to their destination
Quick tutorial on innovation processes – they are structures separate from companies’ existing processes (and the barriers that often slow progress), that allow enough freedom for creativity and experimentation but not so much as to put the company at serious risk, and often have steps or stages that innovators and their projects must leap up in order to launch a scalable business.
Salmon ladders help salmon progress more rapidly and efficiently, decreasing the odds that they die from exhaustion before reaching their destination. Innovation processes help innovators progress ideas more rapidly and efficiently through an organization, decreasing the odds that they die (or quit, or get fired) before reaching their destination.
How to build a salmon ladder for innovators
Google “innovation process” and you will get 1.8 BILLION results in 0.59 seconds. That’s because there is no one magic innovation process that works for everyone.
But as varied as effective innovation processes are, they share common characteristics.
People over process. If you announce the implementation of a new process, send out a user manual, and then walk away, the process will fail. If you involve people in designing and pressure testing the process, support them in the first 6-12 months of use, and they experience the value of the process for themselves, the process will succeed.
Goals are good.Constraints are better. Innovation is an investment, and the company expects a return on that investment. Be clear about those expectations from the start. Innovation is not “anything goes!” Be clear about what the company is and is not willing to support before your start.
Guidance, not direction. Innovation is filled with known unknowns and unknown unknowns and, for that reason, the path to launch isn’t a straight line. But it also can’t be an infinite loop. Innovation processes should set guardrails for the work to be done but shouldn’t be overly prescriptive.
Insights, not information. Innovation processes should enable learning and encourage its sharing. Building in time for teams to reflect on their experience and write down their insights is critical for continued growth. Weighing the team down with detailed analyses, complicated templates, and constant update presentations doesn’t enable and encourage learning, it slows it down.
Celebrate milestones, not just launches. More innovation projects will be stopped than will be launched. The stopped projects aren’t failures, they’re lessons learned and steppingstones to the next big launch. Celebrating the milestones that projects achieve, even the milestone of being stopped, will keep innovators energized and swimming upstream far longer than celebrating only the launches.
Innovators do the hard work of swimming upstream.
Help them out by building a process to guide and propel them.
