Shipulski On Design

Posts Tagged ‘Lessons Learned’

When things don’t go as planned, recognize the Universe doesn’t care about your plan.

When the going gets tough, the Universe is telling you something.  You just don’t know what it’s telling you.

When in doubt, do the next right thing.  That’s how the Universe rolls.

If you don’t like how it’s going, change your situation or change your expectations. Those are the two options sanctioned by the Universe.

If something bad happens, don’t take it personally. The Universe doesn’t know your name.

If you catch yourself taking your plan seriously, don’t. The Universe frowns on seriousness.

Don’t spend time creating a grand plan.  The Universe isn’t big on grand plans.

If your plan requires the tide to stay away, make a different one. The Universe never forgets to tell the tide to come in.

If you find yourself chasing the Idealized Future State, stop.  The Universe has disdain for the ideal.

If something good happens, don’t take it personally. The Universe doesn’t know your name.

When you don’t know the answer, that’s the Universe telling you you may be onto something.

When you have all the right answers, that’s the Universe telling you you’re not asking the right questions.

Image credit — Giuseppe Donatiello

COPYRIGHT GEOFF HENSON

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

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

If you’ve done it before, do it in a tenth of the time.

Do it differently just because you can.

Do it backward. That will make you smile.

Do it with your eyes closed.  That will make a statement.

Do its natural extension. That could be fun.

Do the opposite.  Then do its opposite.  You’ll learn more.

Do what they should have asked for. Life is short.

Do what scares them. It’s sure to create new design space.

Do what obsoletes your most profitable offering. Wouldn’t you rather be the one to do it?

Do what scares you.  That’s sure to be the most interesting of all.

Image credit — Geoff Henson

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

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_

Do the project right or do the right project – which would you choose?

If you improve time to market, the only thing that improves is time to market.  How do you feel about that?

Customers pay for things that make their lives easier.  Time to market doesn’t do that.

There’s no partial credit with new product development projects.  If the product isn’t 100% ready for sale, it’s 0% ready.

If you made 1/8^th progress on 8 projects, you made zero progress. But you did consume valuable resources.

If you made 100% progress on one project, you made progress.

When you have too many projects, you get too few done.

If you don’t know how many projects your company has, you have too many.

Would you rather choose the right project and run it inefficiently or choose the wrong project and run it efficiently?

When you choose the wrong project but run it efficiently, that’s called efficient ineffectiveness.

You can save several weeks making sure you choose the right project by starting the project too soon and running the wrong one for two years.

If your projects are slow, it’s likely the support functions are too highly utilized.  Add capacity to keep their peak utilization below 85%.

When shared resources are sized appropriately, they’re underutilized most of the time.  Think fire station and firefighters – when there’s a fire they respond quickly, and when there’s no fire they improve their skills so they can fight the next one better than the last.

If your projects are slow, check to see if you have resources on the critical path that work part-time.  Part-time resources support multiple projects and don’t work full-time on your project.  And you can’t control when they work on your project.  There’s no place for that on the critical path.

If you’re thinking about using part-time resources on the critical path, don’t.

Know where the novelty is and work that first.  And before you can work on the novelty you’ve got to know where it is.

You can have too little novelty, meaning the new product is so much like the old one there’s no need to launch it.  Mostly, though, projects have too much novelty.

If you are working on a clean-sheet design, there is no such thing.  There are no green-field projects.  All projects are brown-field projects. It’s just that some are browner than others.

Novelty generates problems and problems take three times longer to solve than anyone thinks.  To reduce the number of problems, declare as many as possible as annoyances.  Unlike problems, annoyances don’t have to be solved by the project.  Remember, it’s okay to save some work for the next project.

Even though you have a product development process, that process is powered by people.  People make it work and people make it not work.  If you get one thing right, get the people part right.

Image credit – claudia gabriela marques

If you try to change what you cannot, your trying will not bring about change. But it will bring about 100% frustration, 100% dissatisfaction, 100% missed expectations, 0% progress, and, maybe, 0% employment.

Here’s a rule: If success demands you must change what you cannot, you will be unsuccessful.

If you try to change something you cannot change but someone else can, you will be unsuccessful unless you ask them for help.  That part is clear.  But here’s the tricky part – unless you know you cannot change it and they can, you won’t know to ask them.

If you know enough to ask the higher power for help and they say no but you try to change it anyway, you will be unsuccessful.  I don’t think that needed to be said, but I thought it important to overcommunicate to keep you safe.

Here’s the money question – How do you know if you can change it?

Here’s another rule: If you want to know if you can change something, ask.

