Posts Tagged ‘no-to-yes’

If you want to change things, do a demo.

When you demo something new, you make the technology real.  No longer can they say – that’s not possible.

When you demo something new, you help people see what it is and what it isn’t.  And that brings clarity.

When you demo something new, people take sides. And that says a lot about them.

When you demo something new, be prepared to demo it again. It takes time for people to internalize new concepts.

When someone asks you to repeat the demo so others can see it, it’s a sign there’s something interesting about the demo.  Repeat it.

When someone calls out fault with a minor element of the demo, they also reinforce the strength of the main elements.

When you demo something new and it works perfectly, you should have demo’d it sooner.

When the demo works perfectly, you’re not trying hard enough.

When you demo something new, there is no way to predict the action items spawned by the demo.  In fact, the reason to do the demo is to learn the next action items.

When you demo something new, make the demo short so the conversation can be long.

When you demo something new, shut your mouth and let the demo do the talking.

When you demo something new, keep track of the questions that arise.  Those questions will inform the next demo.

When you demo something new and it’s misunderstood, congratulations. You’ve helped the audience loosen their thinking.

If you want to change people’s thinking, do a demo.

Image credit – Ralf Steinberger

The Difficulty of Goal Setting in Domains of High Uncertainty

When you work in domains of high uncertainty, creating goals for the next year is exceptionally difficult.

When you try to do something that hasn’t been done before, things may blow up instantly, things may work out after two years of hard work, or things may never work.  So, how do you create the goal for that work? Do you give yourself one month to complete the work? And things haven’t worked out at the end of the month, do you stop the work or do you keep going?  If it blows up instantly, but you think you know why, do you keep going? Do you extend the due date for the goal?  At the start of the work, should the timeline have been set to one year instead of one month?  And who decides that?  And how do they decide?

When you have to create your goals for something that hasn’t been done before and the objectives of the work are defined by another team, yet that team hasn’t done the prework and cannot provide those objectives, what do you do? Do you create a goal for the other team to define the objectives? And what if you have no control over that team’s priorities and you don’t know when (or if) they’ll provide the needed information?  What does a goal look like when you don’t know the objectives of the work nor do you know when (or if) you’ll get that information.  Can you even create a goal for the work when you don’t know what that work is?  And how do you estimate a completion date or the resource requirements (both the flavor and quantity) when you don’t know the objectives?  What does that goal look like?

When you have to create your goals for a team of ten specialized people who each have unique skills, but you don’t know the objectives of the work, when that work can start, or when that work will finish, how do you cascade the team’s goals to each team members?  What do their goals look like?  Is the first goal to figure out the goal?  How many goals does it take to fill up their year when you don’t know what the work is or how long it will take?

When working in domains of high uncertainty, the goals go like this: define the system as it is, define something you want to improve, try to improve it, and then do the next right thing.  Unfortunately, that doesn’t fit well with the traditional process of setting yearly goals.

And your two questions should be: How do you decide what to improve? and How do you choose the next right thing?

Image credit — Rab Lawrence

What do you like to do?

I like to help people turn complex situations into several important learning objectives.

I like to help people turn important learning objectives into tight project plans.

I like to help people distill project plans into a single-page spreadsheet of who does what and when.

I like to help people start with problem definition.

I like to help people stick with problem definition until the problems solve themselves.

I like to help people structure tight project plans based on resource constraints.

I like to help people create objective measures of success to monitor the projects as they go.

I like to help people believe they can do the almost impossible.

I like to help people stand three inches taller after they pull off the unimaginable.

I like to help people stop good projects so they can start amazing ones.

If you want to do more of what you like and less of what you don’t, stop a bad project to start a good one.

So, what do you like to do?

Image credit — merec0

How To Be Novel

By definition, the approach that made you successful will become less successful over time and, eventually, will run out of gas.  This fundamental is not about you or your approach, rather it’s about the nature of competition and evolution.  There’s an energy that causes everything to change, grow and improve and your success attracts that energy.  The environment changes, the people change, the law changes and companies come into existence that solve problems in better and more efficient ways.  Left unchanged, every successful business endeavor (even yours) has a half-life.

If you want to extend the life of your business endeavor, you’ve got to be novel.

By definition, if you want to grow, you’ve got to raise your game. You’ve got to do something different.  You can’t change everything, because that’s inefficient and takes too long.  So, you’ve got to figure out what you can reuse and what you’ve got to reinvent.

If you want to grow, you’ve got to be novel.

Being novel is necessary, but expensive.  And risky. And scary.  And that’s why you want to add just a pinch of novelty and reuse the rest.  And that’s why you want to try new things in the smallest way possible.  And that’s why you want to try things in a time-limited way. And that’s why you want to define what success looks like before you test your novelty.

Some questions and answers about being novel:

Is it easy to be novel? No.  It’s scary as hell and takes great emotional strength.

