Shipulski On Design

Archive for the ‘Clarity’ Category

If there’s one superpower to develop, it’s to learn how to assess a project and get a good feel for when it will launch.

When you want to know how long a project will take, ask this simple question: ‘What must the project team learn before the project can launch?”  By starting with this single question, you will start the discussion that will lead you to an understanding of what hasn’t been done before and where the uncertainty is hiding.  And if there’s one thing that can accelerate a project, it’s defining where the uncertainty is hiding. And knowing this doubly powerful, like a pure two-for-one, because if you know where uncertainty is, by definition, you know where it isn’t. Where the uncertainty isn’t, you can do what you did last time, and because you’ve done it before, you know how long it will take.  No new tools, no new methods, no new analyses, no new machines, no new skillsets, no new anything. And for the remaining elements of the project, well, that’s where the uncertainty is hiding and that’s where you will focus on the learning needed to secure the launch.

But it can be difficult to understand the specific learning that must be done for a project to launch.  One trick I like to use is the Same-But-Different method. It goes like this.  Identify a project that launched (Project A) that’s most similar to the one that will launch next (Project B) and perform a subtraction of sorts.  Declare that Project B (the one you want to launch) is the same as Project A (the one you already launched) but different in specific ways and then define those differences as clearly and tightly as possible.  And where it’s different, that’s where the learning energy must be concentrated.

Same-But-Different sounds simplistic and trivial, but it isn’t.  More than anything, it’s powerful.  For the elements that are the same, you do what you did last time, which is freeing.  And for the small subset if things that are different, you dig in!

Same-But-Different drives deep clarity and extreme focus, which result in blistering progress and blinding effectiveness.

And for some reason unknown to me, asking a team to define the novel elements of a project is at least fifty times more difficult than asking them how Project B is different than Project A.  So, it feels good to the team when they can use Same-But-Different to quickly easily define what’s different and then point directly to the uncertainty.  And once the team knows where the uncertainty is hiding, it’s no longer hiding.

And if there’s one thing a project team likes, it’s knowing where the uncertainty is hiding.

“The same, but different by the Paris Photographic Co. (c.1880)” by pellethepoet is marked with CC BY 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.

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

This seems like a repeat of the last time we set a project launch date without regard for the work content.  Do you see it that way?

This person certainly looks the part and went to the right school, but they have not done this work before.  Why do you think we should hire them even though they don’t have the experience?

The last time we ran a project like this it took two years to complete.  Why do you think this one will take six months?

If it didn’t work last time, why do you think it will work this time?

Why do you think we can do twice the work we did last year while reducing our headcount?

The work content, timeline, and budget are intimately linked. Why do you think it’s possible to increase the work content, pull in the timeline, and reduce the budget?

Seven out of thirteen people have left the team. How many people have to leave before you think we have a problem?

Yes, we’ve had great success with that approach over the last decade, but our most recent effort demonstrated that our returns are diminishing.  Why do you want to do that again?

If you think it’s such a good idea, why don’t you do it?

Why do you think it’s okay to add another project when we’re behind on all our existing projects?

Customers are buying the competitive technology.  Why don’t you believe that they’re now better than we are?

This work is critical to our success, yet we don’t have the skills sets, capacity, or budget to hire it out.  Why are you telling us you will get it done?

This problem seems to fit squarely within your span of responsibility. Why do you expect other teams to fix it for you?

I know a resource gap of this magnitude seems unbelievable but is what the capacity model shows.  Why don’t you believe the capacity model?

We have no one to do that work. Why do you think it’s okay to ask the team to sign up for something they can’t pull off?

Based on the survey results, the culture is declining.  Why don’t you want to acknowledge that?

“I have a question” by The U.S. Army is licensed under CC BY 2.0

For work that has not been done before, there’s no right answer.  The only wrong answer is to say “no” to trying something new.  Sure, it might not work.  But, the only way to guarantee it won’t work is to say no to trying.

If innovation projects fail nine out of ten times, you can increase the number of projects you try or you can get better at choosing the projects to say no to.  I suggest you say learn to say yes to the one in ten projects that will be successful.