If the knowledgeable people on the project say they cannot change it, believe them.  Make a record of the assessment for future escalation, define the consequences, and rescope the project accordingly.  Next, search the organization (hint – look north) for someone with more authority and ask them if they can grant the authority to change it.  If they say no, document their decision and stick with the rescoped project plan.  If they say yes, document their decision and revert to the original project plan.

If you do one thing tomorrow, ask your project team if success demands they change something they cannot.  I surely hope their answer is no.

Image credit — zczillinger

In business, we have vision statements, mission statements, strategic plans, strategic initiatives, and operating plans. And every day there are there are countless decisions to make. But, in the end, it all comes down to one thing – how we allocate our resources.  Whether it’s hiring people, training them, buying capital, or funding projects, all strategic decisions come back to resource allocation.  Said more strongly, resource allocation is strategy.

Take a look back at last year.  Where did you allocate your capital dollars?  Which teams got it and which did not?  Your capital allocation defined your priorities.  The most important businesses got more capital.  More to the point – the allocated capital defined their importance. Which projects were fully staffed and fully budgeted? Those that were resourced more heavily were more important to your strategy, which is why they were resourced that way. Which businesses hired people and which did not?  The hiring occurred where it fulfilled the strategy. Which teams received most of the training budget?  Those teams were strategically important.  Prioritization in the form of resource allocation.

Repeat the process for this year’s operating plan.  Where is the capital allocated?  Where is the hiring allocated?  Where are the projects fully staffed and budgeted?  Regardless of the mission statements, this year’s strategy is defined by where the resources are allocated.  Full stop.

Repeat the process for your forward-looking strategic plans.  Where are the resources allocated?  Which teams get more?  Which get fewer?  Answer these questions and you’ll have an operational definition of your company’s forward-looking strategy.

To know if the new strategy is different from the old one, look at the budgets.  Do they show a change in resource allocation?  Will old projects stop so new ones can start? Do the new projects serve new customers and new value propositions?  Same old projects, same old customers, same old value propositions, same old strategy.

To determine if there’s a new strategy, look for changes in capital allocation.  If the same teams are allocated more of the same capital, it’s likely the strategy is also the same. Will one team get more capital while the others get less?  Well, it’s likely a new strategy is starting to take shape.

Look for a change in hiring.  Fewer hires like last year and more of a new flavor probably indicate a change in strategy.  And if people flow from one team to another, that’s the same as one team getting new hires and the other team losing them.  That type of change in resource allocation is an indicator of a strategic change.

If the resource allocation differs from the strategic plan, believe the resource allocation. And if the resource allocation is the same as last year, so is the strategy.  And if there is talk of changing resource allocation but no actual change, then there is no change in strategy.

Image credit – Scouse Smurf

If you didn’t get what you wanted, why not try wanting what you got?

If the timing isn’t right, what can you change so it is right?

If it could get you in trouble, might you be on to something?

If it’s impossible, don’t bother.

If it’s easy, let someone else do it.

If there’s no possibility of bad things, there’s no possibility of magic.

If you need trust but have not yet secured it, declare failure and do something else.

If there is no progress, don’t push.  Move the blocking agent out of the way.

If you don’t know where the cost is, you can’t design it out.

If the timing isn’t right, why didn’t you do it sooner?

If the project went flawlessly, you didn’t try to do anything meaningful.

If you know some people won’t like it, isn’t that reason enough to do it?

If it’s almost impossible, give it a go.

If it’s easy, teach someone else to do it.

If you don’t know where the waste is, you can’t get rid of it.

If you don’t need trust, it’s the perfect time to build it.

If you try the hardest thing first and it doesn’t work, at least you avoid wasting time on the easy stuff.

If you don’t know the number of parts in your product, you have too many.

If the product came out perfectly, you took too long.

If you don’t give it a go, how can you know it’s impossible?

If trust is in short supply, supply it.

If it’s easy, do something else.

If forgiveness is so much better than permission, why do we like to do things under the radar?

If bad things didn’t happen, try harder next time.

Image credit — Gabriel Caparó

Praise is powerful, but not when you don’t give it.

People learn from mistakes, but not when they don’t make them.

Wonderful solutions are wonderful, but not if there are no problems.

Novelty is good, but not if you do what you did last time.

Disagreement creates deeper understanding, but not if there’s 100% agreement.

Consensus is safe, but not when it’s time for original thought.

Progress is made through decisions, but not if you don’t make them.

It’s skillful to constrain the design space, but not if it doesn’t contain the solution.

Trust is powerful, but not before you build it.

A mantra: Praise people in public.

If you want people to learn, let them make mistakes.

Wonderful problems breed wonderful solutions.

If you want novelty, do new things.

There can be too little disagreement.

Consensus can be dangerous.

When it’s decision time, make one.

Make the design space as small as it can be, but no smaller.

Build trust before you need it.

Image credit – Ralf St.

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