Shipulski On Design

Archive for the ‘Trust’ Category

For those who lead projects and people, failure is always lurking in the background.  And gone unchecked, it can hobble. Despite best efforts to put a shine on it, there’s still a strong negative element to failure.  No two ways about it, failure is mapped with inadequacy and error.  Failure is seen as the natural consequence of making a big mistake.  And there’s a finality to failure.  Sometimes it’s the end of a project and sometimes it’s the end of a career.  Failure severely limits personal growth and new behavior.  But at least failure is visible to the naked eye.  There’s no denying a good train wreck.

A fumble is not failure.  When something gets dropped or when a task doesn’t get done, that’s a fumble.  A fumble is not catastrophic and sometimes not even noteworthy.  A fumble is mapped with  a careless mistake that normally doesn’t happen.  No real cause.  It just happens. But it can be a leading indicator of bigger and badder things to come, and if you’re not looking closely, the fumble can go unnoticed. And the causes and conditions behind the fumble are usually unclear or unknown.  Where failure is dangerous because everyone knows when it happens, fumbles are dangerous because they can go unnoticed.

Floundering is not fumbling. With floundering, nothing really happens.  No real setbacks, no real progress, no real energy. A project that flounders is a project that never reaches the finish line and never makes it to the cemetery.  To recognize floundering takes a lot of experience and good judgment because it doesn’t look like much. But that’s the point – not much is happening.  No wind in the sails and no storm on the horizon.  And to call it by name takes courage because there are no signs of danger.  Yet it’s dangerous for that very reason. Floundering can consume more resources than failure.

Fear is the fundamental behind failing, fumbling and floundering. But unlike failure, no one talks about fear. Talking about fear is too scary. And like fumbling and floundering, fear is invisible, especially if you’re not looking.  Like diabetes, fear is a silent killer. And where diabetes touches many, fear gets us all. Fear is invisible, powerful and prolific.  It’s a tall order to battle the invisible.

But where there’s fun there can be no fear. More precisely, there can be no negative consequence of fear. When there’s fun, everyone races around like their hair is on fire.  Not on fire in the burn unit way, but on fire in the energy to burn way. When there’s fun people help each other for no reason. They share, they communicate and they take risks.  When there’s fun no one asks for permission and the work gets done.  When there’s fun everyone goes home on time and their spouses are happy.  Fun is easy to see, but it’s not often seen because it’s rare.

If there’s one thing that can go toe-to-toe with fear, it’s fun. It’s that powerful. Fun is so powerful it can turn failure into learning.  But if it’s so powerful, why don’t we teach people to have fun? Why don’t we create the causes and conditions so fun erupts?

I don’t know why we don’t promote fun.  But, I do know fun is productive and fun is good for business.  But more important than that, fun is a lot of fun.

Image credit – JoshShculz

Expectations result from mental models and wants. When you have a mental model of a system and you want the system to behave in a way that fits your mental model, that’s an expectation.  And when you want the system to behave differently than your mental model, that’s also an expectation.  When the system matches your wants, the world is good.  And when your wants are out of line with the system, the world is not so good.

Speculation is not expectation. Speculation happens when you propose, based on your mental model, how the system will behave. With speculation, there’s no attachment to the result, no wanting it to be one way or another. There’s just watching and learning.  If the system confirms your mental model, the applicability of the model is reinforced (within this narrow context.) And when the system tramples your mental model, you change your mental model.  No attachment, no stress, no whining, no self-judgement.

When doing work that’s new, system response is unknown. Whether the system will be exercised in a new way or it’s an altogether new system, metal models are young and untested.  When it’s the first time, speculation is the way to go. Come up with your best mental model, run the experiment and record the results.  After sitting in data, refine your mental model and repeat.   If your mental model doesn’t fit the system, don’t judge yourself negatively, don’t hold yourself back, don’t shy away.  Refine your mental model and build-test-learn as fast as you can.  And if your mental model fits the system, don’t judge yourself in a positive way.  This was your first test and you don’t understand the system fully.  Refine your model and test for a deeper understanding.  [Note – systems have been known to temporarily conform to mental models to obfuscate their true character.]

