Posts Tagged ‘Trust-based approach’

When Problems Are Bigger Than They Seem

If words and actions are different, believe the actions.

If the words change over time, don’t put stock in the person delivering them.

If a good friend doesn’t trust someone, neither should you.

If the people above you don’t hold themselves accountable, yet they try to hold you accountable, shame on them.

If people are afraid to report injustices, it’s just a matter of time before the best people leave.

If actions are consistently different than the published values, it’s likely the values should be up-revved.

If you don’t trust your leader, respect your instincts.

If people are bored and their boredom is ignored, expect the company to death spiral into the ground.

If behaviors are different than the culture, the culture isn’t the culture.

If all the people in a group apply for positions outside the group, the group has a problem.

When actions seen by your eyes are different than the rhetoric force-fed into your ears, believe your eyes.

If you think your emotional wellbeing is in jeopardy, it is.

If to preserve your mental health you must hunker down with a trusted friend, find a new place to work.

If people are afraid to report injustices, company leadership has failed.

If the real problems aren’t discussed because they’re too icky, there’s a bigger problem.

If everyone in the group applies for positions outside the group and HR doesn’t intervene, the group isn’t the problem.

And to counter all this nonsense:

If someone needs help, help them.

If someone helps you, thank them.

If someone does a good job, tell them.

Rinse, and repeat.

Without trust, there is nothing.

If someone treats you badly, that’s on them. You did nothing wrong.

When you do your best and your boss tells you otherwise, your boss is unskillful.

If you make a mistake, own it. And if someone gives you crap about it, disown them.

If someone is untruthful, hold them accountable. If they’re still untruthful, double down and hold them accountable times two.

If you’re treated unfairly, it’s because someone has low self-esteem. And if you get mad at them, it’s because you have low self-esteem.

What people think about you is none of your concern, especially if they treat you badly.

If you see something, say something, especially when you see a leader treat their team badly.

A leader that treats you badly isn’t a leader.

If you don’t trust your leader, find a new leader. And if you can’t find a new leader to trust, find a new company.

If someone belittles you, that’s about them. Try to forgive them. And if you can’t, try again.

No one deserves to be treated badly, even if they treat you badly.

If you have high expectations for your leader and they fall short, that says nothing about your expectations.

If someone’s behavior makes you angry, that’s about you. And when your behavior makes someone angry, the calculus is the same.

When actions are different from the words, believe the actions.

When the words are different than the actions, there can be no trust.

The best work is built on trust. And without trust, the work will not be the best.

If you don’t feel comfortable calling people on their behavior it’s because you don’t believe they’ll respond in good faith.

If you don’t think someone is truthful, nothing good will come from working with them.

If you can’t be truthful it’s because there is insufficient trust.

Without trust there is nothing.

If there’s a mismatch between someone’s words and their actions, call them on their actions.

If you call someone on their actions and they use their words to try to justify their actions, run away.

You might be a leader if…

If you have to tell people what to do, you didn’t teach them to think for themselves.

If you know one of your team members has something to say but they don’t say it, it’s because you didn’t create an environment where they feel safe.

If your new hire doesn’t lead an important part of a project within the first week, you did them a disservice.

If the team learns the same thing three times, you should have stepped in two times ago.

If you don’t demand that your team uses their discretion, they won’t.

If the project’s definition of success doesn’t correlate with business success, you should have asked for a better definition of success before the project started.

If someone on your team tells you you’re full of sh*t, thank them for their truthfulness.

If your team asks for permission, change how you lead them.

If you can’t imagine that one of your new hires will be able to do your job in five years, you hired the wrong people.

If your team doesn’t disagree with you, it’s because you haven’t led from your authentic self.

If your team doesn’t believe in themselves, neither do you.

If your team disobeys your direct order, thank them for disobeying and apologize for giving them an order.

If you ask a new hire to lead an important part of a project and you don’t meet with them daily to help them, you did them a disservice.

If one of your team members moves to another team and their new leader calls them “unmanageable”, congratulations.

