Shipulski On Design

When you want new thinking or rapid progress, create a small team.

When you have a small team, they manage the handoffs on their own and help each other.

Small teams hold themselves accountable.

With small teams, one member’s problem becomes everyone’s problem in record time.

Small teams can’t work on more than one project at a time because it’s a small team.

And when a small team works on a single project, progress is rapid.

Small teams use their judgment because they have to.

The judgment of small teams is good because they use it often.

On small teams, team members are loyal to each other and set clear expectations.

Small teams coordinate and phase the work as needed.

With small teams, waiting is reduced because the team members see it immediately.

When something breaks, small teams fix it quickly because the breakage is apparent to all.

The tight connections of a small team are magic.

Small teams are fun.

Small teams are effective.

And small teams are powered by trust.

“LEGO Octan pit crew celebrating High Five Day (held every third Thursday of April)” by Pest15 is marked with CC BY-SA 2.0.

Clean-sheet designs are fun, right up until they don’t launch.

When you feel the urge to do a clean-sheet design, go home early.

When you don’t know how to make it better, make it worse and do the opposite.

Without trying, there is no way to know if it will work.

Trying sometimes feels like dying.

But without trying, nothing changes.

Agreement is important, but only after the critical decision has been made.

When there’s 100% agreement, you waited too long to make the decision.

When it’s unclear who the customer is, ask “Whose problem will be solved?”

When the value proposition is unclear, ask ‘What problem will be solved?”

When your technology becomes mature, no one wants to believe it.

When everyone believes the technology is mature, you should have started working on the new technology four years ago.

If your projects are slow, blame your decision-making processes.

Two of the most important decisions: which projects to start and which to stop.

All the action happens at the interfaces, but that’s also where two spans of control come together and chafe.

If you want to understand your silos and why they don’t play nicely together, look at the organizational chart.

When a company starts up, the product sets the organizational structure.

Then, once a company is mature, the organizational structure constrains the product.

At the early stages of a project, there’s a lot of uncertainty.

And once the project is complete, there’s a lot of uncertainty.

“Toys Never Forget” by Alyssa L. Miller is marked with CC BY 2.0.

If you’re asked to be faster, choose to be more effective.  There’s nothing slower than being fast at something that doesn’t matter.

If you’re given a goal to be more productive, instead, improve effectiveness. There’s nothing less productive than making the wrong thing.

If you’re measured on efficiency, focus on effectiveness. Customers don’t care about your efficiency when you ship them the wrong product.

If you’re asked to improve quality, that’s good because quality is an important element of effectiveness.

If you’re asked to demonstrate more activity, focus on progress, which is activity done in an effective way.

If you’re asked to improve your team, ask them how they can be more effective and do that.

Regardless of the question, the answer is effectiveness.

Image credit pbkwee.

When you have no slack time, you can’t start new projects.

When you have no slack time, you can’t run toward the projects that need your help.

When you have no slack time, you have no time to think.

When you have no slack time, you have no time to learn.

When you have no slack time, there’s no time for concern for others.

When you have no slack time, there’s no time for your best judgment.

When there is no slack time, what used to be personal becomes transactional.

When there is no slack time, any hiccup creates project slip.

When you have no slack time, the critical path will find you.

When no one has slack time, one project’s slip ripples delay into all the others.

When you have no slack time, excitement withers.

When you have no slack time, imagination dies.

When you have no slack time, engagement suffers.

When you have no slack time, burnout will find you.

When you have no slack time, work sucks.

When you have no slack time, people leave.

I have one question for you.  How much slack time do you have?

“Hurry up Leonie, we are late…” by The Preiser Project is licensed under CC BY 2.0

When you design something, you create a solution to a collection of problems.  But it goes far beyond creating the solution.  You also must create objective evidence that demonstrates that the solution does, in fact, solve the problems.  And the reason to generate this evidence is to help the organization believe that the solution solves the problem, which is an additional requirement that comes with designing something.  Without this belief, the organization won’t go out to the customer base and convince them that the solution will solve their problems.  If the sales team doesn’t believe, the customers won’t believe.

In school, we are taught to create the solution, and that’s it.  Here are the drawings, here are the materials to make it, here is the process documentation to build it, and my work here is done. But that’s not enough.

