Shipulski On Design

Posts Tagged ‘Trust-based approach’

For the past two decades, I’ve actively developed engineering leaders.  A good friend asked me how I do it, so I took some time to write it down.  Here is the curriculum in the form of How Tos:

How to build trust.  This is the first thing.  Always.  Done right, the trust-based informal networks are stronger than the formal organization chart. Done right, the informal networks can protect the company from bad decisions.  Done right, the right information flows among the right engineers at the right time so the right work happens in the right way.

How to decide what to do next. This is a broad one.  We start with a series of questions: What are we doing now?  What’s the problem? How do you know? What should we do more of?  What should we do less of?  What resources are available? When must we be done?

How to map the current state.  We don’t define the idealized future state or the North Star, we start with what’s happening now.  We make one-page maps of the territory.  We use drawings, flow charts, boxes/arrows, and the fewest words. And we take no action before there’s agreement on how things are.  The value of GPS isn’t to define your destination, it’s to establish your location.  That’s why we map the current state.

How to build momentum. It’s easy to jump onto a moving steam train, but a stationary one is difficult to get moving.  We define the active projects and ask – How might we hitch our wagon to a fast-moving train?

How to start something new. We start small and make a thought-provoking demo.  The prototype forces us to think through all the elements, makes things real, and helps others understand the concept. If that doesn’t work, we start smaller.

How to define problems so we can solve them easily. We define problems with blocks and arrows, and limit ourselves to one page.  The problem is defined as a region of contact between two things, and we identify it with the color red.  That helps us know where the problem is and when it occurs. If there are two problems on a page, we break it up into two pages with one problem.  Then we decide to solve the problem before, during, or after it occurs.

How to design products that work better and cost less. We create Pareto charts of the cost of the existing product (cost by subassembly and cost by part) and set a cost reduction goal.  We create Pareto charts of the part count of the existing product (part count by subassembly and part count by individual part number) and define a goal for part count reduction.  We define test protocols that capture the functionality customers care about. We test the existing product and set performance improvement goals for the new one.  We test the new product using the same protocols and show the data in a simple A-B format. We present all this data at formal design reviews.

How to define technology projects. We define how the customer does their work.  We then define the evolutionary history of our products and services, and project that history forward.  For lines of goodness with trajectories that predict improvement, we run projects to improve them.  For lines of goodness with stalled trajectories, we run projects to establish new technologies and jump to the next S-curve.  We assess our offerings for completeness and create technologies to fill the gap.

How to file the right patents.  We ask these questions: How quickly will the customer notice the new functionality or benefit? Once recognized, will they care? Will the patent protect high-volume / high-margin consumables? There are more questions, but these are the ones we start with.  And the patent team is an integral part of the technology reviews and product development process.

How to do the learning.   We start with the leader’s existing goals and deliverables and identify the necessary How Tos to get their work done. There are no special projects or extra work.

If you’re interested in learning more about the curriculum or how to enroll, send me an email mike@shipulski.com.

Image credit — Paul VanDerWerf

It doesn’t take much to make a difference, but if you don’t recognize the need to make one, you won’t make one.

When you’re in a meeting, watch and listen. If someone is quiet, ask them a question. My favorite is “What do you think?” Your question says you value them and their thinking, and that makes a difference. Others will recognize the difference you made, and that may inspire them to make a similar difference at their next meeting.

When you see a friend in the hallway, look them in the eyes, smile, and ask them what they’re up to.  Listen to their words but more importantly watch their body language.  If you recognize they are energetic, acknowledge their energy, ask what’s fueling them, and listen.  Ask more questions to let them know you care.  That will make a difference.  If you recognize they have low energy, tell them, and then ask what that’s all about.  Try to understand what’s going on for them.  You don’t have to fix anything to make a difference, you have to invest in the conversation.  They’ll recognize your genuine interest and that will make a difference.

If you remember someone is going through something, send them a simple text –  “I’m thinking of you.”  That’s it.  Just say that.  They’ll know you remembered their situation and that you care.  And that will make a difference.  Again, you don’t have to fix anything.  You just have to send the text.

Check in with a friend.  That will make a difference.

When you learn someone got a promotion, send them a quick note.  Sooner is better, but either way, you’ll make a difference.

Ask someone if they need help.  Even if they say no, you’ve made a difference.  And if they say yes, help them.  That will make a big difference.

And here’s a little different spin.  If you need help, ask for it.  Tell them why you need it and explain why you asked them.  You’ll demonstrate vulnerability and they’ll recognize you trust them.  Difference made.  And your request for help will signal that you think they’re capable and caring.  Another difference made.

It doesn’t take much to make a difference.  Pay attention and take action and you’ll make a difference.  But really, you’ll make two differences. You’ll make a difference for them and you’ll make a difference for yourself.

Image credit — Geoff Henson

Holidays aren’t about shopping, gifts, special dinners, or travel.  Holidays are about family.

On holidays, people travel.  They don’t travel to tourist sites, national parks, or big cities for big cities’ stake.  People travel to see their families.

On holidays, people eat special foods prepared in special ways and served on special plates.  But that’s not special.  Family prepares the food, family sits at the table, and family eats the food.  What’s special is family.

Oh holidays, people tell the same stories of old shared experiences.  Everyone knows all the stories, but they’re still told every year.  Sure, the stories are misremembered, but the storyline holds. The family’s shared experiences are reexperienced and relationships deepen.  Family is special because it helps us remember and grounds us.

