Pigeon Project Management Office (PMO)

1906_Whittling_Webster_adx

I just finished stacking two cords of wood, much like a squirrel getting ready for a long cold winter. My feet were doing the “Boy is it cold dance” in an effort to keep the blood circulating.  As I was picking up the scraps, my eldest picked up a piece and placed it in his backpack. When I asked him what he would do with it he told me he was going to carve it after school. His statement brought back boyhood memories of hours of whittling, an activity done if for no other reason than to get from one minute to the next. Grab a stick and whittle it away until there was nothing left.  What next? Grab another. The weight of the pocketknife felt equally good in my hand as it did in my pocket.
When is the last time the thought of whittling crossed your mind? Probably been a long time. It’s an activity meant for idle minds and hands, or minds that should be idle. There are times I find myself questioning what value so and so brings to the party. Do you do that?  “Why is she in this meeting?”  You know who I mean.  You’re sitting there trying to get your work done and all of a sudden, some Mensa wannabe with more idle time on their hands than a Lipitor salesman at a BBQ cook-off, makes an aerial assault on your cubicle like a pigeon on a Rodin bronze.  Drops in and changes the rules of the universe, at least your universe.

This happens more often than is documented on large healthcare IT projects.  People set new courses and define programs rules that may have nothing whatsoever to do with the project’s charter or scope.  You do have a written charter and scope in the project office, don’t you?  If not, it’s easy to see how new directions and rules can be given a certain specious authority.

What’s the best way to handle this situation? Often these management Mensas are nervous about a lack of visible results and they need to report on something.  They may feel the need to be doing something, something resembling leading.  They don’t mean to interfere, and they believe that their little forays into the world of super PMO (Program Management Officer) will actually add value. You tell me, are they adding value, or are they preventing the team from sticking to the scope? There’s that irritating scope word again.  The next time you see one wandering aimlessly through the rows of cubicles, hand that person a pocketknife and a nice piece of balsa wood.  Although their efforts won’t add any value to what you’re trying to accomplish, at least it will get them out of the way for a little while.

saint

EHR leadership isn’t always a democracy

CocoaPuffs

Cerealizable.

That’s my new word. I coined it the last time my wife was traveling and I was in charge of breakfast and making sure nobody missed the bus. Cerealizable is what happens when you walk into the kitchen and are confronted with two hungry dogs, three hungry kids, hair that needs brushing, homework assignments that need to be reviewed, and lunches that have to be packed.

Breakfast orders are shouted at me across the room as though I’m their short-order cook; pancakes, French toast, sausage, and who knows what else. What does one do? I was quickly headed down the path of self destruction, too many tasks and not enough taskers. I needed a light at the end of the tunnel and so I created one. I cerealized the problem; simplified it–turned into something I could solve. Go to the pantry, pull out the cardboard cereal boxes, three bowls, three spoons, and the gallon of milk. Check off breakfast.

In case you’re wondering, Cocoa Puffs still turn the milk brown, just like they did thirty years ago. Lunch orders began to be shouted across the bowls of cereal. Ham and cheese, PB&J, tuna–extra mayo, no celery. Once again small beads of perspiration formed quickly on my brow. For a moment I considered calling the school and telling them that all three were sick. That would solve the lunch problem, but it would also mean that the three of them would be home all day–my own private hostage situation. What to do? My coffee remained out of reach, still untouched. That explained the pending headache. Back to lunch. Cerealize it. “Everyone is buying lunch today,” I announced above the roar.

A half hour later, the din had subsided. I made a fresh cup of coffee and collected my thoughts. What had I learned from the exercise? Three things. One, some situations require leadership. Two, three children and one grownup is not time to establish a democracy. There is no Bill of Rights. To quote Mel Brooks, “It’s good to be the king.” Three, break the problem down into bite-sized pieces, don’t try to swallow the elephant whole.

That same approach works just as well with EHR grownups; clinical grownups and IT grownups. Improving the interaction takes leadership. Large, institution-changing projects involve pulling people out of their normal routines and relationships.  Solving problems will not involve a kumbaya moment–Program management is not a democracy. To succeed, the program champion, having created a vision, will have to break it down into bite-sized pieces.

