" />

« May 2008 | Main | July 2008 »

June 27, 2008

Do As I Do, Not As I Say


The McKinsey gang's ongoing interest in behavioral economics leads from time to time to email alerts about articles that lead off like this:
Hidden flaws in strategy

"Why do top managers, steeped in theories of good business strategy, still make bad decisions? While ignorance and hubris sometimes play a role, the brain itself—how we think—is also a culprit. Insights from behavioral economics help explain why we don't always think rationally and how our logical flaws can lead to bad strategic decisions."

On a day like today, when the stock market dropped over 300 points, the catchiness of that intro is in the contrast between the confidence we want to have in logic and the confidence we want to have in our ability to use it.

Getting strict, we might have to say that when strategy is based on logic, strategy is interpretive -- because in different hands, the same logic might lead to different strategy and/or different strategic outcomes.

But why doesn't it make just as much sense to place the first faith in the strategy and then find the logic to execute it? Well, it does; it's just that in this mode, the "strategy" is not a performance; instead it is a proposition that supplies the point of view to be used when managing functions.

McKinsey's discussion seems to be poised to warn us away from the problem of management personalities corrupting objectivity, and further, poised to argue that this should be the right warning because we can assume that there is usually going to be sufficient objectivity to correctly navigate to the correct destination. That is, the most prominent assumption that we can read into the McKinsey caution is that it's not cool to split from the plan. Logic shall bear decisions and decisions shall bear the plan and the plan shall be righteous.

But isn't that still letting the bad boys off the hook? Levity aside, coaches bring the game plan to the players knowing this: that the players actually have to play, which means that the players will improvise their way to the opportunity to comply, if they understand the strategy -- "strategy" which is again essentially a point of view and not a performance prescription.

Strategy is about belief in the value of your position. It is esentially about where you're going to be, and why you're going to be there. Because of that, any position within a hierarchy of operational dependencies can be a strategic position. In effect, a position represents the opportunity, so the most direct way for a leader or manager to damage the potential of a strategy is to make decisions that inhibit or prohibit the players' opportunity to align and coordinate their compliance to the strategy.

Because of that, we want a model of coaching to rely on, not just retraining (or re-straining) of senior staffers to the logic-decision-plan mode. We want an observation-design-motivation mode just as much if not more. We want the sideline clipboard.

Posted by Malcolm Ryder at 11:21 PM

June 24, 2008

Business-IT Alignment: Who Do that VooDoo?

At Tech Republic, the online resource for IT management information, executive editor Jason Hiner's article "Sanity check: What’s the difference between CIO and CTO?" relays the following quick guide.

Chief Information Officer

  • Serves as the company’s top technology infrastructure manager

  • Runs the organization’s internal IT operations

  • Works to streamline business processes with technology

  • Focuses on internal customers (users and business units)

  • Collaborates and manages vendors that supply infrastructure solutions

  • Aligns the company’s IT infrastructure with business priorities

  • Developers strategies to increase the company’s bottom line (profitability)

  • Has to be a skilled and organized manager to be successful


Chief Technology Officer
  • Serves as the company’s top technology architect

  • Runs the organization’s engineering group

  • Uses technology to enhance the company’s product offerings

  • Focuses on external customers (buyers)

  • Collaborates and manages vendors that supply solutions to enhance the company’s product(s)

  • Aligns the company’s product architecture with business priorities

  • Develops strategies to increase the company’s top line (revenue)

  • Has to be a creative and innovative technologist to be successful

Given that picture, the two top observations are these:

1. Infrastructure affects the bottom line (what you get to keep), while systems affect the top line (what you get to get). Of course, this goes a long way towards explaining why a CIO would report to a CFO, while a CTO would report to a CEO. More importantly, it indicates that strategic resourcing can be a CIO's calling card, but that strategic positioning can be a CTO's calling card.

