You have the data. You heard everyone’s opinions. Now it’s time to decide.
Which projects get funding?
How will headcount change?
What projects are “deprioritized?”
You know that making tough decisions is the essence of leadership, but you’re starting to wonder if maybe life wouldn’t be a whole lot easier if you just stood up, walked out, and moved to a hut on a remote island and ate mangos and fish the rest of your life.
You make 35,000 decisions each day, and some of those decisions are really tough.
They’re tough because you don’t have enough data to be 100% certain of the answer. Or because everyone has a different opinion on what the correct answer is. Or because the consequences, even if you’re right, are breathtakingly high.
But these aren’t the reasons people struggle, even resist, making decisions. After all, you worked hard to get to a position where you could make these decisions.
Decisions are tough because when you say “Yes” to one thing, you’re saying “No” to something else.
Say No to Loss Aversion
When you say “No,” your brain doesn’t focus on what you gained (clarity, resolution). It focuses on what you lost.
This is called Loss aversion, and it’s a common cognitive bias that leads people to do anything they possibly can to avoid losses. Because when your brain focuses on loss, the pain you feel is twice as intense as the pleasure you feel from what you gained.
That’s why when you choose between two equally strategic projects (because you don’t have the resources to launch both), each projected to generate $100M in revenue, you feel like you lost $200M instead of gaining $100M.
Say Yes to Easier Decisions
You can’t make tough decisions, like stopping projects, easy. But you can make them easier.
1. Communicate how you will decide BEFORE starting any work
“I’ll know it when I see it,” is lazy and selfish. It’s lazy because it shows that you haven’t thought through the issue or understand the implications. It’s selfish because you’re forcing your team into a guessing game in which they must do all the work, hoping that they collect the data you need.
If you know how you’ll make the decision, tell the team, saving them time and energy collecting the inputs you need.
If you think you know how you’ll decide but want to preserve the option to consider other inputs, tell your team, “I expect to make a decision based on x, y, and z, but I’m also open to other factors.”
If you don’t know how you’ll make the decision, maybe the decision doesn’t need to be made.
2. Understand if and how the decision can change
Some decisions are forever, and some can be changed. Getting a tattoo is a Forever Decision (yes, you can have it removed later, but it’s painful, expensive, and time-consuming). Getting a body piercing is a For Now Decision (pull out the stud, and you’re set).
What type of decision are you making? A Forever Decision or a For Now Decision? What would cause you to change your mind if it’s a For Now Decision?
Answering these questions helps everyone understand the stakes and avoid surprise and confusion if something changes. And it takes a bit of pressure off your shoulders, too.
3. Reflect and respect the deadline
If you rush into a decision, you’re more likely to make a superficial or short-sighted decision. If you take too long, you may miss an opportunity.
If you don’t have a deadline to make a decision, give yourself one and stick to it. Yes, the deadline may move back, giving you more time. But it may also move up, giving you less. Hope for the best (more time), plan for the worst (less time), and act with what you’ve got.
Then schedule at least a few days between receiving the needed information and making a decision. Doing so gives you time to reflect, ask questions, and follow up with people. It also gives your brain time to work its magic and produce A-Ha! moments.
What are some of the things you know you should do, but you don’t?
Eat five servings of vegetables each day
Take a multivitamin
Do 10 minutes of cardio daily
Why not?
Vegetables don’t taste as good as pizza.
Multivitamins don’t affect how you feel today (or tomorrow or next month)
You don’t have time for the 45 minutes that 10 minutes of cardio actually takes (changing into workout clothes, doing cardio, showering after)
It’s ok. I get it. Heck, I say all the same things.
What about the other things you know you should do but don’t?
Invest in innovation
Invest regularly, not just when business is good
Invest repeatedly because it’s a key driver of revenue growth and competitive advantage
Guess what, the reasons you’re not doing it are similar to why you’re not eating vegetables, taking a multivitamin, or sprinting through your neighborhood:
Innovation is so much more uncertain and complex than running your day-to-day business
Innovation doesn’t affect your bottom line this quarter (or this year or next)
You don’t have time because you’re focused on putting out fires and operating today’s business
It’s ok. We all get it. Heck, I’m absolutely sure we all have the same reasons.
How to Turn Shoulds Into Dids
What can we do about all this? After all, the first step is acknowledging you have a problem (or, at least, aren’t doing something you know you should).
1. Start Small.
It’s not practical (or yummy) to go from zero servings of vegetables to five, so don’t. Try going from zero to one and find a one you like (not just tolerate).
Same thing with innovation. Don’t go from no investment to standing up an entirely new team in new fancy offices with massive budgets. Find a nagging problem that annoys everyone and, if it can be solved, will produce tangible and meaningful results. Tap a few people to work on it full-time, give them a small budget, and a short timeframe within which to make progress (not solve the entire problem), and check in weekly.
2. Piggyback on another habit
A multivitamin won’t change how you feel today, but it could change how you feel years from today. But trying to remember to take a multivitamin every day is mentally exhausting. So try to work your multivitamin into an already existing daily habit. Do you have prescriptions you take every day? Put the vitamin bottle next to those. Stare at the coffee maker waiting for it to finish? Put the vitamins next to it, so you take them while staring.
Same thing with innovation. You have teams in your organization consistently working to make your products and processes better, faster, and cheaper. Have them teach others how to do what they do. You have business leaders projecting ever-increasing revenue. Ask them to explain what needs to happen to make that growth possible and how it will occur. Then invest in the people, skills, and resources required.
3. Say what you mean (even if it’s super uncomfortable)
If it’s important, you make time. After all, research proves that “I don’t have time” means “it’s not a priority. If having great cardio was really important to me (it is), I would make time to run (I don’t). In other words, great cardio is important, but it’s not a priority (or not a higher priority than binging Stranger Things).
When an innovation team asks for time on your calendar, don’t tell them you don’t have time. Be honest and tell the team they’re not a priority or a lower priority than the other things you’re spending time on. Harsh? Yes. Helpful. Absolutely! This level of honesty gives the innovation team a clear sense of what they’re competing against for scarce resources, the bar they have to clear to rise up your priority list, and a starting point from which to work with you to get what they need in a way that works for you.
You can do it
Shoulds fill our lives. But they’re not all equal and won’t all become dids.
If a should is essential, we’ll find a way to make it happen. It won’t be easy, but it is possible. If a should isn’t essential or as important as other shoulds, it will stay a should.
Maybe that’s ok. Maybe it’s not. Maybe I’ll regret choosing fries over mixed veggies as a side.
As an innovator, this question should trigger your fight, flight, or freeze response.
It is often a genuine question asked by a good-hearted colleague who is motivated by a genuine desire to help.
It can also signal the beginning of the end.
Beware Organizational Antibodies
Thanks to COVID-19, we’ve all (re)learned how our bodies’ immune systems work:
A foreign object (a pathogenic bacteria or virus) enters our bodies, and our immune system rallies a bunch of antibodies to identify the unwanted object and neutralize or destroy it.
Yea! Threat neutralized! We’re safe again!
Thank you, antibodies!
Companies work in much the same way (after all, “corporation” traces its roots back to “corpus,” the Latin word for body)
A foreign object (innovation) enters our company, and our immune system (culture, processes, structures) rallies a bunch of antibodies (rules, metrics, stories) to identify the new object and neutralize or destroy it.
Whether you thank the antibodies or curse them depends very much on your point of view. Either way, you can’t argue that the antibodies did precisely what they are designed to do – keep the company operating efficiently with minimum disruption or distraction.
How to spot Organizational Antibodies
Antibodies always appear in human form, usually as allies like colleagues or bosses, and express themselves in a single statement or question.
Here are the five most common:
1. “Can I offer you a bit of advice?” – The antibody is here to help. It wants to spare you the pain your predecessors endured by passing lessons learned and suggestions to make your innovation more acceptable to upper management. Following their advice will neutralize the innovation, transforming it from “something new that creates value” to “something familiar that feels safe.”
2. “Have you thought about…?” – This is a slightly more aggressive antibody than #1, but it operates similarly. Intending to help, this antibody offers an unsolicited and specific piece of advice. If you take the advice, you face the same risk of neutralization as with #1, but if you ignore it, you risk hearing a very public, “I told you so.”
3. “You should talk to (fill in the blank)” – This is another antibody that wants to help, but not enough to do it. It senses the foreignness of your project, so it doesn’t want to get too involved lest it fails. But it wants to do something, so it can claim involvement if your innovation succeeds. So, it sends you to someone it genuinely believes will be helpful. While it’s certainly important to talk to people throughout the company, beware the run-around that results in all talking and no doing.
4. “I don’t have time right now but let’s talk in a month” – This antibody knows that we’re all time-starved, so we won’t argue with this reason. But “I don’t have time” means “It’s not a priority.” If the project isn’t a priority now, it won’t be a priority in a month. And if the project isn’t a priority, it will be starved of resources and die a slow, agonizing death.
5. “Before I can approve this, I need to see (financials, documentation). I’m just holding you to the same standard I hold other projects to.” – When all other antibodies fail, this one is unleashed. Directly or indirectly, it kills every innovation in the organization. It ignores the fact that new things don’t have historical data. It dismisses analogous innovations as too different to be valid. Anything that can’t be proven to be 100% certain contains some amount of risk. And risk must be destroyed.
How to work with Organizational Antibodies
Antibodies mean well. They genuinely want to help. Even when they’re being tough, they believe they’re being fair. It’s essential to respond with an equal measure of kindness and fairness.
Remember, you can’t stop antibodies. You can only hope to contain them with one (or more) of these approaches:
1. Say “Thank you.” – Don’t try to justify, explain, or convince the antibody that they’re wrong. Simply acknowledge that you heard them and say thank you.
2. Ask if they’re open to discussing their suggestion. – Most antibodies have short memories. Once they give advice, they move on to other things and quickly forget about you. But some don’t. Some return to ask what you did or why you didn’t listen to them. As tempting as it is to launch into an explanation or defense, don’t. Ask them if they’re open to a discussion. If they say “yes,” they just agreed to listen to your explanation and (hopefully) engage in a productive conversation. If they say “no” (usually phrased as “not right now”), then you save everyone time and aggravation.
3. Keep a list of people and when you’ll talk to them – You don’t have to talk to everyone before you start. When you are referred to someone, pause to think about when they will be most helpful – at the start of the project, when you have a specific question, or towards the end when you’re working through operational consideration. Keeping a list of who to talk to and when reassures people that you’re collaborating and helps you manage expectations.
4. Before you start, align on priorities – Ultimately, your boss decides what the priorities are. So, no matter how important or urgent something feels to you, if it’s not important or urgent to her, you won’t get the time, attention, or resources you need. Save yourself time and heartache by understanding the important and urgent priorities and aligning your work to those.
5. Before you start, ask, “What do you need to see to say Yes?” – We live in a world of finite resources, which means that every person and dollar you receive is a person or dollar NOT going to another project. So, before you start, ask what the decision-maker needs to make decisions. Suppose the requests are unreasonable (like a 5-year NPV approved by Finance before you even have a proof of concept). In that case, you can try negotiating for more reasonable expectations or shift your focus.
Organizational Antibodies exist in every organization. It’s only a matter of time before they appear and even swarm. For the sake of your innovation efforts and your company’s long-term growth, stay vigilant and have a plan to work with them. It’s how you’ll keep innovation alive.
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
Forget secret handshakes, guarded rituals, and clandestine meetings. The easiest way to show that you’re a part of the “In-Crowd” is by throwing around obscure terms and incomprehensible acronyms.
Every industry has words and acronyms that only make sense to insiders. Stock traders have BOP (Balance of Power), Consumer Goods companies have ACV (All Commodities Volume), and, thanks to the military, we all have SNAFU (Situation Normal: All F-cked Up)
Innovators are no different. We throw around terms like Design Thinking, Lean Startup, ethnography, Discovery Driven Planning. We rattle off acronyms like VUCA JTBD, and MVP.
But do we really know what the industry terms and acronyms mean?
More importantly, are we sure that our definition is the same as our boss’ or colleague’s definition?
If you’re even a little bit like me, your answer to both of those questions is No.
And that feels awkward because it can lead to confusion, frustration, and disappointment in your work and your team.
So, let’s get back on the path to building clarity, efficiency, and support in your innovation efforts!
In Part 1, we’ll get into the What, Why, and How of the 5 of the most popular Innovation frameworks. Next week, in Part 2, we’ll dig into the When of each framework in the innovation process.
Popular “Innovation” Frameworks: What, Why, and How
What it is: A problem-solving framework that integrates the needs of people, the possibilities of technology, and the requirements for business success grounded in 3 principles:
Inspiration: Understand customer needs
Ideation: Generate creative ideas
Iteration: Rapidly prototype and test
Why it is important: Useful in solving “wicked problems,” problems that are ill-defined or tricky and for which pre-existing rules and domain knowledge will be of limited or no help (or potentially detrimental)
How you do it:
Qualitative research with tools like ethnography and Jobs to be Done to build empathy with the customer
Ideation to identify and explore lots of possible solutions
What it is: A way of making sense of the world’s complexity by looking at it in terms of wholes and relationships rather than by splitting it down into its parts; grounded in 5 principles:
Acknowledge the interrelatedness of problems
Develop empathy with the system
Strengthen human relationships to enable creativity and learning
Influence mental models to facilitate change
Adopt an evolutionary design approach to desired systemic change.
Why it is important: The increased complexity caused by globalization, migration, sustainability renders traditional design methods insufficient and increases the risk that designs result in unintended side effects.
How you do it:This is an emerging innovation discipline with multiple schools of thought and dozens of potential tools. To learn more and find tools, check out the Systemic Design Association.
What it is: A framework in which usability goals, user characteristics, environment, tasks, and workflow of a product, service, or process are given extensive attention at each stage of the design process and grounded in 6 principles
Design is based upon an explicit understanding of users, tasks and environments.
Users are involved throughout design and development.
Design is driven and refined by user-centered evaluation.
Process is iterative.
Design addresses the whole user experience.
Design team includes multidisciplinary skills and perspectives.
Why it is important: Optimizes the product around how users can, want, or need to use it so that users are not forced to change their behaviors and expectations to accommodate the product.
How you do it:Personas, scenarios, and use cases that capture the context, behaviors, habits, and instincts with
What it is: A methodology for developing businesses and products that emphasizes customer feedback over intuition and flexibility over planning, grounded in 5 principles:
Entrepreneurs are everywhere.
Entrepreneurship is management.
Validated learning.
Innovation Accounting.
Build-Measure-Learn
Why it is important: Aims to shorten product development cycles and rapidly discover if a proposed business model is viable
What it is: A project management philosophy that expanded to be used in innovation and business transformation
Individuals and Interactions Over Processes and Tools
Working Software Over Comprehensive Documentation
Customer Collaboration Over Contract Negotiation
Responding to Change Over Following a Plan
Why it is important: Improves time to market, quality, and employee morale
How you do it:The most common tools are:
Agile teams that are small, entrepreneurial, and empowered groups
Operating Model with focuses on leadership and culture, management systems, structures, talent, and processes
So What?
By now, you’ve probably noticed that the frameworks above are very similar – many of them are centered on the customer, value diverse experience expertise when creating solutions, and prioritize iteration over perfection.
So, which should you use?
The answer to that question depends on two things: your company and where you are in the innovation process. We’ll dive into those topics next week.
As you wait patiently for Part 2:
Tell me what I got wrong, what I missed, and what you think in the comments
Download this handy cheat sheet to the What, Why, and How of 5 Popular Innovation Frameworks
Before setting off on a journey to strange lands, most travelers take time to learn an essential phrase or two in the native tongue. After all, the ability to say “Hello” or “Help” or “Where’s the bathroom?” in the local language can mean the difference between a trip you remember forever and one that you want to forget immediately.
The same is true for people in large companies who set off on a quest to innovate – you’re in a strange land, and having a few handy phrases at the tip of your tongue can mean the difference between success and failure.
Here are the four most important phrases you should know as a corporate innovator
What does success look like?
Ask this at the beginning of every innovation effort. If you don’t, it’s very likely that what you view as success and what decision-makers view as success will be two different things.
Staffing up a new innovation team? What does success look like?
Starting a new project? What does success look like?
Developing and testing a prototype? What does success look like?
And don’t accept a vague or even qualitative answer to the question, like “we’ll know it when we see it” or “better employee engagement.” You need to know precisely what an effort contributes to and how leaders will evaluate the effort. Otherwise, it’s easy for managers to “move the goalposts” right when you think you’re about to score.
We expect a new innovation team to hold five brainstorming sessions and test 3 new products this year
We need this project to generate $10M revenue in 3 years from today
We need to understand how consumers will use this if we don’t give them any directions
Will you help me?
This question is perhaps the most challenging but most potent phrase in the innovation-to-corporate dictionary.
By the very nature of your work – making something new that creates value – you’re doing something that doesn’t fit cleanly into the existing structure. While that can be liberating, it also means that there are few, if any, people obligated to give you advice, resources, or support. That’s where this phrase comes in.
We all love to feel important and valued, and nothing makes people feel more important or valued than being asked for help. Plus, when you ask for help, people feel like they’re contributing to what you’re doing and start to feel a bit of ownership (or at least fondness) for it. Soon, you not only have advisors, but you also have partners, advocates, and champions.
Tell me more
This phrase is the ultimate innovation jiu-jitsu phrase because it turns your opponents’ strength (of opinion) against them and gives you powerful insights.
That will never work. Intriguing, tell me more.
We tried it, and it failed; the same thing will happen this time. I didn’t know that, tell me more.
If you do that, you’ll be fired. We don’t want that, so tell me more about why that would result.
Sometimes the rationale behind powerfully delivered dogmatic statements is logical and valid. Often, it’s emotional. The person who said it would never work is afraid that, if it does, their job will be in jeopardy. The person who remembers when it was tried before still bears the scars of that attempt and wants to protect you from the same experience. The person who says you’ll be fired for doing something may think that the rules are stricter than they are, and they’re trying to help you.
This phrase helps you figure out the reason behind the statement, the Why behind the What, so you can figure out what is true versus believed and how to get to your desired outcome.
What do you need to see to say “Yes”?
This question is my personal favorite, taught to me by a good friend, career innovator, and successful entrepreneur.
It is easy to say “No” and, in fact, that is the purpose of many people in a large organization.
Legal says No to keep the company o the right side of the law and out of lawsuits.
Accounting says No to keep the company financially healthy
Your boss says no because you have more work than you can handle, and this doesn’t seem essential.
Sometimes “No” is the correct answer. But if you start there, you’ll never know if it is the right answer or just the first, easiest, or most instinctual answer.
So, once you hear “No,” engage the person you’re talking to in a quick intellectual exercise and ask what they need to see to say “Yes.” By engaging them as an expert and your thought partner, you’re lowering their defenses and bringing them into a problem-solving mindset. Plus, you’re getting valuable insight into the type of data and evidence required to make progress.
What are other phrases every innovator should know?
As anyone who has ever tried to quickly learn a language for an extended trip, you’re best served by seeking out multiple sources.
After all, if I relied solely on Rosetta Stone to learn Danish before I moved to Copenhagen, I would have arrived knowing only how to say “the girl is on top of the airplane” (phonetically, it’s “pia pa flu-va-ma-skine”) and not “Hello” or “Help” or “Where’s the bathroom?”
So what are the phrases you repeatedly use to navigate your corporate innovation journey?
