Shipulski On Design

We all have to-do lists. We add things and we check them off.  This list grows and shrinks.  We judge ourselves negatively when we check off fewer than expected and positively when we check off more than that.  But what’s the right number of completed tasks for us to feel good? How many completed tasks is enough?

If you complete one task per week that saves $5000, is that enough? Is it enough to complete fifty tasks per year?  If you create the conditions that make possible a new product line that delivers $1B over three years, but you do that only once every five years, is that enough? Is it enough to do just that one right thing over five years? What does it look like to others when you complete one exceptionally meaningful task every five years? I think it looks like most of the time you are doing very little.

Sometimes you complete small things and sometimes you don’t.  And sometimes you learn what doesn’t work and that’s the completed task.  And sometimes there are long stretches where nothing is accomplished until you create something magical. Counting tasks is no way to go through life.

But counting and measuring is all the rage.  Look at your yearly goals.  Do ten of these.  Run six of those. Complete twelve of the other.  Why do we think we can predict what we should do next year?  Even sillier, do we really believe we know how many of these, those, and the others we will be able to get done next year?  C’mon.  Really?

What if all this counting prevents us from imagining the future? And what if our unhealthy fascination with measuring blocks us from creating it?

If it’s all about the measurable, there’s no room for the Magical.

Why not make some room for the Magical?

Image credit — Philip McErlean

Can you go on holiday and not think about work?

How long does it take your brain to join your body on vacation?

If your boss calls on vacation, what do you do?  And what does that say about you?

If your boss calls on vacation, what does that say about your boss?

Doing something else can help you see things differently when you return from vacation.

Doing nothing is something.

If you can’t let go, might you see your vacation as an opportunity for others to shine?

A new environment can stimulate new thinking.  Why not see your vacation as a new environment?

Hanging around with new people can help you see things differently.  Don’t you meet new people on holiday?

If your company will falter if you’re away for two weeks, it’s time to develop new talent.

If you have access to your email on vacation, are you sure you’re on vacation?

If you look at your email, you blew a whole vacation day.  Switching cost is real.  So is rumination.

You don’t have to be anyone special on vacation.  Why not try that at work?

Vacation isn’t selfish.  It’s healing.

Vacation isn’t time away from work, it’s time immersed in life.

There is no such thing as a halfway vacation.  It’s all-in or it’s not vacation.

Why not go all in?

It’s not possible until you demonstrate it.

It can’t be done until you show it being done.

It won’t work until you make it work.

It must be done using the standard process until you do it a much better way.

It’s required until you violate the requirement and everything is fine.

It’s needed until you show people how to do without.

It’s no one’s responsibility until you take responsibility and do it yourself.

It’s not fun until you have fun doing it.

It’s not sanctioned until you create something magical in an unsanctioned way.

It’s a crappy assignment until you transform it into a meaningful assignment.

It’s a lonely place until you help someone do their work better.

It’s a low-trust place until you trust someone.

It’s scary until you do it anyway.

So do it anyway.

Image credit — Tambako The Jaguar

For right frustration to emerge, you need an accurate understanding of how things are, a desire for them to be different, and a recognition you can’t remedy the situation.

The emergence of your desire for things to be different starts with knowing how things are.  And to see things as they are, you’ve got to be in the right condition – well-rested, unstressed, and sitting in the present moment. When you’re tired, stressed, or sitting in the past or future you can’t pay attention.  And when you don’t pay attention, you miss details or context and see something that isn’t.  Or, if you’re tired or stressed you can have clear eyes and a muddy interpretation. Either way, you’re off to a bad start because your desire for things to be different is wrongly informed. Sure, your misunderstanding can lead to a desire for things to be different, but your desire is founded on the wrong understanding.  If you want your frustration to be right frustration, seeing things as they are is the foundational step.  But it’s not yet a desire for things to be different.

Your desire for things to be different is a subtraction of sorts – when how things are minus how you want them to be equals something other than zero. (See Eq. 1)  Your brain-body uses that delta to create a desire for things to be different.  If how things are is equal to how you want them to be, the difference is zero (no delta) and there is no forcing function for your desire.  In that way, if you always want things to be as they are, there can be no desire for difference and frustration cannot emerge.  But frustration can emerge if you know how you want things to be and you recognize they’re not that way.

Eq. 1   Forcing Function for Desire (FFD) = (how things are) – (how you want them to be)

There is a more complete variant of the above equation where FFD is non-zero (there’s a difference between how things are and how you want them) yet frustration cannot emerge.  It’s called the “I don’t care enough” variant. (See Eq. 2) With this variant, you recognize how things are, you know how you want them to be, but you don’t care enough to be frustrated.