When doing work that’s new, expectation gets in the way. If you expect your models to be right and they’re not, you learning rate is slower than your expectations.  That’s not such a big deal on its own, but the rippling self-judgement can be crippling. Your emotional state becomes fragile and it’s difficult to keep pushing through the work. You doubt yourself and your abilities; you won’t put yourself out there; and you won’t propose radical mental models for fear of looking like you don’t know what you’re doing.  You won’t run the right experiments and you never the understand the fundamental character of the system. You block your own learning.  If you expect your models won’t to fit the system, you block your learning from the start.  Sometimes your lack of confidence blocks you from even trying. [Note – not trying is the only way to guarantee you won’t learn.]

Within the domain of experiments, mental models and generic systems, it’s relatively easy to see the wisdom of speculations and the perils of expectations, where wanting leads to judging and judging leads to self-blocking.  But it’s not so easy to see in the domain of life where experiments are replaced with personal interactions and generic systems are replaced with everyday situations and mental models are ever-present.  But in both domains the rules and consequences are the same.

Just as in the lab, in day-to-day life expectations are dangerous.

Image credit – Dermot  O’Halloran

Anything that happens happens because of people, and anything that doesn’t happen doesn’t happen because of people.  Technology doesn’t create itself, products don’t launch themselves, companies don’t build themselves and trust doesn’t grow on its own.  Any kind of work, any kind of service, any kind of organizing – it’s all done by people.

The productivity/quality movement has been good for factories – parts move in a repeatable flow and they’re processed in repeatable ways by machines that chunk out repeatable output.  Design the process, control the inputs and turn the crank. Invest in the best machines and to do the preventative maintenance to keep them in tip-top shape.  Just follow the preventive maintenance (PM) schedule and you’ll be fine.  But when the productivity/quality movement over-extended into the people domain, things don’t go as well.

People aren’t machines, and their work product is not cookie-cutter parts.  And, there’s no standard PM schedule for people. We all know this, but we behave like people are machines – we design their work process, train them on it and measure their output. But machines are iron-based entities that don’t have consciousness and people are carbon-based beings with full consciousness.  The best machines do what their told, but the best people tell you what to do.  Machines and people are fundamentally different, but how we run them is markedly similar.

Where machines need oil, people need empathy. And for empathy you need vulnerability and for that you need trust. But there’s no standard PM schedule for trust.  There’s no flowchart or troubleshooting protocol for helping people.  What work do you give them? It depends. When do you touch base and when do you leave them alone? It depends. How much responsibility do you give them? It depends.  With machines it’s follow the PM schedule and with people – it depends.

Where machines wear out, people develop and grow. And to grow people you need to see them as they are and meet them where they are. And to do that you’ve got to see yourself as you are.  You can’t give people what they need if you add to the drama with your reactivity and you can’t discern their suffering from your projections if you’re not grounded. How much time do you spend each day to learn to dampen your reactivity?  How much time do you spend to slow your monkey mind so you can see your projections?

With machines it’s control the inputs and get what you got last time.  With people it’s maybe; it depends; don’t worry about how it will go; and why don’t you try? Growing people is much more difficult than keeping machines running smoothly.  But, there is nothing more fulfilling than helping people grow into something they couldn’t imagine.

Image credit – Benjamin Balazs

Hep

People ask why.

People buy products from people.

The right people turn activity into progress.

People want to make a difference, and they do.

People have biases which bring a richer understanding.

People use judgement – that’s why robots don’t run projects.

People recognize when the rules don’t apply and act accordingly.

Business models are an interconnected collection of people processes.

The simplest processes require judgement, that’s why they’re run by people.

People don’t like good service, they like effective interaction with other people.

People are the power behind the tools.  (I never met a hammer that swung itself.)

Progress is powered by people.

Image credit – las – intially

Once you have a project to work on, it’s always a challenge to choose the first task.  And once finished with the first task, the next hardest thing is to figure out the next next task.

Two words to live by: Critical Path.

