Archive for the ‘management’ Category

The Cart Before the Horse

Tuesday, February 21st, 2012

For more than the last 10 years I’ve been thinking a lot about CMMI.  Many of these thoughts have been ruminating on the ideas of how to incorporate CMMI in ways that add value, demonstrate effectiveness, and don’t disrupt the operation.  I’ve even opined much in this blog (in too many ways) on the need to know what your processes are before you can use CMMI to improve them, and that for many operations, CMMI isn’t even appropriate.

A few recent discussions and experiences put a particularly fine point on the extent to which CMMI is really the ‘cart before the horse’ when applied within an operation that has yet to clearly discern its process, and here’s why:

Most operations I’ve encountered are not ready to use CMMI because they are unclear on exactly how they make money.

Obviously, I’m not talking about the accounting process of billing out invoices and depositing checks.  And, I’m not even talking about the voodoo around figuring out how to ensure that internal costs (salaries, equipment, etc.) are less than what they charge clients for the work they do.

So, I must be talking about something more subtle.  I wish I were.  And, this is what’s both frightening and sad.  I’m merely talking about the relationship between capacity and demand.  For that matter, I’m not even worried much about demand, which is another matter.  I’m mostly talking about capacity.

What is capacity?

According to some, capacity is a measure of volume of work.  Throughput, for instance.  According to others, it’s the wherewithal to do the work.  Either way, too many operations don’t know what their capacity is. 

What does it actually take to get work done?  And, along with that, can it be reasonably expected of the operation to reliably and predictably continue to run how it runs (not knowing exactly how it runs) and to have any right to greater-than-zero confidence that they will continue to run as it does?

For one thing, many operations run outside of reasonable tolerances. In particular, people put in many many hours of unpaid over-time [in the US this is common for salaried employees].  This is an "out-of-tolerance" condition.  It is unreasonable to expect an operation’s greatest source of working knowledge to continue to work nights and weekends.  Furthermore, it is risky to do so.  One client said he couldn’t be away from the office for 5 minutes before product would stop shipping.  Eventually he will get married or his wife will have a child, or, heaven-forbid, he may take vacation! 

What’s worse is the extra time he and his team put in is entirely unaccounted-for.  His employer merely estimates, contracts, and bills enough to cover his and the team’s salaries, not what it actually takes to get work done.

Another reason true capacity is obscured is because more work going into the operation than there’s product (or services) coming out.  The most common cause of this is the misperception that work started = work completed, but this is an incomplete equation.  But a better equation to work with is work worked-on = work completed.  The key mistakes is the assumption that started = in-work.  That’s true for maybe 50% of the actual started work (often less).

This next reason for the lack of insight into true capacity (or capability, really) is that so many operations don’t account (either in their estimates — which sort-of makes sense — or in their capture of time-spent — which is unforgivable) for the time to correct defects, time to perform rework, time for paying-down technical debt, or time and effort to tracking-down the causes of defects and rework to avoid defects, rework, and technical debt in the first place!

I’ll end with one of the toughest, most sensitive observations of the last few months.  Some of my best clients (from the perspective of having their act together) have strong confidence in functional competence and, admittedly, weaker confidence in their programmatic credibility.  And, to put it plainly, by "programmatic" I mean their ability to have the same confidence in the rationale for their estimates and plans as they have in their ability to produce what their clients want. 

In these operations, I’ve found fundamental disconnects between how work is estimated and why clients should trust the technical competence of the operation.  In other words, they build trust with their prospects and clients on their ability to do the work and build the products, but in order to get the work in the first place they have to use a lot of hand-waving and breath-holding when it comes to their estimates.

A more-or-less summary way to describe all of this is as follows:

Most operations have Built a way of working that they’ve managed to Capitalize.  Over time, they’ve found that their Build*Capitalize approach is tough to Sustain.  Try that they might, whether it’s CMMI or something else, they’re looking to "fix" the equation on the "Sustain" side.  The problem is that CMMI *does* operate on the Sustain side, but the problems with the operation aren’t in the "Sustain", it’s that their approach to Capitalizing on what they Built is no longer Sustainable.  What needs to change is on the Build side.  Occasionally, there’s a need to revisit the Capitalize component, but most often it’s the Build that needs refactoring.