If your team knows what you’ll say before they ask you, you’ve led them from your authentic self.

If you haven’t chastised your team members for their lack of disagreement with you, you should.

If you don’t tell people they did a good job, they won’t.

Image credit — Hamed Saber

People, Money and Time

If you want the next job, figure out why.
There’s nothing wrong with wanting the job you have.
When you don’t care about the next job it’s because you fit the one you have.

A larger salary is good, but time with family is better.
Less time with family is a downward spiral into sadness.
When you decide you have enough, you don’t need things to be different.

A sense of belonging lasts longer than a big bonus.
A cohesive team is an oasis.
Who you work with makes all the difference.

More stress leads to less sleep and that leads to more stress.
If you’re not sleeping well, something’s wrong.
How much sleep do you get? How do you feel about that?

Leaders lead people.
Helping others grow IS leadership.
Every business is in the people business.

To create trust, treat people like they matter. It’s that simple.
When you do something for someone even though it comes at your own expense, they remember.
You know you’ve earned trust when your authority trumps the org chart.

Image credit — Jimmy Baikovicius

The Difficulty of Commercializing New Concepts

If you have the data that says the market for the new concept is big enough, you waited too long.

If you require the data that verifies the market is big enough before pursuing new concepts, you’ll never pursue them.

If you’re afraid to trust the judgement of your best technologists, you’ll never build the traction needed to launch new concepts.

If you will sell the new concept to the same old customers, don’t bother. You already sold them all the important new concepts. The returns have already diminished.

If you must sell the new concept to new customers, it could create a whole new business for you.

If you ask your successful business units to create and commercialize new concepts, they’ll launch what they did last time and declare it a new concept.

If you leave it to your successful business units to decide if it’s right to commercialize a new concept created by someone else, they won’t.

If a new concept is so significant that it will dwarf the most successful business unit, the most successful business unit will scuttle it.

If the new concept is so significant it warrants a whole new business unit, you won’t make the investment because the sales of the yet-to-be-launched concept are yet to be realized.

If you can’t justify the investment to commercialize a new concept because there are no sales of the yet-to-be-launched concept, you don’t understand that sales come only after you launch. But, you’re not alone.

If a new concept makes perfect sense, you would have commercialized it years ago.

If the new concept isn’t ridiculed by the Status Quo, do something else.

If the new concept hasn’t failed three times, it’s not a worthwhile concept.

If you think the new concept will be used as you intend, think again.

If you’re sure a new concept will be a flop, you shouldn’t be. Same goes for the ones you’re sure will be successful.

If you’re afraid to trust your judgement, you aren’t the right person to commercialize new concepts.

And if you’re not willing to put your reputation on the line, let someone else commercialize the new concept.

Image credit – Melissa O’Donohue

As a leader, be truthful and forthcoming.

144 Truthful, at Ping Sien Si, Pasir Panjang, Perak, Malaysia

Have you ever felt like you weren’t getting the truth from your leader? You know – when they say something and you know that’s not what they really think. Or, when they share their truth but you can sense that they’re sharing only part of the truth and withholding the real nugget of the truth? We really have no control over the level of forthcoming of our leaders, but we do have control over how we respond to their incomplete disclosure.

There are times when leaders cannot, by law, disclose things. But, even then, they can make things clear without disclosing what legally cannot be disclosed. For example, they can say: “That’s a good question and it gets to the heart of the situation. But, by law, I cannot answer that question.” They did not answer the question, but they did. They let you know that you understand the situation; they let you know that there is an answer; and the let you know why they cannot share it with you.  As the recipient of that non-answer answer, I respect that leader.

There are also times when a leader withholds information or gives a strategically partial response for inappropriate reasons. When a leader withholds information to manipulate or control, that’s inappropriate. It’s also bad leadership. When a leader withholds information from their smartest team members, they lose trust.  And when leaders lose trust, the best people are crestfallen and withhold their best work. The thinking goes like this. If my leader doesn’t trust me enough to share the complete set of information with me it’s because they don’t think I’m worthy of their trust and they don’t think highly of me.  And if they don’t think I’m worthy of their trust, they don’t understand who I am and what I stand for.  And if they don’t understand me and know what I stand for, they’re not worthy of my best work.