Eq. 2  FFD = [(how things are) – (how you want them to be)] * (Care Factor)

When you don’t care, your Care Factor (CF) = 0.  And when the non-zero delta is multiplied by a CF of zero, FFD is zero.  This means there is no forcing function for desire and frustration cannot emerge.  But this is not a good place to be.  Sure, frustration cannot emerge, but when you don’t care there is no forcing function for change.  Yes, you see things aren’t as you want, but you go along for the ride and don’t do anything about it.  I think that’s sad.  And I think that’s bad for business.  I’d rather have frustration.

Eq. 2 can be used by Human Resources as an Occom’s Razor of sorts.  If someone is frustrated, their CF is non-zero and they care.

Now the third factor required for frustration to emerge – a recognition you can’t do anything about the mismatch between how things are and how you want them. If you don’t recognize you can’t do anything to equalize how things are and how you want them, there can be no frustration.  Think – ignorance is bliss.  If you think you can do something to make how things are the same as how you want them, there is no frustration.  Because it’s important to you (CF is non-zero), you will devote energy to bringing the two sides together and there will be no frustration.  But when there’s a mismatch between how things are and how you want them, you care about making that mismatch go away, and you recognize you can’t do anything to eliminate the mismatch, frustration emerges.

What does all this say about people who display frustration? Do you want people that know how to see things as they are?  Do you want people who can imagine how things can be different?  Do you want people who understand the difference between what they can change and what they cannot? Do you want people who care enough to be frustrated?

Image credit — Atilla Kefeli

Put it out there.  You don’t have time to do otherwise.

Be true to yourself.  No one deserves that more than you do.

Tell the truth, even when it’s difficult for people to hear.  They’ll appreciate your honesty.

Believe the actions and not the words.  Enough said.

Learn to listen to what is not said.  That’s usually the juicy part.

Say no to good projects so you can say yes to great ones.

Say what you will do and do it.  That’s where trust comes from.

Deliver praise in public.  Better yet, deliver praise in front of their spouse.

Develop informal networks.  They are more powerful than the formal org chart.

Learn to see what’s not happening.  You’ll understand what’s truly going on.

Help people.  It’s like helping yourself twice.

Don’t start a project you’re not committed to finishing. There’s no partial credit with projects.

Do the right thing, even if it comes at your expense.

And be your best self.  Isn’t that what you do best?

Image credit — Tambako The Jaguar

What do you say when someone in power over you asks you to do something that violates your ethics?  Do you say yes because you know it’s that’s what they want and avoid conflict? Or do you say no because it’s unethical from your perspective?  Seems like a no-brainer, right?  A hard no, 100%.  And maybe with a violation of your ethics, it is a 100% no.  But practically, I can imagine a situation where the consequences would be dire if you lost a steady paycheck, for example, you would not be able to care for your family. Is a no to power also a no to your family?  Can you say no to power and yes to your family?

What do you say when someone with power over you asks you to do something you think is bad for the business? This one is a little tougher.  What does a yes say yes to?  Does it say you are willing to do something you think is bad for business? Does it say the person with power has better judgment? What does a yes say no to?  Does it say no to your judgment?  Does it say no to your self-worth?  What would you say no to?

What do you say when someone with power over you wants to drastically expand your responsibility without a change in compensation, authority, or title?  Is this an offer you cannot refuse?  A yes can be a yes to a desire to climb the ladder, to learn and grow, or to work more for the same pay.  A no can be a no the demotion masquerading as a promotion, to increased stress, to decreased mental and physical health, and to career growth at the company.  What would you say no to?

These contrived scenarios were created to help me talk through this yes-no business.  Any company that used the “power over” approach would drive away its best people.  I created them to make three points. Firstly, a yes to one thing is also a no to other things.  Secondly, it can be difficult to know what you are saying yes to and no to.  Thirdly, saying no can be difficult.

If you want to understand someone, watch what they say no to.

Image credit — Kjetil Rimolsrønning

Tell me what you want done, but don’t tell me how. You’ve got to leave something for me.

Better yet, ask me to help you with a problem and let me solve it.  I prefer asking over telling.

Better still, explain the situation and ask me what I think.  We can then discuss why I see it the way I do and we can create an approach.

Even better, ask me to assess the situation and create a proposal.

Better still, ask me to assess the situation, create a project plan, and run the project.

If you come up with a solution but no definition of the problem, I will ask you to define the problem.

If you come up with a solution and a definition of the problem, I will ask you to explain why it’s the right solution.

If you come up with a problem, a solution, and an analysis that justifies the solution, I will ask why you need me.

If you know what you want to do, don’t withhold information and make me guess.

