Posts Tagged ‘Creativity’

If you want to understand innovation, understand novelty.

If you want to get innovation right, focus on novelty.

Novelty is the difference between how things are today and how they might be tomorrow.  And that comparison calibrates tomorrow’s idea within the context of how things are today.  And that makes all the difference. When you can define how something is novel, you have an objective measure of things.

How is it different than what you did last time?  If you don’t know, either you don’t know what you did last time or you don’t know the grounding principle of your new idea. Usually, it’s a little of the former and a whole lot of the latter.  And if you don’t know how it’s different, you can’t learn how potential customers will react to the novelty.  In fact, if you don’t know how it’s different, you can’t even decide who are the right potential customers.

A new idea can be novel in unique ways to different customer segments and it can be novel in opposite ways to intermediaries or other partners in the business model.  A customer can see the novelty as something that will make them more profitable and an intermediary can see that same novelty as something that will reduce their influence with the customer and lead to their irrelevance.  And, they’ll both be right.

Novelty is in the eye of the beholder, so you better look at it from their perspective.

Like with hot sauce, novelty comes in a range of flavors and heat levels.  Some novelty adds a gentle smokey flavor to your favorite meal and makes you smile while the ghost pepper variety singes your palate and causes you to lose interest in the very meal you grew up on.  With novelty, there is no singular level of Scoville Heat Unit (SHU) that is best.  You’ve got to match the heat with the situation.  Is it time to improve things a bit with a smokey, yet subtle, chipotle? Or, is it time to submerge things in pure capsaicin and blow the roof off?  The good news is the bad news – it’s your choice.

With novelty, you can choose subtle or spicy.  Choose wisely.

And like with hot sauce, novelty doesn’t always mix well with everything else on the plate. At the picnic, when you load your plate with chicken wings, pork ribs, and apple pie, it’s best to keep the hot sauce away from the apple pie.  Said more strongly, with novelty, it’s best to use separate plates.  Separate the teams – one team to do heavy novelty work, the disruptive work, to obsolete the status quo, and a separate team to the lighter novelty work, the continuous improvement work, to enhance the existing offering.

Like with hot sauce, different people have different tolerance levels for novelty. For a given novelty level, one person can be excited while another can be scared.  And both are right.  There’s no sense in trying to change a person’s tolerance for novelty, they either like it or they don’t.  Instead of trying to teach them to how to enjoy the hottest hot sauce, it’s far more effective to choose people for the project whose tolerance for novelty is in line with the level of novelty required by the project.

Some people like habanero hot sauce, and some don’t.  And it’s the same with novelty.

How to Decide if Your Problem is Worth Solving

How to decide if a problem is worth solving?

If it’s a new problem, try to solve it.

If it’s a problem that’s already been solved, it can’t be a new problem.  Let someone else re-solve it.

If a new problem is big, solve it in a small way.  If that doesn’t work, try to solve it in a smaller way.

If there’s a consensus that the problem is worth solving, don’t bother. Nothing great comes from consensus.

If the Status Quo tells you not to solve it, you’ve hit paydirt!

If when you tell people about solving the problem they laugh, you’re onto something.

If solving the problem threatens the experts, double down.

If solving the problem obsoletes your most valuable product, solve it before your competition does.

If solving the problem blows up your value proposition, light the match.

If solving the problem replaces your product with a service, that’s a recipe for recurring revenue.

If solving the problem frees up a factory, well, now you have a free factory to make other things.

If solving the problem makes others look bad, that’s why they’re trying to block you from solving it.

If you want to know if you’re doing it right, make a list of the new problems you’ve tried to solve.

If your list is short, make it longer.

“CERDEC Math and Science Summer Camp, 2013” by CCDC_C5ISR is licensed under CC BY 2.0

If nine out of ten projects projects fail, you’re doing it wrong.

For work that has not been done before, there’s no right answer.  The only wrong answer is to say “no” to trying something new.  Sure, it might not work.  But, the only way to guarantee it won’t work is to say no to trying.

If innovation projects fail nine out of ten times, you can increase the number of projects you try or you can get better at choosing the projects to say no to.  I suggest you say learn to say yes to the one in ten projects that will be successful.

If you believe that nine out of ten innovation projects will fail, you shouldn’t do innovation for a living.  Even if true, you can’t have a happy life going to work every day with a ninety percent chance of failure.  That failure rate is simply not sustainable.  In baseball, the very best hitters of all time were unsuccessful sixty percent of the time, yet, even they focused on the forty percent of the time they got it right.  Innovation should be like that.