Hence, applying CMMI to an operation whose "build" is broken is putting the cart before the horse.  While it’s possible to build CMMI practices into the operation’s way of working, this is an activity of the "build" side of the equation, the sort I noted above contrasting from applying CMMI to the sustain side.  If CMMI is to be truly about improving the processes of the operation in a "sustaining" sort of way, and not defining them, the operation must understand what’s going on, and that means it must know its capacity.  Because unless it knows its capacity, it doesn’t really know what’s going on.

The Cart Before the Horse

Sunday, February 19th, 2012

For more than the last 10 years I’ve been thinking a lot about CMMI. Many of these thoughts have been ruminating on the ideas of how to incorporate CMMI in ways that add value, demonstrate effectiveness, and don’t disrupt the operation. I’ve even opined much in this blog (in too many ways) on the need to know what your processes are before you can use CMMI to improve them, and that for many operations, CMMI isn’t even appropriate.

A few recent discussions and experiences put a particularly fine point on the extent to which CMMI is really the ‘cart before the horse’ when applied within an operation that has yet to clearly discern its process, and here’s why:

Most operations I’ve encountered are not ready to use CMMI because they are unclear on exactly how they make money.

Obviously, I’m not talking about the accounting process of billing out invoices and depositing checks. And, I’m not even talking about the voodoo around figuring out how to ensure that internal costs (salaries, equipment, etc.) are less than what they charge clients for the work they do.

So, I must be talking about something more subtle. I wish I were. And, this is what’s both frightening and sad. I’m merely talking about the relationship between capacity and demand. For that matter, I’m not even worried much about demand, which is another matter. I’m mostly talking about capacity.

What is capacity?

According to some, capacity is a measure of volume of work. Throughput, for instance. According to others, it’s the wherewithal to do the work. Either way, too many operations don’t know what their capacity is.

What does it actually take to get work done? And, along with that, can it be reasonably expected of the operation to reliably and predictably continue to run how it runs (not knowing exactly how it runs) and to have any right to greater-than-zero confidence that they will continue to run as it does?

For one thing, many operations run outside of reasonable tolerances. In particular, people put in many many hours of unpaid over-time [in the US this is common for salaried employees]. This is an “out-of-tolerance” condition. It is unreasonable to expect an operation’s greatest source of working knowledge to continue to work nights and weekends. Furthermore, it is risky to do so. One client said he couldn’t be away from the office for 5 minutes before product would stop shipping. Eventually he will get married or his wife will have a child, or, heaven-forbid, he may take vacation!

What’s worse is the extra time he and his team put in is entirely unaccounted-for. His employer merely estimates, contracts, and bills enough to cover his and the team’s salaries, not what it actually takes to get work done.

Another reason true capacity is obscured is because more work going into the operation than there’s product (or services) coming out. The most common cause of this is the misperception that work started = work completed, but this is an incomplete equation. But a better equation to work with is work worked-on = work completed. The key mistakes is the assumption that started = in-work. That’s true for maybe 50% of the actual started work (often less).

This next reason for the lack of insight into true capacity (or capability, really) is that so many operations don’t account (either in their estimates — which sort-of makes sense — or in their capture of time-spent — which is unforgivable) for the time to correct defects, time to perform rework, time for paying-down technical debt, or time and effort to tracking-down the causes of defects and rework to avoid defects, rework, and technical debt in the first place!

I’ll end with one of the toughest, most sensitive observations of the last few months. Some of my best clients (from the perspective of having their act together) have strong confidence in functional competence and, admittedly, weaker confidence in their programmatic credibility. And, to put it plainly, by “programmatic” I mean their ability to have the same confidence in the rationale for their estimates and plans as they have in their ability to produce what their clients want.

In these operations, I’ve found fundamental disconnects between how work is estimated and why clients should trust the technical competence of the operation. In other words, they build trust with their prospects and clients on their ability to do the work and build the products, but in order to get the work in the first place they have to use a lot of hand-waving and breath-holding when it comes to their estimates.

A more-or-less summary way to describe all of this is as follows:

