Tag Archives: project management

Power of a PMO

Posted by on

Many organizations have a Project or Program Management Office (PMO). If not at an organization wide level, at least within the IT department. There are different models. Some PMOs provide standards, tools, canstockphoto10610367methodology and overall tracking. Others provide this foundation as well as a team of project managers (PMs) who can be assigned as needed to major projects. Our PMO at University Hospitals is the latter model.

Our PMO has evolved under our new manager, Joe Stuczynski. He and his team are making significant improvements with the support of IT leadership. They have developed a roadmap for further changes and improvements for the next year.

It is refreshing to be in an organization where we are not debating about the tools and whether they are good enough. We are not debating about what projects need to run through the PMO and if everyone needs to follow the standards.

Instead, we are embracing and leveraging the tools and the PMO is able to focus on what it should be – tracking projects and providing PMs to manage projects. Continue reading →

What upgrade?

Posted by on

This past weekend we did another major upgrade – this time the ambulatory EMR. It went extremely well and was met with smiles and kudos from our senior executives. While we’ve done several major upgrades canstockphoto13469755recently including revenue cycle and acute EMR, this one had a lot of eyes on it. Those same senior executives have been rightly concerned about the performance of our ambulatory EMR while we worked through some significant issues during the past several months, including software, hardware and infrastructure. So, kudos to the team that turned the corner on those issues and pulled off a very successful upgrade with minimal issues and disruption to our physician providers and operational practice teams.

We called our 200+ physician practices before the upgrade to make sure they felt prepared.  A few actually said “what upgrade?”. Apparently they had not read the any of the advance communications. So we worked with each of them to make sure they were ready.

The command center was open all week and will close early today as we have fewer and fewer calls.  Over 62% of the reported issues had been resolved as of late yesterday. Our users gained a lot of new functions and features which has made everyone happy.

In addition to a strong and collaborative relationship with your vendor, here are some critical success factors for any major software upgrade: Continue reading →

Who’s on first?

Posted by on

Picture this. One of your IT leaders tells you they have been pulled into a project by a senior executive; they are trying to figure out who in IT owns it. You tell them that another of your leaders owns it. They arecanstockphoto2538045 working out the specific issues with yet another leader. The first person says it’s still not clear. So you pull all three of them together for 15 minutes and try to sort it out.

With a collaborative team that works well together, that 15 minutes is relatively easy. Your first question is who’s on first? You want to know who owns it and what’s going on.

My team has learned that one of my questions about problems is “who wakes up in the morning worried about it?”  Not that I want people worrying and losing sleep. But, it’s a way to identify who owns something and is accountable for it. “Who’s on first?” is another one of those questions. It may be a messy, complex project. It may be off to the side or on the fringe but it still needs a clear owner.

After just 15 minutes, my three leaders and I confirmed the right roles for each of them, and next steps. And of course we talked about lessons learned. So what did we learn again in this situation?

Role clarification – this is critical for all projects, small or large, high priority or not. Clarifying and communicating sponsor, business owner, project manager, and decision makers is key.

Communication – proactive communication throughout the life of a project to all members of the core team and the stakeholders is another key.

Setting and managing expectations – this is especially true when dealing with many concurrent efforts with the same set of users and stakeholders. It’s also important when a project that seems simple actually has a lot of complex issues:  technical, operational, legal or something else.

I’ll bet you can think of a messy project in your experience that swirled or stalled. You might have some bad memories. Most likely, what went wrong ties back to one of these basics. So clarify roles, communicate, and manage expectations, but make sure you know who’s on first.

Keep it simple and visual

Posted by on

CIO Board 11-2015The past month has been a particularly busy one for me. I have spoken locally a few times and gone out of town on business several times as well. I’ve been to the CHIME Fall Forum, made a site visit at Duke, and attended an AAMI board meeting. During that same period, I’ve given a talk on “Women in Technology” and participated on a CIO panel at the Midwest Fall Technology Conference in Detroit. I spoke on “High Impact IT” at the 2015 ICHITA Conference sponsored by the Center for Health Information Technology Advancement at Western Michigan University in Kalamazoo. I was one of two CIO guests on the CIO TalkRadio Show last week. And we published our monthly newsletter and held one of our twice a year department all staff meetings.

I have a busy schedule of meetings at multiple UMHS locations every day, so how did all these commitments come off without a hitch? The visual board my support staff and I started some weeks ago has made the difference! The only commitment that I scrambled on at the last minute was the one that hadn’t made it onto the board. That’s telling.

Prior to our visual board, I sometimes scrambled at the last minute to finish a presentation or finalize flight arrangements in time to get a reasonable price. Now, as a team, we can see into all the major events and commitments and take an organized approach to the shared tasks involved.  Continue reading →

Plans, processes, people: lessons from a successful EHR implementation

Posted by on

I had the opportunity to talk about lessons learned from EHR implementations as part of the faculty for the “Leadership Strategies for Information Technology in Health Care” course at the Harvard School of Public Health (HSPH) last week.  And yes, I was fortunate to make it in and out of Boston between snowstorms for the one day I was there.

