" />

« February 2007 | Main | April 2007 »

March 24, 2007

Big Brass versus Crystal

Some balls are easier to juggle than others. But is that stance any way to run a company?

Something we certainly think we'll have to read is Michael Raynor's book The Strategy Paradox. Why? Because, as Deloitte puts it in their website's introduction to the book, "Management orthodoxy demands that strategies be built on commitments, which leaves no alternative to basing today’s decisions on assumptions about an unknowable future." This observation quickly drives down to the more important point they cite from Raynor: "The board should not evaluate the chief executive officer (CEO) based on the company’s performance but instead on the firm’s strategic risk profile..."

Since a review of the book is not where these paragraphs are going (yet), please visit Deloitte or even Raynor himself. What the heck: skip all that and read the book.

Before I read it, I'll turn my cards face up: if Raynor's book winds up telling me something other than that enterprise architecture, theory of constraints, and real options analysis is what's needed (and we assume it should), then I'll probably talk about it again. Maybe here, like, you know, in the next paragraph that could follow this one. Why not. While we're at it, let's go dust off our books about Royal Dutch Shell, do 'em again, and come back in a while.

For those of you with not that much time on your hands, a suitable companion piece is still available from Strategy+Business thanks to our buddies at Booz Allen, whose website offered this bit last year (as announced through emails to the faithful). I'm going to assume that advertising this for them will leave me in friendly territory vis-a-vis their copyright on what they sent, shown here for your convenience:

Sharpening Your Business Acumen
by Ram Charan

Dallas, March 30, 2006 -- The ability to see the big picture, anticipate external trends, and adapt accordingly requires plenty of practice, but can create unique moneymaking opportunities. It requires executives to transcend old rules of thumb and take strategic risks that don't follow precedent; to envision the effects of change before change happens. Here's a six-step thinking process to help anticipate external influences in the marketplace and craft smart strategies accordingly.To read the full article:

http://www.strategy-business.com/enewsarticle/enews033006

Posted by Malcolm Ryder at 4:34 PM | Comments (0) | TrackBack

The Rite(s) of Way

Today's coffee talk topic: performance improvement is neither performed nor improved. Talk amongst yourselves.

If you've been reading stuff around here before, you know that we always separate performance, competency and capability the same way we separate effects, causes and prerequisites. We even generally eschew pondering the catness of dogs and the appleness of oranges. But that doesn't mean we blow off the criss-crossings of ideas. This piece is about the intersection of Susan Conway in Optimize Magazine (January 2007, p. 50), and our everpresent mates at McKinsey.

Conway, driving north-south, describes her trip: "In my research over the past several years, I've found that measuring specific business challenges is possible using a productivity-impact framework (PIF) to understand what IT solutions are needed to increase productivity... PIF is a Lean Six Sigma (LSS)-compliant process that supports the correlation of ... variables ... to measure the impact of information and technology on an enterprise's productivity... Measuring, mapping, and understanding the right combination of technology and business processes, practices, and procedures let an organization achieve productivity gains...both capability and the efficiency or speed of delivery ... of products and services to customers."

McKinsey, driving East-West, routinely promotes the need to understand what kind of "productivity" would be most relevant by distinguishing and targeting the three essential strategic business needs: "Stay in the Race", "Win the Race", and "Change the Rules"... Their thought: when you come to the three-pronged fork in the road, chances are you need to pick one of the prongs before proceeding.

Conway's path is about using tools to speed up work that can also be procedurally optimized. We can call that "how to work" or "Do the Work Right". McKinsey's concern, on the other hand, is about heading in the right direction in the first place -- or let's call it "Do the Right Work".

This still allows us to see how they can -- and arguably should -- complement each other. There are lots of intersections. In drawing that up (below), a larger frame of reference emerges that starts to "organize" the ongoing 3-letter-hell blitz of "solutions" crowding our many fields of enterprise management.

We like the idea that Conway's three terms can represent what the enterprise ought to be worried about getting good at. Still, with that frame of reference, I took a second pass. In the second pass I stretched but not shifted what appears to be Conway's focus on IT per se. Why? Because: as tools, IT gets (from Conway) a specific kind of attention as an "enabler" bottom layer or element in a "productivity model" (north-south axis); but in effect, there are no managerial solutions listed in the framework here that are really practiceable without IT. As a result, we should revisit this "productivity" issue in Conway's north-south axis. What is shown below is a better version of the frame using some alternative terms. The new frame's north-south terms (or second dimension) -- information, communications/workflow, and governance/practices -- describe and stack the supporting roles of those solutions shown, in a model of "strategic" productivity. That is, the bottom row supports the middle row, which supports the top row. Meanwhile, this new frame assumes that all three of Conway's PIF terms are really a third dimension -- the PIF pertains to tactical productivity within each (and every) "solution" shown in the frame.

