By
Download on the App Store

episodes

  • Off With Their Heads!

    My promised column on threads will appear in this space on Friday. It would have appeared here today but the crumbling global financial system suddenly seemed a more appropriate topic.

    We're in trouble and by "we" I mean the whole darned planet. What started as a mortgage problem in the U.S. has blown into global financial paralysis that threatens us all with recession and maybe even with depression. I know I'm feeling depressed, how about you? The crisis seems immune to any and all efforts to fix or end it. NOT passing a $700 billion mortgage bailout can send Wall Street into a tailspin, for example, but then finally passing the bailout didn't seem to improve things, either. The Federal Reserve and Treasury Department are running out of tools and time yet still the system flirts with suicide. So I say it is time to take a completely different view of the problem and to look to a new leader to solve it, in this case Jack Welch.

    Jack Welch is the retired chairman and CEO of General Electric who took the company during his 23-year tenure from being worth about $14 billion to about $410 billion by really MANAGING the business and concentrating on creative use of capital. I've written columns and columns deriding managers as a profession but none of that applies to Jack Welch and GE, where managers really manage -- they manage the heck out of the place and to generally good effect. Jack Welch built that system, he has time on his hands, I say let's give him a new job.

    There is very little difference, in fact, between the global financial system and General Electric. Welch saw GE entirely in terms of cash flows and the application of capital to those parts of the business where it would do the most good. Welch also thought in terms of continuous quality improvement, which is virtually unknown on Wall Street OR in Washington, where such things aren't even talked about, much less measured.

    I've been thinking about this crisis and a lot of it comes down, I believe, to a fear of failure especially on the part of the banks. There is no credit available to anyone, anywhere, no matter what the credit rating or score. This is because the banks are frozen by fear to the point where they won't even lend to each other much less to customers. This fear of failure seems to be pretty much guaranteeing failure. And the regulators are now throwing what will soon be trillions of dollars at trying to break these bankers out of their paralysis. But I think there is a better way: use this very fear of failure as a motivator.

    Before we get to Jack let's deconstruct this current psychological crisis on the part of the banks. They aren't lending money because they are afraid it won't be repaid. They won't lend even to each other because banks seem to be failing all over yet there hasn't been an instance yet when an overnight loan has resulted in default. So what's the problem? More properly, what is the outcome the banks fear?

    They fear going out of business either through honest failure or through being forced to merge or having their deposits taken away by the Federal Deposit Insurance Corporation (FDIC). In short it comes down to fear of losing their licenses, because as a highly regulated industry the banks can only do business at all with the permission of government. Right now they are totally fixated on the idea that if they lend money and it isn't repaid the government will pull their licenses. Yet the government has made it clear that the most important thing is to LEND MONEY, breaking this credit paralysis. All the banks know this but none of them want to be the first to take the big risk of lending money.

    You do it! No, you!!

    Enough of this crap. What if Jack Welch was the U.S. banking czar? We know the result of all such crises these days in the U.S. is the appointment of a czar -- a new government official drawn from industry and charged with cutting across agency lines and streamlining an ultimate solution. We did it in energy and terrorism and I'm sure we'll do the same thing now so let's just think ahead a bit. Let's assume that's the case here and that whatever President is in office names Welch. What would Jack Welch do?

    If Welch ran the U.S. banking system like he ran GE, he'd kill the bottom 10 percent of banks every year and fire the lowest 10 percent of bankers.

    What impact would that have on the system? Would it make it better or worse? Well it couldn't be worse, could it?

    Doctors have a way of measuring pain. It seems our brains can only focus on one pain source at a time, so if you have a pain in your gut you really don't notice the pain in your ankle. So there is a device called a palpometer that goes on your arm or leg and is calibrated to produce standardized and replicable levels of pain. Put this gizmo on, turn up the pain, and when you get to the point where the patient suddenly goes from saying, "My head hurts," to "My leg hurts," then you know how much pain they are in.

    This was all pre-waterboarding mind you.

    Right now all the bankers are afraid to lend money because they are afraid of failure. As the new banking czar Jack would much rather have them be afraid of HIM. If the bottom 10 percent of bankers were fired every year and the bottom 10 percent of banks had their branches and deposits redistributed, wouldn't they be more afraid of THAT than of making bad loans? Their motivation would still be to make GOOD loans, but the penalty for making NO loans would be there, too.

    Our problem then is that we're throwing money at something we should be handling using a different regulatory tool -- licensing.

    U.S. bank regulators should go to all the banks this afternoon and say, "You aren't making loans, which is part of the definition of what it is to be a bank. If you aren't acting like a bank by tomorrow we'll take away your banking license and transfer your deposits to another bank that WILL make loans."

    Problem solved overnight.

    It's only one part of the problem, of course, but this solution will cost a lot less than $700 billion. It will cost nothing.

    And if you think it won't work, then you don't know Jack.

    7 min
  • Data Debasement

    Last week I was in Boston to moderate a panel at the MIT Technology Review’s Emerging Technologies Conference — one of those tech shindigs so expensive I can only attend as hired help. My panel was on parallel computing and it produced this column and another I’ll file early next week. This week is about databases and next week is about threads. Isn’t this a grand time to be a nerd?

    Thanks in part to Larry Ellison’s hard work and rapacious libido, databases are to be found everywhere. They lie at the bottom of most web applications and in nearly every bit of business software. If your web site uses dynamic content, you need a database. If you run SAP or any ERP or CRM application, you need a database. We’re all using databases all the time, whether we actually have one installed on our personal computers or not.

    But that’s about to change.

    We’re entering the age of cloud computing, remember? And clouds, it turns out, don’t like databases, at least not as they have traditionally been used.

    This fact came out in my EmTech panel and all the experts onstage with me nodded sagely as my mind reeled. No database?

    No database.

    Parallel computing used to mean scientific computing, where hundreds or thousands of processors were thrown at technical problems in order to solve them faster than Moore’s Law might otherwise have allowed. The rest of us were relying on rising clock rates for our performance fix, but scientists — scientists with money — couldn’t wait so they came up with the idea of using multiple CPUs to solve problems that were divided into tasks done in parallel then glued back together into a final result. Parallel computing wasn’t easy, but sometimes that was the whole point — to do it simply because it was so difficult. Which is probably why parallel computing remained a small industry until quite recently.

    What changed was Moore’s Law put an end to the clock rate war because chips were simply getting too hot. While faster and faster chips had for the most part linear performance increases along with cost and power consumption decreases, the core temperature inside each microprocessor chip was going up at a cubic rate. Back in 2004 Intel released a chart showing that any clock speed over 5 GHz was likely to melt silicon and Moore’s Law would, by 2010, make internal processor temperatures similar to those on the surface of the Sun!

    For those, including me, who think that’s pretty darned hot I’ll point out one of my astronomer readers immediately had to mention that the Sun’s chromosphere is actually much hotter than the surface. Forgive him, he means well.

    Faced with this absolute thermal performance barrier, Intel and AMD and all the other processor companies had to give up incessant clock speed increases and get us to buy new stuff by putting more than one CPU core in each processor chip can. Now chips with two and four processor cores are common and Intel hints darkly that we’ll eventually see hundreds of cores per chip, which brings us right back into the 1970s and ’80s and the world of parallel computing, where all those principles that seemed to have no real application are becoming very applicable, indeed.

    And that’s exactly where databases start to screw up.

    Bob Lozano, chief visionary, evangelist, father-of-eight (same woman) at Appistry came up with the first database example I’d heard and it was eye opening. Appistry (I’ve written about them before — it’s in the links) specializes in distributing what would normally be mainframe applications across tens, hundreds, or even thousands of commodity computers that act as one. If a government agency wanted to do meter-scale analysis of very high-resolution images from spy satellites, it might use Appistry, I’d imagine (just a guess, of course).

    The database example Bob used at MIT was of an unnamed customer that is a credit card transaction processor. Their core application — the processing of credit card transactions — was happening on IBM Z-series mainframes (the biggest of big iron) and the client wanted to port the whole mess to commodity PCs.

    Google did it, why not them?

    But the first time they tried it at Appistry, it didn’t work.

    “We hired a technical team that had done similar applications before so they started with replicating the mainframe architecture on the commodity computers, database and all,” Lozano recalled. “But when they finished it wasn’t appreciably faster than the mainframe it replaced. Even worse, it wouldn’t scale. So we fired the team and started over.”

    The problem, it turned out, was in the database.

    The way the original mainframe application functioned was by first receiving transactions, writing them to the database, reading them from the database, then doing the actual processing before writing them again back to the database. That’s read-write-read-process-write.

    The second time through the Appistry team tossed the database, at least for its duties as a processing platform, instead keeping the transaction — in fact ALL transactions — in memory at the same time. This made the work flow into read-process-write (eventually). The database became more of an archive and suddenly a dozen commodity PCs could do the work of one Z-Series mainframe, saving a lot of power and money along the way.

    If this sounds like a risky way to do business — not writing the data to disk until things slow up enough — remember that’s the way Google runs its search engine and why it is so darned fast. Google has THE ENTIRE INTERNET IN MEMORY AT ONCE. If the application slows down they just add more hardware.

    This is good news for cloud computing and bad news for mainframes, because systems like Appistry and its competitors (there are several) are going to eventually bury the mainframe by putting the “cloud” into cloud computing. Suddenly a Storage Area Network with a relatively weak database controller is good enough for archiving while the parallel or even massively parallel cloud does the real work.

    Later this month Microsoft will announce a cloud version of Windows Server and it will be very interesting to see how it handles database integration and dis-integration.

    The database problem is much more than just slow reads and writes. Relational databases also create false dependencies between pieces of data. Dependencies of any kind break parallelism, and therefore make an application hostile to commodity platforms. That is, if one chunk of data (A) is dependent on another chunk of data (B), then no work can be done on A until all work on B is complete. If the dependency is real, like when A and B are both withdrawals from the same bank account, then there are hacks we can try like one I will describe in my next column, but most programmers just choose to have a cup of coffee and wait for B to finish.

    But if these are withdrawals from different bank accounts, or maybe even different banks, then no true dependencies exist. Unfortunately, if all of this has been stored in a single relational database then we unintentionally create a false dependency, since that database can only handle a fairly limited amount of items concurrently — we’ve created a bottleneck that will choke the application.

    While the database guys are busy figuring out how to add more and more concurrency internally, in reality when you take a few steps back and think of a large set of commodity boxes all executing a single data munching app, then no matter how sophisticated we get, the relational database will still effectively be a single thread to that app.

    A traditional response is to pour dollars into the data tier, buy faster, more concurrent SANs, better interconnects, and bigger database servers. That works up to a point and pleases Sun and IBM no end.

    Somewhat more helpful though are data grid products like Coherence or eXtreme Scale (IBM), or Appistry’s Fabric Accessible Memory (FAM). For many applications those can take more of the lifetime of each chunk of data and keep it in memory in the middle tier — hopefully on the same boxes where this large data-munching app resides. But this still doesn’t completely solve the problem because there remain limits on how far the relational database can scale.

    Here’s how Google attacks this problem, which goes beyond simply keeping the entire Internet in memory. The problem, of course, is that you can’t keep the entire Internet in memory in every server because then you’d need more memory chips than even Google can afford to buy.

    To scale the Google search service, then, they figured that many large problems did not intrinsically require doing actions one at a time. But Google first had to free itself of the false dependencies. So they coined the term MapReduce and created both a set of operations and a way to store the data for those operations natively, all while preserving the natural independence that is inherent in each problem, building the whole mess atop the remarkable Google File System, which I’ll cover some other day.

    Google led the way but many other companies have followed suit, opening doors to a wide range of new ways of thinking about large-scale data manipulation. Suddenly there are different ways to store the data, new ways to write applications, and new places (thousands of cheap boxes) to run such applications.

    What this does for Larry Ellison and his libido is a great question, because it looks like he’s bought up most of the traditional database-centric software industry just in time for it to be declared obsolete.

    Sorry Larry.

    11 min
  • The Cringely Plan

    In the early 1980s I was a volunteer firefighter for a tiny community in the Santa Cruz Mountains of Northern California. We all lived in a beautiful redwood forest and our task was to keep that forest from burning down in a huge conflagration, taking us all with it. The job was made all the harder because our little part of paradise hadn't burned since the 1920s, so there was 60+ years of flammable undergrowth just waiting to light off. The current financial crisis facing the United States and the world really isn't much different from that.

    An unmanaged forest, one without the sort of fire control we attempted to provide, would naturally burn every few years. The undergrowth would build up, reach a critical mass, some source of ignition would come along -- usually lightning -- and all that undergrowth would burn. The redwoods themselves would be scarred but not really threatened, as we could see from the charring that marked them from countless such fires over centuries. Of course burning undergrowth threatened homes and property, too, so there was a natural desire on the part of that community to want the next burn to not come this year, please not this year. So there came a policy of aggressively fighting fires with the result that we eventually faced 60 (now 90!) years of flammable material growth rather than six or eight years. And the probable fire fueled by 60 years of undergrowth would have been so bad that our job changed to one of trying to prevent fires from happening, well, ever. This was an impossible task, of course. Eventually the stars would align the wrong way and the whole place would burn down, we all knew it. Just let it not happen on our watch.

    Does this sound familiar?

    Now America and much of the world face the possibility of recession and we handle that by first arguing about the definition of the term. Are we or are we not in recession? This distinction appears to be very important to some who view it like a forest fire: is it burning or not? Implicit in this distinction, I suppose, is the idea that if we're not burning -- if we are not in recession -- that maybe through some miracle we'll never face that problem. Whether this is a practical attitude or not depends entirely on your event horizon -- how soon you expect things to change.

    The people in power in this country have a relatively short event horizon. Politicians tend to think of two, four, or eight years as the longest periods of time that matter. Corporate honchos might look out further, you could guess, but they don't since the average duration for a U.S. Fortune 500 CEO is under four years. So while the intent of the fire chief and the mayor and the governor and the Congressman and the President and the CEO is that there be no unpleasant surprises during their watch, all of them know such surprises are coming.

    This short-term focus in the face of long-term difficulties leads to odd behavior at times. In the forest it is usually better to let smaller fires burn or even to deliberately set them, yet few fire chiefs are willing to take that risk, even though NOT taking the risk is so much worse. In financial markets, as companies crumble and governments prepare bailouts, short sellers pile on in scrums of doom that make the shorts rich yet hurt society. Traders with a trading mentality, they can't help themselves any more than Ralph Nader can keep from running for President. "But George Soros did it to the Bank of England," they say, as if that makes everything okay.

    The American economy is at the end of its longest-ever period without a recession. Through sleight of hand and a fair amount of financial fraud we've managed to keep the "R" word out of our communal vocabulary for 14+ years. We did this through a succession of bubbles -- first the Internet bubble and then the real estate bubble with a little war bubble thrown in between. Financial bubbles are unnatural enough in themselves, but piling bubble atop bubble defies logic, yet still we managed to make it happen, helped somewhat by half a trillion dollars in war spending, all with borrowed money.

    By rights the end of the Internet bubble should have sent us into recession, burning the financial undergrowth and setting up the next period of prosperity. But we avoided that and the result is what we see now -- something far worse.

    Recession is inevitable at this point, yet still we talk about avoiding it. This is crazy talk. If we as an economy somehow push the next recession back a few more years, it will be all the worse when it comes. AND IT WILL COME. Everybody in power knows this; none of them argue against it; they all know recession is inevitable; they know that forestalling a recession at this point will only make it worse. Yet still they pray, "Not on our watch, please."

    So we plan $700 billion bailouts on top of hundreds of billions in other knee-jerk measures all intended simply to forestall the inevitable and therefore ultimately bound to fail. "Just not on our watch, please."

    The cost of delaying the inevitable is high, but we won't pay it, our children and grandchildren will. We can argue policy all day and whether this matters or not, but it is hard to argue that any such cost doesn't matter IF IT DOESN'T WORK.

    So I propose The Cringely Plan -- a relatively small attempt to point public policy in a direction that makes sense for a change. The Cringely Plan won't avoid a recession because that's impossible. The Cringely Plan is intended, rather, to look beyond the inevitable recession and assist with the ultimate recovery and beyond.

    What we need are energy and economic policies that play to the strengths of government, not its weaknesses. Governments are good at big moves that force changes of direction, not little moves intended to, for example, create the economic "soft landing" we'll start to hear about in a couple months.

    Governments are best at turning super tankers, not at docking them.

    And while governments can print money and thereby pay for a lot of stuff, they are actually most effective just telling us what we can or can't do, more than anything else. We can see that, for example, in the Clean Air and Clean Water Acts of the 1960s that significantly improved the lives of all Americans without the government having to pay for it.

    The Cringely Plan does nothing for banks or mortgages. That's a problem that will have to work itself out, I think, and will if we give it a chance to do so. But we won't give it such a chance, I'm guessing, because it is an election year and because government is viewed as stupid and able to be threatened into paying for the most amazing things that it shouldn't. So The Cringely Plan has to look past banks and mortgages to energy policy and economic stimulus.

    It would be interesting to know what the mortgage market would be like had the price of a barrel of oil not hit $140+. There still would have been a mortgage bubble bursting, but I wonder when?

    Whatever the banking situation, though, we still need an energy policy and simply have not had one for decades. So get ready, here it comes; The Cringely Plan calls for:

    Prohibiting the manufacture and sale of incandescent lights.

    Kind of a letdown, eh?

    That's it. No ethanol subsidies, no drilling in wilderness preserves, no tax credits, no artificial price supports, no enriching good ol' boys from the oil patch. And no cost to government at all.

    As our incandescent lights wear out we'll have to replace them with something else, primarily compact fluorescents and LEDs.

    Yes, this will lead to the closure of light bulb and filament plants in Ohio and elsewhere, costing a few thousand jobs. At the same time it will create jobs in the non-incandescent light industries as those ramp up. But most importantly, it will within a year (based on a 700-hour life for incandescent bulbs) lead to an 18 percent drop in U.S. electrical demand.

    Dropping electricity demand by 18 percent will have an interesting effect on the electric utility industry. A simplistic view would suggest that our electric bills should drop by 18 percent. Cynics will point out that fixed overhead built into the regulated industry will keep bills from dropping that much simply because doing so would unduly hurt utility profits.

    I don't think so.

    Our utility bills pay for power that comes from many sources, some more efficient or profitable than others. Our bills also pay for building new power plants, some of which are again more efficient or profitable than others. An 18 percent cut in demand will have a huge impact on the production strategies and capital spending plans of every U.S. utility. More expensive plants built to serve marginal demand -- plants like smaller gas turbines for example -- could be taken off-line, dropping the average cost per kilowatt. Large new plants that have been in the works (and that we've been paying for) for years can be eliminated or delayed. Cancelled plants would lead to higher profits that lead to lower electrical rates. So our electric bill won't go down 18 percent, they'll go down 25 percent, which is a savings of $22 per month for the average American home.

    Twenty-two dollars per month!? Big deal. Was there an economic component of this energy policy?

    Well, it's a savings of $29 billion per year EVERY YEAR FROM NOW ON, which pales the recent and easily forgotten economic stimulus package that sent $600 checks generally not to the people who needed them most. How much of a positive effect those checks had on the economy is open to debate, but how much effect they had on reducing energy consumption isn't, because that effect was nada, zilch, zero.

    $29 billion also amounts to about the annual debt service cost of either the Iraq war or the coming $700 billion bailout. Take your pick.

    Want another energy policy with positive economic implications? Make single-phase lighting illegal for businesses with ceiling heights above 15 feet. Three-phase power at 380 or 440 volts is more efficient, requires less copper, and saves money overall. Once you have it in place for lighting it's a no-brainer to also use it for electric motors, where the savings are HUGE. The financial payback period for such conversion is under two years, which is an imputed annual interest rate of 50 percent. What investment can you reliably make that pays back 50 percent year after year after year?

    Still no government money has been spent.

    Take this a step further and require all new residential construction to use 380V three-phase power for EVERYTHING, which is to say turn the U.S. into Europe, where homes already use less power for the same level of service because of three-phase efficiency. Now this is a big change, of course, because it means getting all new electric appliances, TVs, everything. What's wrong with that? It's not like the products don't exist, since the same manufacturers are already making them for sale in Europe. Market expansion leads to lower prices. Swapping out 10 percent of the U.S. appliance market per year ON TOP OF NORMAL ATTRITION would create a huge boom in electronics and electrical goods. Okay, maybe this one will cost some money, but no more than those $40 digital decoder subsidies the government is already handing out.

    These are just a few examples of what can thoughtfully be accomplished. There's a natural role for government here and that's setting rules. They are good at that. Government hasn't always been as good at enforcing rules as setting them, but that doesn't mean rules aren't worth having. Let's just set a few new ones that make sense as we recover and rebuild after the economic fire to come.

    12 min
  • Door Number Three

    I’ll begin this third and (I promise) last column on IT management with a confession: I have been fired from every job I have ever held. This is certainly not something I set out to do, nor did I even realize it until one day my young and lovely wife mentioned that I had never told her about voluntarily leaving any position. It’s not that I’ve had so many jobs, either. This one and the one before it have kept me going for more than 20 years. But they always seem to end the same way. This one might, too. You can never tell.

    Most of the times I have been fired it’s because I’ve been judged to be unmanageable, which is to say I won’t shut up. The ultimate reason given is usually something minor. The last time around, for example, I was fired because I didn’t transfer the cringely.com domain to my employer. They asked me to do it and I said “no.” Had they said, “Transfer the domain or you will be fired,” I might have decided differently. But they never said that — never gave a hint of the consequences — so I assume the real goal was less to get the domain and more to get rid of me.

    The guy who had me fired, Stewart Alsop (maybe you’ve heard of him), ultimately lost his own job for firing me, at least according to International Data Group Chairman Pat McGovern, who told the story to 300 people once at a DEMO conference.

    Back when I was a kid and working at WWST Radio in Wooster, Ohio, I was fired for writing those seven unspeakable words in the middle of a livestock auction report. Another kid had been playing similar tricks on me for weeks, but when I finally retaliated he turned me in. I guess I was a threat to him and didn’t know it.

    One company hired and fired me three times and another company hired and fired me twice. And somehow in all this I’ve never received severance or unemployment compensation. I just found another job or it found me.

    There’s a point to all these firing stories and they actually do relate to IT. I’m typical of a lot of IT types. You know us. We are useful but sometimes a pain in the ass. We have opinions and speak our minds and don’t suffer fools at all. We stand up to authority from time to time. Sometimes we’re wrong. We get fired a lot and hired a lot, too, because we are generally useful, though dangerous.

    What do you do with folks like me if you are a manager? At a traditional newspaper you’d either fire me or make me a columnist. And, sure enough, look where I am. In an IT shop you give me a task to do and let me do it, generally on my own, and never EVER put anyone under me, because I am hopeless as a manager.

    But it turns out I’m not so bad as a leader.

    Weird, eh?

    The last two columns have shown that IT is the Cousin It of American industry. We serve the company but often don’t feel part of it. Certainly the value structures and lines of authority that function perfectly well for most of the rest of the company don’t work at all well for IT. We’re vital but at the same time, well, so different that it’s hard to imagine a CEO emerging from the IT ranks. It happens from time to time. Everyone points to John Reed, who rose from IT to CEO of Citicorp, but Reed was an exceptional case. He succeeded because his predecessor, Walter Wriston, had an unusual interest in IT and mentored Reed. Reed succeeded, too, because he didn’t really come from IT but from Data Processing, which was more hierarchical. And ultimately he didn’t succeed at all, by some measures, because John Reed was fired.

    So right now let’s just accept that it is very unlikely that, coming from IT, you’ll ever become the CEO of your company. That means you are instantly off the traditional management track and have the option of either eventually moving on to some other organization or taking what’s behind Door Number Three.

    Remember Door Number Three from Let’s Make a Deal? It could reveal a sports car or a donkey, but whatever was behind Door Number Three was unlike anything you could imagine.

    We need a Door Number Three for IT professionals.

    I have a friend of 20 years who is in a key technical role at a very large company. He’s too vital to the company to risk losing but too geeky to fit in. He’s on the craft (non-management) salary scale, but way higher than he ought to be for having no direct responsibility. All he does, in fact, is from time to time save his company from ruin. And even more rarely, he saves all the rest of us from ruin, too, in ways I am not at liberty to explain. How do you manage such a guy? Where he works they have him report to the CEO. The Big Guy has 5-6 direct reports and one of them — my friend — doesn’t manage anyone or anything.

    THAT’S Door Number Three.

    We’re in an important transition period not just for IT, but also for business in general. Everything seems to be in flux. And that means the old ways of doing things are changing and ought to. And in this way IT is leading — or ought to lead — the way. Later this week I’ll be making a dramatic shift and proposing the Cringely Energy/Economic Policy, but first I need to drive home the point that, however different it is from the rest of the company, IT is generally the vanguard for a new corporate culture and whole new ways of doing business for the world.

    We’re in a mess. The world is screwed up and some of that can be traced to the improper use of IT as a financial weapon. But the people of IT actually present many of the answers we need, because they are living much deeper in technology than other parts of the company or of our society.

    Think about it. There has nearly always been a class of eggheads showing us a path toward new business models, whether it was Edison and Firestone, Hewlett and Packard, Noyce and Moore, Gates and Allen, or Brin and Page. It takes in each case a generation to happen, but ultimately we all (and I mean ALL — everyone in the total organization) come to look like the geeks of the generation before. So let’s lean into that, get on with the transition, and get past this place we’re in right now where nobody wants to be. Let’s consciously embrace the next model that’s generally running fitfully right now inside every company, down in the more functional parts of the IT department.

    What I mean by this is that times have changed and the world can no longer afford even John Reed’s world view with its needs analysis, design, debug, test, rollout strategy — whether we’re talking about a new app or a new marketing campaign. By the time the app (or the campaign) is rolled out, the world changed from HTML to Javascript/SOAP/Ajax (or from financial regulation is bad to financial regulation will save us).

    At the heart of this is a concept completely foreign to traditional business — Open Source. What the open source community has demonstrated is the superiority of a strategy that emphasizes early proof of concept, early release, and frequent releases with features added as needed — probably totaling 20 percent of the features identified in a needs assessment.

    This is the new IT strategy we live with every day — 80 percent solutions because they are fast, increasingly reliable, and keep the end users in the loop from almost the beginning. All made possible because of an open Internet (at least until Comcast succeeds and enslaves us), easily grasped standards and impressive demonstrations by companies like Amazon, Google, Facebook, and a ton of start-ups. Wall Street back offices figured this out long ago, they just never got their boss’s bosses to understand.

    Last week’s column was a utopian vision that simply requires all the old managers to be reprogrammed or accept a bullet in the head. But it is not at all utopian if applied solely (or initially) to IT, where this stuff actually works pretty well.

    IT people are most of the time building fortresses or feeling unappreciated — often both at the same time. Yet to our discredit, we’ve done a very poor job of explaining or demonstrating or outright selling our utility to the broader organization. Where are our Geek Appreciation Days? Take a Geek to Lunch? Bring Your Geek to School? Taciturn, we disparage our co-workers for not appreciating us while giving them little obvious reason why they should appreciate us.

    That has to change.

    Door Number Three isn’t just an escape hatch for nerds, it is the way business and culture and civic life will be for most of us a generation further into this information age. We’re just leading the way. And if we’re leading the way let’s embrace that role and become leaders.

    If, like me, you are likely to be fired, anyway, there’s no real downside to this strategy. Let’s give it a try.

    10 min
  • Leadership

    Last week’s column on bad IT management and the strong response from readers that followed show this to be a huge issue. There are WAY too many IT managers who either can’t or shouldn’t manage technical teams. Last week I maintained that having a firm technology base, or at least the ability and willingness to acquire one, was essential for good managers. While readers got carried away with which technical test is the best, I don’t think there is much dispute that there are certain aspects of technical management that are helped by the manager being a code god. But that’s far from all there is to the job. So this week I want to go deeper and look at what’s really missing in nearly every instance of such bad management, which is leadership.

    The distinction between management and leadership is a critical one. Management is — at its very best — an exercise in coping while leadership is so much more. Last week’s simple idea that the manager ought to at least be able to tell good work from bad is exemplified by Bill Gates, who liked to claim that he could tell good code from across the room and that whatever task a team was facing was something he could code in Visual Basic over a weekend. Both statements are nonsense, of course, but Bill knew he had to talk the talk, making him at least an adequate manager.

    Does it make him a leader? I don’t think so. But let’s not blame Bill for that. Let’s blame Charles Simonyi.

    Charles is the guy who came up with Microsoft’s development process — an outgrowth of his research at Xerox PARC. I covered this extensively in my book, Accidental Empires, but the short version is that Charles came to advocate a strong program manager as the central controller of any development group. One person made all the decisions and as long as that one person was correct 85 percent of the time, it was better to have a dictatorship than a democracy or even a meritocracy. This was an effective way to extend Bill’s will to Microsoft programmers Bill would never even meet. And to Charles’ credit the system worked well enough if the dictator was really, really smart and the task at hand wasn’t too complex. It was perfect for the 1980s.

    But it is far from perfect today and represents one of the fundamental reasons why Windows Vista was so late to market and such a mess when it finally shipped. Vista had plenty of management, but not very much leadership.

    When I think of leaders what comes to mind first are political and military leaders. We use the term “leadership” to describe those roles far more than we do for what ought to be similar roles in business or technology. This week former Hewlett-Packard CEO Carly Fiorina said that John McCain, Barack Obama, Sarah Palin, and Joe Biden were all ill-suited to be CEOs of major corporations. However badly the statement went over (Carly supports McCain, by the way), her real point was that there are different skill sets for leaders than managers. And she’s right to an extent, but it also says a lot about her own tenure at H-P, which was long on management and short on leadership.

    Management is telling people what to do, which is a vital part of any industrial economy. Leadership is figuring out what ought to be done then getting people to do it, which is very different. It is a vital part of any successful post-industrial economy, too, but most managers don’t know that.

    Let’s use the U.S. military involvement in Iraq as an example of the difference between leadership and management. As more books are written and stories come out we can see that there is a lot of arguing that goes on inside the military. Officers are onboard or not. They are proposing various strategies and taking positions generally advocating what’s perceived as safest for both the mission they have accepted and the preservation of life among their troops. Eventually someone makes or imposes an order, but even then there is a lot of second-guessing in the military, which has to be ready with Plans B through G just in case they are needed. This is a lot different from the image many of us have of General Patton pointing toward Berlin, imposing a singular view and forcing it through.

    In contrast to the military, most businesses do a lot less explaining and pondering and a lot more laying down edicts. That’s management, which works fine on an assembly line, but not at all well building a big software application or winning a war.

    Janna Raye is someone I worked with at InfoWorld half a lifetime ago who has built a consulting career on understanding this stuff and helping companies to transcend 20th century corporate hierarchies and become what she calls “fractal organizations.” Janna’s consulting business is called Strategems and here is her take on this issue:

    “Modern corporations suffer from systemic-level issues that emerge in top-down hierarchies. Managers are there to control staff and budgets, not to lead. Although you can make valiant and often successful attempts to control things and processes, you will never again be able to control people. We’ve evolved, basically, and the information age has had a lot to do with it. So we still “manage” companies the same way as when we actually operated assembly lines in America—the good old days! Now, people need leaders, not managers, and that’s what a fractal organization enables.

    “In fractal organizations, it’s the staff deciding how to continuously improve processes in their functional areas for efficiency of time and resources. These organizations thrive with a new pay model also, based upon results or value of work delivered and not how much time it takes to do the task. Those who are really good will get to go home early! These are not the organizations that are shrinking. Like galaxies, they continue to expand, actually aided by a strong gravitational pull of the leaders at the center. Those who do it well create a compelling vision and keep it alive. They allocate resources to projects that align with the vision, and reward arm- and team-cluster leaders for the creative ideas their staff bring to the organization. It’s a shared vision and collective goals that are missing from the vast majority of organizations, which is why failing projects continue to drain resources. Really caring about what you do and feeling proud to be a part of something special and wonderful is what every human desires, even if they say they don’t.”

    So what’s Janna’s model for the ideal 21st century organization? Pixar.

    “They let creativity run wild at Pixar!” says Janna. “Ed Catmull, Pixar’s president, wrote an article for the Harvard Business Review on their collective creativity. Ed and John Lasseter (and sometimes Steve Jobs) are in the center of the galaxy, keeping the gravitational pull strong and the company rotating, so to speak. Around them are the directors, who in the fractal org model lead the arms (no more divisions!). Each film team or cluster, from the storyboard artists to the renderers, goes through the iterations necessary to achieve the best results. Everyone is on board with creating exemplary films and they are relentless in demanding only the best. But in this process, as they say, they have to get all the “sucky” ideas out first. If they don’t reveal all the ideas, they don’t get all the perspectives and therefore might miss something important. In quantum physics and information theory, this relates to the observer effect and the importance of acknowledging the perspective influence of everyone in a scene.

    “In top-down hierarchies, the opposite occurs, yet the people on the front lines are the ones dealing with the evolutionary changes going on around them and are the best source of ideas for solving tactical issues. You wouldn’t need “change management” if you made continuous improvements at the functional level the responsibility of every individual and team cluster. Yet Pixar makes incredible films in this manner, so you could certainly accomplish it anywhere, even in a supermarket! In fact, some of Whole Foods’ leadership practices are fractal — in-store teams make decisions about products and their placement, based on their observations of customer patterns.

    “Most start-ups are fractal in their nature, especially those that have exciting visions and get everyone on the same page with collective purpose, goals, and objectives. Most investors, however, are bought into the conventional org chart; when the company devolves into top-down, the turnover begins. That’s because of the internal competition that emerges in top-down organizations. The perception is that there’s only so much room at the top. At each level of management, the competition increases as cooperation decreases. Thus are created the ubiquitous “silos” of information that thwart collaboration and encourage redundant, wasteful business practices.

    “Managers are supposedly promoted because of their ability to outperform others and not because of an intention to provide inspiration, guidance, and mentoring to their staff, nor are they openly rewarded for this behavior, even though it usually produces a healthier bottom line. The usual way of rewarding based upon meeting financial goals and managing budgets keeps the focus on short-term financial results only, whereas continuous improvement leadership by frontline staff creates more long-term successes.

    “When managers don’t mentor staff, focusing only upon numbers and bossing people around, it leads to an illusion of control, of which there’s no such thing. In these situations, they begin to feel they must continually prove their worthiness and so defend their territories against possibly brilliant staff working “beneath” them. This is a systemic issue, not a personality quirk, though some personalities are more susceptible than others. In most companies, the idea of climbing over others on your way to the top and throwing people who get in your way under buses is de rigueur. The top-down hierarchy was designed to manage industrial-age processes, not information-age challenges. You didn’t want the door guy getting creative when attaching the door. Nor did he need to collaborate with the bumper dude. The information age is vastly different. Each scene we’re in presents new circumstances and opportunities.

    “Pixar claims they have a meritocracy. This is a good description of the atmosphere that emerges in fractal organizations. Google was likely more fractal in the beginning, before they brought in managers trained in top-down hierarchies and engrained with the accompanying behavioral patterns, such as knee-jerk resistance to ideas they haven’t thought of themselves. Not everyone is like this, of course, but usually those who aren’t have had confident mentors themselves who encouraged creative participation. In Catmull’s HBR article, he says they insist that everyone in the company contribute ideas, across all functions and levels, or they will perish. Interestingly, he mentions the difficulty in getting new hires to feel comfortable with this process. This results from cultural-level systems that keep people in competition rather than cooperation. Though Catmull tells readers what they do at Pixar and why, he doesn’t instruct on how to make the organizational changes that enable this approach to creativity.”

    I guess that last part is Janna’s job.

    All this fractal stuff is interesting, but I’m guessing it is also difficult to implement, because it may describe Pixar but it DOESN’T accurately describe Apple — the other place where Steve Jobs is king. Still, Apple’s product success shows that something is being transferred from one company to the other. It’s just that at Apple, Steve Jobs can’t make himself stay out of the way.

    13 min