We consultants live and die on methodologies. Just as double-blind therapeutic trials are what make modern doctors are more reliable than shamans for preventing and curing diseases, the methodologies we consultants use are what make our analyses and recommendations more reliable than an executive’s gut feel.

Take, for example, the methodology I use for application, application portfolio, and application integration rationalization (AR/APR/AIR).

It starts with collecting data about more than twenty indicators of application health, redundancy, and integration for each application in the portfolio. It’s by analyzing this health data that my colleagues and I are in a position to reliably and provably recommend programs and strategies for improving the enterprise technical architecture’s application layer, along with the information and platform layers the applications rely on.

For large application portfolios the process is intimidating, not to mention invasive and expensive. Fortunately for you and unfortunately for me when I’m trying to persuade clients to engage our services, there is a more frugal alternative. In most situations it’s amply reliable for guiding AR/APR/AIR priorities as our sophisticated methodology, while costing quite a lot less.

Call it the TYE methodology, TYE standing for “Trust Your Experts.”

But first, before we get to TYE, take the time to clean up your integration architecture.

Maybe the techniques you use to keep redundant data synchronized and present it for business use through systematic APIs are clean and elegant. If so, you can skip this step on the grounds that you’ve already taken it. Also, congratulate everyone involved. As near as I can tell you’re in the minority, and good for you.

Otherwise, you need to do this first for two big reasons: (1) it’s probably the single biggest architecture-related opportunity you have for immediate business and IT benefit; and (2) it creates a “transition architecture” that will let you bring new application replacements in without hugely disrupting the business areas that currently rely on the old ones.

And now … here’s how TYE works: Ask your experts which applications are the biggest messes. Who are your experts? Everyone — your IT staff who maintain and enhance the applications used by the rest of the business, and the business users who know what using the applications is like.

And a bit often missed, no matter the methodology: Make sure to include the applications used by IT to support the work it does. IT is just as much a business department as any other part of the enterprise. Its supporting applications deserve just as much attention.

What do you ask your experts? Ask them two questions. #1: List the five worst applications you use personally or know about, in descending order of awfulness. #2: What’s the worst characteristic of each application on your list?

Question #1 is for tabulation. Whichever applications rank worst get the earliest attention.

Question #2 is for qualification. Not all question #1 votes are created equal, and you’re allowed to toss out ballots cast by those who can produce no good reason for their opinions.

Once you’ve tabulated the results, pick the three worst applications and figure out what you want to do about them — the term of art is to determine their “dispositions.”

Charter projects to implement their dispositions and you’re off and running. Once you’ve disposed of one of the bottom three, determine the disposition of what had been the fourth worst application; repeat for the fifth.

After five it will probably be a good idea to re-survey your experts, as enough of the world will have changed that the old survey’s results might no longer apply.

You can use the basic TYE framework for much more than improving the company’s technical architecture. In fact, you can use it just about any time you need to figure out where the organization is less effective than it ought to be, and what to do about it.

It’s been the foundation of most of my consulting work, not to mention being a key ingredient in Undercover Boss.

TYE does rely on an assumption that’s of overwhelming importance: That you’ve hired people worth listening to. If you have, they’re closer to the action than anyone else, and know what needs fixing better than anyone else.

And if the assumption is false … if you haven’t hired people worth listening to, what on earth were you thinking?

Thanksgiving is coming right up. As modern, change-embracing trend-setters, I know you and your fellow members of the KJR community will be taking advantage of convection ovens to cook your birds faster than your parents achieved with their quaint conventional roasting technologies.

No? You don’t use a convection oven? Me neither. But if you’re like me, you’ll warm up your leftovers in the microwave.

Microwave ovens were hugely successful. Convection ovens weren’t. Recognizing why will make you and your teams more successful in rolling out the incipient changes you’re championing.

When microwaves first appeared on the scene (the ovens, that is, not the 300 MHz to 300 GHz electromagnetic radiation, which after all appeared on the scene shortly after the universe got started) … where was I?

Oh, yes, when microwave ovens appeared on the scene, Americans had already embraced convenience foods, whose principle attractions were (1) they were packaged as single portions so everyone could eat what they were in the mood for; (2) they needed far less effort to prepare (none) than the equivalent meal made from a recipe (between some and a lot); and (3) they were ready to eat far more quickly than the equivalent meal made from scratch.

Convenience foods might not have been as tasty as home-cooked meals, but they were palatable enough that the convenience outweighed the difference for many households on many evenings.

The microwave made convenience foods even more convenient, along with the salutary speed they brought to defrosting frozen food and the ease with which they warm coffee that’s become lukewarm.

Speaking of which, excuse me a moment …


Compare microwaves to convection ovens. Convection ovens are for cooks, not for folks heating prepared meals. For cooks they speed up baking and roasting by maybe 25%. That’s nice but not transformational. And it added enough uncertainty that cooks couldn’t rely on the conversion charts that came with the convection oven.

They also couldn’t rely on their experience … their feel for conventional cooking, refined over a lifetime of kitchen endeavor.

Convection cooking either meant abandoning recipes collected and practiced over years, decades, even generations in favor of those in a convection oven cookbook. Or else it meant subjecting every recipe to trial and error to get the convection time and temperature right.

And oh, by the way, the cook doesn’t have the luxury of serving a few burned or undercooked meals to the family while getting the hang of the new appliance.

This meant cooks, faced with a convection oven, had to start over. I, faced with a microwave and a frozen burrito, did not.

One more bit of information: Convection ovens haven’t been a dismal failure. They’ve been a dismal failure in the home marketplace, but as I learned while researching this article, they’re quite popular in commercial kitchens.

This makes perfect sense. When you’re running a restaurant, cutting baking and roasting cycle time by 25% or more means delivering meals to customers that much faster, which in turn means turning over tables by roughly the same amount.

Which, following the logic chain to its unavoidable conclusion, means that comparing otherwise identical restaurants, one using convection ovens has 25% more capacity than a competitor that uses conventional ones, with no loss of meal quality.

Of course restaurants learned to use convection ovens. They couldn’t afford not to. And their chefs were (and are) developing new recipes all the time. Developing them for convection ovens took no more effort than developing them for conventional ones.

To summarize:

> A major cultural change had preconditioned the home-kitchen marketplace, plowing the metaphorical field for microwave ovens. Convection ovens had no such advantage.

> Convection ovens made competent cooks less competent. Microwaves might have encouraged laziness and less discerning palates, but their only impact on home cooks was to make convenience foods even more convenient, thereby letting them off the hook for even more meals.

> In commercial situations, convection ovens offered direct financial benefit, with few or no serious negatives for the chefs.

Ask your change teams: Are their plans consistent with business culture? Will they make change targets’ lives better in some easily explained way? Enough better to offset their short-term loss of competence, if it’s going to have that effect?

Because when it comes to making change happen, business benefit might be the goal.

But it has little impact on success.