Posts Tagged ‘Fear’

Celebrating Seven Years of Blog Posts – what I’ve learned about writing.

%desxToday marks seven years of weekly blog posts.  Here’s what I’ve learned so far:

When you can write about anything, what you choose tells everyone what you’re about.

Sometimes you’ve got to start writing to figure out what you have to say.

Some people think semicolons are okay; others don’t like to show off.

When you don’t want to write and you write anyway, you feel good when you’re done.

Use short sentences. Use fewer words.

Writing is the best way to learn you don’t know what you’re talking about.

Writing is a good way to have a deep conversation with yourself.

Worrying about what people will think is the surest way to write like crap.

Writing improves by writing.

When the topic comes slowly, start writing. And when the words don’t come at all, repeat.

If you don’t know what you are talking about before you start writing, no worries. You’ll know when you’re done.

When you have nothing to say it’s because what you have to say is too personal share.

For me, writing is learning.

 

Image credit David Kutschke

 

The Cycle of Success

coccoon-now-transparentThere’s a huge amount of energy required to help an organization do new work.

At every turn the antibodies of the organization reject new ideas.  And it’s no surprise.  The organization was created to do more of what it did last time.  Once there’s success the organization forms structures to make sure it happens again.  Resources migrate to the successful work and walls form around them to prevent doing yet-to-be-successful work. This all makes sense while the top line is growing faster than the artificially set growth goal.  More resources applied to the successful leads to a steeper growth rate.  Plenty of work and plenty of profit.  No need for new ideas.  Everyone’s happy.

When growth rate of the successful company slows below arbitrary goal, the organization is slow to recognize it and slower to acknowledge it and even slower to assign true root cause.  Instead, the organization doubles down on what it knows.  More resources are applied, efficiency improvements are put in place, and clearer metrics are put in place to improve accountability.  Everyone works harder and works more hours and the growth rate increases a bit.  Success.  Except the success was too costly.  Though total success increased (growth), success per dollar actually decreased.  Still no need for new ideas.  Everyone’s happy, but more tired.

And then growth turns to contraction. With no more resources move to the successful work, accountability measures increase to unreasonable levels and people work beyond their level of effectiveness. But this time growth doesn’t come.  And because people are too focused on doing more of what used to work, new ideas are rejected.  When a new idea is proposed, it goes something like this “We don’t need new ideas, we need growth.  Now, get out of my way.  I’m too busy for your heretical ideas.”  There’s no growth and no tolerance for new ideas.  No one is happy.

And then a new idea that had been flying under the radar generates a little growth.  Not a lot, but enough to get noticed.  And when the old antibodies recognize the new ideas and try to reject it, they cannot.  It’s too late.  The new idea has developed a protective layer of growth and has become a resistant strain.  One new idea has been tolerated. Most are unhappy because there’s only one small pocket of growth and a few are happy because there’s one small pocket of growth.

It’s difficult to get the first new idea to become successful, but it’s worth the effort.  Successful new ideas help each other and multiply.  The first one breaks trail for the second one and the second one bolsters the third.  And as these new ideas become more successful something special happens.  Where they were resistant to the antibodies they become stronger than the antibodies and eat them.

Growth starts to grow and success builds on success.  And the cycle begins again.

Image credit – johnmccombs

Be done with the past.

graspThe past has past, never to come again.  But if you tell yourself old stories the past is still with you.  If you hold onto your past it colors what you see, shapes what you think and silently governs what you do.  Not skillful, not helpful.  Old stories are old because things have changed.  The old plays won’t work. The rules are different, the players are different, the situation is different.  And you are different, unless you hold onto the past.

As a tactic we hold onto the past because of aversion to what’s going on around us. Like an ostrich we bury our head in the sands of the past to protect ourselves from unpleasant weather buffeting us in the now.  But there’s no protection. Grasping tightly to the past does nothing more than stop us in our tracks.

If you grasp too tightly to tired technology it’s game over.  And it’s the same with your tired business model – grasp too tightly and get run through by an upstart.  But for someone who wants to make a meaningful difference, what are the two things that are sacred? The successful technology and successful business model.

It’s difficult for an organization to decide if the successful technology should be reused or replaced.  The easy decision is to reuse it.  New products come faster, fewer resources are needed because the hard engineering work has been done and the technical and execution risks are lower.  The difficult decision is to scrap the old and develop the new.  The smart decision is to do both.  Launch products with the old technology while working feverishly to obsolete it.  These days the half-life of technology is short.  It’s always the right time to develop new technology.