Before designing the solution, you’ve got to design the tests that create objective evidence that the solution actually works, that it provides the right goodness and it solves the right problems.  This is an easy thing to say, but for a number of reasons, it’s difficult to do.  To start, before you can design the right tests, you’ve got to decide on the right problems and the right goodness.  And if there’s disagreement and the wrong tests are defined, the design community will work in the wrong areas to generate the wrong value.  Yes, there will be objective evidence, and, yes, the evidence will create a belief within the organization that problems are solved and goodness is achieved.  But when the sales team takes it to the customer, the value proposition won’t resonate and it won’t sell.

Some questions to ask about testing. When you create improvements to an existing product, what is the family of tests you use to characterize the incremental goodness?  And a tougher question: When you develop a new offering that provides new lines of goodness and solves new problems, how do you define the right tests? And a tougher question: When there’s disagreement about which tests are the most important, how do you converge on the right tests?

Image credit — rjacklin1975

If you see a problem, tell someone.  But, also, tell them how you’d like to improve things.

Once you see a problem, you have an obligation to seek a solution.

Complaining is telling someone they have a problem but stopping short of offering solutions.

To stop someone from complaining, ask them how they might make the situation better.

Problems are good when people use them as a forcing function to create new offerings.

Problems are bad when people articulate them and then go home early.

Thing is, problems aren’t good or bad.  It’s our response that determines their flavor.

If it’s your problem, it can never be our solution.

Sometimes the best solution to a problem is to solve a different one.

Problem-solving is 90% problem definition and 10% getting ready to define the problem.

When people don’t look critically at the situation, there are no problems.  And that’s a big problem.

Big problems require big solutions. And that’s why it’s skillful to convert big ones into smaller ones.

Solving the right problem is much more important than solving the biggest problem.

If the team thinks it’s impossible to solve the problem, redefine the problem and solve that one.

You can relabel problems as “opportunities” as long as you remember they’re still problems

When it comes to problem-solving, there is no partial credit. A problem is either solved or it isn’t.

“Fry complaining” by kaibara87

People don’t leave a company because they feel appreciated.

People don’t leave a company because they feel part of something bigger than themselves.

People don’t leave a company because they see a huge financial upside if they stay.

People don’t leave a company because they are treated with kindness and respect.

People don’t leave a company because they can make less money elsewhere.

People don’t leave a company because they see good career growth in their future.

People don’t leave a company because they know all the key players and know how to get things done.

People don’t leave the company so they can abandon their primary care physician.

People don’t leave a company because their career path is paved with gold.

People don’t leave a company because they are highly engaged in their work.

People don’t leave a company because they want to uproot their kids and start them in a new school.

People don’t leave a company because their boss treats them too well.

People don’t leave a company because their work is meaningful.

People don’t leave a company because their coworkers treat them with respect.

People don’t leave a company because they want to pay the commission on a real estate transaction.

People don’t leave a company because they’ve spent a decade building a Trust Network.

People don’t leave a company because they want their kids to learn to trust a new dentist.

People don’t leave a company because they have a flexible work arrangement.

People don’t leave a company because they feel safe on the job.

People don’t leave a company because they are trusted to use their judgment.

People don’t leave the company because they want the joy that comes from rolling over their 401k.

People don’t leave a company when they have the tools and resources to get the work done.

People don’t leave a company when their workload is in line with their capacity to get it done.

People don’t leave a company when they feel valued.

People don’t leave a company so they can learn a whole new medical benefits plan.

People don’t leave a job because they get to do the work the way they think it should be done.

So, I ask you, why are people leaving your company?

“Penguins on Parade” by D-Stanley is licensed under

Creating new ideas is easy.  Sit down, quiet your mind, and create a list of five new ideas.  There.  You’ve done it.  Five new ideas.  It didn’t take you a long time to create them.  But ideas are cheap.

Converting ideas into sellable products and selling them is difficult and expensive. A customer wants to buy the new product when the underlying idea that powers the new product solves an important problem for them.  In that way, ideas whose solutions don’t solve important problems aren’t good ideas.  And in order to convert a good idea into a winning product, dirt, rocks, and sticks (natural resources) must be converted into parts and those parts must be assembled into products.  That is expensive and time-consuming and requires a factory, tools, and people that know how to make things. And then the people that know how to sell things must apply their trade.  This, too, adds to the difficulty and expense of converting ideas into winning products.