2. Much less explicit but still clearly in evidence is the difference between being a chief operations technologist (a.k.a. CIO) and a chief business technologist (a.k.a. CTO). Naturally, the easy way of understanding how to assess their respective progress and performance would rely on understanding the consequences -- of not having good infrastructure (provision of operations technology) and not having good systems (provision of market interaction technology). But getting it figured out in positive terms has stumped the panel often enough and long enough that these job descriptions still have to get spelled out long after the hiring has been done . What's still needed furthermore to get the dust to settle is a plan of co-production between them. Whereas neither effort alone could get the whole job done, the combined efforts of the two groups would offer a company an office of Business-IT Alignment...

Posted by Malcolm Ryder at 8:48 AM | Comments (0) | TrackBack

June 18, 2008

When is "value" not valuable?

A wonderful discussion on Bruce MacEwen's website Adam Smith, Esquire included this challenging note from Paul Lippe about what logic is available to explain the connection between quality and value. While he questions "reputation" as an indication of warm fuzzies like "quality", he also kicks off his note citing the less fuzzy implication that better performance presumes to justify higher price:

"I'd be curious if anyone can come forth with any data to show that in fact (as opposed to in repute) more expensive law firms produce better results, e.g. can it be shown that the investment banks who had the largest losses on their mortgage portfolios were served by lower reputation law firms?

Once this conversation settles down, I will start a separate string (and perhaps a wiki to really pull something together) on what I consider to be the core issue: how can we develop a definition of VALUE in legal services that is meaningful and useful, and not simply measuring inputs like hours spent, diligence of lawyers, law school attended or reputation of the firm. With such a definition of value, I think we could expect that some lawyers' reputations and income would go up, but some would not."

Let's dig into that overall observation by making the undercurrents obvious.


  1. "Value" is a label for the significant distinctions attributed to something. "Value" in professional services is 3-dimensional, at minimum. A certain method of co-operation with the customer interacts with a certain type of target outcome at a certain level of effective cost to the customer. The method, outcome, and customer cost are variables, each having a range of acceptability, which in turn allows some universe of acceptable overall impact to sprout from their combination. Now, from that dynamic, some professional service providers are great at being predictably consistent within a smaller universe (range of impacts) that the customer prefers. Some are great at being agile enough to cover a larger universe, keeping up with a customer who has more volatile preferences. And there are several other "flavors" of competency that a service provider may have. Ultimately the provider wants to be paid for the competency, and then be paid even more for a competitively greater level of competency. But the customer wants to pay for customer satisfaction, which is something different. And what mediates the balance of the two things is often just culture. I wouldn't choose to drive a perfectly good Tercel to the White House Christmas Ball, but I could; and I wouldn't choose to drive a Bentley to the 7-Eleven, but I could. In fact, I could use either car to get to either destination.


  2. That's all well and good in theory, but in practice the realization of the potential value is hugely affected by the ability of the customer to appropriately and effectively align to it. (There is even plenty of historical evidence that customers sometimes buy based on how they wanna be seen, not based on how they really are.) That reality is the "forest". Relentless pursuit of profit is the bulldozer that strips the forest. Atomic metrical inputs like law schools and hours spent risk merely being "trees", where excessive attention obscures the view of the forest and therefore obscures the proper understanding of the value.
    3. Profit and arbitrary metrics actually must not dominate an analysis of value. Instead, value, properly identified, can be correlated with profits and other interesting measures, and the correlations may be revealing or even exciting.

  3. The final point from the above is that it is probably important to use rigor in discussing value, because "value" is not a reliable synonym for other things that deserve their own names, such as "competency" and "satisfaction", and "culture". It's important to know what is actually being taken into consideration and not gloss over things for convenience, because otherwise we find out too late that we're actually sitting on some key coordinate that does not allow us to "get there from here" (i.e., to the necessary value) on time. Meanwhile -- if we would like to elevate the discussion of value from the 3-D space of CustomerCost /Outcome/Method to the 3-D space of Competency/CustomerSat/Culture, while remembering to map the current coordinates in both spaces, well that's fine.



Posted by Malcolm Ryder at 12:17 PM