As a leader, you must share all you can.  And when you can’t, you must tell your team there are things you can’t share and tell them the reasons why. Your team can handle the fact that there are some things you cannot share. But what your team cannot hand is when you withhold information so you can gain the upper hand on them. And your team can tell when you’re withholding with your best interest in mind. Remember, you hired them because they were smart, and their smartness doesn’t go away just because you want to control them.

If your direct reports always tell you they can get it done even when they don’t have the capacity and capability, that’s not the behavior you want. If your direct reports tell you they can’t get it done when they can’t get it done, that’s the behavior you want. But, as a leader, which behavior do you reward? Do you thank the truthful leader for being truthful about the reality of insufficient resources and do you chastise the other leader for telling you what you want to hear? Or, do you tell the truthful leader they’re not a team player because team players get it done and praise the unjustified can-do attitude of the “yes man” leader? As a leader, I suggest you think deeply about this. As a direct report of a leader, I can tell you I’ve been punished for responding in way that was in line with the reality of the resources available to do the work. And I can also tell you that I lost all respect for that leader.

As a leader, you have three types of direct reports. Type I are folks are happy where they are and will do as little as possible to keep it that way. Type II are people that are striving for the next promotion and will tell you whatever you want to hear in order to get the next job. Type III are the non-striving people who will tell you what you need to hear despite the implications to their career. Type I people are good to have on your team.  They know what they can do and will tell you when the work is beyond their capability. Type II people are dangerous because they think only of themselves. They will hang you out to dry if they think it will advance their career. And Type III people are priceless.

Type III people care enough to protect you.  When you ask them for something that can’t be done, they care enough about you to tell you the truth. It’s not that they don’t want to get it done, they know they cannot. And they’re willing to tell you to your face. Type II people don’t care about you as a leader; they only care about themselves. They say yes when they know the answer is no. And they do it in a way that absolves them of responsibility when the wheels fall off. As a leader, which type do you want on your team? And as a leader, which type do you promote and which do you chastise. And, how do you feel about that?

As a leader, you must be truthful. And when you can’t disclose the full truth, tell people. And when your Type II direct reports give you the answer they know you want to hear, call them on their bullshit.  And when your Type III folks give you the answer they know you don’t want to hear, thank them.

Image credit — Anandajoti Bhikkhu

Seeing Things as They Can’t Be

When there’s a big problem, the first step is to define what’s causing it. To do that, based on an understanding of the physics, a sequence of events is proposed and then tested to see if it replicates the problem. In that way, the team must understand the system as it is before the problem can be solved.

Seeing things as they are. The same logic applies when it’s time to improve an existing product or service. The first thing to do is to see the system as it is. But seeing things as they are is difficult. We have a tendency to see things as we want them or to see them in ways that make us look good (or smart). Or, we see them in a way that justifies the improvements we already know we want to make.

To battle our biases and see things as they are, we use tools such as block diagrams to define the system as it is. The most important element of the block diagram is clarity.  The first revision will be incorrect, but it must be clear and explicit. It must describe things in a way that creates a singular understanding of the system. The best block diagrams can be interpreted only one way.  More strongly, if there’s ambiguity or lack of clarity, the thing has not yet risen to the level of a block diagram.

The block diagram evolves as the team converges on a single understanding of things as they are. And with a diagram of things as they are, a solution is readily defined and validated. If when tested the proposed solution makes the problem go away, it’s inferred that the team sees things as they are and the solution takes advantage of that understanding to make the problem go away.

Seeing things as they may be. Even whey the solution fixes the problem, the team really doesn’t know if they see things as they are. Really, all they know is they see things as they may be. Sure, the solution makes the problem go away, but it’s impossible to really know if the solution captures the physics of failure.  When the system is large and has a lot of moving parts, the team cannot see things as they are, rather, they can only see the system as it may be. This is especially true if the system involves people, as people behave differently based on how they feel and what happened to them yesterday.