If you know what you want to do, ask me to help and I will help you with your plan.

If you know what you want to do and want to improve your plan, ask me how to make your plan better.

If you want your plan to become our plan, bring me in from the start and ask me what I think we should do.

Image credit — x1klima

Demoing something for the first time is difficult, but doing it for the second time is easy.  And when you demo a new solution the first time, it (and you) will be misunderstood.

What is the value of this new thing?  This is a good question because it makes clear they don’t understand it. After all, they’ve never seen it before.  And it’s even better when they don’t know what to call it. Keep going!

Why did you do this?  This is a good question because it makes clear they see the demo as a deviation from historically significant lines of success.  And since the lines of success are long in the tooth, it’s good they see it as a violation of what worked in the olden days.  Keep going!

Whose idea was this? This is code: “This crazy thing is a waste of time and we could have applied resources to that tired old recipe we’ve been flogging for a decade now.”  It means they recognize the prototype will be received differently by the customer.  They don’t think it will be received well, but they know the customer will think it’s different.  Keep going!

Who approved this work? This is code: “I want to make this go away and I hope my boss’s boss doesn’t know about it so I can scuttle the project.”  But not to worry because the demo is so good it cannot be dismissed, ignored, or scuttled. Keep going!

Can you do another demo for my boss?  This one’s easy.  They like it and want to increase the chances they’ll be able to work on it.  That’s a nice change!

Why didn’t you do this, that, or the other? They recognized the significance, they understood the limitations, and they asked a question about how to make it better. Things are looking up!

How much did the hardware cost? They see the new customer value and want to understand if the cost is low enough to commercialize with a good profit margin.  There’s no stopping this thing!

Can we take it to the next tradeshow and show it to customers?  Success!

Image credit — Bennilover

It’s fine if you’re asked to do too much occasionally.  Things come up and must be addressed.  Sometimes it’s your turn and sometimes it’s others’ turn.  No one can argue with that.  And sometimes the work demands your special skills and you go the extra because the work is important and urgent.  You know how to do it and there’s no time to bring someone else up to speed.  That makes sense to everyone.  We all know sometimes is our turn to take on too much.  That’s just how it is.  But it’s not sustainable (or fair) when doing too much once in a while becomes insufficient and you’re expected to do too much all the time.  But this creates a problem.

You want to grow in your career and you want to get ahead.  That’s good.  But when “too much every day” becomes the norm, your desire to climb the ladder makes it difficult to say no to “too much every day.”  Say yes to too much and you’ll earn your stripes.  Say no and your career plateaus. What to do?

I think the only way to beat this double bind is to be happy with your current role, be satisfied with your strong efforts to make meaningful (and reasonable) contributions, and continually grow and develop. I think this recipe will lead to great work and I think doing great work is the best way to battle the double bind.

And when it comes to great work, you are responsible for doing great work and your company is responsible for how they respond.  If you hold onto that, your next steps will be clear.

When you do great work and your company doesn’t notice, their response sends a strong message.  And your next step – do more great work.  Their response will change or you will change companies.

When you do great work, your work gets noticed, and all your company gives you is more work, their response sends a strong message.  And your next step – do more great work but constrain your output to a reasonable level.  Their response will change or you will change companies.

If you do great work, your work gets noticed, and you get a raise, a promotion, a bigger team, responsibility for the most important projects, and the authority to get it all done, your company’s response makes it easy for you to do more great work for them.  And that’s just what you should do.

Keep it simple – when in doubt, do great work.

Image credit — _Veit_

Startups are good at making something work in the lab for the first time. However, startups are not good at moving their one-in-a-row prototypes to the manufacturing floor.  But if startups are to scale, that’s exactly what they must do.  For startups to be successful, they must continually change the design to enable the next level of production volume.

To do that, I propose a 10, 100, 1000 approach.

After the one-in-a-row prototypes, how will you make 10?  Can the crude assembly process produce 10 prototypes?  If so, use the same crude assembly process.  The cost of the prototypes is not a problem at this stage, so there’s no need to change the manufacturing processes to reduce the cost of the components.  And at these low volumes, it’s unlikely the existing assembly process is too labor intensive (you’re only making 10) so there’s likely no need to change the process from a “time to build” perspective. But if the variation generated by the assembly process leads to prototypes that don’t function properly, the variation of the assembly process must be controlled with poke-yoke measures.  Add only the controls you need because that work takes money and time which you don’t have as a startup.  Otherwise, build the next 10 like you built the first one.

