Shipulski On Design

Archive for the ‘Culture’ Category

Life can get busy and complicated, with too many demands on our time and too little time to get everything done.  But why do we accept all the “demands” and why do we think we have to get everything done? If it’s not the most important thing, isn’t a “demand for our time” something less than a demand? And if some things are not all that important, doesn’t it say we don’t have to do everything?

When life gets busy, it’s difficult to remember it’s our right to choose which things are important enough to take on and which are not.  Yes, there are negative consequences of saying no to things, but there are also negative consequences of saying yes.  How might we remember the negative consequences of yes?

When you say to yes to one thing, you say no to the opportunity to do something else.  Though real, this opportunity cost is mostly invisible.  And that’s the problem.  If your day is 100% full of meetings, there is no opportunity for you to do something that’s not on your calendar.  And in that moment, it’s easy to see the opportunity cost of your previous decisions, but that doesn’t do you any good because the time to see the opportunity cost was when you had the choice between yes and no.

If you say yes because you are worried about what people will think if you say no, doesn’t that say what people think about you is important to you? If you say yes because your physical health will improve (exercise), doesn’t that say your health is important to you? If you say yes to doing the work of two people, doesn’t it say spending time with your family is less important?

Here’s a proposed system to help you.  Open your work calendar and move one month into the future.  Create a one-hour recurring meeting with yourself.  You just created a timeslot where you said no in the future to unimportant things and said yes in the future to important things.  Now, make a list of three important things you want to do during those times.  And after one month of this, create a second one-hour recurring meeting with yourself.  Now you have two hours per week where you can prioritize things that are important to you.  Repeat this process until you have allocated four hours per week to do the most important things.  You and stop at four hours or keep going.  You’ll know when you get the balance right.

And for Saturday and Sunday, book a meeting with yourself where you will do something enjoyable.  You can certainly invite family and/or friends, but it the activity must be for pure enjoyment.  You can start small with a one-hour event on Saturday and another on Sunday.  And, over the weeks, you can increase the number and duration of the meetings.

Saying yes in the future to something important is a skillful way to say no in the future to something less important.  And as you use the system, you will become more aware of the opportunity cost that comes from saying yes.

Image credit – Gilles Gonthier

When new ideas come from the outside, they are dismissed out of hand.  The technical term for this behavior is Not Invented Here (NIH).  Because it was not invented by the party with official responsibility, that party stomps it into dust.  But NIH doesn’t stomp in public; it stomps in mysterious ways.

Wow!  That’s a great idea!  Then, mysteriously, no progress is made and it dies a slow death.

That’s cool! Then there’s a really good reason why it can’t be worked.

That’s interesting!  Then that morphs into the kiss of death.

We never thought of that.  But it won’t scale.

That’s novel!  But no one is asking for it.

That’s terribly exciting! We’ll study it into submission.

That’s incredibly different!  And likely too different.

When the company’s novel ideas die on the vine, they likely die at the hands of NIH. If you can’t understand why a novel idea never made it out of the lab, investigate the crime scene and you may find NIH’s fingerprints.  If customers liked the new idea yet it went nowhere, it could be NIH was behind the crime. If it makes sense, but it doesn’t make progress, NIH is the prime suspect.

If a team is not receptive to novel ideas from the outside, it’s because they consider their own ideas sufficiently good to meet their goals.  Things are going well and there’s no reason to adopt new ideas from the outside.  And buried in this description are the two ways to overcome NIH.

The fastest way to overcome NIH is to help a new idea transition from an idea conceived by someone outside the team to an idea created by someone inside the team.  Here’s how that goes.  The idea is first demonstrated by the external team in the form of a functional prototype.  This first step aims to help the internal team understand the new idea.  Then, the first waiting period is endured where nothing happens.  After the waiting period, a somewhat different functional prototype is created by the external team and shown to the internal team.  The objective is to help the internal team understand the new idea a little better.  Then, the second waiting period is endured where nothing happens.  Then, a third functional prototype is created and shown to the internal team.  This time, shortcomings are called out by the external team that can only be addressed by the internal team.  Then, the last waiting period is endured.  Then, after the third waiting period, the internal team addresses the shortcomings and makes the idea their own.  NIH is dead, and it’s off to the races.