If you’ve failed on ninety percent of the projects you’ve worked on, you’ve probably been run out of town at least several times.  No one can fail ninety percent of the time and hold onto their job.

If you’ve failed ninety percent of the time, you’re doing it wrong.

If you’ve failed ninety percent of the time, you’ve likely tried to solve the wrong problems.  If so, it’s time to learn how to solve the right problems.  The right problems have two important attributes: 1) People will pay you if they are solved. 2) They’re solvable.  I think we know a lot about the first attribute and far too little about the second. The problem with solvability is that there’s no partial credit, meaning, if a problem is almost solvable, it’s not solvable. And here’s the troubling part: if a problem is almost solved, you get none of the money.  I suggest you tattoo that one on your arm.

As a subject matter expert, you know what could work and what won’t.  And if you don’t think you can tell the difference, you’re not a subject matter expert.

Here’s a rule to live by: Don’t work on projects that you know won’t work.

Here’s a corollary: If your boss asks you to work on something that won’t work, run.

If you don’t think it will work, you’re right, even if you’re not.

If it might work, that’s about right. If it will work, let someone else do it. If it won’t work, run.

If you’ve got no reason to believe it will work, it won’t.

If you can’t imagine it will work, it won’t.

If someone else says it won’t work, it might.

If someone else tries to convince you it won’t work, they may have selfish reasons to think that way.

It doesn’t matter if others think it won’t work. It matters what you think.

So, what do you think?

If you someone asks you to believe something you don’t, what will you do?

If you try to fake it until you make it, the Universe will make you pay.

If you think you can outsmart or outlast the Universe, you can’t.

If you have a bad feeling about a project, it’s a bad project.

If others tell you that it’s a bad project, it may be a good one.

Only you can decide if a project is worth doing.

It’s time for you to decide.

“Good example of Crossfit Weight lifting – In Crossfit Always lift until you reach the point of Failure or you tear something” by CrossfitPaleoDietFitnessClasses is licensed under CC BY 2.0

Some Problems With Problems

If you don’t know what the problem is, that’s your first problem.

A problem can’t be a problem unless there’s a solution.  If there’s no possible solution, don’t try to solve it, because it’s not a problem.

If there’s no problem, you have a big problem.

If you’re trying to solve a problem, but the solution is outside your sphere of influence, you’re taking on someone else’s problem.

If someone tries to give you a gift but you don’t accept it, it’s still theirs. It’s like that with problems.

If you want someone to do the right thing, create a problem for them that, when solved, the right thing gets done.

Problems are good motivators and bad caretakers.

A problem is between two things, e.g., a hammer and your thumb.  Your job is to figure out the right two things.

When someone tries to give you their problem, keep your hands in your pockets.

A problem can be solved before it happens, while it happens, or after it happened.  Each time domain has different solutions, different costs, and different consequences.  Your job is to choose the most appropriate time domain.

If you have three problems, solve one at a time until you’re done.

Solving someone else’s problem is a worst practice.

If you solve the wrong problem, you consume all the resources needed to solve the right problem without any of the benefits of solving it.

Ready, fire, aim is no way to solve problems.

When it comes to problems, defining IS solving.

If you learn one element of problem-solving, learn to see when someone is trying to give you their problem.

“My first solved Rubik’s cube” by Nina Stawski is licensed under CC BY 2.0

Continuous Improvement Is Dead

Continuous Improvement – Do what you did last time, just three percent better, so none of your people can try new things.

Discontinuous Improvement – Make a radical step-change in performance at the expense of continuously improving it.

 

Continuous Improvement – Do what you did last time so you can say “no” to projects that are magical.

No-To-Yes – Make the product do something it cannot.  That way you can sell a new value proposition to new customers and new markets.  And you can threaten those that are clinging to your tired value proposition.

 

Continuous Improvement – Do what you did last time so no one will be threatened by meaningful change.

Less With Far Less – Reduce the goodness of today’s offering to free up design space and create an entirely new offering that provides 80% of the goodness at 20% of the price. That way, you can sell a whole new family of offerings to customers that cannot buy today’s offering.

 

Continuous Improvement – Do what you did last time so we can rest on our laurels.

Obsolete Your Best Work – Design and commercialize new offerings that purposefully make obsolete your most profitable offering.  This requires level 5 courage.

 

And how do you do all this? Mobilize the Trust Network.

 

“fear — may 9 (day 9)” by theogeo is licensed under CC BY 2.0

The Innovation Mantra

