Shipulski On Design

Archive for the ‘Culture’ Category

Here’s what it looks like when the same old tricks no longer carry the day.

Efficiency of effort

• For the same energy, you get more in return.
• For the same energy, you get the same in return.
• For more energy, you get the same in return.
• For more energy, you get less in return.
• Out of energy.

Efficiency of profit

• Increased profit and increased sales.
• Lesser increased profit and unchanged sales.
• Unchanged profit and unchanged sales.
• Decreased profit and unchanged sales.
• Decreased profit and decreased sales.
• No profit and no sales.

Vibrancy

• High-energy citizens with a strong customer focus.
• Medium energy team members with some customer focus.
• Medium-energy people with little customer focus.
• Lethargic nameless humans with no customer focus.
• Nobody home.

Time Horizon

• Long-term purpose, medium-term execution, short-term adaptation.
• Medium-term execution, short-term adaptation.
• Short-term execution, shorter-term bickering.
• Shortest-term floundering.
• Out of time.

Truthfulness

• Truthful communication is delivered clearly and skillfully.
• Truthful communication is delivered less skillfully.
• Partial truths delivered.
• Partial truths delivered unskillfully.
• No truths.

Trust

• Many tight groups of informal networks share information naturally and effectively.
• Informal networks share information naturally.
• Informal networks share information.
• Informal networks go underground to share information.
• Informal networks go underground and band together to protect each other.
• Informal networks give up.

Image credit — philhearing

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

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

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_

We wait because we don’t have enough information to make a decision.

We wait until the decision makes itself because no one wants to be wrong.

We wait for permission because of the negative consequences of being wrong.

We wait to use our judgment until we have evidence our judgment is right.

We wait for support resources because they are spread over too many projects.

We wait for a decision to be made because no one is sure who makes it.

We wait to reduce risk.

We wait to reduce costs.

We wait to move at the speed of trust.

We wait because too many people must agree.

We wait because disagreement comes too slowly.

We wait for disagreement because we don’t subscribe to “clear is kind.”

We wait when decisions are unmade.

We wait because there is insufficient courage to stop the bad projects.

We wait to stop things slowly.

We use waiting as a slow no.

We wait to reallocate resources because even bad projects have momentum.

We wait when we dislike the impending outcome.

We wait for the critical path.

We wait out of fear.

Image credit — Sylvia Sassen

When you catch someone doing good work, do you praise them?  If not, why not?

Praise is best when it’s specific – “I think it was great when you [insert specific action here].”

If praise isn’t authentic, it’s not praise.

When you praise specific behavior, you get more of that great behavior.  Is there a downside here?

As soon as you see praise-worthy behavior, call it by name. Praise best served warm.

Praise the big stuff in a big way.

Praise is especially powerful when delivered in public.

If praise feels good when you get it, why not help someone else feel good and give it?

If you make a special phone call to deliver praise, that’s a big deal.

If you deliver praise that’s inauthentic, don’t.

Praise the small stuff in a small way.

Outsized praise doesn’t hit the mark like the real deal.

There can be too much praise, but why not take that risk?

If praise was free to give, would you give it?  Oh, wait.  Praise is free to give.  So why don’t you give it?

Praise is powerful, but only if you give it.

Image credit — Llima Orosa

If you have nothing to say, be the person that doesn’t say it.

If you’re not the right person to do it, you’re also the right person not to do it.  Why is it so difficult for to stop doing what no longer makes sense?

If it made sense to do it last time, it’s not necessarily the right thing to do this time, even if it was successful last time.  But if it was successful last time, it will be difficult to do something different this time.

If we always standardize on what we did last time, mustn’t this time always be the same as last time? And musn’t next time always be the same as this time?

If it’s new, it’s scary.  And if it’s scary, it’s bad.  And we don’t like to get in trouble for doing bad things. And that’s why it’s difficult to do new things.

Deming said to “Drive out fear.” But that’s scary.  What are the attributes of the people willing to face the fear and demonstrate that fear can be overcome?  At your company are they promoted? Do they stay? Do they leave?

Without someone overcoming their internal fear, there can be no change.

If a new thing is blocked from commercialization because it wasn’t invented here, why not reinvent it just as it is, declare ownership, and commercialize it?

If prevention is worth a pound of cure, why do people that put out forest fires get the credit while those that prevent them go unnoticed? Does that mean your career will benefit it you start small fires in private and put them out quickly for all to see?

If you always do what’s best for your career, that’s not good for your career.

When you do something that’s good for someone’s career but comes at the expense of yours, that’s good for your career.

Why not say nothing when nothing is the right thing to say?

Why not say no when no is the right thing to say?

Why not do something new even though it’s different than what was successful last time?

Why not demonstrate fearlessness and break the trail for others?

Why not be afraid and do it anyway?

Why not build on something developed by another team and give them credit?

Why not do what’s right instead of doing what’s right for your career?

Why not do something for others?  As it turns out, that’s the best thing to do for yourself.

Image credit — Steve Hammond

With projects, there is no partial credit.  They’re done or they’re not.

Solve the toughest problems first.  When do you want to learn the problem is not solvable?

Sometimes slower is faster.

Problems aren’t problems until you realize you have them.  Before that, they’re problematic.

If you can’t put it on one page, you don’t understand it. Or, it’s complex.

Take small bites.  And if that doesn’t work, take smaller bites.

To get more projects done, do fewer of them.