By definition, the next task to work on is the next task on the critical path.  How do you tell if the task is on the critical path?  When you are late by one day on a critical path task, the project, as a whole, will finish a day late.  If you are late by one day and the project won’t be delayed, the task is not on the critical path and you shouldn’t work on it.

Rule 1: If you can’t work the critical path, don’t work on anything.

Working on a non-critical path task is worse than working on nothing.  Working on a non-critical path task is like waiting with perspiration.  It’s worse than activity without progress.  Resources are consumed on unnecessary tasks and the resulting work creates extra constraints on future work, all in the name of leveraging the work you shouldn’t have done in the first place.

How to spot the critical path? If a similar project has been done before, ask the project manager what the critical path was for that project.  Then listen, because that’s the critical path.  If your project is similar to a previous project except with some incremental newness, the newness is on the critical path.

Rule 2: Newness, by definition, is on the critical path.

But as the level of newness increases, it’s more difficult for project managers to tell the critical path from work that should wait.  If you’re the right project manager, even for projects with significant newness, you are able to feel the critical path in your chest.  When you’re the right project manager, you can walk through the cubicles and your body is drawn to the critical path like a divining rod.   When you’re the right project manager and someone in another building is late on their critical path task, you somehow unknowingly end up getting a haircut at the same time and offering them the resources they need to get back on track.  When you’re the right project manager, the universe notifies you when the critical path has gone critical.

Rule 3: The only way to be the right project manager is to run a lot of projects and read a lot.  (I prefer historical fiction and biographies.)

Not all newness is created equal.  If the project won’t launch unless the newness is wrestled to the ground, that’s level 5 newness. Stop everything, clear the decks, and get after it until it succumbs to your diligence.  If the product won’t sell without the newness, that’s level 5 and you should behave accordingly.  If the newness causes the product to cost a bit more than expected, but the project will still sell like nobody’s business, that’s level 2.  Launch it and cost reduce it later.  If no one will notice if the newness doesn’t make it into the product, that’s level 0 newness. (Actually, it’s not newness at all, it’s unneeded complexity.)  Don’t put in the product and don’t bother telling anyone.

Rule 4: The newness you’re afraid of isn’t the newness you should be afraid of.

A good project plan starts with a good understanding of the newness.  Then, the right project work is defined to make sure the newness gets the attention it deserves.  The problem isn’t the newness you know, the problem is the unknown consequence of newness as it ripples through the commercialization engine. New product functionality gets engineering attention until it’s run to ground.  But what if the newness ripples into new materials that can’t be made or new assembly methods that don’t exist?  What if the new materials are banned substances?  What if your multi-million dollar test stations don’t have the capability to accommodate the new functionality?  What if the value proposition is new and your sales team doesn’t know how to sell it?  What if the newness requires a new distribution channel you don’t have? What if your service organization doesn’t have the ability to diagnose a failure of the new newness?

Rule 5: The only way to develop the capability to handle newness is to pair a soon-to-be great project manager with an already great project manager. 

It may sound like an inefficient way to solve the problem, but pairing the two project managers is a lot more efficient than letting a soon-to-be great project manager crash and burn.  After an inexperienced project manager runs a project into the ground, what’s the first thing you do?  You bring in a great project manager to get the project back on track and keep them in the saddle until the product launches.  Why not assume the wheels will fall off unless you put a pro alongside the high potential talent?

Rule 6: When your best project managers tell you they need resources, give them what they ask for.

If you want to deliver new value to new customs there’s no better way than to develop good project managers.  A good project manager instinctively knows the critical path; they know how the work is done; they know to unwind situations that needs to be unwound; they have the personal relationships to get things done when no one else can; because they are trusted, they can get people to bend (and sometimes break) the rules and feel good doing it; and they know what they need to successfully launch the product.

If you don’t know your critical path, you don’t know very much.  And if your project managers don’t know the critical path, you should stop what you’re doing, pull hard on the emergency break with both hands and don’t release it until you know they know.

Image credit – Patrick Emerson