We have an immense distaste for uncertainty. And, as a result, we create for ourselves a radical and unskillful overestimation of our ability to control things. Our distaste of uncertainty is really a manifestation of our fear of death. When we experience and acknowledge uncertainty, it’s an oblique reminder that we will die. And that’s why talk ourselves into the belief we can control thing we really cannot.  It’s a defense mechanism that creates distance between ourselves and from feeling our fear of death.  And it’s the obliquity that makes it easier to overestimate our ability to control our environment.  Without the obliquity, it’s clear we can’t control our environment, the very thing we wake up to every morning, and it’s clear we can’t control much. And if we can’t control much, we can’t control our aging and our ultimate end.  And this is why we reject uncertainty at all costs.

Predictable, controllable, repeatable, measurable – overt rejections of uncertainty. Six Sigma – Measure, Analyze, Improve, Control – overt rejection of uncertainty.  Standard work – rejection of uncertainty. Don’t change the business model – a rejection of uncertainty. A rejection of novelty is a rejection of uncertainty. And that’s why we don’t like novelty. It scares us deeply. And it scares us because it reminds us that everything changes, including our skin, joints, and hairline. And that’s why it’s so challenging to do innovation.

Innovation reminds us of our death and that’s why it’s difficult?  Really? Yes.

Six Sigma is comforting because its programmatic illusion of control lets us forget about our death? Yes.

The aging business model reminds us of our death and that’s why we won’t let it go? Yes.

That’s crazy! Yes, but at the deepest level, I think it’s true.

I understand if you disagree with my rationale. And I understand if you think my thinking is morbid. If that’s the case, I suggest you write down why you think it’s so incredibly difficult to create a new business model, to do novel work, or to obsolete your best work. I’ll stop for a minute to give you time to grab a pen and paper. Okay, now put your pen to paper and write down why doing innovation (doing novel work) is so difficult. Now, ask yourself why that is. And do that three more times. Where did you end up? What’s the fundamental reason why doing new work (and the uncertainty that comes with it) is so difficult to do?

To be clear, I’m not advocating that you tell everyone that innovation is difficult because it reminds them that they’ll die. I explained my rationale to give you an idea of the magnitude of the level of fear around uncertainty so that, when someone is scared to death of novelty, you might help them navigate their fear.

Trying something new doesn’t invalidate what you did over the last decade to grow your business, nor will it replace it immediately, if it all.  Maybe the new work will add to what you’ve done over the last decade. Maybe the new work will amplify what’s made you successful. Maybe the new work will slowly and effectively migrate your business to greener pastures. And maybe it won’t work at all. Or, maybe your customers will make it work and bury you and your business.

With innovation, start small.  That way the threat is smaller.  Run small experiments and share the results, especially the bad results.  That way you demonstrate that unanticipated results don’t kill you and, when you share them, you demonstrate that you’re not afraid of uncertainty. Try many things in parallel to demonstrate that it’s okay that everything doesn’t turn out well and you’re okay with it.  And when someone asks what you’ll do next, tell them “I don’t know because it depends on how the next experiment turns out.”

When you’re asked when you’ll be done with an innovation project, tell them “I don’t know because the work has never been done before.” And if they say you must give them a completion date, tell them “If you must have a completion date, you do the project.”

When you’re running multiple experiments in parallel and you’re asked what you’ll do next, tell them you’ll do “more of what works and less of what doesn’t.” And if they say “that’s not acceptable”, then tell them “Well, then you run the project.”

We don’t have nearly as much control as our minds want to us believe, but that’s okay as long as we behave like we know it’s true. Uncertainty is uncomfortable, but that’s not a bad thing. In fact, I think it’s a good thing.

If people aren’t afraid, there can be no uncertainty. And if there’s no uncertainty, there can be no novelty. And if there’s no novelty, there can be no innovation. If people aren’t afraid, you’re doing it wrong.

As a leader, tell them you’re afraid but you’re going to do it anyway.

As a leader, tell your team that it’s natural to be afraid and their fear is a leading indicator of innovation.

As a leader, tell them there’s one thing you’re certain about – that innovation is uncertain.

And when things get difficult, repeat the Innovation Mantra: Be afraid and do it anyway.

“Mantra” by j / f / photos is licensed under CC BY-ND 2.0

It’s time to start starting.

What do we do next? I don’t know

What has been done before?

What does it do now?

What does it want to do next?

If it does that, who cares?

 

Why should we do it? I don’t know.

Will it increase the top line?  If not, do something else.

Will it increase the bottom line?  If so, let someone else do it.

What’s the business objective?

 