The second fastest way to overcome NIH is to wait for the internal team to transition to a team that is receptive to new ideas initiated outside the team.  The only way for a team to make the transition is for them to realize that their internal ideas are insufficient to meet their objectives.  This can only come after their internal ideas are shown to be inadequate multiple times.  Only after exhausting all other possibilities, will a team consider ideas generated from outside the team.

When the external team recognizes the internal team is out of ideas, they demonstrate a functional prototype to the internal team.  And they do it in an “informational” way, meaning the prototype is investigatory in nature and not intended to become the seed of the internal team’s next generation platform.  And as it turns out, it’s only a strange coincidence that the functional prototype is precisely what the internal team needs to fuel the next-generation platform.  And the prototype is not fully wrung out.  And as it turns out, the parts that need to be wrung out are exactly what the external team knows how to do.  And when the internal team needs expertise from the external team to address the novel elements, as it turns out the external team conveniently has the time to help out.

Not Invented Here (NIH) is real.  And it’s a powerful force. And it can be overcome.  And when it is overcome, the results are spectacular.

Image credit — Becky Mastubara

Doing what you did last works well, right up until it doesn’t.

When you put 100% effort into doing what you did last time and get 80% of the output of last time, it’s time to do something different next time.

If it worked last time, but the environment or competition has changed, chances are it won’t work this time.

You can never step in the same river twice, and it’s the same with best practices.

Doing what you did last time is predictable until it isn’t.

The cost of trying the same thing too often is the opportunity cost of unlearned learning, which only comes from doing new things in new ways.

Our accounting systems don’t know how to capture the lost value due to unlearned learning, but your competition does.

Doing what you did last time may be efficient, but that doesn’t matter when it becomes ineffective.

Without new learning, you have a tired business model that will give you less year on year.

If you do what you did last time, you slowly learn what no longer works, but that’s all.

The best practice isn’t best when the context is different.

It’s not okay to do what you did last time all the time.

If you always do what you did last time, you don’t grow as a person.

If you do what you did last time, there are no upside surprises but there may be downside surprises.

Doing what you did last time is bad for your brain and your business.

How much of your work is repeating what you did last time? And how do you feel about that?

If you are tired of doing what you did last time, what are you going to do about it?

Might you sneak in some harmless novelty when no one is looking?

Might you conspire to try something new without raising the suspicion of the Standard Work Police?

Might you run a small experiment where the investment is small but the learning could be important?

Might you propose trying something new in a small way, highlighting the potential benefit and the safe-to-fail nature of the approach?

Might you propose small experiments run in parallel to increase the learning rate?

Might you identify an important problem that has never been solved and try to solve it?

Might you come up with a new solution that radically grows company profits?

Might you create a solution that obsoletes your company’s most profitable offering?

Might you bring your whole self to your work and see what happens?

Image credit – Marc Dalmulder

Stop, Start, Continue is a powerful, straightforward way to manage things.

If it’s not working, Stop.

If it’s working well, Continue.

If there’s a big opportunity to grow, Start.

Sounds pretty simple, but it’s often executed poorly.

The most dangerous variant of Stop, Start, Continue is Start, Start, Continue.  Regardless of how well projects are doing, they Continue.  The market has changed but the product hasn’t launched yet, Continue the project.  Though the technical risk is increasing instead of decreasing, keep your mouth shut and Continue the project.  Though resources have moved to different projects (that have recently started), Continue the project and pretend progress is being made.  And though Continue is a big problem, Starting is a bigger one.