There are many different organizational structures, each with its unique set of strengths and weaknesses. The top-down organization has its strong alignment and limited flexibility while the bottom-up has its empowering consensus and sloth-like pace.  Which one’s better?  Well, it depends.

The function-based organization has strong subject matter expertise and weak cross-function coordination, while the business unit-based organization knows its product, market and customers but has difficulty working east-west across product families and customer segments.  Is one better than the other?  Same answer- it depends.

The matrix organization has the best of both worlds – business unit and functional – and isn’t particularly good at either.  And there’s the ambidextrous organization that I don’t pretend to understand.  If I had to choose one, which would I choose? It depends.

The best organizational structure depends on what you’re trying to do, depends on the environmental context, depends on the organization’s history and biases and the general state of organizational capability, capacity and profitability.  But that’s not the whole picture because none of this is static.  All of this changes over time and it changes in an unpredictable way.  Because the best organizational structure depends on all these complicating factors and the factors change over time, there is never a “best” organizational structure.

Constant change has always been the dominant fundamental perturbing and disturbing our organizational structures.  But, as competition turns up the wick and the pace of learning builds geometrically, change’s ability to influence our organizational structures has grown from disturbing to dismantling.

Change is the dominant fundamental, but its real power comes from the uncertainty it brings to the party.  Our tired, old organizational structures were designed to survive in a long-dead era of glacial change and rationed uncertainty.  And though our organizational structures were built in granite, the elevated sea levels of uncertainty are creating fissures in our inflexible organizational structures and profitability is leaking from all levels

If uncertainty is the disease, adaptability is the antidote.  The organization must continually monitor its environment for changes.  And when it senses an emerging shift, the organization it must move resources in a way that satisfies the new reality.  The organization structure shifts to fit the work.  The structure changes as the character of the projects change.  The organizational structure never reaches equilibrium; it survives through continual evolutionary loop of sense-change-sense.

I don’t have a name for an organization like this, and I think it’s best not to name it.  Instead, I think it’s best to describe how it behaves.  It’s a living organization that behaves like a living organism.  It wants to survive, so it changes itself based on changes in its environment.  It’s an organization that self organizes.

Directionally, organizational structures should be less static and more dynamic, and they should evolve to fit the work.  The difficult part is how to define the explicit rules on how it should change, when it should change and how it decides.  But it’s more than difficult to describe explicit rules, it’s impossible.  In domains of high levels of uncertainty there can be no predictability and without predictability a finite set of explicit rules will not work.  The DNA of this living organization is implicit knowledge, evolutionary experimentation and personal judgement.

I’m not sure what to call this type of organizational structure, and I’m not exactly sure how to create one. But it sure sounds like a lot of fun.

Image credit — actor212

Do good work and people will notice.  Do work to get noticed and people will notice that too.

Try to do good work and you’ll get ahead. Try to get ahead and you won’t.

If the work feels good while you’re doing it, it’s good work.  If it doesn’t, it’s not.

If you watch the clock while you work, that says nothing about the clock.

When you surf the web at work, you’re not working.  When you learn from blog posts, podcasts and TED talks, you are.

Using social media at work is good for business, except when it isn’t.

When you feel you don’t have the authority, you don’t.  If you think you need authority, you shouldn’t.

When people seek your guidance you have something far more powerful than authority, you have trust.

Don’t pine for authority, earn the right to influence.

Influence is to authority as trust is to control.

Personal relationships are more powerful than org charts.  Work the relationships, not the org chart.

There’s no reason to change right up until there’s a good reason.  It may be too late, but at least you’ll have a reason.

Holding on to what you have comes at the expense of creating the future.

As a leader don’t take credit, take responsibility.

And when in doubt, try something.

Image credit — Peter Clark

Sometimes people are unskillful with their words, and what they say can have multiple interpretations.  But, though you don’t have control over their words, you do have control over how you interpret them. And the translation you choose makes all the difference.  On the flipside, when you choose your words skillfully they can have a singular translation. And that, too, makes all the difference.  Here are some examples.