Can anyone be novel? Yes. But you need a good reason or you’ll do what you did last time.

How can I tell if I’m being novel? If you’re not scared, you’re not being novel.  If you know how it will turn out, you’re not being novel.  If everyone agrees with you, you’re not being novel.

How do I know if I’m being novel in the right way? You cannot. Because it’s novel, it hasn’t been done before, and because it hasn’t been done before there’s no way to predict how it will go.

So, you’re saying I can’t predict the outcome of being novel?  Yes.

If I can’t predict the outcome of being novel, why should I even try it? Because if you don’t, your business will go away.

Okay.  That last one got my attention.  So, how do I go about being novel? It depends.

That’s not a satisfying answer. Can you do better than that? Well, we could meet and talk for an hour.  We’d start with understanding your situation as it is, how this current situation came to be, and talk through the constraints you see.  Then, we’d talk about why you think things must change.  I’d then go away for a couple of days and think about things.  We’d then get back together and I’d share my perspective on how I see your situation.  Because I’m not a subject matter expert in your field, I would not give you answers, but, rather, I’d share my perspective that you could use to inform your choice on how to be novel.

“Giraffe trying to catch a twig with her tongue” by Tambako the Jaguar is licensed under CC BY-ND 2.0

The Power of Prototypes

A prototype moves us from “That’s not possible.” to “Hey, watch this!”

A prototype moves us from “We don’t do it that way.” to “Well, we do now.”

A prototype moves us from “That’s impossible.” to “As it turns out, it was only almost impossible.”

A prototype turns naysayers into enemies and profits.

A prototype moves us from an argument to a new product development project.

A prototype turns analysis-paralysis into progress.

A prototype turns a skeptical VP into a vicious advocate.

A prototype turns a pet project into top-line growth.

A prototype turns disbelievers into originators of the idea.

A prototype can turn a Digital Strategy into customer value.

A prototype can turn an uncomfortable Board of Directors meeting into a pizza party.

A prototype can save a CEO’s ass.

A prototype can be too early, but mostly they’re too late.

If the wheels fall off your first prototype, you’re doing it right.

If your prototype doesn’t dismantle the Status-Quo, you built the wrong prototype.

A good prototype violates your business model.

A prototype doesn’t care if you see it for what it is because it knows everyone else will.

A prototype turns “I don’t believe you.” into “You don’t have to.”

When you’re told “Don’t make that prototype.” you’re onto something.

A prototype eats not-invented-here for breakfast.

A prototype can overpower the staunchest critic, even the VP flavor.

A prototype moves us from “You don’t know what you’re talking about.” to “Oh, yes I do.”

If the wheels fall off your second prototype, keep going.

A prototype is objective evidence you’re trying to make a difference.

You can argue with a prototype, but you’ll lose.

If there’s a mismatch between the theory and the prototype, believe the prototype.

A prototype doesn’t have to do everything, but it must do one important thing for the first time.

A prototype must be real, but it doesn’t have to be really real.

If your prototype obsoletes your best product, congratulations.

A prototype turns political posturing into reluctant compliance and profits.

A prototype turns “What the hell are you talking about?” into “This.”

A good prototype bestows privilege on the prototyper.

A prototype can beat a CEO in an arm-wrestling match.

A prototype doesn’t care if you like it. It only cares about creating customer value.

If there’s an argument between a well-stated theory and a well-functioning prototype, it’s pretty clear which camp will refine their theory to line up with what they just saw with their own eyes.

A prototype knows it has every right to tell the critics to “Kiss my ass.” but it knows it doesn’t have to.

You can argue with a prototype, but shouldn’t.

A prototype changes thinking without asking for consent.

Image credit — Pedro Ribeiro Simões

When it’s Time to Make a Difference

 

When it’s time to make meaningful change, there’s no time for consensus.

When the worn path of success must be violated, use a small team.

When it’s time for new thinking, create an unreasonable deadline, and get out of the way.

The best people don’t want the credit, they want to be stretched just short of their breaking point.

When company leadership wants you to build consensus before moving forward, they don’t think the problem is all that important or they don’t trust you.

When it’s time to make unrealistic progress, it’s time for fierce decision making.

When there’s no time for consensus, people’s feelings will be hurt. But there’s no time for that either.

When you’re pissed off because there’s been no progress for three years, do it yourself.

When it’s time to make a difference, permission is not required. Make a difference.

The best people must be given the responsibility to use their judgment.

When it’s time to break the rules, break them.

When the wheels fall off, regardless of the consequences, put them back on.

When you turn no into yes and catch hell for violating protocol, you’re working for the wrong company.

When everyone else has failed, it’s time to use your discretion and do as you see fit.

When you ask the team to make rain and they balk, you didn’t build the right team.

When it’s important and everyone’s afraid of getting it wrong, do it yourself and give them the credit.