After the first 10, how will you make the next 100?  Building 100 units doesn’t sound like a big deal, but 100 is a lot more than 10.  Do you have suppliers who will sell you 100 of each part?  Do you have the factory space to store the raw materials?  Do you have the capability and capacity to inspect the incoming material? Do you have the money to buy all the parts?  If the answer to all these questions is yes, it’s time to ask the difficult questions.

The cost of the units is likely still not a problem because the volumes are still small.  There’s likely no need to change the manufacturing process (e.g., moving from machining to casting) to reduce the cost of the units.  And it’s unlikely the time to build the units is becoming a problem because a super long build time isn’t all that problematic when building 100 units.  So it’s not time to reduce the number of parts in the product (product simplification through part count reduction – aka, Design for Assembly).  But it’s likely time to reduce the variation of the assembly process and eliminate the rework-inspect-test loop that comes when each unit that emerges from the production process is different.  It’s time for assembly instructions, assembly fixtures, dedicated tools at each workstation, measurement tools to inspect the final product, and a group of quality professionals to verify the product is built correctly.

After the first 100, how will you make the next 1000? If you can, avoid changing the design, the manufacturing processes, or the assembly process.  Keep everything the same and build 1000 units just as you built the first 100.  But that’s unlikely because the cost will be too high and the assembly time will be too long. For the most expensive parts, consider changing the manufacturing process to one that can support higher volumes at a lower cost.  You likely will have to buy the parts from another supplier who specializes in the new process and for that, you’ll need a purchasing professional with a quality background.  To reduce build time, do Design for Assembly (DFA) to eliminate parts (fasteners and connectors).  And for the processes that generate the highest rework times and scrap, add the necessary process controls to reduce variation and eliminate defects.  Do the minimum (lowest investment dollars and design time) to achieve the appropriate cost and quality levels and declare success.

After 1000 units, it’s time to automate and move to new manufacturing processes.  For the longest assembly processes, change the design (the parts themselves) to enable automated assembly processes. For the highest cost parts, change the parts (the design itself) to enable the move to manufacturing processes with lower cost signatures.  The important idea is that the design and its parts must change to automate and enable lower-cost manufacturing processes.  You’ll need new suppliers and purchasing professionals to bring them on board.  You’ll need quality professionals to verify the quality of the incoming parts and the output of the assembly process.  You’ll need manufacturing and automation engineers to simplify and automate the manufacturing processes.

The 10, 100, 1000 process is rather straightforward but it’s difficult because it requires judgement.  At what production volume do you move to higher volume manufacturing processes to reduce costs?  At what production volumes do you change the design to automate the assembly process to reduce assembly time?  At what point do you add assembly fixtures to reduce variation?  Which assembly processes do you improve and which do you leave as-is?  When do you spend money on improvements and when do you buckle down and grind it out without making improvements?

The answer to all these questions is the same – hire a pro who has done it before.  Hire a pro who knows when (and how) to do Design for Manufacturing and when to keep the design as it is.  Hire a pro who knows when (and how) to add poke-yoke solutions and when to keep the assembly process as it is and rework the defects because that’s the lowest cost and fastest way to go. Hire a pro who knows when to change the design to reduce assembly time (Design for Assembly) and when to change the design and invest in automated assembly.  Hire a pro who knows how (and when) to implement a full-blown quality system.

When it’s time to move from the lab to the factory floor, it’s time to hire a pro.

Image credit — Jim Roberts Gallery

Be successful, but be yourself.

Accept people for who they are and everything else gets better.

Tell the truth, even if it causes stress.  In the short term, it is emotionally challenging but in the long term, it builds trust.

Disagree, yes.  Disappoint, yes.  Disavow, no.

Be effective, but be yourself.

If your actions cause pain, apologize. It’s that simple.

It’s easier to accept others as they are when you can do the same for yourself.

Judging yourself is the opposite of accepting yourself as you are.

When someone needs help, help them.

Be skillful, but be yourself.

If there’s an upside to judging yourself, I don’t know it.

When you’re true to yourself, people can disagree with your position but not your truthfulness.

When you help someone, it’s like helping yourself twice.

There are plenty of people who will judge you.  There’s no need to join that club.

When you stand firmly on emotional bedrock, your perspective is unassailable.

When you’re true to yourself, it’s easier for others to do the same.

Be yourself especially when it’s difficult.  Your courage will empower others.

If there’s no upside to judging yourself, why do it?

Some questions for you:

How would things be different if you stopped judging yourself? Why not give it a try tomorrow?

Wouldn’t you like to be unassailable? Why not stand on your emotional bedrock tomorrow?

Over the next week, how many people will you help?

Over the next week, how many times will you demonstrate courage?

Over the next week, how many times will you be true to yourself, even when it’s difficult?

Image credit – _Veit_