Respond Flawlessly to MEDITECH Report Writing Requests
My attitude towards new MEDITECH projects over the years, has ranged from grandiosity (nothing will go wrong) to a chicken little approach (you want what by when?, and 10 reasons that's not going to be possible). If only I'd heard of and followed Brad's advice instead.
Here's a scenario from a database administrator's (DBA's) world we can glean lessons from and apply in our role as MEDITECH report writers:
You have just found out that management wants to upgrade all 350 SQL Servers instances from SQL Server 2005 to SQL Server 2008, by the end of the quarter. Rather than immediately raise objections, the Exceptional DBA will scope out the project, create a plan, and put it into effect as soon as possible. If the DBA determines, after scoping, that it is impossible to complete the job in time given current resources, then he will determine what additional resources are needed and present his findings to his manager.
Instead of quietly proceeding with impossible deadlines or iterating all the reasons something isn't possible, you and I have a 3rd option: scope out the new project with necessary resources to achieve the proposed deadline and present our findings back to the requester. If the necessary resources are in place, proceed with next steps. If more resources are needed, simply presenting that back to the requester is a flawless response on our part. The situation may require you to begin with out the necessary time and resources, yet by scoping and presenting the facts we can rest assured knowing our actions have been perfect in spite of the circumstances.
Scenario Reference: How To Become An Exceptional DBA by Brad McGehee
Want an alert when the next post is published? Click the phone and Subscribe to the MEDITECH Reports Blog!