Who will buy it? I don’t know.

How will you find out?

What does it look like when you know they’ll buy it?

Why do you think it’s okay to do the work before you know they’ll buy it?

 

What problem must be solved? I don’t know.

How will you define the problem?

Why do you think it’s okay to solve the problem before defining it?

Why do you insist on solving the wrong problem? Don’t you know that ready, fire, aim is bad for your career?

Where’s the functional coupling? When will you learn about Axiomatic Design?

Where is the problem? Between which two system elements?

When does the problem happen? Before what? During what? After what?

Will you separate in time or space?

When will you learn about TRIZ?

 

Who wants you to do it? I don’t know.

How will you find out?

When will you read all the operating plans?

Why do you think it’s okay to start the work before knowing this?

 

Who doesn’t want you to do it? I don’t know.

How will you find out?

Who looks bad if this works?

Who is threatened by the work?

Why do you think it’s okay to start the work before knowing this?

 

What does it look like when it’s done? I don’t know.

Why do you think it’s okay to start the work before knowing this?

 

What do you need to be successful? I don’t know.

Why do you think it’s okay to start the work before knowing this?

 

Starting is essential, but getting ready to start is even more so.

 

Image credit — Jon Marshall

Wrong Questions to Ask When Doing Technology Development

I know you’re trying to do something that has never been done before, but when will you be done? I don’t know.  We’ll run the next experiment then decide what to do next.  If it works, we’ll do more of that.  And if it doesn’t, we’ll do less of that. That’s all we know right now.

I know you’re trying to create something that is new to our industry, but how many will we sell? I don’t know. Initial interviews with customers made it clear that this is an important customer problem. So, we’re trying to figure out if the technology can provide a viable solution.  That’s all we know right now.

No one is asking for that obscure technology. Why are you wasting time working on that?  Well, the voice of the technology and the S-curve analyses suggest the technology wants to move in this direction, so we’re investing this solution space.  It might work and it might not.  That’s all we know right now.

Why aren’t you using best practices? If it hasn’t been done before, there can be no best practice.  We prefer to use good practice or emergent practice.

There doesn’t seem like there’s been much progress.  Why aren’t you running more experiments? We don’t know which experiments to run, so we’re taking some time to think about what to do next.

Will it work?  I don’t know.

That new technology may obsolete our most profitable product line.  Shouldn’t you stop work on that? No. If we don’t obsolete our best work, someone else will. Wouldn’t it be better if we did the obsoleting?

How many more people do you need to accelerate the technology development work? None.  Small teams are better.

Sure, it’s a cool technology, but how much will it cost?  We haven’t earned the right to think about the cost.  We’re still trying to make it work.

So, what’s your solution? We don’t know yet.  We’re still trying to formulate the customer problem.

You said you’d be done two months ago.  Why aren’t you done yet? I never said we’d be done two months ago. You asked me for a completion date and I could not tell you when we’d be done.  You didn’t like that answer so I suggested that you choose your favorite date and put that into your spreadsheet. We were never going to hit that date, and we didn’t.

We’ve got a tight timeline.  Why are you going home at 5:00? We’ve been working on this technology for the last two years.  This is a marathon.  We’re mentally exhausted.  See you tomorrow.

If you don’t work harder, we’ll get someone else to do the technology development work.  What do you think about that? You are confusing activity with progress.  We are doing the right analyses and the right thinking and we’re working hard.  But if you’d rather have someone else lead this work, so would I.

We need a patented solution.  Will your solution be patentable? I don’t know because we don’t yet have a solution. And when we do have a solution, we still won’t know because it takes a year or three for the Patent Office to make that decision.

So, you’re telling me this might not work?  Yes. That’s what I’m telling you.

So, you don’t know when you’ll be done with the technology work, you don’t know how much the technology will cost, you don’t know if it will be patentable, or who will buy it? That’s about right.

Image credit — Virtual EyeSee

Two Sides of the Equation

If you want new behavior, you must embrace conflict.

If you can’t tolerate the conflict, you’ll do what you did last time.

If your point of view angers half and empowers everyone else, you made a difference.

If your point of view meets with 100% agreement, you wasted everyone’s time.

If your role is to create something from nothing, you’ve got to let others do the standard work.

If your role is to do standard work, you’ve got to let others create things from scratch.

If you want to get more done in the long term, you’ve got to make time to grow people.

If you want to get more done in the short term, you can’t spend time growing people.

If you do novel work, you can’t know when you’ll be done.

If you are asked for a completion date, I hope you’re not expected to do novel work.