Most operations have Built a way of working that they’ve managed to Capitalize. Over time, they’ve found that their Build*Capitalize approach is tough to Sustain. Try that they might, whether it’s CMMI or something else, they’re looking to “fix” the equation on the “Sustain” side. The problem is that CMMI *does* operate on the Sustain side, but the problems with the operation aren’t in the “Sustain”, it’s that their approach to Capitalizing on what they Built is no longer Sustainable. What needs to change is on the Build side. Occasionally, there’s a need to revisit the Capitalize component, but most often it’s the Build that needs refactoring.

Hence, applying CMMI to an operation whose “build” is broken is putting the cart before the horse. While it’s possible to build CMMI practices into the operation’s way of working, this is an activity of the “build” side of the equation, the sort I noted above contrasting from applying CMMI to the sustain side. If CMMI is to be truly about improving the processes of the operation in a “sustaining” sort of way, and not defining them, the operation must understand what’s going on, and that means it must know its capacity. Because unless it knows its capacity, it doesn’t really know what’s going on.

A Tale of Two Companies

Sunday, June 26th, 2011

Earlier this month I had the utmost pleasure to visit one of the most innovative, successful, ground-breaking and thought-provoking companies on the planet.  I really wanted to immediately blog about them but was having trouble coming up with something more than an "I <3 ____" entry.

Earlier this weekend I had the utmost disappointment to patronize a company that provided me with such a contrast to the first company that I immediately had sufficient content to do justice to a blog post with something constructive.  Little did I know that as I was amidst my experience and formulating this entry in my head, the latter company would be generating the exact sort of "proof" to support predictions I had planned to make about the company’s performance.  As I write this, events are unfolding to practically word-for-word demonstrate my points for me.

I’m sorry this entry is very long… but you’ll see why soon.

The former company is growing at lightning speed in size, revenues, and profit.  In The latter company has already pulled out of several markets and scaled back operations in others, is adopting tactics known to disenfranchise customers and seems utterly oblivious to it’s operation’s lack of efficiency.

Sadly, chances are the latter company will continue to make decisions that will negatively affect their outlook while the former company could easily be turning the latter around if the latter would bother to pay even the slightest attention the the cause-and-effect of their actions.

The former company, to a person, is keenly aware of what makes a satisfied customer.  Their policies, hiring practices, operating values and reward systems are all consistent with and fully cognizant of what makes people (employees and customers) satisfied.  Their people exhale good will and sweat fun.

The latter company seems to have scraped up some dusty "how-to" manual — probably chiseled in a cave somewhere — full of the best ways to be oblivious to the desires of humankind.  Their policies — as evinced by the tactics and activities of their people — clearly convey that those who wrote them haven’t thought-through what people want or how people think; their operations manuals were written without ever considering how the people who’d have to follow them would feel about behaving as set-forth in those procedures.

The former company wouldn’t give a second thought to treat a customer with a level of service above and beyond what the customer may have paid to expect at any almost cost, while the latter company goes out of it’s way — to the point of introducing gross inefficiencies — to separate levels of service along artificial lines of "classist" service levels.

Finally, the former company would encourage its employees to invent ways to simultaneously raise good will, raise the customer experience and raise the overall efficiency of the business.  At the former company, every employee understands the value of relationship capital as much as they understand the value of the company’s performance.  Meanwhile, at the latter company, instead of looking at the negative effect of cost of delay, the negative effect of not offering their best "deal" up-front, and the negative effect of blatant classism, they artificially construct a workplace where employees are more worried about being "stingy" with what they offer customers, and then flaunt their lack of service with cold reminders of the service they’re not giving and go out of their way to be patronizing about the limited service they do provide.

So… Now for the reveal.

The first company is Zappos.  I blogged about Zappos and CEO Tony Hsieh’s book, "Delivering Happiness" about a year ago.  Let me tell you in pictures about my visit to Zappos and why I’m so impressed with them.  The descriptions to go along with those pictures tell the rest of the story.  There’s so much to tell, and these shots don’t tell the half of it.

Photo Jun 07, 8 59 43 Starting from the moment you walk in the door at the reception area, you know you’re not in a typical operation.  The space is raucous.  The guys behind the desks are handing out bottles of water, playfully joshing the guests on anything they can quickly turn into fun, running friendly competitions among the visitors and staff, and cutting the ties of unsuspecting (but should have known better) visitors.  In a sitting area behind where this photo was taken is the company library where a QR code will take you to their recommended reading list.