There’s inherent uncertainty when working with larger systems and systems that involve people.  It’s not insurmountable, but you’ve got to acknowledge that your understanding of the system is less than perfect. If your company is used to solving small problems within small systems, there will be little tolerance for the inherent uncertainty and associated unpredictability (in time) of a solution.  To help your company make the transition, replace the language of “seeing things as they are” with “seeing things as they may be.”  The same diagnostic process applies, but since the understanding of the system is incomplete or wrong, the proposed solutions cannot not be pre-judged as “this will work” and “that won’t work.”  You’ve got to be open to all potential solutions that don’t contradict the system as it may be. And you’ve got to be tolerant of the inherent unpredictability of the effort as a whole.

Seeing things as they could be. To create something that doesn’t yet exist, something does things like never before, something altogether new, you’ve got to stand on top of your understanding of the system and jump off.  Whether you see things as they are or as they may be, the new system will be different. It’s not about diagnosing the existing system; it’s about imagining the system as it could be. And there’s a paradox here. The better you understand the existing system, the more difficulty you’ll have imagining the new one. And, the more success the company has had with the system as it is, the more resistance you’ll feel when you try to make the system something it could be.

Seeing things as they could be takes courage – courage to obsolete your best work and courage to divest from success. The first one must be overcome first. Your body creates stress around the notion of making yourself look bad. If you can create something altogether better, why didn’t you do it last time? There’s a hit to the ego around making your best work look like it’s not all that good. But once you get over all that, you’ve earned the right to go to battle with your organization who is afraid to move away from the recipe responsible for all the profits generated over the last decade.

But don’t look at those fears as bad. Rather, look at them as indicators you’re working on something that could make a real difference.  Your ego recognizes you’re working on something better and it sends fear into your veins. The organization recognizes you’re working on something that threatens the status quo and it does what it can to make you stop. You’re onto something. Keep going.

Seeing things as they can’t be. This is rarified air. In this domain you must violate first principles. In this domain you’ve got to run experiments that everyone thinks are unreasonable, if not ill-informed. You must do the opposite. If your product is fast, your prototype must be the slowest. If the existing one is the heaviest, you must make the lightest. If your reputation is based on the highest functioning products, the new offering must do far less.  If your offering requires trained operators, the new one must prevent operator involvement.

If your most seasoned Principal Engineer thinks it’s a good idea, you’re doing it wrong. You’ve got to propose an idea that makes the most experienced people throw something at you. You’ve got to suggest something so crazy they start foaming at the mouth. Your concepts must rip out their fillings. Where “seeing things as they could be” creates some organizational stress, “seeing things as they can’t be” creates earthquakes. If you’re not prepared to be fired, this is not the domain for you.

All four of these domains are valuable and have merit. And we need them all. If there’s one message it’s be clear which domain you’re working in. And if there’s a second message it’s explain to company leadership which domain you’re working in and set expectations on the level of uncertainty and unpredictability of that domain.

Image credit – David Blackwell.

Innovation isn’t uncertain, it’s unknowable.

Where’s the Marketing Brief? In product development, the Marketing team creates a document that defines who will buy the new product (the customer), what needs are satisfied by the new product and how the customer will use the new product.  And Marketing team also uses their crystal ball to estimate the number of units the customers will buy, when they’ll buy it and how much they’ll pay.  In theory, the Marketing Brief is finalized before the engineers start their work.

With innovation, there can be no Marketing Brief because there are no customers, no product and no technology to underpin it.  And the needs the innovation will satisfy are unknowable because customers have not asked for the them, nor can the customer understand the innovation if you showed it to them.  And how the customers will use the? That’s unknowable because, again, there are no customers and no customer needs. And how many will you sell and the sales price? Again, unknowable.

Where’s the Specification? In product development, the Marketing Brief is translated into a Specification that defines what the product must do and how much it will cost.  To define what the product must do, the Specification defines a set of test protocols and their measurable results.  And the minimum performance is defined as a percentage improvement over the test results of the existing product.