The best people crave ridiculous challenges.

When the work must be different, create an environment that demands the team acts differently.

When it’s time for magic, keep the scope tight and the timeline tighter.

When the situation is dire and you use your discretion, to hell with anyone who has a problem with it.

When it’s time to pull a rabbit out of the hat, you get to decide what gets done and your special team member gets to decide how to go about it.  Oh, and you also get to set an unreasonable time constraint.

When it’s important, to hell with efficiency.  All that matters is effectiveness.

The best people want you to push them to the limit.

When you think you might get fired for making a difference, why the hell would you want to work for a company like that?

When it’s time to disrespect the successful business model, it’s time to create harsh conditions that leave the team no alternative.

The best people want to live where they want to live and do impossible work.

Image credit — Bernard Spragg. Nz

The Five Hardships of Success

Everything has a half-life, but we don’t behave that way.  Especially when it comes to success.  The thinking goes – if it was successful last time, it will be successful next time.  So, do it again. And again.  It’s an efficient strategy – the heavy resources to bring it to life have already been spent. And it’s predictable – the same customers, the same value proposition, the same supply base, the same distribution channel, and the same technology. And it’s dangerous.

Success is successful right up until it isn’t. It will go away. But it will take time.  A successful product line won’t fall off the face of the earth overnight. It will deliver profits year-over-year and your company will come to expect them.  And your company will get hooked on the lifestyle enabled by those profits. And because of the addiction, when they start to drop off the company will do whatever it takes to convince itself all is well.  No need to change.  If anything, it’s time to double-down on the successful formula.

Here’s a rule: When your successful recipe no longer brings success, it’s not time to double-down.

Success’s decline will be slow, so you have time.  But creating a new recipe takes a long time, so it’s time to declare that the decline has already started. And it’s time to learn how to start work on the new recipe.

Hardship 1 – Allocate resources differently. The whole company wants to spend resources on the same old recipes, even when told not to.  It’s time to create a funding stream that’s independent of the normal yearly planning cycle.  Simply put, the people at the top have to reallocate a part of the operating budget to projects that will create the next successful platform.

Hardship 2 – Work differently. The company is used to polishing the old products and they don’t know how to create new ones. You need to hire someone who can partner with outside companies (likely startups), build internal teams with a healthy disrespect for previous success, create mechanisms to support those teams and teach them how to work in domains of high uncertainty.

Hardship 3 – See value differently. How do you provide value today? How will you provide value when you can’t do it that way? What is your business model? Are you sure that’s your business model? Which elements of your business model are immature? Are you sure? What is the next logical evolution of how you go about your business? Hire someone to help you answer those questions and create projects to bring the solutions to life.

Hardship 4 – Measure differently. When there’s no customer, no technology and no product, there’s no revenue.  You’ve got to learn how to measure the value of the work (and the progress) with something other than revenue.  Good luck with that.

Hardship 5 – Compensate differently. People that create something from nothing want different compensation than people that do continuous improvement. And you want to move quickly, violate the status quo, push through constraints and create whole new markets. Figure out the compensation schemes that give them what they want and helps them deliver what you want.

This work is hard, but it’s not impossible. But your company doesn’t have all the pieces to make it happen.  Don’t be afraid to look outside your company for help and partnership.

Image credit — Insider Monkey

What Good Ideas Feel Like

If you have a reasonably good idea, someone will steal it, make it their own and take credit. No worries, this is what happens with reasonably good ideas.

If you have a really good idea, you’ll have to explain it several times before anyone understands it. Then, once they understand, you’ll have to help them figure out how to realize value from the idea. And after several failed attempts at implementation, you’ll have to help them adjust their approach so they can implement successfully. Then, after the success, someone will make it their own and take credit. No worries, this is what happens with really good ideas.

When you have an idea so good that it threatens the Status Quo, you’ll get ridiculed. You’ll have to present the idea once every three months for two years. The negativity will decrease slowly, and at the end of two years the threatening idea will get downgraded to a really good idea. Then it will follow the wandering path to success described above. Don’t feel special. This is how it goes with ideas good enough to threaten.

And then there’s the rarified category that few know about. This is the idea that’s so orthogonal it scares even you. This idea takes a year or two of festering before you can scratch the outer shell of it. Then it takes another year before you can describe it to yourself. And then it takes another year before you can bring yourself to speak of it. And then it takes another six months before you share it outside your trust network.  And where the very best ideas get ridiculed, with this type of idea people don’t talk about the idea at all, they just think you’ve gone off the deep end and become unhinged. This class of idea is so heretical it makes people uncomfortable just to be near you. Needless to say, this class of idea makes for a wild ride.

Good ideas make people uncomfortable. That’s just the way it is.  But don’t let this get in the way.  More than that, I urge you to see the push-back and discomfort as measures of the idea’s goodness.