Photo Jun 07, 9 18 51 While our effusive, outgoing, bright-eyed tour guide, Renea, happens to be in the middle of this shot, she’s not what I’m actually focusing on.  It’s what happens to be directly behind her head.  The office of the company’s goal coach.  You have a goal?  The goal coach’s job is to help you reach it.  Personal?  Professional?  Educational?  No matter.  The goal coach’s job is just that: coach people to help them achieve their goals.  No bounds, no strings, no pre-set expectations.  Just positive goals.

Photo Jun 07, 9 21 03 Real life doesn’t have a "pause" button.  Zappos gets that.  So, to help with "real life" while work life intrudes, Zappos has a continually evolving set of services it makes available to its employees to help minimize the inconvenience of being at work when "real life" must go on.  Notice that most (if not all) of these services are not necessarily free.  But they are convenient, and in some cases, they are discounted through group negotiations.  Whether any are actually subsidized by the company, I don’t know, but that’s not important. 

One thing to note, however, is that the company cafe is highly subsidized with all but hot, prepared foods being free or nearly free, and the hot entrees are very inexpensive.  All with as much attention to nutrition and dietary needs as to taste and convenience.  I don’t have a picture of the cafe.

Photo Jun 07, 9 24 05 This shot might just about say it all, if you really read into the statement being made at the company.  Many companies have a hallway where they post their ongoing achievements.  Zappos has such a wall, but theirs has something you don’t see everywhere.  The top row of framed images are various financial (usually sales) achievements (pretty common).  Also on this top row are included related achievements such as volume of transactions.  In particular, phone call orders processes in a single day — in total, when supplemented by people whose primary jobs are not to take calls (not as common).  The bottom row of framed items are copies of the company’s annual "year book".  Only at Zappos, this year book is about the company’s culture.  Every employee, every year, is encouraged to submit an original work in any format describing their experience with the Zappos culture.  Good, bad, or pretty, or ugly.  Everything is open and transparent and everything is published unedited.  (Not common at all!)  This is why I said that this shot might "say it all".  The company celebrates its ongoing cultural achievements with the same enthusiasm as it celebrates its financial and operational accomplishments.

Photo Jun 07, 9 25 04 To me, the fact that the incredible accomplishment noted on the left-hand-side of this picture is still nothing more than something printed on office paper six months after the event tells me that their celebration of success is both understated and not so high a priority — as in many other businesses — as to cause anyone to go out of their way to rush a costly picture onto the wall.  You can also see here that this accomplishment is celebrated as much — if not more — for its reflection of the work put into it as it is for the financial results it caused.  Also visible in this shot are a couple of the author-signed books given to Zappos CEO on behalf of the company.  They’re not in his personal collection.

Photo Jun 07, 9 29 30 Every work team at Zappos is encouraged to decorate their spaces in their own way.  Groups typically decide on a theme and the themes change from space to space.  This image is of the team of people who work to decide what products to sell at Zappos, ("merchandising").  If you look in the center of the image, you may see what appears to be a dark green area.  That’s the short row of cubes where the C-level executives of Zappos have their desks.  Called, "Monkey Row", the next image is a close-up of this area. 

The anthropomorphic glove sits on the divider between the executive assistant’s Photo Jun 07, 9 32 40area in the foreground, and the CEO’s cube, behind the glove.  The COO and CFO’s spaces are on the right with a conference room in the back.  This day, all the C-levels are elsewhere.

These chicken heads are the company’s Photo Jun 07, 9 38 02"retail systems" group.  A QR code on the outside wall instructed me to ask them to put on their masks and take a picture to win a prize.  The caped, masked rubber bathtub duckie wasn’t nearly as priceless as this photo.  One might wonder whether such disruptions were deleterious to productivity.  In fact, the opposite has been found.  The tours are scheduled, not ad hoc.  The employees are encouraged to take a break, interact and be friendly and welcoming to the visitors.  There are only four tours a day and only on certain days, and the entire "disruption" lasts a few minutes.  Fun and weirdness are both important and so the company creates opportunities for both.  Zappos is an amazingly productive place.