The business model is even more difficult to scrap. It cuts across every team and every function.  It’s how the company did its work.  It’s how the company made its name. It’s how the company made its money.  It’s how families paid their mortgages.  It’s grasping to the past success of the business model that makes it almost impossible to obsolete.

People grasp onto the past for protection and companies are nothing more than a loosely connected network of people systems.  And these people systems have a shared past and a good memory.  It’s no wonder why old technologies and business models stick around longer than they should.

To let go of the past people must see things as they are.  That’s a slow process that starts with a clear-eyed assessment today’s landscapes. Make maps of the worldwide competitive landscape, intellectual property, worldwide regulatory legislation, emergent technologies (search YouTube) and the sea of crazy business models enabled by the cloud.

The best time to start the landscape analyses was two years ago, but the next best time to start is right now.  Don’t wait.

Image credit – John Fife

If you believe…

walking to his first day of school

If you believe the work is meaningful, best effort flows from every pore.

If you believe in yourself, positivity carries the day.

If you believe the work will take twelve weeks, you won’t get it done in a day-and-a-half.

If you believe in yourself, when big problems find you, you run them to ground.

If you believe people have good intensions, there are no arguments, there is only progress.

If you believe in yourself, you are immune to criticism and negative self-talk.

If you believe people care about you, you’re never lonesome.

If you believe in your team, there’s always a way.

If you believe in yourself, people believe in you.  And like compound interest, the cycle builds on itself.

 

Image credit – Joe Shlabotnik

 

Hire people that run toward even the toughest problems.

the clown eats itIf you don’t have a problem, there’s no problem. There are no resources without a problem and certainly no focus or momentum.  If you don’t know your problem, stop.  Take time to define your problem using a single page.  Make a sketch or make a block diagram but make it clear.  Make it so the problem description stands on its own. After you’ve defined your problem and someone calls it an “opportunity”, walk away because they can’t help you.  Taking advantage of opportunities is optional, but solving problems is mission critical.  No one worth their salt works on opportunities.  Rock stars solve problems.

After you’ve gnawed on a problem for a month and it hasn’t given in, what do you do?  When you’ve thrown everything at a problem and it still stands tall, what do you do?  When you’ve tried all your tricks and the intractable problem is still blocking an already overdue product launch, what do you do?  What you do is find someone who is unafraid trade an intractable problem for a solvable one, someone who will courageously give ground with the hope of opening up new design space, someone who will unabashedly take an anti-conventional (and hopefully controversial) approach.  What you do is find a rock star.

Intractable problems are not usually intractable; rather, intractable problems are either poorly-defined problems or are the wrong problem altogether.  Either way, it takes someone with courage, usually an outsider, to redefine the problem or see it differently.  But because of pride, an outsider can be brought in only after the team has exhausted all other possibilities.  Unless there’s a problem with the problem solving team (they can’t solve the problem), there’s no problem.  And without a problem, the team won’t accept help from an outsider.

At the rodeo when the cowboy is bucked off the raging bull, the cowboy runs away from the bull but the rodeo clown runs toward the bull to distract it.  Like the rodeo clown, the problem solving rock star runs toward raging problems at full tilt.  The rock star puts it all on the line as she grabs the problem by the scruff of the neck, wrestles it to the ground and hog ties it.  There’s no shyness, just well-practiced technique wrapped in implicit knowledge.  With courage and a cloud of dust, it’s no-holds-barred problem solving until the problem gives it up. Nothing is sacred, no assumptions go unchallenged, and no details are too small to ignore.  Like rodeo clowns, rock stars know their work looks funny from the outside, but they don’t care.  All they care about is solving the problem at hand. Right here, right now.

Before your next intractable problem, take a minute to scan your organization for the special people who have the courage to run toward even the most difficult problems.  Don’t be fooled by titles, positional power or how they dress.  Look deeply because like rodeo clowns, your magical problem solvers may not look the part on the outside.

Image credit – Ed Schipul

How To Create Eye-Watering Ideas

Rocket manWith creativity, the leading thinking says the most important thing is to create many of ideas.  When asked to generate many of ideas, the thinking goes, the team lets go of their inhibitions and good ideas slip through their mental filters.  I’ve found that thinking misleading.  I’ve found that creating many ideas results in many ideas, but that’s it. Before the session to create new ideas, you already had a pile of ideas you weren’t working on, and after the session is bigger, but not better.