With Start, Start, Continue, the company’s eyes are too big for their stomach.  Because there is no mechanism to limit the start of new projects based on the available resources (people, tools, infrastructure), projects start without the resources needed to get them done.  In the short term, there’s a celebration because an important new project has started.  But a month later, everyone on the project team knows the project is doomed because the project is largely unstaffed. And because of the tight lips, no one in company leadership knows there’s a problem.  The telltale signs of Start, Start, Continue are long projects (insufficient resources) and a lack of Finishing (too many projects and too little focus).

There is a little-known process that can overpower Start, Start, Continue.  It’s called Stop, Stop, Stop.  It’s simple and powerful.

With Stop, Stop, Stop, stalled projects are stopped and resources are freed up to accelerate the best remaining projects.  Think of it as moving from Continue existing projects to Accelerate the most important projects.  And with Stop, Stop, Stop, there is no starting.  None.  There is only stopping, at least to start.  Pet projects are stopped. Long-in-the-tooth projects are stopped. Irrelevant projects are stopped.  And even good projects are stopped to allow great projects to Start.

With Stop, Stop, Stop, at least two projects must stop before a new project can start.  And it’s better to stop three.

The result of Stop, Stop, Stop is a glut of freed-up resources that can be applied to amazing new projects.  And because the resources are unallocated and ready to go, those new projects can be fully staffed and can make progress quickly.  And because there are now fewer projects overall, the shared resources can respond more quickly for double acceleration.  And with fewer projects, there are fewer resource collisions among projects and fewer slowdowns. Triple acceleration and a lighter project management burden.

If your projects are moving too slowly, use Stop, Stop, Stop to stop the worst projects.  If you have too many projects and too few resources, Stop, Stop, Stop can set you free.  If you want to Start an amazing new project, use Stop, Stop, Stop to free up the resources to make it happen.

Before you Start, Stop.  And before you Continue, Stop. And instead of pretending to Stop or talking about Stopping, Stop.

When there’s a disagreement between the stated strategy and the active projects, believe the active projects.

When there’s a formal objective to reduce the number of meetings and the number of meetings doesn’t decrease, the desired outcome isn’t really desired.

When there’s a desire to reduce costs and there’s no hiring freeze, there’s no real desire to reduce costs.

When it’s acknowledged that there are too many projects and more projects are added, the doers’ morale tanks while the approvers’ credibility is decimated.

When people don’t talk openly about the mismatch between words and behavior, it does not mean they’re unaware.

When there’s a mismatch between words and behavior, people see it.

When you notice someone having a difficult time, take the time to check in with them.  An in-person “Are you okay?” is probably the best way, but a phone call, text, or video chat will also do nicely.

When you’re having a difficult time, when someone notices and checks in you feel a little better.

When someone reacts in an outsized way, use that as a signal to check in with them.  Your check-in can help them realize their reaction was outsized, as they may not know.  It’s likely a deeper conversation will emerge naturally.  This is not a time to chastise or judge, rather it’s a time to show them you care.  An in-person “You got a minute?” followed by a kind “Are you doing okay?” work well in this situation.  But a phone call or text message can also be effective.  The most important thing, though, is you make the time to check in.

When you check in, you make a difference in people’s lives.  And they remember.

Is a simple check-in really that powerful?  Yes. Does it really make a difference?  Yes. But don’t take my word for it.  Run the experiment for yourself.  Here’s the experimental protocol.

1. Pay attention.
2. Look for people who are having a difficult time or people whose behavior is different than usual.
3. When you notice the behavior of (2), make a note to yourself and give yourself the action item to check in.
4. As soon as you can, check in with them. Do it in person, if possible.  If you cannot, call them on the phone or send them a text.  Email is too impersonal. Don’t use it.
   1. To initiate the check-in, use the “You got a minute?” and “Are you doing okay?” language. Keep it simple.
   2. After using the language of (4.1), listen to them. No need to fix anything.  Just listen.  They don’t want to be fixed; they want to be heard.
5. Enjoy the good feeling that comes from checking in.
6. Repeat 1-5, as needed.