Photo Jun 07, 9 52 29Communication is at a premium in Zappos.  Here were see an example of a screen where questions and answers are posted continuously on customer and other issues resolved throughout the company.  Nearby, we see an example of one of the many ways in which employees are reminded of the company’s core values.  A new value is chosen for emphasis each month as a means of generating ideas and making progress towards common goals as a group. 

Photo Jun 07, 9 52 45 When you read the company’s list of core values, you see they show up in everything their people do.  They’re not necessarily formally measured by how they "stack up" against these statements, but they are continually grounded in whether or not their actions are consistent with the values.  While promoting a particular value each month may seem hollow, what makes it meaningful is that each employee is encouraged to express their manifestation of these values in however they believe they can contribute — as long as it’s consistent with the other values.

 

Photo Jun 07, 9 54 42 Let’s switch gears to metrics.  One might conclude that a company with the sort of values linked above might minimize or eschew the use of metrics.  One would conclude such things erroneously.  Zappos is famous for, among other reasons, their willful bucking of industry norms by not forcing time quotas for how quickly people are expected to handle phone and text chat inquiries.  Not using quotas and stop-watches running for each call, and not rewarding call-handling in terms of calls per hour may sound like the company doesn’t use metrics, nothing could be further from reality.  The company devours metrics.  They just don’t use them for petty, demoralizing, and customer-infuriating reasons.  They use them to manage capacity and availability.  In other words, they use them to ensure they have enough staff to handle their workload and to keep customer service levels as high as they can push them.  These measures are directly across the entryway to the call-center area, not in some manager’s area.  Besides, the manager would be sitting among the team anyway.  Everyone knows the measures and no one has any reason not to use them.

Photo Jun 07, 9 57 09 This whole area (most of the floor) is called the "CLT" for "customer loyalty team".  They take the calls, operate online chat, and are just about the entirety of the live, human, customer-facing operation.  But the group of desks in this shot are one of the most impressive investments I’ve seen anywhere.  Zappos has a name for them, I believe it’s "Resource Team", but I call them the "slack team".  Very simply, these people have full time jobs to go help anyone else anywhere else for any reason and for any amount of time.  In other words, they take up the slack to keep things running smoothly.  In most other operations, such jobs are "other duties as assigned" to people who already have jobs.  In other operations, this sort of work is why people work late.  At Zappos, these people work a regular work day doing nothing but making sure everyone else can work a regular work day — among other things.

Photo Jun 07, 9 57 22 This is the last of my Zappos shots and the end of my Zappos explanation-by-pictures on just how deeply Zappos internalizes the needs of their customers.  In this view we see an entire team dedicated to responding to inquiries made directly to the Zappos CEO, who’s made his email address, Twitter, and Facebook identities public knowledge.  While Tony reads all his mail, responding is another matter.  These people do nothing but respond to incoming messages for Tony — making no attempt to hide that they’re not Tony as we’ve seen in some businesses.  While Tony does read and sometimes responds to his own mail and tweets, he can’t expect to get to a fraction of it.  This group helps him manage all that.

And now we come to the "other" company.  The second company is an airline.  The pictures give away which one.  There really only need to be the two pictures because just these two convey so much.

Photo Jun 25, 0 45 39 This card was sitting on the arm-rest between the two seats where I was seated.  I guess they reconfigured this plane to two classes because my ticket was bought in the next lower class called "Economy Comfort", but I didn’t see that class of seat on the plane. Only this ("Saga" class, i.e., "business class") and economy.  But it seems this card is designed to warm me that they plan to treat me as though I’m in economy.  In other words, they went out of their way to ensure one row of people — all of 4 seats — knew they were being excluded from the remaining 18 seats in the same cabin! They actually spent money to be inefficient AND lose all credibility with good will and a service attitude!

Photo Jun 25, 0 50 03 In this next image you see that they bothered to put a sign on the headrest in front of this row just in case the card wasn’t clear: "You’re not wanted here and we’ll make sure you know it."  How must it feel to be an employee told to visibly treat people as unwanted directly before their own eyes?!  To offer headsets, champagne, gifts, menus with choices, and hot towels to people then stop short of offering the same to people inches away?!  I’d feel ridiculous and I’d probably go home with an ulcer.