With innovation, there can be no Specification because there are no customers, no product, no technology and no business model. In that way, there can be no known test protocols and the minimum performance criteria are unknowable.

Where’s the Schedule? In product development, the tasks are defined, their sequence is defined and their completion dates are defined. Because the work has been done before, the schedule is a lot like the last one.  Everyone knows the drill because they’ve done it before.

With innovation, there can be no schedule.  The first task can be defined, but the second cannot because the second depends on the outcome of the first. If the first experiment is successful, the second step builds on the first. But if the first experiment is unsuccessful, the second must start from scratch. And if the customer likes the first prototype, the next step is clear. But if they don’t, it’s back to the drawing board.  And the experiments feed the customer learning and the customer learning shapes the experiments.

Innovation is different than product development. And success in product development may work against you in innovation. If you’re doing innovation and you find yourself trying to lock things down, you may be misapplying your product development expertise. If you’re doing innovation and you find yourself trying to write a specification, you may be misapplying your product development expertise. And if you are doing innovation and find yourself trying to nail down a completion date, you are definitely misapplying your product development expertise.

With innovation, people say the work is uncertain, but to me that’s not the right word.  To me, the work is unknowable. The customer is unknowable because the work hasn’t been done before.  The specification is unknowable because there is nothing for comparison. And the schedule in unknowable because, again, the work hasn’t been done before.

To set expectations appropriately, say the innovation work is unknowable. You’ll likely get into a heated discuss with those who want demand a Marketing Brief, Specification and Schedule, but you’ll make the point that with innovation, the rules of product development don’t apply.

Image credit — Fatih Tuluk

The Trust Network II

I stand by my statement that trust is the most important element in business (see The Trust Network.)

The Trust Network are the group of people who get the work done. They don’t do the work to get promoted, they just do the work because they like doing the work. They don’t take others’ credit (they’re not striving,) they just do the work. And they help each other do the work because, well, it’s the right thing to do.

Sometimes, they use their judgement to protect the company from bad ideas. But to be clear, they don’t protect the Status Quo. They use their good judgement to decide if a new idea has merit, and if it doesn’t, they try to shape it. And if they can’t shape it, they block it.  Their judgement is good because their mutual trust allows them to talk openly and honestly and listen to each other. And through the process, they come to a decision and act on it.

But there’s another side to the Trust Network.  They also bring new ideas to the company.

Trying new things is scary, but the Trust Network makes it safe. When someone has a good idea, the Network positively reinforces the goodness of the idea and recommends a small experiment. And when one installment of positivity doesn’t carry the day, the Trust Network comes together to create the additional positivity need to grow the idea into an experiment.

To make it safe, the Trust Network knows to keep the experiment small.  If the small experiment doesn’t go as planned, they know there will be no negative consequences. And if the experiment’s results do attract attention, they dismiss the negativity of failure and talk about the positivity of learning. And if there is no money to run the experiment, they scare it up. They don’t stop until the experiment is completed.

But the real power of the Trust Network shows its hand after the successful experiment. The toughest part of innovation is the “now what” part, where successful experiments go to die. Since no one thought through what must happen to convert the successful experiment to a successful product, the follow-on actions are undefined and unbudgeted and the validated idea dies. But the Trust Network knows all this, so they help the experimenter define the “then what” activities before the experiment is run.  That way, the resources are ready and waiting when the experiment is a success.  The follow-on activities happen as planned.

The Trust Network always reminds each other that doing new things is difficult and that it’s okay that the outcome of the experiment is unknown. In fact, they go further and tell each other that the outcome of the experiment is unknowable. Regardless of the outcome of the experiment, the Trust Network is there for each other.

To start a Trust Network, find someone you trust and trust them. Support their new ideas, support their experiments and support the follow-on actions.  If they’re afraid, tell them to be afraid and run the experiment. If they don’t have the resources to run the experiment, find the resources for them. And if they’re afraid they won’t get credit for all the success, tell them to trust you.