The course is part of Executive and Continuing Professional Education at HSPH. It is a two week course with 4 modules.  The first week covers Module 1 on IT Strategy and Governance and Module 2 on the EHR.

The faculty lineup for the first week is impressive.  John Glaser, CEO Health Services at Siemens Healthcare and former CIO at Partners HealthCare System, lectured on “IT Strategy Considerations.” John Halamka, CIO at Beth Israel Deaconess Medical Center in Boston covered “The National Perspective and IT in the Era of Health Care Reform.”  Vi Shaffer, Research Vice President and Global Industry Services Director at Gartner, provided an “Overview of the IT Industry.” Meg Aranow, Senior Research Director and Health Care IT Advisor at The Advisory Board Company, discussed analytics. New care models including telehealth, retail clinics, and accountable care organizations were also covered by various faculty members.  Mary Finlay, Professor Simmons School of Management and former Deputy CIO at Partners, discussed IT Governance. Mary is the program director for the course and does a terrific job.

Students come from various roles in health care. The course has also become well known internationally at this point – with about 30% from other countries. For this session some students came from as far away as Australia and India.

I was happy to be part of the faculty and get a chance to hear a few other lectures that day as well as interact with the students over lunch. Here are some of the EHR implementation lessons I shared in my talk:

  • The CIO and executive leadership in health care organizations have many priority initiatives at any given time. The EHR implementation will become a primary focus, especially as it gets closer to the go live date. As the CIO, you need to know where and when to be deeply involved vs. maintaining an overall awareness of the project’s progress, being ready to address issues as they are escalated.
  • Engaged executive sponsors are needed throughout the life of the project. If the CIO is the only one worrying about the project, there’s something wrong. At the same time, the CIO should avoid saying “it is not an IT project”. To be successful, it has to be a true partnership between clinicians, operations, and IT.
  • An EHR implementation has a significant impact on your entire organization and all staff members. A robust change management program is critical given the multi-disciplinary effort that EHRs require.
  • Many decisions get made through the life of the project. Establish early on very clear decision rights. Know which group makes what decisions and define the escalation path when issues can’t get resolved at lower levels of the project governance structure.
  • Your plan should include a “Go Live Readiness Assessment” at 120, 90, 60 and 30 days prior to go live. All teams are expected to report out their progress and open issues in detail. Project leadership then creates a readiness scorecard. This allows leadership to focus on the areas that are behind schedule and address issues to ensure an on-time, successful go live.
  • Contingency planning needs to be part of the overall plan. Any major system implementation needs a back-out plan if something goes wrong. But you also need to account for the operational impact. You can’t stop the flow of patients into the emergency room but do you reduce your surgical or clinic schedules? Each organization has to determine what’s right for them. And then there’s the unrelated and unanticipated crisis that you have no control over – it could be a major facility issue like a power outage, a weather incident like the snowstorms we’ve seen the past few weeks, or a mass casualty incident in your area. Be sure to include your organization’s emergency management team in your activation and contingency planning.
  • At go live, it’s all hands on deck in the command center and throughout the organization. Everyone has their specific roles. Leaders need to be present. The CIO may not be running the project but maintains a very visible presence in and around the command center. It’s a 24/7 operation for the first few weeks after go live. And be sure to round – find out how things are going for front-line staff and thank them for their work.
  • Once the system is up and running, you have to recognize that optimization is ongoing. Don’t minimize the requests. Listen carefully to your users. At the same time, manage expectations about how much will get done and by when. Help shape the message. Multiple communications channels are important. Structured processes for intake of requests and a formal prioritization process with agreed upon criteria are critical. While optimization for your organization and the unique workflows is needed, don’t get stuck there. Learn from others how they have leveraged the product. Reach out to your colleagues and learn from them. Many have gone before you at this point.

And when you’re ready, be sure to share your own lessons with others.

 

Resources 

Harvard School of Public Health’s Executive and Continuing Professional Education program, “Leadership Strategies for Information Technology in Health Care”

Related posts

Three Days and Counting. . .

Values in action. . .

MiChart summer interns – a win-win!

Operation Baby Blanket

Posted by on

Operation Baby Blanket? What’s that? Is that the code name for a new software implementation?

This CIO is the grandma of Hannah, an adorable two year old; two more grandbabies are on the way.  While I’ve done various crafts in my adult life, I don’t do it enough to call it a hobby. And my crochet experience is limited. I did make a baby blanket for one of my daughters 30 years ago.

So I surprised my family two years ago when I told them that I would make a baby blanket for Hannah, and I actually did it. Now, a second grandchild is due in December. Could I make a baby blanket for her in time? Would I be able to squeeze enough time out of my evening email work session to get one done?

I needed to design and create a baby blanket in time for the baby shower.

I am happy to announce that I presented a finished crocheted baby blanket to my daughter, Katie, at the shower last weekend.

How did I meet this goal? Basic Project Management! Continue reading →