What’s needed is several outlandish ideas that make your hair stand on end. The ideas should be so different that they cause you to chuckle to mask your discomfort.  These ideas should be borderline unbelievable and just south of impossible. The ideas should have the possibility to change the game and tip your industry on its head.

The “many ideas” thinking has the right intent – to loosen the team’s thinking so they generate good ideas, but the approach is insufficient.   To force the team to generated outlandish ideas they must be turned inside-out and put on the rack.  Heretical ideas don’t come easily and drastic measures are needed.  The team must be systematically stripped of the emotional constraints of their success using the Innovation Burst Event (IBE) method.

To prepare for the IBE, a reward-looking analysis is done to identify traditional lines of customer goodness (for example, miles per gallon for automobiles) and define how that goodness has changed over time (position it on the S-curve.)  If the improvement has been flat, it’s time for a new line of customer goodness, and if the goodness is still steadily increasing, it’s time to create a new technology that will provide the next level of improvement.  With this analysis the disposition of the system is defined and potentially fertile design space is identified.  And within this design space, design challenges are created that force the team to exercise the highly fertile design space during the IBE.

Everything about the IBE is designed to strip the team of its old thinking.  The IBE is held at an offsite location to change the scenery and eliminate reminders of traditional thinking and good food is served to help the team feel the day is special.  But the big medicine is the design challenges.  They are crafted to outlaw traditional thinking and push the team toward new thinking.  The context is personal (not corporate) and the scale of the challenge is purposefully small to help the team let go of adjacent concerns.  And, lastly, the team is given an unreasonably short time (five to ten minutes) to solve the problem and build a thinking prototype (a prototype that stands for an idea, not at functional prototype.)

Everything about the IBE helps the team let go of their emotional constraints and emit eye-watering solutions.  The design challenges force them to solve problems in a new design space in a way and does not give them a chance to limit their thinking in any way.  The unrealistic time limit is all-powerful.

Four design challenges is about all team can handle in the one-day IBE.  With the IBE they come up with magical ideas clustered around four new areas, new areas that have the potential to flip your industry on its head.  In one day, a team can define market-changing ideas that obsolete your best products and even your business model.  Not bad for one day.

It may be popular wisdom that it’s best to create many new ideas, but it’s not the best way.  And it contradicts popular belief that a team can create three or four game-changing ideas in a single day.  But the IBEs work as advertised.

Don’t waste time creating a pile of ideas.  Spend the time to identify fertile design space and hold a one-day IBE to come up with ideas that will create your future.

Image credit – moonjazz

Stop bad project and start good ones.

Ria Munk On Her DeathbedAt the most basic level, business is about allocating resources to the best projects and executing those projects well.  Said another way, business is about deciding what to work on and then working effectively.  But how to go about deciding what to work on?  Here is a cascade of questions to start you on your journey.

What are your company’s guiding principles?  Why does it exist? How does it want to go about its life?   These questions create context from which to answer the questions that follow.  Once defined, all your actions should align with your context.

How has the business environment changed? This is a big one.  Everything is impermanent.  Change is the status quo.  What worked last time won’t work this time.  Your success is your enemy because it stunts intentions to work on new things.  Define new lines of customer goodness your competitors have developed; define how their technologies have increased performance; search YouTube to see the nascent technologies that will displace you; put yourself two years in the future where your customers will pay half what they pay today.  These answers, too, define the context for the questions that follow.

What are you working on? Define your fully-staffed projects. Distill each to a single page. Do they provide new customer value?  Are the projects aligned with your company’s guiding principles? For those that don’t, stop them.  How do your fully-staffed projects compare to the trajectory of your competitors’ offerings?  For those that compare poorly, stop them.

For projects that remain, do they meet your business objectives?  If yes, put your head down and execute.  If no, do you have better projects?  If yes, move the freed up resources (from the stopped projects) onto the new projects.  Do it now.  If you don’t have better projects, find some.  Use lines of evolution for technological systems to figure out what’s next, define new projects and move the resources.  Do it now.

The best leading indicator of innovation is your portfolio of fully-staffed projects.  Where other companies argue and complain about organizational structure, move your best resources to your best projects and execute.  Where other companies use politics to trump logic, move your best resources to your best projects and execute.  Where other successful companies hold on to tired business models and do-what-we-did-last-time projects, move your best resources to your best projects and execute.

Be ruthless with your projects.  Stop the bad ones and start some good ones. Be clear about what your projects will deliver – define the novel customer value and the technical work to get there.  Use one page for each.  If you can’t define the novel customer value with a simple cartoon, it’s because there is none.  And if you can’t define how you’ll get there with a hand sketch, it’s because you don’t know how.