Behavioral and psychological differences aside, do they have any idea how inefficient treating one row differently from the remainder of an entire cabin is?  Clearly not. The transaction costs are obviously unknown. No wonder their banks failed.

What the pics don’t tell is the story of what took place in the terminal for nearly an hour before we boarded late.  Starting 30 minutes before boarding, announcements began to be broadcast seeking two volunteers to give up their seats in exchange for business class seats the following day from a different city — a city the volunteers would have to fly to, presumably the next day as well, and, presumably on the airline’s account but on another airline.

Twenty minutes after boarding was to have started, they began to "sweeten the offer" with adding that the volunteers would receive one round-trip ticket anywhere the airline flew, and meal and hotel vouchers for their immediate over-night stay.  It took another 15 minutes before they had their volunteers, and, I do not know what the actual final "deal" was — whether the volunteers took the announced deal or made a counter-offer.  I do know that had my plans allowed me make such a last-minute change, I would have had a much more appealing offer to counter with.  But that’s neither here nor there.

What’s wrong with this picture?

Is there anything right with this picture?

Does anyone believe there’s no relationship between the failure to make a compelling offer in time to keep the flight on time and the notes and signs and behaviors moments later exhibited on-board?  Does anyone believe there’s no relationship between these events and the misconfiguration of the aircraft for the seats sold?

Did anyone at the company notice that they actually spent money to work-around this known issue rather than to simply go all-the-way and give the "upgraded" seat-sitters the full business-class treatment?  Did anyone there notice how much inefficiency they incurred?  Multiple meals, multiple amenities, multiple passes through the same place for different reasons?  They even handed us different headsets!  The flight attendants from the main cabin had to come through the curtain to give us our drinks and meals!  For ONE row!

What about the sum of all these and the economics of having to divide how a single set of staff split their behavior, their resources, and their services within the confines of the same cabin?  All for the sake of treating a single row of four seats differently from the remaining 18 seats?  Any wonder that they’ve cut routes and scaled back others?  Aircraft space is at a premium.  It would have been much easier, not to mention far more enrolling to everyone, to have the entire cabin treated as the same class. 

What makes this experience noteworthy is just how far out of norms it is.  While many airlines go out of their way to find efficiencies, this one seems to go the other way.  While many airlines take some pride in being able to treat some customers to upgrades, this one goes out of its way to remind customers they’re clearly not welcomed.  Sadly, it’s also noteworthy that there doesn’t seem to be much the staff can do about any of it.  This is clearly how the company wants the operation to run.  They go out of their way to build the system so that it runs this way.

Little did I know at the time, but upon arrival in the country, I learned that some of the pilots of this airline have decided to "strike" and not fly.  Without warning.  Not as part of an organized effort, but on their own.  While in the US, this would never work for companies based there, it seems to be common in more socialist economies like in Europe.  Let’s look at what causes a company’s people to strike: um… problems with their employer! 

As a result, a number of invited guests are not going to make it to the event and other are delayed indefinitely and may miss the events here entirely.  With the experience fresh in my mind (and ongoing), I tapped out most of the text of this post while in flight.  I had not idea about the strike.  But I could not have imagined a more appropriate demonstration of the negative and permeating affects of bad policy.  Clearly, the striking pilots are not happy about how they’re being treated. 

I’m sure there will be executive blow-hards at this company and elsewhere quick to say that they have nothing in common.  That how my experience in the terminal and ob-board have nothing to do with the pilots’ gripes.  I, Zappos, and those of us who see the connection between company culture, employee satisfaction, and customer satisfaction would vehemently disagree.

Zappos could teach these people a lot.  No wonder people have suggested to Tony that Zappos starts an airline.  Though… there already is one Southwest and both Zappos and I love them.

[Note: lest anyone think that the actions and behaviors and attitudes I note are just me and my "Western sensitivities" to class structures, I should point out a number of things: I fly enough to fly in business and first class a lot-- both by upgrades as well as by purchasing the appropriate fares.  It doesn't bother me when I'm in a more economical class and the more expensive classes get better service.  In those situations, the airlines at least do what they can to separate the service classes, and besides, I know what I've gotten myself into and the airlines don't rub it in my face.  Furthermore, the European guy next to me had the exact same impressions... All the way from the volunteer fiasco to the notes and signs to the differences in treatment.]