After running the experiment, I think you’ll learn that checking in is powerful and helps both parties feel better.  And the more you run the experiment (demonstrate the behavior), the more likely it will spread.

And, just maybe, at some point down the road, someone may reach out to you and ask “You got a minute?” and “Are you doing okay?”.

Image credit — Funk Dooby

Companies that are good at planning their projects create roadmaps spanning about three years, where individual projects are sequenced to create a coordinated set of projects that fit with each other.  The roadmap helps everyone know what’s important and helps the resources flow to those most important projects.

Through the planning process, the collection of potential projects is assessed and the best ones are elevated to the product roadmap.  And by best, I mean the projects that will generate the most incremental profit.  The projects on the roadmap generate the profits that underpin the company’s financial plan and the company is fanatically committed to the financial plan. The importance of these projects cannot be overstated.  And what that means is once a project makes it to the roadmap, there’s only one way to get it off the roadmap, and that’s to complete it successfully.

For the next three years, everyone knows what they’ll work on.  And they also know what they won’t work on.

The best companies want to be efficient so they staff their projects in a way that results in high utilization.  The most common way to do this is to load up the roadmap with too many projects and staff the projects with too few people.  The result is a significant fraction of people’s time (sometimes more than 100%) is pre-allocated to the projects on the roadmap.  The efficiency metrics look good and it may actually result in many successful launches.  But the downside of ultra-high utilization of resources is often forgotten.

When all your people are booked for the next three years on high-value projects, they cannot respond to new opportunities as they arise.  When someone comes back from a customer visit and says, “There’s an exciting new opportunity to grow the business significantly!” the best response is “We can’t do that because all our people are committed to the three-year plan.”.  The worst response is “Let’s put together a team to create a project plan and do the project.”.  With the first response, the project doesn’t get done and zero resources are wasted trying to figure out how to do the project without the needed resources.  With the second response, the project doesn’t get done but only after significant resources are wasted trying to figure out how to do the project without the needed resources.

Starting new projects is difficult because everyone is over-booked and over-committed on projects that the company thinks will generate significant (and predictable) profits.  What this means is to start a new project in this high-utilization environment, the new project must displace a project on the three-year plan.  And remember, the projects that must be displaced are the projects the company has chosen to generate the company’s future profits.  So, to become an active project (and make it to the three-year plan) the candidate project must be shown to create more profits, use fewer resources and launch sooner than the projects already on the three-year plan.  And this is taller than a tall order.

So, is there a solution?  Not really, because the only possible solution is to reduce resource utilization to create unallocated resources that can respond to emergent opportunities when they arise.  And that’s not possible because good companies have a deep and unskillful attachment efficiency.

Image credit — Bernard Spragg NZ

It’s difficult to describe what an innovative company looks like, and there’s no singular recipe or direction that is right for all companies.  Here are some From: To: pairings that I hope will help you in your migration toward innovation.  You’re heading in the right direction as your company generates Tos and fewer Froms.

From:  No one is asking for that technology.

To:       What does this new technology stand for?

From:  How will the company benefit?

To:       How will the customer benefit?

From:  What’s the smallest improvement that will make a difference?

To:       How can we make the most significant difference?

From:  When will you be done?

To:       What will you learn?

From:  This might not work.

To:       How might this work?

From:  Start, Start, Continue.

To:       Stop, Start, Continue.

From: We’ve tried that before and it didn’t work.

To:      What’s changed since last time?

From:  What does perfect look like?

To:       How is the work done today and which elements can we improve?

From:  Defend and Defend the core.

To:       Extend and Defend the core.

From:  Define the idealized future state.

To:       Start with the work.

From:  That won’t work!

To:       Hey, watch this!

When you see something, do you care enough to say something?

If you disagree, do you care enough to say it out loud?

When the emperor has no clothes, do you care enough to hand them a cover-up?

Cynicism is grounded in caring.  Do you care enough to be cynical?

Agreement without truth is not agreement.  Do you care enough to disagree?

Violation of the status quo creates conflict.  Do you care enough to violate?