And to grow your Trust Network, find someone else you trust and trust them. And, repeat.

Image credit — Rolf Dietrich Brecher

As a leader, your response is your responsibility.

When you’re asked to do more work that you and your team can handle, don’t pass it onto your team.  Instead, take the heat from above but limit the team’s work to a reasonable level.

When the number of projects is larger than the budget needed to get them done, limit the projects based on the budget.

When the team knows you’re wrong, tell them they’re right. And apologize.

When everyone knows there’s a big problem and you’re the only one that can fix it, fix the big problem.

When the team’s opinion is different than yours, respect the team’s opinion.

When you make a mistake, own it.

When you’re told to do turn-the-crank work and only turn-the-crank work, sneak in a little sizzle to keep your team excited and engaged.

When it’s suggested that your team must do another project while they are fully engaged in an active project, create a big problem with the active project to delay the other project.

When the project is going poorly, be forthcoming with the team.

When you fail to do what you say, apologize.  Then, do what you said you’d do.

When you make a mistake in judgement which creates a big problem, explain your mistake to the team and ask them for help.

If you’ve got to clean up a mess, tell your team you need their help to clean up the mess.

When there’s a difficult message to deliver, deliver it face-to-face and in private.

When your team challenges your thinking, thank them.

When your team tells you the project will take longer than you want, believe them.

When the team asks for guidance, give them what you can and when you don’t know, tell them.

As leaders, we don’t always get things right.  And that’s okay because mistakes are a normal part of our work.  And projects don’t always go as planned, but that’s okay because that’s what projects do. And we don’t always have the answers, but that’s okay because we’re not supposed to. But we are responsible for our response to these situations.

When mistakes happen, good leaders own them. When there’s too much work and too little time, good leaders tell it like it is and put together a realistic plan. And when the answers aren’t known, a good leader admits they don’t know and leads the effort to figure it out.

None of us get it right 100% of the time. But what we must get right is our response to difficult situations.  As leaders, our responses should be based on honesty, integrity, respect for the reality of the situation and respect for people doing the work.

Image credit – Ludovic Tristan

Subtle Leadership

You could be a subtle leader if…

You create the causes and conditions for others to shine. And when they shine, you give them the credit they’re due.

You don’t have the title, but when the high-profile project hits a rough patch, you get called in to create the go-forward plan.

One of your best direct reports gets promoted out from under you, but she still wants to meet with you weekly.

When you see someone take initiative, you tell them you like their behavior.

You get to choose the things you work on.

You can ask most anyone for a favor and they’ll do it, just because it’s you. But, because you don’t like to put people out, you rarely ask.

When someone does a good job, you send their boss a nice email and cc: them.

When it’s time to make a big decision, even though it’s outside your formal jurisdiction, you have a seat at the table.

When people don’t want to hear the truth, they don’t invite you to the meeting.

You are given the time to think things through, even when it takes you a long time.

Your young boss trusts you enough to ask for advice, even when she knows she should know.

In a group discussion, you wait for everyone else to have input before weighing in. And, if there’s no need to weigh in, you don’t.

When you see someone make a mistake, you ignore it if you can. And if you can’t, you talk to them in private.

Subtle leaders show themselves in subtle ways but their ways are powerful. Often, you see only the results of their behaviors and those career-boosting results are mapped to someone else. But if you’ve been the recipient of subtle leadership, you know what I’m talking about. You didn’t know you needed help, but you were helped just the same. And you were helped in a way that was invisible to others. And though you didn’t know to ask for advice, you were given the right suggestion at the right time. And you didn’t realize it was the perfect piece of advice until three weeks later.

Subtle leaders are difficult to spot. But once you know how they go about their business and how the company treats them, you can see them for what they are. And once you recognize a subtle leader, figure out a way to spend time with them.  Your career will be better for it.

Image credit – rawdonfox

 

Mike Shipulski Mike Shipulski
Subscribe via Email

Enter your email address:

Delivered by FeedBurner

Archives