Corrected frame:

Glossary of solutions:
ITSM - IT Service Management
BSM - Business Service Management
PLM - Product Lifecycle Management

SOA - Service Oriented Architecture
BPM - Business Process Management
OPM - Operational Performance Management

KM / BI - Knowledge Management, and Business Intelligence
SCM - Supply Chain Management
CRM - Customer Relationship Management

Posted by Malcolm Ryder at 7:10 AM | Comments (0) | TrackBack

March 18, 2007

Personal Value, Company Worth

Despite the buzzing about organizational flatness, it is still customary to think hierarchically about the relative importance of individuals in the corporate workforce. This is continuously fortified by the dual notions of "promotions" and "tiers" that characterize most organization charts.

The attendant mythology is that if people are higher up the chart, then they are more important. More factually, there's little debate that more organizational power resides at higher altitudes -- but what must not be lost on everyone, meritocracy notwithstanding, is that even higher power is not the same as higher performance.

Org charts are just a sketch, with limited ability to explain three key issues.

1. How does the individual decide what kind of contribution to make? Does he want to be influential or just billable? Particularly critical, or broadly resourceful? What does it take, and is it possible in his workplace?

2. Conversely, when a particular company initiative or problem rolls around, what kind of value is most needed from the individual, and therefore what individual has the appropriate profile to meet the need?

3. Finally, is the company really cultivating the potential for getting the contributions that it most needs -- or is it just coasting on organizational conventions?

From the standpoint of performance, not only can higher ranking individuals be objectively evaluated in the same way that lower ranking ones are, but every individual actually thinks in the same terms to decide what kind of value he or she is really going to bring to the organization's performance. For everyone, there are the same two steps: they make decisions about modeling themselves, and they align the personal model with the circumstances. The effects are not uniform -- not for one person over time, nor for different people in the same moment. But what actually gets done by the organization is pretty much the consequence of all these individual decisions pitted or adapted against the day's environment.

To see how the self-model fits in at work, first walk through the self-modeling picture:


Here, within the main oval, we see the four key reference terms that the individual uses to describe their predisposition coming into the work situation: Billable, Critical, Resourceful, and Influential.

It's fair to see these terms as multiple "ambitions" occurring simultaneously but with varying degrees of strength; thus at any time the individual has a "profile", which may fluctuate from one time to the next.

Some individuals fluctuate more than others. But more to the point, there are surrounding factors that encourage or inhibit the person's profile, and that is how the rest of the picture comes in.

From the management viewpoint, the objective notion of the individual's value is simple, and twofold, in summary:


In effect, this is what the company is trying to do with or get from the individual.