Define your company’s purpose and use that to decide what to work on.  If a project is misaligned, kill it. If a project is boring, don’t bother.  If it’s been done before, don’t do it.  And if you know how it will go, do something else.

If you’re not changing, you’re dying.

Image credit – David Flam

Doing New Work

first rideIf you know what to do, do it.  But if you always know what to do, do something else.  There’s no excitement in turning the crank every-day-all-day, and there’s no personal growth.  You may be getting glowing reviews now, but when your process is documented and becomes standard work, you’ll become one of the trivial many that follow your perfected recipe, and your brain will turn soggy.

If you want to do the same things more productively, do continuous improvement.  Look at the work and design out the waste.  I suggest you look for the waiting and eliminate it.  (One hint – look for people or parts queueing up and right in front of the pile you’ll find the waste maker.)  But if you always eliminate waste, do something else.  Break from the minimization mindset and create something new.  Maximize something. Blow up the best practice or have the courage to obsolete your best work.  In a sea of continuous improvement, be the lighthouse of doing new.

When you do something for the first time, you don’t know how to do it. It’s scary, but that’s just the feeling you want.  The cold feeling in your chest is a leading indicator of personal growth.  (If you don’t have a sinking feeling in your gut, see paragraph 1.) But organizations don’t make it easy to do something for the first time.  The best approach is to start small.  Try small experiments that don’t require approval from a budget standpoint and are safe to fail.  Run the experiments under the radar and learn in private.  Grow your confidence in yourself and your thinking.  After you have some success, show your results to people you trust.  Their input will help you grow.  And you’ll need every bit of that personal growth because to staff and run a project to bring your new concept to life you’ll need resources.  And for that you’ll need to dance with the most dangerous enemy of doing new things – the deadly ROI calculation.

The R is for return.  To calculate the return for the new concept you need to know: how many you’ll sell, how much you’ll sell them for, how much it will cost, and how well it will work.  All this must be known BEFORE resources can be allocated. But that’s not possible because the new thing has never been done before.  Even before talking about investment (I), the ROI calculation makes a train wreck of new ideas.  To calculate investment, you’ve got to know how many person-hours will be needed, the cost of the materials to make the prototypes and the lab resources needed for testing.  But that’s impossible to know because the work has never been done before.  The ROI is a meaningless calculation for new ideas and its misapplication has spelled death for more good ideas than anything else known to man.

Use the best practice and standardize the work. There’s immense pressure to repeat what was done last time because our companies prefer incremental growth that’s predictable over unreasonable growth that’s less certain.  And add to that the personal risk and emotional discomfort of doing new things and it’s a wonder how we do anything new at all.

But magically, new things do bubble up from the bottom. People do find the courage to try things that obsolete the business model and deliver new lines of customer goodness.  And some even manage survive the run through the ROI gauntlet.  With odds stacked against them, your best people push through their fears cut through the culture of predictability.

Imagine what they will do when you demand they do new work, give them the tools, time and training to do it, and strike the ROI calculation from our vocabulary.

Image credit – Tony Sergo

Step-Wise Learning

staircaseAt every meeting you have a chance to move things forward or hold them back.  When a new idea is first introduced it’s bare-naked.  In its prenatal state, it’s wobbly and can’t stand on its own and is vulnerable to attack. But since it’s not yet developed, it’s impressionable and willing to evolve into what it could be.  With the right help it can go either way – die a swift death or sprout into something magical.

Early in gestation, the most worthy ideas don’t look that way.  They’re ugly, ill-formed, angry or threatening.  Or, they’re playful, silly or absurd.  Depending on your outlook, they can be a member of either camp. And as your outlook changes, they can jump from one camp to the other.  Or, they can sit with one leg in each.  But none of that is about the idea, it’s all about you.  The idea isn’t a thing in itself, it’s a reflection of you. The idea is nothing until you attach your feelings to it.  Whether it lives or dies depends on you.

Are you looking for reasons to say yes or reasons to say no?

On the surface, everyone in the organization looks like they’re fully booked with more smart goals than they can digest and have more deliverables than they swallow, but that’s not the case.  Though it looks like there’s no room for new ideas, there’s plenty of capacity to chew on new ideas if the team decides they want to.  Every team can spare and hour or two a week for the right ideas.  The only real question is do they want to?