saint

Healthcare Informatics: one time at band camp…

band

Here’s a response I posted to a Healthcare Informatics article, by Mark Hagland, “Revenge of the Clinical Informaticists”.

The link is: http://healthcare-informatics.com/ME2/dirmod.asp?sid=349DF6BB879446A1886B65F332AC487F&nm=&type=Blog&mod=View+Topic&mid=67D6564029914AD3B204AD35D8F5F780&tier=7&id=5E2E36E45CB54ECA8D2B08DC3E4D679C

I wrote the following:

I wrote on this same topic yesterday, albeit with a slightly different bent.  Like you, I see two distinct groups who do not play well in the same sandbox—clinical and IT.  Having one group go to the other’s summer camp to pick up a few skills is not the same as pulling a few costly and hairy projects from the bowels of project hell any more than it would be to have an IT executive take an EMT course and then assume that person was qualified to perform surgery—this one time at band camp…

Before I get up on my stool and knock myself off, I know CMIOs and CIOs who have made HIT and EHR very successful.  To them I ask, do not rake me across the Twitter coals as I try to make a point.

There’s knowledge, and then there’s qualified.  Doctors do four years of medical school, they intern, and if they specialize, they throw in a few more years before they become the in-charge.  Years of training and practice before the doctor is allowed to run the show.  Why?  Because what they are about to undertake requires practice, tutelage, and expertise.  Most of the actual learning occurs outside the classroom.

There are those—not Mr. Hagland—who suggest that the skills needed to manage successfully something as foreboding as full-blown EHR can be picked up at IT Camp.  They do a disservice to seasoned IT professionals.

Most large IT projects fail.  I believe large EHR projects will fail at an even higher rate.  Most clinical procedures do not fail, even the risky ones.

What’s the spin line from this discussion?

  • Rule 1—large EHR projects will fail at an alarming rate
  • Rule 2—sending a doctor to band camp probably won’t change rule one

Don’t believe me?  Ask friends in other industries how their implementation of an ERP or manufacturing system went.  There are consulting firms who make a bundle doing disaster recovery work on failed IT projects.  They circle the halls like turkey vultures waiting for CIO or project manager carrion.

Back to Rule 1 for a moment.  How can I state that with such assurance?  Never before in the history of before—I know that’s not a proper phrase—has any single industry attempted to use IT to:

  • impart such radical charge (patients, doctors, employees)
  • impart it on a national basis
  • hit moving and poorly defined targets—interoperability, meaningful use, certification
  • take guidance from nobody—there is no EHR decider
  • implement a solution from amongst hundreds of vendors
  • implement a solution with no standards
  • move from an industry at 0.2 to 2.0 business practices
  • concurrently reform the entire industry

Just what should a CMIO be able to do?  What are the standards for a CMIO?  To me, they vary widely.  Is a CMIO considered an officer in the same sense as the other “O’s” in the organization, or is it simply a naming convention?  The answer to that question probably depends on the provider.

Here’s how I think it should work—I realize nobody has asked for my opinion, but this way I’ll at least provide good fodder for those who are so bold as to put their disagreement in writing.

I love the concept of the CMIO and think it is essential to move the provider’s organization from the 0.2 model to the 2.0 model.  Same with the CIO.  However, getting them to pool their efforts on something like EHR is likely to fail as soon as one is placed in a position of authority over the other.  It’s sort of like getting the Americans and French to like one another.

I liken the CMIO’s value-add to that of the person providing the color commentary on ESPN—it adds meaning and relevancy.  The CMIO owns and answers a lot of the “what” and the CIO owns and answers a lot of the “How”.

Still unanswered are the “Why” and “When”.  A skill is needed that can state with assurance, “Follow me.  Tomorrow we will do this because this is what needs to be done tomorrow.”  That skill comes from an experienced Project Management Officer, the PMO.  It does not come from someone who “we think can handle the job.”  Nobody will respect that person’s ability, and if they can’t lead, yo can plan on doing the project over.

Oh, if anyone is still reading, here’s my original post; https://healthcareitstrategy.com/2009/09/28/what-should-be-the-role-of-the-cmio/

pastedGraphic.tiff.converted