If there’s no discomfort, ridicule or fear, the idea simply isn’t good enough.

Image credit – Mindaugas Danys

Transcending a Culture of Continuous Improvement

We’ve been too successful with continuous improvement. Year-on-year, we’ve improved productivity and costs.  We’ve improved on our existing products, making them slightly better and adding features.

Our recipe for success is the same as last year plus three percent. And because the customers liked the old one, they’ll like the new one just a bit more. And the sales can sell the new one because its sold the same way as the old one.  And the people that buy the new one are the same people that bought the old one.

Continuous improvement is a tried-and-true approach that has generated the profits and made us successful. And everyone knows how to do it.  Start with the old one and make it a little better. Do what you did last time (and what you did the time before). The trouble is that continuous improvement runs out of gas at some point. Each year it gets harder to squeeze out a little more and each year the return on investment diminishes. And at some point, the same old improvements don’t come. And if they do, customers don’t care because the product was already better than good enough.

But a bigger problem is that the company forgets to do innovative work. Though there’s recognition it’s time to do something different, the organization doesn’t have the muscles to pull it off. At every turn, the organization will revert to what it did last time.

It’s no small feat to inject new work into a company that has been successful with continuous improvement.  A company gets hooked on the predictable results of continuous which grows into an unnatural aversion to all things different.

To start turning the innovation flywheel, many things must change. To start, a team is created and separated from the continuously improving core.  Metrics are changed, leadership is changed and the projects are changed. In short, the people, processes, and tools must be built to deal with the inherent uncertainty that comes with new work.

Where continuous improvement is about the predictability of improving what is, innovation is about the uncertainty of creating what is yet to be. And the best way I know to battle uncertainty is to become a learning organization.  And the best way to start that journey is to create formal learning objectives.

Define what you want to learn but make sure you’re not trying to learn the same old things. Learn how to create new value  for customers; learn how to deliver that value to new customers; learn how to deliver that new value in new ways (new business models.)

If you’re learning the same old things in the same old way, you’re not doing innovation.

Innovation Truths

If it’s not different, it can’t be innovation.

With innovation, ideas are the easy part. The hard part is creating the engine that delivers novel value to customers.

The first goal of an innovation project is to earn the right to do the second hardest thing. Do the hardest thing first.

Innovation is 50% customer, 50% technology and 75% business model.

If you know how it will turn out, it’s not innovation.

Don’t invest in a functional prototype until customers have placed orders for the sell-able product.

If you don’t know how the customer will benefit from your innovation, you don’t know anything.

If your innovation work doesn’t threaten the status quo, you’re doing it wrong.

Innovation moves at the speed of people.

If you know when you’ll be finished, you’re not doing innovation.

With innovation, the product isn’t your offering. Your offering is the business model.

If you’re focused on best practices, you’re not doing innovation. Innovation is about doing things for the first time.

If you think you know what the customer wants, you don’t.

Doing innovation within a successful company is seven times hard than doing it in a startup.

If you’re certain, it’s not innovation.

With innovation, ideas and prototypes are cheap, but building the commercialization engine is ultra-expensive.

If no one will buy it, do something else.

Technical roadblocks can be solved, but customer/market roadblocks can be insurmountable.

The first thing to do is learn if people will buy your innovation.

With innovation, customers know what they don’t want only after you show them your offering.

With innovation, if you’re not scared to death you’re not trying hard enough.

The biggest deterrent to innovation is success.

Image credit — Sherman Geronimo-Tan

Don’t change culture. Change behavior.

There’s always lots of talk about culture and how to change it.  There is culture dial to turn or culture level to pull. Culture isn’t a thing in itself, it’s a sentiment that’s generated by behavioral themes.  Culture is what we use to describe our worn paths of behavior.  If you want to change culture, change behavior.

At the highest level, you can make the biggest cultural change when you change how you spend your resources. Want to change culture? Say yes to projects that are different than last year’s and say no to the ones that rehash old themes.  And to provide guidance on how to choose those new projects create, formalize new ways you want to deliver new value to new customers.  When you change the criteria people use to choose projects you change the projects.  And when you change the projects people’s behaviors change. And when behavior changes, culture changes.

The other important class of resources is people.  When you change who runs the project, they change what work is done.  And when they prioritize a different task, they prioritize different behavior of the teams.  They ask for new work and get new behavior. And when those project leaders get to choose new people to do the work, they choose in a way that changes how the work is done.  New project leaders change the high-level behaviors of the project and the people doing the work change the day-to-day behavior within the projects.

Change how projects are chosen and culture changes. Change who runs the projects and culture changes. Change who does the project work and culture changes.

Image credit – Eric Sonstroem

Mike Shipulski Mike Shipulski
Subscribe via Email

Enter your email address:

Delivered by FeedBurner

Archives