If someone shows interest and initiative, it’s important to support their idea.  The smallest acceptable investment is a follow-on question that positively reinforces the behavior.  “That’s interesting, tell me more.” sends the right message.  Next, “How do you think we should test the idea?” makes it clear you are willing to take the next step.  If they can’t think of a way to test it, help them come up with a small, resource-lite experiment.  And if they respond with a five year plan and multi-million dollar investment, suggest a small experiment to demonstrate worthiness of the idea.  Sometimes it’s a thought experiment, sometimes it’s a discussion with a customer and sometimes it’s a prototype, but it’s always small.  Regardless of the idea, there’s always room for a small experiment.

Like a staircase, a series of small experiments build on each other to create big learning.  Each step is manageable – each investment is tolerable and each misstep is survivable – and with each experiment the learning objective is the same: Is the new idea worthy of taking the next step?  It’s a step-wise set of decisions to allocate resources on the right work to increase learning.  And after starting in the basement, with step-by-step experimentation and flight-by-flight investment, you find yourself on the fifth floor.

This is about changing behavior and learning.  Behavior doesn’t change overnight, it changes day-by-day, step-by-step.  And it’s the same for learning – it builds on what was learned yesterday.  And as long at the experiment is small, there can be no missteps.  And it doesn’t matter what the first experiment is all about, as long as you take the first step.

Your team will recognize your new behavior because it respectful of their ideas.  And when you respect their ideas, you respect them.  Soon enough you will have a team that stands taller and runs small experiments on their own.  Their experiments will grow bolder and their learning will curve will steepen.  Then, you’ll struggle to keep up with them, and you’ll have them right where you want them.

image credit — Rob Warde

There is no failure, there is only learning.

worst parent failsYou’re never really sure how your new project will turn out, unless you don’t try.  Not trying is the only way to guarantee certainty – certainty that nothing good will come of it.

There’s been a lot of talk about creating a culture where failure is accepted.  But, failure will never be accepted, and nor should it be.  Even the failing forward flavor won’t be tolerated.  There’s a skunk-like stink to the word that cannot be cleansed. Failure, as a word, should be struck from the vernacular.

If you have a good plan and you execute it well, there can be no failure.  The plan can deliver unanticipated results, but that’s not failure, that’s called learning.  If the team runs the same experiment three times in a row, that, too, is not failure.  That’s “not learning”.  The not learning is a result of something, and that something should be pursued until you learn its name and address.  And once named, made to go away.

When the proposed plan is reviewed and improved before it’s carried out, that’s not failure.  That’s good process that creates good learning.  If the plan is not reviewed, executed well and generates results less than anticipated, it’s not failure.  You learned your process needs to change. Now it’s time to improve it.

When a good plan is executed poorly, there is no failure. You learned that one of your teams executed in a way that was different than your expectations.  It’s time to learn why it went down as it did and why your expectations were the way they were.  Learning on all fronts, failing on none.

Nothing good can come of using the f word, so don’t use it.  Use “learn” instead.  Don’t embrace failure, embrace learning. Don’t fail early and often, learn early and often. Don’t fail forward (whatever that is), just learn.

With failure there is fear of repercussion and a puckering on all fronts.  With learning there is openness and opportunity.  You choose the words, so choose wisely.

Image credit –  IZATRINI.com

Celebrating Six Years of Blog Posts

Happy Birthday AmandaToday marks six years of blog posts published every Wednesday evening.  300 weeks in a row and I haven’t skipped, forgot, or repeated.  All written without an editor, though you knew that by the typos and grammar stumbles.

It’s a challenge to write every week, but it’s worth it.  Writing demands thinking things through, which can be difficult especially if you want to write clearly, but thinking things through creates knowledge.  Deep knowledge.

Over the last year I wrote a lot about self-awareness, mindfulness and intentions.  I’m better for my meditations, and through osmosis, so are some of the people closest to me. I expect you’ll hear more on these themes over the next year.

I’ve put myself out there with my writing.  With some posts I’m afraid to hit the publish key, and those are the posts that matter.  My fear is the signal there’s something important in the post.  I hope to write more of those.

I strive to write clearly and densely and avoid buzzwords.  Innovation is the buzzword that trips me up.  But like He-Who-Shall-Not-Be-Named, I’ll see if I can avoid calling it by name. (And never three times in the same post.)  And my call-to-arms will be clearer, plainer, denser.

I’m not sure what next year will bring, but I hope it will be 52 more posts.

Thanks for reading.

Mike

Image credit – Bart.

 

 

 

Mike Shipulski Mike Shipulski
Subscribe via Email

Enter your email address:

Delivered by FeedBurner

Archives