The only thing more expensive than converting new ideas into winning products is reusing your tired, old ideas until your offerings run out of sizzle. While you extend and defend, your competitors convert new ideas into new value propositions that bring shame to your offering and your brand.  (To be clear, most extend-and-defend programs are actually defend-and-defend programs.)  And while you reuse/leverage your long-in-the-tooth ideas, start-ups create whole new technologies from scratch (new ideas on a grand scale) and pull the rug out from under you.  The trouble is that the ultra-high cost of extend-and-defend is invisible in the short term. In fact, when coupled with reuse, it’s highly profitable in the moment.  It takes years for the wheels to fall off the extend-and-defend bus, but make no mistake, the wheels fall off.

When you find the urge to create a laundry list of new ideas, don’t.  Instead, solve new problems for your customers.  And when you feel the immense pressure to extend and defend, don’t.  Instead, solve new problems for your customers.

And when all that gets old, repeat as needed.

“Cave paintings” by allspice1 is licensed under CC BY-ND 2.0

We’ve heard a lot about long supply chains that have broken down, parts shortages, and long lead times.  Granted, supply chains have been stressed, but we’ve designed out any sort of resiliency.  Our supply chains are inflexible, our products are intolerant to variation and multiple sources for parts, and our organizations have lost the ability to quickly and effectively redesign the product and the parts to address issues when they arise. We’ve pushed too hard on traditional costing and have not placed any value on flexibility.  And we’ve pushed too hard on efficiency and outsourced our design capability so we can no longer design our way out of problems.

Our supply chains are inflexible because that’s how we designed them.  The products cannot handle parts from multiple suppliers because that’s how we designed them.  And the parts cannot be made by multiple suppliers because that’s how we designed them.

Now for the upside.  If we want a robust supply chain, we can design the product and the parts in a way that makes a robust supply chain possible. If we want the flexibility to use multiple suppliers, we can design the product and parts in a way that makes it possible.  And if we want the capability to change the product to adapt to unforeseen changes, we can design our design organizations to make it possible.

There are established tools and methods to help the design community design products in a way that creates flexibility in the supply chain.  And those same tools and methods can also help the design community create products that can be made with parts from multiple suppliers.  And there are teachers who can help rebuild the design community’s muscles so they can change the product in ways to address unforeseen problems with parts and suppliers.

How much did it cost you when your supply chain dried up? How much did it cost you the last time a supplier couldn’t deliver your parts? How much did it cost you when your design community couldn’t redesign the product to keep the assembly line running? Would you believe me if I told you that all those costs are a result of choices you made about how to design your supply chain, your product, your parts, and your engineering community?

And would you believe me if I told you could make all that go away?  Well, even if you don’t believe me, the potential upside of making it go away is so significant you may want to look into it anyway.

Image credit — New Manufacturing Challenge, Suzaki, 1987.

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

Next year will be different, but we don’t know how it will be different. All we know is that it will be different.

Some things will be the same and some will be different.  The trouble is that we won’t know which is which until we do.  We can speculate on how it will be different, but the Universe doesn’t care about our speculation.  Sure, it can be helpful to think about how things may go, but as long as we hold on to the may-ness of our speculations.  And we don’t know when we’ll know. We’ll know when we know, but no sooner. Even when the Operating Plan declares the hardest of hard dates, the Universe sets the learning schedule on its own terms, and it doesn’t care about our arbitrary timelines.

What to do?

Step 1. Try three new things. Choose things that are interesting and try them.  Try to try them in parallel as they may interact and inform each other. Before you start, define what success looks like and what you’ll do if they’re successful and if they’re not.  Defining the follow-on actions will help you keep the scope small.  For things that work out, you’ll struggle to allocate resources for the next stages, so start small.  And if things don’t work out, you’ll want to say that the projects consumed little resources and learned a lot.  Keep things small.  And if that doesn’t work, keep them smaller.

Step 2. Rinse and repeat.

I wish you a happy and safe New Year.  And thanks for reading.

Mike

“three” by Travelways.com is licensed under CC BY 2.0