On holidays, people don’t always get along.  Some of the same arguments arise and some new ones are born.  Tempers flare and then cool. Because of the significant body of shared experiences and shared memories, there are more opportunities to disagree.  And because family creates a safe space, sharing strong feelings is okay.  It’s easy to see (and hear) the arguments and it isn’t easy to see what makes them possible – shared context, shared memories, and a safe space built on trust.   Without these regular arguments cannot rise to the level of family arguments.  Family arguments are a higher genus of arguments; they are noble arguments. Family arguments can realized only by families.

I hope you can spend the holidays with your family.  If not, I hope you can have a great video call with them, have a meaningful phone call with them, or even a funny text exchange.  And if you can’t, I hope you can spend time with good friends who are like family.

Image credit – Craig Sefton

Be bold – the alternative is boring.

Be the first to forgive – it’s like forgiving twice.

Be yourself – you’re the best at that.

Be afraid – and do it anyway.

Be effective – and to hell with efficiency.

Be happy – if that’s what’s inside.

Be authentic – it’s invigorating.

Be energetic – it’s contagious.

Be a listener – that’s where learning comes from.

Be on time – it says you care.

Be early if you can’t be on time – but just a little.

Be courageous – but sparingly.

Be kind – people remember.

Be truthful – that’s how trust is built.

Be a learner – by learning to listen.

Be sad – if that’s what’s inside.

Be a friend – it’s good for them and better for you.

Be nobody – it’s better for everybody, even you.

Image credit — Irene Steeves

Here are the questions I ask myself when I’m asked to take on new work….

Do I know what the work is all about?

Is it well-defined?

Would it make a big difference if the work is completed successfully?

Would it make a big difference if it’s not?

Is it clear how to judge if the work is completed successfully?

Is the work important and how do I know?

Is it urgent? (The previous question is far more important to me.)

Is there more important work?

Who would benefit from the work and how do I feel about it?

Would I benefit and how do I feel about it?

Am I uniquely qualified or can others do the work?

Am I interested in the work?

Would I grow from the work?

Who would I work for?

Who would I work with?

Would my career progress?

Would I get a raise?

Would I spend more time with my family?

Would I spend more time in meetings?

Would I travel more?

What does my Trust Network think?

Would I have fun? (I think this is a powerful question.)

These aren’t the questions you should ask yourself, but I hope the list helps you develop your own.

Image credit — broombesoom

If you want people to work together, give them a reason.  Tell them why it’s important to the company and their careers.

If you want people to change things, change how they interact.  Eliminate leaders from some, or all, of the meetings.  Demand they set the approach. Give them control over their destiny. Make them accountable to themselves.  Give them what they ask for.

If you want to create a community, let something bad happen.  The right people will step up and the experts will band together around the common cause.  And after they put the train back on the track, they’ll be ready and willing for a larger challenge.

If you want the team to make progress, make it easy for them to make progress.  Stop the lesser projects so they can focus.  Cancel meetings so they can focus. Give them clear guidance so they can focus on the right work.  Give them the tools, time, training, and a teacher.  Ask them how to make their work easier and listen.

If you want the team to finish projects faster, ask them to focus on effectiveness at the expense of efficiency.

If you want the organization to be more flexible, create the causes and conditions for trust-based relationships to develop.  When people work shoulder-to-shoulder on a difficult project trust is created.  And for the remainder of their careers, they will help each other.  They will help each other despite the formal organizational structure.  They will help each other despite their formal commitments.  They will help each other despite the official priorities.

If you want things to change, don’t try to change people.  Move things out of the way so they can make it happen.

Image credit — frank carman

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

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

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_

Credibility built – when the situation is not good, you say “the situation is not good.”  And when things went poorly you say “things went poorly.”

Trust built – when things go well you give away the credit.

Credibility built – when you provide a controversial perspective and three years later it turns out you were right.

Trust built – when you share your frustrations in confidence.

Credibility built – when you ground your argument in facts, especially inconvenient ones.

Trust built – when you say “I will keep that in confidence” and you do.

Credibility built – when you don’t know, you say “I don’t know.”

Trust built – when you do something that benefits others but comes at your own expense.

Credibility destroyed – when you tell people things are one way when they know it’s the other.

Trust destroyed – when you respond from a hardened heart.

Credibility destroyed – when you tell partial truths.

Trust destroyed – when you avoid doing the right thing.

Credibility and trust are a powerful one-two punch, but only if you build them.

Image credit — _Veit_

Strivers do what’s best for them.

Thrivers do what’s right.

Strivers want more.

Thrivers want what they have.

Strivers can’t push back on people that are higher on the org chart or disagree with them.

Thrivers push back and disagree regardless of the org chart.

Strivers trade promotions for family.

Thrivers put family first – no exceptions.

Strivers are less than forthcoming to avoid conflict.

Thrivers put it straight over the plate to create the right conflict.

Strivers get led around by the nose.

Thrivers will punch you in the nose when you deserve it.

Strivers don’t have time for trust.

Thrivers put trust ahead of all things.

Strivers do the wrong things that come at your expense.

Thrivers do the right things that come at their expense.

Strivers step on your head.

Thrivers put you on their shoulders.

Strivers create headwinds to slow their peers.

Thrivers create tailwinds for all.

Strivers are afraid of thrivers because they cannot manipulate thrivers.

Thrivers don’t like strivers because they manipulate.

Strivers use the formal organizational structure to exert power.

Thrivers use their informal networks to make the right things happen.

Strivers blame.

Thrivers make it right.

Strivers are forgotten.

Thrivers are remembered.

Will you be forgotten or remembered?