It can’t be done.  Translations: 1) We’ve never tried it and we don’t know how to go about it.  2) We know you’ll not give us the time and the resources to do it right, and because of that, we won’t be successful.  3) Wow. I like that idea, but we’re already so overloaded. Do you think we can talk about that in the second half of the year?

We tried that but it didn’t work.  Translations: 1) Twelve years ago someone who made a prototype and it worked pretty well.  But, she wasn’t given the time to take it to the next level and the project was abandoned.  2) We all think that’s a wonderful idea and really want to work on it, but we’re too busy to think about that. If I come clean, will you give me the resources to do it right?

Why didn’t you follow the best practice? Translations: 1) I’m afraid of the uncertainty around this innovation work and I’ve heard best practices can reduce risk.  2) I don’t really know what I’m talking about, but this seems like a safe question to ask without tipping my hand.  3) I want to make a difference at the company, but I’ve never been part of a project with so much newness. Can you teach me?

That’s not how we do it. Translations: 1) I’ve always done it that way, and thinking about doing it differently scares me.  2) Though the process is clunky, we’ve been told to follow it.  And I don’t want to get in trouble. 3) That sounds like a good idea, but I don’t have the time to think through the potential implications to our customers.

What are you working on? Translation: I’m interested in what you’re working on because I care about you.

Can I help you? Translation: You’ve helped me in the past and I see you’re in a tough situation.  I care about you.  What can I do to help?

Good job. Translation: I want to positively reinforce your good work in front of everyone because, well, you did good work.

That’s a good idea. Translation: I think highly of you, I like that you stuck out your neck, and I hope you do it regularly.

I need help. Translation: I know you are highly capable and I trust you. I’m in a tight spot here.  Can you help me?

Thank you.  Translation: You were helpful and I appreciate it.  Thank you.

How you choose your words and how you choose to assign meaning to others’ words make all the difference.  Choose skillfully.

image credit — woodleywonderworks

When the mainstream products become tired, there’s incentive to replace it, but while sales are good there’s no compelling reason to obsolete your best work.  Things that matter start from things that no longer matter.

The gestation period for a novel idea to transition to viable technology then to a winning product and the processes to bring it market is longer than anyone wants to admit.  If you haven’t done it before it takes twice as long as you think and three times longer than you want.  If you stomp on the accelerator once there’s consensus you should, you waited too long.

There’s a simple way to tell it’s time to accelerate. When the status quo sets the cruise control to “coast”, it’s time.  When new there’s no time to work on new concepts, that’s coasting.  When ROI analyses are required for most everything, that’s coasting.  When forward-looking work is cut and cost reduction work is accelerated, that’s a sure sign of coasting.

As soon as you recognize coasting, it’s time to circle the wagons and create an acceleration plan. It’s not across-the-board acceleration, nor is it founded on people working harder or taking on more projects.  The plan starts with a business objective and a commitment to add resources to speed things up.  If the plan isn’t tied tightly to an important business objective it will miss the mark, and if incremental resources are not applied to the work, it won’t accelerate.

Here’s a rule – if projects and resources don’t change, you haven’t changed anything.

When you can feel the low pressure system in your body and can smell the storm brewing over the horizon, you have an obligation to do something about it.  But moving resources and starting projects at the expense of stopping others is emotionally charged work, and the successful organization will reject these changes at every turn.  And everyone will think there’s no need to change, but they’ll be wrong.

It’s will be tough going, but your instincts are good and intuition is on-the-mark – there is a storm brewing over the horizon. Push through the discomfort, push through the fear, push through the self-doubt.

It’s time to believe in yourself.  It’s the only thing powerful enough to make a difference.

Image credit – Chris Kim

Supply and demand have been joined at the hip since the beginning.  When demand is high, the deck is shuffled so supply seems low.  The fabricated scarcity drives up prices and shareholders are happy.  When demand is low, the competition pushes each other on price.  The abundance creates a commodity, and it’s a race to the bottom.

But this is old thinking.