If you’re in business, you’re in the people business.

If you’re not in the people business, you’ll soon be out of business.

If you call someone on their behavior and they thank you, you were thanked by a pro.

If you call someone on their behavior and they call you out for doing it, you were gaslit.

If you can’t justify doing the right project, reduce the scope, and do it under the radar.

If you can’t prevent the start of an unjust project, find a way to work on something else.

If you are given a fixed timeline and fixed resources, flex the schedule.

If you are given a fixed timeline, resources, and schedule, you’ll be late.

If you get into trouble, ask your Trust Network for help.

If you have no Trust Network, you’re in trouble.

If you have a problem, tell the truth and call it a problem.

If you can’t tell the truth, you have a big problem.

If you are called on your behavior, own it.

If you own your behavior, no one can call you on it.

Image credit – Mary Trebilco

Bringing Your Whole Self to Work

Do you bring your whole self to work? If not, how do you feel about that?

When you demonstrate your unique goodness and it’s met with “You don’t fit in.” they may say they want you to fit in, but, really, that’s objective evidence that they need your unique goodness.

Witches were burned at the stake because their special powers frightened people.

If it’s a good idea, don’t block it because people call it heresy.

The Universe doesn’t care if it’s heresy, as long as it’s a good idea.

The Universe doesn’t discriminate against witches.

If you’re a plumber that fixes pipes and fixes potholes, they’ll expect you to fix pipes and fill potholes.

Sometimes you’ve got to withhold the solution If you want the organizational learning to happen.

If you fill all the potholes, the company never learns that someone’s not doing their job.

A plumber who fixes pipes and fills potholes should be paid more than a plumber that just fixes pipes.

When no one listens to reason, the only thing left to do is let the wheels fall off.

And if you really care about the long-term success of the company, you’ll let them fall off.

If you see things differently, you’re obligated to say so, even if you’re wrong.

When you speak truth to Power, does Power thank you or kick you?

If after speaking unsayable truth to Power, they kick you, that says a lot about Power.

When you’re satisfied with what you have, striving-based motivation tactics have no power.

It’s easy to mentor down into the organization, but it takes a special person to mentor uphill.

Never do your boss’s job.

When successful thinking becomes geriatric, it’s time for hospice.

Successful business models change only after they become unsuccessful.

Change happens only after exhausting all other possibilities. And it takes special people to make it happen.

If you ‘re afraid and hold back because you’re concerned about being burned at the stake, you should put your magic wand in your pocket, jump on your broom (or vacuum cleaner), and find another job.

Image credit — Jerzy Kociatkiewicz

Want to succeed? Learn how to deliver customer value.

Whatever your initiative, start with customer value. Whatever your project, base it on customer value. And whatever your new technology, you guessed it, customer value should be front and center.

Whenever the discussion turns to customer value, expect confusion, disagreement, and, likely, anger. To help things move forward, here’s an operational definition I’ve found helpful:

When they buy it for more than your cost to make it, you have customer value.

And when there’s no way to pull out of the death spiral of disagreement, use this operational definition to avoid (or stop) bad projects:

When no one will buy it, you don’t have customer value and it’s a bad project.

As two words, customer and value don’t seem all that special. But, when you put them together, they become words to live by.  But, also, when you do put them together, things get complicated.  Here’s why.

To provide customer value, you’ve got to know (and name) the customer.  When you asked “Who is the customer?” the wheels fall off. Here are some wrong answers to that tricky question. The Board of Directors is the customer. The shareholders are the customers. The distributor is the customer. The OEM that integrates your product is the customer. And the people that use the product are the customer. Here’s an operational definition that will set you free:

When someone buys it, they are the customer.

When the discussions get sticky, hold onto that definition. Others will try to bait you into thinking differently, but don’t bite. It will be difficult to stand your ground.  And if you feel the group is headed in the wrong direction, try to set things right with this operational definition:

When you’ve found the person who opens their wallet, you’ve found the customer.

Now, let’s talk about value. Isn’t value subjective? Yes, it is.  And the only opinion that matters is the customer’s. And here’s an operational definition to help you create customer value:

When you solve an important customer problem, they find it valuable.

And there you have it.  Putting it all together, here’s the recipe for customer value:

  1. Understand who will buy it.
  2. Understand their work and identify their biggest problem.
  3. Solve their problem and embed it in your offering.
  4. Sell it for more than it costs you to make it.

Image credit — Caroline

Mike Shipulski Mike Shipulski
Subscribe via Email

Enter your email address:

Delivered by FeedBurner

Archives