Say no.

Stop starting and start finishing.

Effectiveness over efficiency. It’s no good to do the wrong thing efficiently.

Function first, no exceptions. It doesn’t matter if it’s cheaper to build if it doesn’t work.

No sizzle, no sale.

And customers are the ones who decide if the sizzle is sufficient.

Solve a customer’s problem before solving your own.

Design it, break it, and fix it until you run out of time.  Then launch it.

Make the old one better than the new one.

Test the old one to set the goal. Test the new one the same way to make sure it’s better.

Obsolete your best work before someone else does.

People grow when you create the conditions for their growth.

If you tell people what to do and how to do it, you’ll get to eat your lunch by yourself every day.

Give people the tools, time, training, and a teacher.  And get out of the way.

If you’ve done it before, teach someone else to do it.

Done right, mentoring is good for the mentor, the mentee, and the bottom line.

When in doubt, help people.

Trust is all-powerful.

Whatever business you’re in, you’re in the people business.

Image credit — Hartwig HKD

What does it mean to have enough?

If you don’t want more, doesn’t that mean you have enough?

And if you want what you have, doesn’t that mean you don’t want more?

If you had more, would that make things better?

If you had more, what would stop you from wanting more?

What would it take to be okay with what you have?

If you can’t see what you have and then someone helps you see it, isn’t that like having more?

What do you have that you don’t realize you have?

Do you have a pet?

Do you have the ability to walk?

Do you have friends and family?

Do you have people that rely on you?

Do you have a place where people know you?

Do you have people that care about you?

Do you have a warm jacket and hat?

When you have enough you have the freedom to be yourself.

And when you have enough it’s because you decided you have enough.

Image credit — Irudayam

If you give a person the tools, time, and training, you’ve empowered them.  They know what to do, they have supporting materials, and they have the permission to spend the time they need to get it done.

If you give a person the tools and the time but not the training, they will struggle to figure out the tools but they’ll likely get there in the end.  It won’t be all that efficient, but because you’ve given them the time they’ll be able to figure out the tools and get it done.

If you give a person the time but not the tools or the training, they’ll go on a random walk and make no progress.  Yes, you’ve given them the time, but you’ve given them no real support or guidance.  They’ll likely become tired and frustrated and you’ll have allocated their time yet made no progress.

If you give a person the tools and training but not the time, you’ve demoralized them.  They have new skills and new tools and want to use them, but they’re too busy doing their day job.  This is the opposite of empowerment.

If you’re not willing to give people the time to do new work, don’t bother providing new tools, and don’t bother training them.  Stay the course and accept things as they are.  Otherwise, you’ll disempower your best people.

But if you want to empower people, give them all three – tools, time, and training.

Image credit — Paul Balfe

When planning the projects for next year, how do you decide which projects are a go and which are a no?  One straightforward way is to say yes to projects when there are resources lined up to get them done and no to all others.  Sure, the projects must have a good return on investment but we’re pretty good at that part.  But we’re not good at saying no to projects based on real resource constraints – our people and our budgets.

It’s likely your big projects are well-defined and well-staffed.  The problem with these projects is usually the project timeline is disrespectful of the work content and the timeline is overly optimistic.  If the project timeline is shorter than that of a previously completed project of a similar flavor, with a similar level of novelty and similar resource loading, the timeline is overly optimistic and the project will be late.

Project delays in the big projects block shared resources from moving onto other projects within the appropriate time window which cascades delays into those other projects.  And the project resources themselves must stay on the big projects longer than planned (we knew this would happen even before the project started) which blocks the next project from starting on time and generates a second set of delays that rumble through the project portfolio.  But the big projects aren’t the worst delay-generating culprits.

The corporate initiatives and infrastructure projects are usually well-staffed with centralized resources but these projects require significant work from the business units and is an incremental demand for them.  And the only place the business units can get the resources is to pull them off the (too many) big projects they’ve already committed to.  And remember, the timelines for those projects are overly optimistic.  The big projects that were already late before the corporate initiatives and infrastructure projects are slathered on top of them are now later.

Then there are small projects that don’t look like they’ll take long to complete, but they do.  And though the project plan does not call for support resources (hey, this is a small project you know), support resources are needed.  These small projects drain resources from the big projects and the support resources they need.  Delay on delay on delay.

Coming out of the planning process, all teams are over-booked with too many projects, too few resources, and timelines that are too short. And then the real fun begins.

Over the course of the year, new projects arise and are started even though there are already too few resources to deliver on the existing projects.  Here’s a rule no one follows:  If the teams are fully-loaded, new projects cannot start before old ones finish.

It makes less than no sense to start projects when resources are already triple-double booked on existing projects.  This behavior has all the downside of starting a project (consumption of resources) with none of the upside (progress).  And there’s another significant downside that most don’t see.   The inappropriate “starting” of the new project allows the company to tell itself that progress is being made when it isn’t.  All that happens is existing projects are further starved for resources and the slow pace of progress is slowed further.

It’s bad form to play Tetris with your project portfolio.

Running too many projects in parallel is not faster.  In fact, it’s far slower than matching the projects to the resources on-hand to do them.  It’s essential to keep in mind that there is no partial credit for starting a project.  There is 100% credit for finishing a project and 0% credit for starting and running a project.

With projects, there are two simple rules.  1) Limit the number of projects by the available resources.  2) Finish a project before starting one.

Image credit – gerlos