Scarcity isn’t a lever to jack up prices or manipulate relationships, it’s an opportunity to spend your limited resources on the most important work and to build relationships.  When you tell a potential partner you want work with them and you are willing to spend your finite resources to make it happen, it’s a huge compliment.  Voting with your feet makes a powerful statement that you’re serious about working with them because you think they’re special.  You are telling them that you will say no to others so you can say yes to them.  Both know they’re part of something important and the free-flowing positivity results in something otherwise impossible.

Scarcity is limiting only if your mental framework thinks it is.  If you hoard and hold tightly, scarcity breeds win-lose relationships governed by power dynamics.  But if you choose the anti-framework, scarcity creates trust.

Played differently, abundance does not create commodity, it’s opportunity to show others you have enough to spare.  In personal relationships, when you share some of your work for free your relationships blossom.  When you give it away you are signaling that you have plenty to spare.  It’s clear to everyone you are a geyser of new thinking.  Here – take this.  I’ll make more.  These simple words create a foundation of trust which bolsters your personal brand.  And because all business relationships are personal relationships, it does the same thing for your company’s brand.

Make it a commodity or give it away – how you see abundance is your choice.  The old way breeds bare-knuckled competition.  The new way creates a brand steeped in trust.

If you have scarcity, be thankful for it.  Allocate your precious resources thoughtfully and with love.  Spend your time with the people and causes that matter.  It will feel good to everyone, including you.  And if you have abundance, be thankful.  Choose to develop closer relationships based on trust. Choose to give it away.

Happy Thanksgiving.

image credit — GloriaGarcia

Companies don’t need more ideas, they need ideas that are more meaningful.  Companies have plenty ideas because they measure and track the number of new ideas generated.  Enter your idea on the company’s open innovation web portal, and you’re done. Let the record show that a new idea was added to the hopper.  Increment the counter and update the metrics.  One new idea for the good guys.  It’s a good day to be alive.

For some reason leaders are comforted by a large number of new ideas in the hopper even though there’s no hope of working on them.  Maybe they think there’s value in a backlog of ideas they can fall back on if the existing work doesn’t pan out.  If that’s the case, they probably think the ideas in the hopper have good potential.  But because the ideas are not graded on their potential, that’s simply wishful thinking.

The only thing good about counting the number of new ideas is that the number of new ideas is easy to count.  The good thing about grading ideas on their level of meaningfulness is it causes the most meaningful ideas to rise to the top.  The bad thing about grading ideas is that it requires judgement. And today, judgment is in short supply.  If you use your judgement poorly your career suffers, but if you avoid using your judgement no one notices.  Here’s a rule: If you never you use your judgement, you can never use it poorly.

For a select few, any work that doesn’t require judgment doesn’t rise to the level of work worth doing.  For them, only the most meaningful work will do, and rolling the dice on their career is simply the cost of doing business.  For them, it’s judgement or bust.

If you use your judgement and choose to work on a meaningful idea, be prepared for the loneliness.  Meaningful ideas are, by definition, understood by a few and misunderstood by the rest.  It’s lonely to advance an idea that most don’t understand.  And prepare to be misjudged for your actions because your steadfast pursuit of the idea will also be misunderstood. Your vigor and aliveness will be seen as aggressiveness, anger, negativity, closemindedness, or political incorrectness.  But this misjudgment comes with the territory.  There’s no way around it.  It’s just how it goes.  It’s not personal.

But just as the trivial many will try to tear you down, there are a vital few who will praise you, support you and bolster you.  These are the special people in your organization.  You know who I’m talking about.  You have a personal relationship with them.  You know about their families. You’ve been through tough times together.  They’ve seen you struggle, stumble and tumble, and they’ve seen you get up and move forward.  They’ve seen you run into a brick wall and helped you back to your feet.  Don’t dismiss their praise and don’t feel guilty about accepting help from them. They don’t want credit for helping you, they want you to succeed.

You don’t know this, but those special people want to help you because you’ve already helped them.  Some time ago you unknowingly helped them through a tough time, or were kind to them.  Or, you invested in them or believed in them.  More than likely, though, you inspired them.

Keep moving forward.  Keep pushing.  And take comfort from the special people that believe in you.

Image credit – Ice Man