Monday, August 22, 2011

Classic & Contemporary Lessons Learned - For Your ICD-10 Project (Part 3)

Here’s Part 3 of my on-going, multipart series on Classic & Contemporary Lessons Learned.

See Part 1 here and see Part 2 here.

1.       Spend time to think through resource requirements and their on-boarding process. Try not to bring resources on too early – or too late. Make sure you have the right resources in targeted roles and that their roles and responsibilities are defined, assigned and able to be measured BEFORE they start.

{All people are NOT interchangeable!  And all people generally want to do a good job!}

2.       Recognize and plan for the challenge of simultaneously maintaining legacy platforms and non-ICD-10 projects while advancing your ICD-10 efforts.

{In my opinion, this will be one of the most challenging aspects for ICD-10 compliance projects.}

3.       Identify simple ways to leverage virtual conferencing, instant messaging, content tagging and social media distribution channels into a content management system. Require and support project stakeholders to persist and leverage knowledge as it is acquired and clarified.

{Build your corporate knowledgebase and intellectual capital!}

4.       Keep direct and indirect stakeholders up to date on what’s going on.  Post major milestones, activities, issues and risks for all stakeholders to be kept up to date on a regular basis. Consider how to highlight successes and request ideas to mitigate issues and risks.

{Err on the side of over-communication so as to avoid confusion and the “but no one told me” toward the end of your project.}

5.       Create a means to report status to executives and other leads with as little overhead expended by those originating the information as possible.  Start out with a “less is more’ approach – Capture status as events occur - you can always add to your reports later based on feedback from consumers.

{Capture status as events occur - status reporting as merely an administrative task is worthless}

Simple ideas, eh?  Check back for Part 4 of this multipart series.

No comments:

Post a Comment