If you believe that nine out of ten innovation projects will fail, you shouldn’t do innovation for a living.  Even if true, you can’t have a happy life going to work every day with a ninety percent chance of failure.  That failure rate is simply not sustainable.  In baseball, the very best hitters of all time were unsuccessful sixty percent of the time, yet, even they focused on the forty percent of the time they got it right.  Innovation should be like that.

If you’ve failed on ninety percent of the projects you’ve worked on, you’ve probably been run out of town at least several times.  No one can fail ninety percent of the time and hold onto their job.

If you’ve failed ninety percent of the time, you’re doing it wrong.

If you’ve failed ninety percent of the time, you’ve likely tried to solve the wrong problems.  If so, it’s time to learn how to solve the right problems.  The right problems have two important attributes: 1) People will pay you if they are solved. 2) They’re solvable.  I think we know a lot about the first attribute and far too little about the second. The problem with solvability is that there’s no partial credit, meaning, if a problem is almost solvable, it’s not solvable. And here’s the troubling part: if a problem is almost solved, you get none of the money.  I suggest you tattoo that one on your arm.

As a subject matter expert, you know what could work and what won’t.  And if you don’t think you can tell the difference, you’re not a subject matter expert.

Here’s a rule to live by: Don’t work on projects that you know won’t work.

Here’s a corollary: If your boss asks you to work on something that won’t work, run.

If you don’t think it will work, you’re right, even if you’re not.

If it might work, that’s about right. If it will work, let someone else do it. If it won’t work, run.

If you’ve got no reason to believe it will work, it won’t.

If you can’t imagine it will work, it won’t.

If someone else says it won’t work, it might.

If someone else tries to convince you it won’t work, they may have selfish reasons to think that way.

It doesn’t matter if others think it won’t work. It matters what you think.

So, what do you think?

If you someone asks you to believe something you don’t, what will you do?

If you try to fake it until you make it, the Universe will make you pay.

If you think you can outsmart or outlast the Universe, you can’t.

If you have a bad feeling about a project, it’s a bad project.

If others tell you that it’s a bad project, it may be a good one.

Only you can decide if a project is worth doing.

It’s time for you to decide.

“Good example of Crossfit Weight lifting – In Crossfit Always lift until you reach the point of Failure or you tear something” by CrossfitPaleoDietFitnessClasses is licensed under CC BY 2.0

Speak up.  Your ideas can’t see daylight unless others know about them.

Be wrong. When you’re wrong, you sharpen the rightness.

Be right. When you’re right in the face of wrongness, everyone wins, except for you.

Stand tall. Stand behind your decisions, but you can’t be responsible for their outcome.

Be truthful, but not hurtful.

Be overwhelmed.  This is difficult.

Give it away. When things go well, delegate credit to the up-and-coming.  They’ll remember.

Support others. When someone’s in the bucket, pull them out. They’ll remember.

Pay it forward. A kind soul gave it to you, and it’s time to give it to someone else. They’ll remember.

Say “thank you.” And mean it.

Be quiet. When things are on the right track, there’s no need to derail.

Take the heat. When there’s a mistake, own it so the young don’t have to. They’ll remember.

Make room for others. Nothing blocks their growth like your career aspirations.

Say nothing negative, unless you can’t. And if you must, say it in private.

Praise publicly, loudly, and often.

Set up others for success. And when accused of doing so, plead ignorance.

Share your frustrations, but sparingly. Done skillfully, it’s a compliment.

Be human.  People will notice.

“Uncomfortable Fisher” by DaveFayram is licensed under CC BY-SA 2.0

When there’s disagreement between words and behavior, believe the behavior.  This is especially true when the words deny the behavior.

When there’s disagreement between the data and the decision, the data is innocent.

When there’s agreement that there’s insufficient data but a decision must be made, there should be no disagreement that the decision is judgment-based.

When there’s disagreement on the fact that there’s no data to support the decision, that’s a problem.

When there’s disagreement on the path forward, it’s helpful to have agreement on the process to decide.

When there’s disagreement among professionals, there is no place for argument.