When evaluation time rolls around, the question is largely one of whether the individual has committed to these two conversions as much as the company wanted him to. (In our research, we've noted that most observers initially believe the terms provided here are mis-ordered, and that the conversions should be "skills into quality" and "time into revenue". But, through most simple ROI analyses for intellectual capital and capacity management -- mandatory stuff for an enterprise -- that belief is quickly shown to be misguided.)

So, to understand why any success was possible or achieved in the person's alignment with the company's wish, it is necessary to see how the person's self-modeling fits into the company's model.

As arranged below, the remainder of the terms from our first illustration are indicators of that company model. They bring up the points at which the company makes things more or less hospitable through making investments that resolve key resources and constraints.


If the company doesn't make the investments, then the constraints do not enhance; instead, they become "restraints" -- and the resources (people) cannot be effectively heightened in value.

Roughly speaking, that final illustration compares "what kind of workplace" is available (worker in context) with "what kind of company" is there (work in context). Not coincidentally, these are the two key perspectives that the worker intuitively brings to the situation, greatly affecting his motivation (at least) or ambition (at most).

Back in the initial illustration above, the interdependencies involved in that comparison of workplace and company are laid out along the main oval, where they can be individually inspected.

Companies often make defacto decisions regarding those interdependencies that seem like no-brainers but may really be value-inhibiting. For example, assignments are an ordinary feature of the organization's workday. But assignments link skills to time and literally position the worker in the workflows. Thus, the potential of the business process is critically afffected; meanwhile, the logic of the process design is either a smart reason to invoke the worker or a not-so-smart reason. Bad processes can easily mis-position (i.e., waste) a worker, just as a bad worker can make a process ineffective. Management needs them both to be "good".

Likewise, it isn't hard to understand that overworking the person (in the "billable" link of time and revenue) lowers morale, or that training (education) would beneficially link skills and the quality wanted from the use of time.

Similarly, other "ordinary" aspects of the company will predictably map to the dynamics underlying value-capture. Depending on the point-of-view, these aspects may be recognized through other names or circumstances. For example, in our illustration's set of work-in-context constraints:
- Policy = "governance"
- Expertise = "intellectual property"
- Process = "organization" (dynamic, not static)
- Capacity = "goodwill" (of the stakeholders)

This helps us envision what impacts are really being obtained from things we know we're already thinking about or doing. But as arranged in the original oval, the most interesting part of the dynamics shown may be their bilateral nature. For example, just as education should be derived from investing in expertise, the picture asserts that strategy execution should be cultivated from policy (governance) -- certainly not only the reverse.

It is easy to recognize that the corporate valuation relies on those very issues of policy, capacity, etc. But now it is also easy to see how they are not just "performance results" but instead actually success factors -- due to the need for the company to invest in them as constraints to be managed around workers.

By tracking decisions and actions about the key factors illustrated above, we get answers to performance questions that may not have been apparent before.

Posted by Malcolm Ryder at 7:28 AM | Comments (1) | TrackBack

Lies, Damn Lies, and Innovation

"Improvement" is always near the top of our agenda, if we think we can have it. But meanwhile, method and performance are so deeply intwined in our thinking that we have a hard time untangling the language to think about them differently. The problem with this is that we are so reluctant to give credence to alternative methods. We see something being done differently and actually think that it can't be successful because of that, until proved otherwise.

Because of the misunderstanding, scientific management is still amazed by the vaguery of creativity and innovation, and with 20/20 hindsight struggles to find their formulae.

This pursuit of formula is legitimized by what is thought to be the example of science, which accounts for nature (the essence of creation) in the metrical way. We then generalize the practice to our professions when we need similar balm for our uncertainties... and (except in marketing) we push back against accepting theory without the proofs. To get closer to the truth, we'll sign up the experts -- people on whom we can impose performance standards as our paid proxies -- to bring academic proofs to the problem.

The enduring vanity of academia, as opposed to intellectualism, is the scientific method. Ironically, the scientific method accumulates a shroud of dificult esoterica that obscures what may be its most important characteristic: good science is essentially democratic. The whole point is to lay it out so that anyone who follows the instructions can do it. It's just that it is often really hard to follow the instructions. So when it comes to scientific experts, we wind up commissioning their stamina even more than their knowledge.

The alternative approach to credence is evidenced by the great artists and athletes of any time, who's business of constant microinnovation under pressure is their working definition of performance. What underpins their performance is experience and the consciousness of that experience -- and there they have the key reference needed to justify their claims: the school of hard knocks. Getting back to science, it isn't really the metrics that drive things, is it? It's the experiments!

No reason to discount the "excellence of expertise"; on our budgets there often isn't enough to go around. But the "genius of experience" is equally valid, established through a different mode. The thing is, for most of us, genius is actually no less accessible than academia is, and practically speaking, it is "most of us" that cause something to happen with what we can get. Until we use what we can have, we can't discredit it. When it comes to pursuing improvement, the real difference is in whether we want to prove something or whether we just want the proof.

Posted by Malcolm Ryder at 4:12 AM | Comments (0) | TrackBack

March 17, 2007

Coffee Break in the Garden of Good and Evil

It's been only a week since Hassan Fattah broke the news in the NY Times that should break the back of popular publically traded Bay Area upstart coffee purveyor "Peets". Although Peets has far nicer gizmos and stylish vessels to manage your coffee from the bean to the belly, the chemically faithful amongst its rival Starbucks crowd will no longer have to choose which of 27,615 directions to face when its time for another fix. Starbucks will now, as we all really knew was inevitable, be opening in Mecca in about a year's time. "This is the end of Mecca," said Dr. Irfan Ahmed in London.

So. Who cares.

Posted by Malcolm Ryder at 6:29 AM | Comments (0) | TrackBack

March 13, 2007

Fast and Pretty, but not Cheap

Normally you'll find an article here instead of a conventional blog posting, but today Michael Hugos, of CIO Insider, caught my attention with his blog posting about agility on his site, Doing Business In Real Time. It definitely warranted a fast reply of comparative and perhaps contrasting views, reproduced here below. (Be sure also to see his Comment following.)

Very often the agility issue comes up in conversations with managers, and there are two interesting and recurring characteristics when it does.

One, it comes up *after* results have been calculated and posted. That is, managers see what already happened and ask "if we had been more agile, would it have made a difference?"

And two, there is tremendous confusion of agility with other ideas including "flexibility", "resilience", and "versatility".

The one-two punch of being reactive and confused makes "agility" something that remains vaguely ambitious as most managers don't know where to start, on which aspect they are really concerned about, or whether it is the right aspect.

Let's call that the worst case scenario. Hugos' article addresses that by outlining "agility" measurements -- which turn out to be what is largely now identified as Operational Performance Management (OPM) -- great stuff that is not the same as "agility" but is the same as "alignment".

I propose that the agility issue comes in when OPM is a strong practice, allowing targets and their pursuit to change in ways that are (here's the punchline):
- easily operationalized...
- with successful change management...
- to realign on time...
- without breaking things.

There, in a nutshell, you have the four points of reference that allow you to spot why your company is or is not agile. It's a process matter.

As for the 2% to 4% financial improvement that Hugos uses to stand for agility, that's a target, interesting as a representation of what ROI might justify the effort to be agile. But knowing where the target is doesn't tell you how to get there. For most managers, it is not so much that being agile will "cause" the percentage increase; instead, the issue is one of "prerequisities" -- namely, the probability of getting the increase without being agile is so poor.

Posted by Malcolm Ryder at 12:15 PM | Comments (1) | TrackBack

March 11, 2007

The Ontology of Support in IT-Business Alignment

Business-IT alignment is an ongoing critical success factor of enterprise performance. There, "support" functions of aligning IT with the business are all part of just two basic management issues that describe the problem of responsibility in the business-IT relationship. One, how does IT production fare in providing the deliverables to the business? And two, how well do the needs of the business associate to IT's support? The issues mark the distinction between what IT can do on its own accord (production) and what the business finds valuable about IT (support).


.
Once fully articulated, the factors of the relationship's "operationalization" show the belief system that underlies the standing functional organization of the relationship at the given business.


From the bottom up, the layout reflects how the IT "service desk" attains a central role in the alignment. The primary responsibility of the service desk is to bring proper workflow to the support request incoming from the business. The nature of these requests follows along the type of concern that the business has, which falls within three main topics in the relationship's ongoing "conversation". Within each topic, the problem is to solve the potential imbalance or mismatches inherent between the subjects of the topic. These solutions are what comprise the ability of IT to properly align to the business.

As shown, the organization begins with taking what management has in hand -- SME's and assignment authority -- and codifying it for continual reuse by the business, in the form of two key interfaces: a catalog and workflow.


These interfaces moderate any mechanisms for systematically addressing the three key topics of the business-IT relationship:
- business (demand vs. supply)
- service (performance vs. operations) and
- IT (capacity vs. systems).
As seen below, catalogs and workflow each have roles in two of the three topics.


.
The substance of the three topics is found in the dynamics of the business-IT relationship, shown here as three factors -- effects, drivers and constraints. In each topic, those dynamics represent how the resolution of the topic's issues may arrive at a suitable level and type of affect on the business.


A key finding in the above is that we can count on the IT "effects" to be critical to the service "constraints", and count on the service "effects" to be critical to the business "constraints".
.
Another key finding is that any of the "effects" can be (and usually are) both categorized and measured, with the categorizations sometimes being both hierarchical and deeply detailed. However, management often gets lost in those "trees" to the extent of not being able to see the "forest".

At the higher level, the management effort must accomplish the following:

1. Define the business scope of the service responsibility: this means creating and "productizing" services. What are the SLAs actually covering?

2. Define most requests for operational support in terms of managing service quality. Classes of requests should indicate what depth of exposure must be addressed in the service's handling of the IT provision to the IT user (incidents, problems, changes, etc. a la ITIL). Within each request class, further categorizations should point at the two critical factors of continuity and quality. (Understand how incidents relate to continuity and quality; how changes relate to continuity and quality; etc.)

3. Based on evidence (probably "symptoms") from the IT user, categorize the suspected perpetrators in the request's issue about (or requirement for) continuity or quality.
.
This identifies, as seen below, where the touchpoint arises between the request and the workflow needed to satisfy it.

Posted by Malcolm Ryder at 4:38 AM | Comments (0) | TrackBack

March 10, 2007

Retro Chic in the Garden of Good and Evil

This just in: Analysts this week have discovered the first circumstantial evidence of a disturbing pop conspiracy involving the now infamous Britney Spears. Pop aficionados remember the sensational moment when Spears smooched the Material Girl, Madonna, on television during an otherwise presumably harmless awards show. It now appears that Madonna's kiss was more of a kiss off -- just the beginning of an intricate plan to ultimately drop Spears in the airwave standings and reclaim her own preeminence during Spears' downtime. Observers noted that Spears, during her current anxieties, received no support whatsoever from Madonna, and tipsters amongst them became suspicious. Detectives, speaking anonymously about previously unrevealed investigative findings, now believe that Madonna framed Spears for the murder of Anna Nicole Smith, the occasionally zoftig ersatz Marilyn Monroe. In the wake of the misdeed, Spears' sales and airplay have not enjoyed the Insanity Exemption presumed by all erratically behaving pop stars since Michael Jackson, and Madonna cuts have rushed in to fill the void. However, magazine ad rates and volume have both quadrupled in the celebrity softcore newstand segment, and Smith's lawyer, Howard Stern, is rumored to be in negotiations with Spears to become her publishing agent.

Posted by Malcolm Ryder at 6:42 AM | Comments (0) | TrackBack