Showing posts with label initiatives. Show all posts
Showing posts with label initiatives. Show all posts

Tuesday, August 23, 2011

The Oyster, the Grain of Sand, and the Pearl

It’s funny how a metaphor suddenly appears and yet is so obvious you wonder what took you so long to see it.

Over the last month, I’ve taken to joking that the name of my consulting firm should be changed to Oyster Consulting, because “We’re the grain of sand that irritates the hell out of everyone, but when we’re done, you’ve got a pearl.”

It’s amazing how true that is. 

Significant strategic change is never easy.  People resist, no matter how clear it is that the change is needed and it’s the right thing to do.  People are more comfortable with the Status Quo.

And because of that, change won’t happen without getting people out of their comfort zone. It is only then that people will be willing to move in the new direction.  Thus, the need for that grain of sand.  That grain of sand is so irritating, it makes people uncomfortable – uncomfortable enough to change.

Being the grain of sand from within an organization is career threatening.  Once the process is done, people won’t remember the benefit you delivered – they’ll just remember that you were really irritating.  That’s why bringing in the grain of sand from outside can be so valuable.  That outside grain can help irritate people, make change happen, and then leave. All that’s left behind is that beautiful pearl.


Friday, July 10, 2009

Quality Counts

I had a great conversation with a client this week about Quality.

A team was given a task - to provide new technology to the field organization - by the company's CEO, and she wanted it done fast. The CEO had a clear vision of what she wanted and described it in detail to her team. She made clear what resources would be available to the team. And she gave them the deadline by which she wanted it in place and operating.

The team sprang to work. It knew it had a tremendous challenge on its hands. The time frame was extremely tight - call it too tight. The resources were extremely limited - call them too limited. And the CEO's vision of what she wanted was clear and ambitious - call it too ambitious. Something had to give. And in this case - it was Quality.

The team delivered on time - the technology got out into the field. The cost was within budget - there was no tolerance (nor availability) for anything more. And the scope - well, the technology was designed to do everything the CEO wanted.

You know the punch line: It didn't work.

You've probably seen the Scope-Resources-Time triangle. Many organizations have adopted it, with the mantra: Pick any two. The concept is simple. Management can fix any two of the three components, so long as the third can flex. Try it:
  • Scope and Resources are fixed - The project may take longer than planned
  • Time and Resources are fixed - The project may have less scope (functionality) than desired
  • Time and Scope are fixed - You may need more resources to get the full functionality complete on time.
The triangle is very valuable - but as you can tell from the story (oh, and the title of this blog), it's not complete. The missing ingredient is Quality.

The fact is, you can fix three components: Scope, time, and resources. But what gives then is the quality. It's not tested, it's not right, it doesn't work.

Here's a simple example you can try on for size: Cooking a gourmet meal. (Have you ever watched one of the reality cooking shows?) Requirements (scope) are fixed - 3 courses, including certain key ingredients. Check. Time is fixed - one hour. Check. Resources are fixed - one chef plus kitchen equipment. Check. So, are the "True Goals" of a great meal always met? Of course not. The missing variable is Quality.

There are plenty of examples of failed execution because of failed Quality. Quality is hard to protect, frequently because it is "expected" and therefore not made explicit nor monitored and measured. We know what happens when something isn't measured, don't we? Right. "You want it respected? Then inspect it."

What happened with this CEO and her challenge? Well, it's in clean-up mode. More dollars (lots) and resources (ditto) have been thown at the problem, trying to fix it. Even worse, putting bad quality out in the field has major, long-term ramifications. You lose trust and credibility. The next solution will be looked at with skepticism and suspicion ("Hah, you think that's going to work? Don't you remember...?"). Fortunately, this was an internally focused initiative. Could you imagine the problems created if this had been client-facing?

It's not pick any two - it's pick any three. Quality is not a given - it is a choice. The commitment to Quality needs to be explicit. It needs to be monitored and measured. Otherwise, Quality can fail, like any other unmeasured metric. And if quality fails, you (and your initiative) will never Reach its True Goals.


Wednesday, April 29, 2009

True Goals



I spend a lot of time talking to people about "reaching (their) true goals" - but what does that mean?  

There are 4 components to reaching true goals:

1) Accomplish the objective.  Do what you want to do.  Get it done.  Succeed.  Reach the finish line.  Anyway you want to define it, it's all about figuring out what you want to do and doing it...

Umm - hey, Gregg.  You said there were 4 parts to "reaching true goals."  But number 1 seems to sum it up pretty well.  What are the other pieces? 

Easy:

2) On time.
3) Within budget.
4) And with the right level of quality.



It's a constant struggle.  True goals, done right, is defined in the context of all four quadrants:  What you want to accomplish, by when, at what cost, and with what level of quality.

Accomplishing any subset of those - by my definition - means you haven't reached your true goals.

Let me belabor the point for a minute to, well, make a point:
  • I got what I wanted, but later than I needed.  True goals?  No.
  • I didn't quite get what I wanted.  TG? No.
  • Got it - but it cost more than planned.  Nope.
  • Well, I got it, on time, within budget - but it wasn't as good as it should have been.  Strike 4.
Too many organizations take the easy way out.  They don't fully identify what they're trying to accomplish up front, defined by all 4 attributes of the Challenge.  That way, it's easy to claim that you've succeeded... even when you really haven't.

The best result?  Know exactly what your True Goals are before you start - defined as reaching the desired result, on time, within budget, and with the right level of quality - and then go get them.