When there’s disagreement, there is respect for the individual and a healthy disrespect for the ideas.

When there’s disagreement, the decisions are better.

When there’s disagreement, there’s independent thinking.

When there’s disagreement, there is learning.

When there’s disagreement, there is vulnerability.

When there’s disagreement, there is courage.

When there’s disagreement, there is trust.

“Teamwork” by davis.steve32 is licensed under CC BY 2.0

Good coaches listen to you.  They don’t judge, they just listen.

Good coaches continually study the game.  They do it in private, but they study.

Good coaches tell you that you can do better, and that, too, they do in private.

Good coaches pick you up off the floor. They know that getting knocked over is part of the game.

Good coaches never scream at you, but they will cry with you.

Good coaches never stop being your coach. Never.

Good coaches learn from you, and the best ones tell you when that happens.

Good coaches don’t compromise. Ever.

Good coaches have played the game and have made mistakes. That’s why they’re good coaches.

Good coaches do what’s in your best interest, not theirs.

Good coaches are sometimes wrong, and the best ones tell you when that happens.

Good coaches don’t care what other people think of them, but they care deeply about you.

Good coaches are prepared to be misunderstood, though it’s not their preference.

Good coaches let you bump your head or smash your knee, but, otherwise, they keep you safe.

Good coaches earn your trust.

Good coaches always believe you and perfectly comfortable disagreeing with you at the same time.

Good coaches know it’s always your choice, and they know that’s how deep learning happens.

Good coaches stick with you, unless you don’t do your part.

Good coaches don’t want credit. They want you to grow.

Good coaches don’t have a script. They create a custom training plan based on your needs.

Good coaches simplify things when it’s time, unless it’s time to make things complicated.

Good coaches aren’t always positive, but they are always truthful.

Good coaches are generous with their time.

Good coaches make a difference.

With one eye open and the other closed, you have no depth perception. With two eyes open, you see in three dimensions.  This ability to see in three dimensions is possible because each eye sees from a unique perspective.  The brain knits together the two unique perspectives so you can see the world as it is. Or, as your brain thinks it is, at least.

And the same can be said for an organization.  When everyone sees things from a single perspective, the organization has no depth perception.  But with at least two perspectives, the organization can better see things as they are.  The problem is we’re not taught to see from unique perspectives.

With most presentations, the material is delivered from a single perspective with the intention of helping everyone see from that singular perspective.  Because there’s no depth to the presentation, it looks the same whether you look at it with one eye or two.  But with some training, you can learn how to see depth even when it has purposely been scraped away.

And it’s the same with reports, proposals, and plans. They are usually written from a single perspective with the objective of helping everyone reach a single conclusion.  But with some practice, you can learn to see what’s missing to better see things as they are.

When you see what’s missing, you see things in stereo vision.

Here are some tips to help you see what’s missing.  Try them out next time you watch a presentation or read a report, proposal, or plan.

When you see a WHAT, look for the missing WHY on the top and HOW on the bottom. Often, at least one slice of bread is missing from the why-what-how sandwich.

When you see a HOW, look for the missing WHO and WHEN.  Usually, the bread or meat is missing from the how-who-when sandwich.

Here’s a rule to live by: Without finishing there can be no starting.

When you see a long list of new projects, tasks, or initiatives that will start next year, look for the missing list of activities that would have to stop in order for the new ones to start.

When you see lots of starting, you’ll see a lot of missing finishing.

When you see a proposal to demonstrate something for the first time or an initial pilot, look for the missing resources for the “then what” work.  After the prototype is successful, then what?  After the pilot is successful, then what?  Look for the missing “then what” resources needed to scale the work.  It won’t be there.

When you see a plan that requires new capabilities, look for the missing training plan that must be completed before the new work can be done well. And look for the missing budget that won’t be used to pay for the training plan that won’t happen.

When you see an increased output from a system, look for the missing investment needed to make it happen, the missing lead time to get approval for the missing investment, and the missing lead time to put things in place in time to achieve the increased output that won’t be realized.