If you care, speak your truth.

“Great Grey Owl (Strix nebulosa)” by Bernard Spragg is marked with CC0 1.0.

What does work look like when you prioritize your happiness?

When it’s announced that open positions will not be backfilled to meet the practical realities of a recession, you reduce the scope of your projects and push out their completion dates to match the reduction in resources. And the impact on your career?  I don’t know, but the people that work for you and everyone else that knows how the work is done will move mountains for you.

Under the banner of standard work, you are given the same task as the one you just completed.  Sure, you can do it efficiently and effectively, but if you do that same work one more time, your brain will fall off.  So, instead of doing it yourself, you give the work to a lesser-experienced person who is worthy of investment and help them get the work done.  They get to learn new skills and the work is done well because you keep them on the straight and narrow. And you get to be a teacher and create a future leader that the company will need in a couple of years.  And the downside?  The work takes a little longer, but so what.

What does work look like when you prioritize your health?

When an extra-early meeting is scheduled because everyone’s regular day is already fully booked with meetings, you decline the meeting so you can get the recommended amount of sleep recommended by the health professionals.  And the negative consequences to your career progression?  Well, that’s a choice for your company.

When you get home from work, you disconnect your phone from the company network so you won’t be distracted by work-related interruptions.  Because you separated yourself from work, after dinner is cleaned up you can make a healthy lunch for tomorrow.  If there’s some downside risk to your career, find another company to work for.

What does work look like when you prioritize your family?

When an extra-late meeting is scheduled because everyone’s regular day is already fully booked with meetings, you decline the meeting so you can cook dinner and eat with your family.  The conversation with the kids is mundane and meaningful and ten years from now they’ll be better for it. And the negative consequences?  None, because tomorrow morning you can read the minutes of the meeting.

When you’re on your yearly holiday with your family and your boss calls your cell phone to ask you to come back to work early to deal with an emergency, you don’t answer the call and let it go to voicemail.  Then, when you get back to the office after vacation, you listen to the voicemail and check in with your boss.  And because you didn’t pick up the call, someone else had greatness thrust upon them and developed into someone who can solve emergencies.  Now there are two of you.  And the downside?  Well, I think that depends on your boss.

“Looking For Clues (188 / 365)” by somegeekintn is licensed under CC BY 2.0.

When you spend time with a group in person, you get to know them in ways that can’t be known if you spend time with them using electronic means.  When meeting in person, you can tell when someone says something that’s difficult for them.  And you can also tell when that difficulty is fake.  When using screens, those two situations look the same, but, in person, you know they are different. There’s no way to quantify the value of that type of discernment, but the value borders on pricelessness.

When people know you see them as they really are, they know you care.  And they like that because they know your discernment requires significant effort.  Sure, at first, they may be uncomfortable because you can see them as they are, but, over time, they learn that your ability to see them as they are is a sign of their importance.  And there’s no need to call this out explicitly because all that learning comes as a natural byproduct of meeting in person.

And the game changes when people know you see them (and accept them) for who they are. The breadth of topics that can be discussed becomes almost limitless.  Personal stories flow; family experiences bubble to the surface; misunderstandings are discussed openly; vulnerable thoughts and feelings are safely expressed; and trust deepens.

I think we’ve forgotten the power of working together in person, but it only takes three days of in-person project work to help us remember.  If you have an important project deliverable, I suggest you organize a three-day, in-person event where a small group gets together to work on the deliverable.  Create a formal agenda where it’s 50% work and 50% not work.  (I’ve found that the 50% not work is the most valuable and productive.)  Make it focused and make it personal.  Cook food for the group. Go off-site to a museum. Go for a hike.  And work hard.  But, most importantly, spend time together.

Things will be different after the three-day event.  Sure, you’ll make progress on your project deliverable, but, more importantly, you’ll create the conditions for the group to do amazing work over the next five years.

“Elephants Amboseli” by blieusong is licensed under CC BY-SA 2.0.