When you see a completion date, look for the missing breakdown of the work content that wasn’t used to arbitrarily set the completion date that won’t be met.

When you see a cost reduction goal, look for the missing resources that won’t be freed up from other projects to do the cost reduction work that won’t get done.

It’s difficult to see what’s missing.  I hope you find these tips helpful.

“missing pieces” by LeaESQUE is licensed under CC BY-ND 2.0

If you want to grow leaders, meet with them daily.

If you want to grow leaders, demand that they disagree with you.

If you want to grow leaders, help them with all facets of their lives.

If you want to grow leaders, there is no failure, there is only learning.

If you want to grow leaders, give them the best work.

If you want to grow leaders, protect them.

If you want to grow leaders, spend at least two years with them.

If you want to grow leaders, push them.

If you want to grow leaders, praise them.

If you want to grow leaders, get them comfortable with discomfort.

If you want to grow leaders, show them who you are.

If you want to grow leaders, demand that they use their judgment.

If you want to grow leaders, give them just a bit more than they can handle and help them handle it.

If you want to grow leaders, show emotion.

If you want to grow leaders, tell them the truth, even when it creates anxiety.

If you want to grow leaders, always be there for them.

If you want to grow leaders, pull a hamstring and make them present in your place.

If you want to grow leaders, be willing to compromise your career so their careers can blossom.

If you want to grow leaders, when you are on vacation tell everyone they are in charge.

If you want to grow leaders, let them chose between to two good options.

If you want to grow leaders, pay attention to them.

If you want to grow leaders, be consistent.

If you want to grow leaders, help them with their anxiety.

If you want to grow leaders, trust them.

If you want to grow leaders, demonstrate leadership.

“Mother duck and ducklings” by Tambako the Jaguar is licensed under CC BY-ND 2.0

 

Your truth is what you see.  Your truth is what you think.  Your truth is what feel.  Your truth is what you say. Your truth is what you do.

 

If you see something, say something.

If no one wants to hear it, that’s on them.

 

If your truth differs from common believe, I want to hear it.

If your truth differs from common believe and no one wants to hear it, that’s troubling.

 

If you don’t speak your truth, that’s on you.

If you speak it and they dismiss it, that’s on them.

 

Your truth is your truth, and no one can take that away from you.

When someone tries to take your truth from you, shame on them.

 

Your truth is your truth. Full stop.

And even if it turns out to be misaligned with how things are, it’s still your responsibility to tell it.

 

If your company makes it difficult for you to speak your truth, you’re still obliged to speak it.

If your company makes it difficult for you to speak your truth, they don’t value you.

 

When your truth turns out to be misaligned with how things are, thank you for telling it.

You’ve provided a valuable perspective that helped us see things more clearly.

 

If you’re striving for your next promotion, it can be difficult to speak your dissenting truth.

If it’s difficult to speak your dissenting truth, instead of promotion, think relocation.

 

If you feel you must yell your dissenting truth, you’re not confident in it.

If you’re confident in your truth and you still feel you must yell it, you have a bigger problem.

 

When you know your truth is standing on bedrock, there’s no need to argue.

When someone argues with your bedrock truth, that’s a problem for them.

 

If you can put your hand over mouth and point to your truth, you have bedrock truth.

When you write a report grounded in bedrock truth, it’s the same as putting your hand over your mouth and pointing to the truth.

 

If you speak your truth and it doesn’t bring about the change you want, sometimes that happens.

And sometimes it brings about its opposite.

 

Your truth doesn’t have to be right to be useful.

But for your truth to be useful, you must be uncompromising with it.

 

You don’t have to know why you believe your truth; you just have to believe it.

It’s not your responsibility to make others believe your truth; it’s your responsibility to tell it.

 

When your truth contradicts success, expect dismissal and disbelief.

When your truth meets with dismissal and disbelief, you may be onto something.

 

Tomorrow’s truth will likely be different than today’s.

But you don’t have a responsibility to be consistent; you have a responsibility to the truth.

 

image credit — “the eyes of truth r always watching u” by TheAlieness GiselaGiardino²³ is licensed under CC BY-SA 2.0