At the end of the case, Sadlemire observes, “This project sometimes plays second fiddle to other projects that I believe are less critical.” What “other projects” do you think he is referring to here? What advice would you give Sadlemire to help him address this issue of conflicting priorities?
Reader Interactions
Comments
Leave a Reply
You must be logged in to post a comment.
Other Projects” Referenced by Sadlemire
Sadlemire likely refers to:
1. Basic Infrastructure Initiative ($17M network/PC upgrades) – Diverted IT resources (e.g., Eary’s team delayed Y2K work for Windows NT migration).
2. Telemedicine & Regional Network ($13M) – Prioritized “future-focused” tech over urgent Y2K fixes.
Advice for Sadlemire
1. Reallocate Resources Temporarily
-Propose a “Y2K Sprint” (e.g., pause non-critical infrastructure work for 3–6 months). Cite IDX’s 5-month delay (Page 3) as precedent for timeline slippage.
2. Leverage External Pressure
-Share Gartner’s $600B global cost estimate (Page 1) and VHA’s findings (Exhibit 6) to justify urgency. Frame Y2K as a reputational risk for the board.
3. Simplify Departmental Compliance
-Replace lengthy questionnaires (Exhibit 5) with targeted audits for high-risk areas (e.g., billing, life-support devices). Offer IT support to streamline fixes.
To resolve the project priority conflicts, the projects that conflict with the Y2K project include infrastructure upgrades, the Meditech clinical system migration, and the regional information network construction. To resolve these conflicts and elevate the priority of the Y2K project, the first step is to present to senior leadership the severity of the potential issues that would arise from Y2K project failure, such as the legal liabilities and financial losses that could occur in the event of a failure. Additionally, the Steering Committee should be asked to conduct monthly resource allocation assessments for all projects and delay the resource needs of non-critical projects, giving priority to the Y2K project’s requirements. Regarding suppliers, the audit department can be involved to review the compliance progress of vendors and apply pressure where necessary.
Sadlemire is likely referring to the “Basic Infrastructure” initiative and other ongoing projects that have been prioritized over the Year 2000 (Y2K) project. These projects include: basic infrastructure initiative, IDX project, peoplesoft conversion, meditech project, and so on.
To address the issue of conflicting priorities, Sadlemire should consider the following strategies:
1. Emphasize the critical nature of the Y2K problem to senior management and the Board of Trustees. Highlight the potential risks and liabilities associated with non-compliance, including disruptions to patient care, financial losses, and legal exposure.
2. Increase communication and engagement with key stakeholders, including department heads and clinical directors.
3. Advocate for dedicated resources specifically for the Y2K project. Propose reallocating resources from less critical projects or hiring temporary staff to assist with the Y2K efforts.
4. Develop a comprehensive risk management plan that outlines potential scenarios and their impacts.
Other projects may include basic infrastructure initiative, regional information network, IDX project, and so on.
Sadlemire needs to continue communicating the potential risks of Y2K to senior management and other key stakeholders to ensure they understand and support the Y2K project as part of the overall hospital strategy, including how it impacts patient care, financial operations, and legal risks. Demonstrate the consequences of failing to solve Y2K problems by providing specific case studies or simulated failure scenarios.
And establish clear project prioritization criteria and strengthen collaboration with other project teams, for example, to check Y2K compliance while working on other IT projects. Maintain effective communication with all relevant personnel, update progress reports regularly and clearly identify any delays and their causes.
As far as I am concerned, “other projects” he is referring to here are related to these areas mainly:
1. Basic Infrastructure Initiative ($17 Million);
2. IDX Project (Replacing Old HIS Applications);
3. Peoplesoft Conversion (HR and Payroll);
4. Meditech Project (Clinical Applications);
5. Regional Information Network ($13 Million);
6. Desktop Rollout and Network Upgrade.
I will suggest several methods as follows:
1. highlight Y2K risks to senior leadership;
2. align Y2K with strategic projects;
3. create a cross-departmental accountability framework;
4. develop a phased risk mitigation plan;
5. use data to drive urgency;
6. foster a culture of Y2K awareness.
Other projects include a $17 million “infrastructure” plan, which involves upgrading the Burlington network, integrating patient registration and appointment systems, developing a new patient data repository, and creating a care management information system. The $1.3 million regional information network project provides remote medical services. And the delayed IDX system migration.
I think he can explain to the senior management the consequences of not prioritizing Y2K, including the economic losses and legal liabilities caused by patient care disruptions, as well as the importance of Y2K compliance for the organization’s stability and reputation, in order to obtain the support of the senior management and the board of directors.
Other projects refer to basic infrastructure projects costing $17 million and encompassing network upgrades, new PC deployments and telemedicine systems. There are also migration projects for Meditech and PeopleSoft, which will take up some of the resources. These projects could affect the timely completion of the Millennium Bug project.
To raise the priority of the MILLennium Bug project, Sadlemire can emphasize to senior management the criticality of the MILLennium Bug project and the financial loss and legal liability to the organization if the project is not completed on time. So that he can try to get management to reallocate resources to the various projects or mobilize more manpower to join the project.
Other projects:
1. Migrate Fanny Allen hospital information system (on IBM AS 400 computer) to Medical Center platform.
2. Convert an old payroll application to MVS. 3. Replace many old HIS applications for patient admitting, billing, managed care, and medical records with
Unix-based applications from IDX, running on an Alpha6 server.
4. Convert the mainframe (MVS) payroll and human resources applications to a Unix-based Peoplesoft package, which would run an IBM RS6000 midrange computer.
5. Migrate nursing scheduling, pharmacy and other clinical applications (part of the old HIS system) to a Meditech package
6. Implement an integrated surgical application (ORSOS), a nurse scheduling system (ANSAS)
and a radiology system (IDX Rad).
Advice for Sadlemire:
1. Establish a priority matrix to prioritize the projects and ensure that the Y2K project is at a high priority.
2. Draw up a detailed schedule for the Y2K project to ensure that each stage has a clear deadline.
Communicate with the CIO of the hospital using the former matrix and schedule to ask for more resources and higher priorities. Apply for training for the staff using the hospital information system to enhance their awareness and sense of responsibility.
“Other projects” Sadlemire referred to likely included:
• Basic Infrastructure Initiative ($17M): This included network upgrades, PC replacements, and the Patient Data Repository.
• IDX and Peoplesoft Migrations: These aimed to replace legacy systems but overlapped with Y2K deadlines, competing for staff time and budget.
• Telemedicine Projects: Fletcher-Allen’s telemedicine initiatives, though innovative, were prioritized over Y2K compliance.
Advice:
• Align Y2K with Strategic Goals: Frame Y2K as critical to enabling new initiatives (e.g., telemedicine relies on functional systems post-2000).
• Secure Executive Buy-In: Escalate to CEO William Boettcher to mandate Y2K as a top priority, using the Steering Committee to enforce deadlines.
• Resource Reallocation: Request dedicated Y2K teams separate from other projects. Cite Gartner’s $600B global Y2K cost estimate to justify budget shifts.
• Phased Prioritization: Focus first on high-risk systems (e.g., life-support devices, billing) and use vendor compliance data (via VHAseCURE.net) to fast-track low-risk fixes.
Sadlemire’s “other projects” refer to the $17 million infrastructure upgrade plan, the IDX system replacement project, the Peoplesoft HR and payroll system conversion, and the Meditech clinical system upgrade, all of which have impacted Y2K-related work due to their respective priorities. To address the resulting conflicts, solutions include enhancing senior management’s quantitative understanding of Y2K risks, restructuring project management with cross-departmental priority arbitration frameworks, proactively reallocating resources, and positioning Y2K as a strategic enabling project. The core contradiction lies in the game between the visibility of short-term projects and long-term systemic risks, with the breakthrough being to elevate Y2K to an enterprise survival strategy and establish it as a hard constraint for resource allocation.
To address project priority conflicts intersecting with the Y2K initiative—specifically infrastructure upgrades, Meditech clinical system migration, and regional information network construction—strategic realignment is essential. First, senior leadership must be apprised of the critical risks associated with Y2K project failure, including legal liabilities and potential financial losses. This requires articulating the severity of consequences, such as operational disruptions and reputational damage, to justify resource reallocation.
Additionally, the Steering Committee should implement monthly resource allocation reviews across all projects, deferring non-critical initiatives’ resource demands to prioritize Y2K requirements. This phased approach ensures that critical-path tasks for Y2K compliance are not compromised by competing projects.
On the vendor management front, involving the audit department to monitor suppliers’ compliance progress can enforce accountability. This oversight mechanism should include periodic reviews of deliverables and contractual obligations, with escalations with vendors where delays or incomplete work threaten project timelines.
Sadlemire referred to other projects with higher priority than the Y2K project mainly as large infrastructure and system upgrade projects the hospital was advancing. These included a $17 million basic infrastructure plan involving upgrading全院 computers to Windows NT, replacing personal computers, and building a new network, which were regarded as “visible projects” to enhance operational efficiency and occupied the technical team’s main energy. There was also the IDX system replacement project to switch the old HIS system to IDX’s Unix system, which had been delayed by 5 months when launched in 1997, consuming a lot of IT manpower and budget. Additionally, a $13 million regional information network project included equipping medical staff with workstations featuring Internet and video conferencing functions, and developing a telemedicine diagnosis system, which the hospital considered could directly improve service capabilities.
Advice for Sadlemire is to persuade management with specific loss data, calculating the actual risks of not solving Y2K, such as medical accidents possibly caused by time errors in life support equipment and the hospital possibly failing to recover $26-40 million in账款 due to payer system failures. He should apply for temporary personnel transfer from other projects or extra budget for outsourcing teams, bind Y2K with patient safety, emphasizing it is a medical safety issue, and negotiate with other project leaders for phased priorities, allowing the infrastructure project to complete key parts first to free up manpower for Y2K core system repair.
Sadlemire is probably talking about projects like the $17 million network upgrade that took priority over Y2K hardware checks. These projects were seen as more urgent by the technical team, even though Y2K was super critical.
To address this, Sadlemire should clearly communicate the risks of ignoring Y2K. He needs to show how Y2K problems could bring the whole system down, affecting everything else they’re working on. He should also try to get higher-ups to reallocate resources or set clearer priorities. Maybe he can find a way to combine Y2K tasks with other projects to save time and effort.
The “other projects” mentioned by Sadlemire might include the network upgrade being carried out by the hospital (such as the migration to the Windows NT system), the deployment of new software (such as the IDX and Peoplesoft systems), and the infrastructure renovation (such as the replacement of the telephone system). These projects consumed the time and budget of the IT team, resulting in the postponement of the millennium bug fix work.
It is suggested that Sadlemire take the following actions:
1. Use data to prove: Present to the top management the serious consequences of the millennium bug risk (such as the paralysis of medical equipment, the collapse of the financial system), and compare the urgency of these other projects;
2. Seek leadership support: Request the CEO or the board of directors to clearly prioritize the millennium bug and suspend or postpone non-critical projects;
3. Simplify the process: Handle low-risk systems quickly and concentrate resources on solving core issues (such as the compliance of life support equipment). Just as the CIO stated in the text: “As long as we complete it on time, we can pass the test.” – The key is to make everyone realize that the Y2K issue has no room for delay, while other projects can be adjusted flexibly.
Sadlemire’s “other projects” most likely refer to the $17 million “Basic Infrastructure” initiative, which included network upgrades and system integration, as well as the migration of legacy systems to new platforms like IDX and PeopleSoft. The Meditech clinical system migration and ongoing technical upgrades also competed for resources. These projects were prioritized due to immediate operational needs, but Sadlemire considered them less important than Y2K compliance, as Y2K issues posed existential risks to patient care and legal liability.
To address the priority conflict, Sadlemire should:
1. Submit a formal risk assessment to senior leadership, highlighting how Y2K failures could disrupt critical operations and incur legal costs.
2. Advocate for integrating Y2K remediation into ongoing projects. For example, ensuring new systems are Y2K-compliant during the IDX migration to avoid duplicate efforts.
3. Strengthen cross-departmental accountability by mandating Y2K status reports from all project leads as required by the Steering Committee.
Sadlemire likely refers to projects like the $17 million Basic Infrastructure initiative (network upgrades, PC replacements), the IDX system migration for patient admitting/billing, the Peoplesoft conversion for payroll/Human Resources, and the Meditech clinical applications project, which diverted technical resources and budget from Y2K compliance . To address conflicting priorities, he should: 1) Quantify Y2K risks (e.g., $26–$40M cash flow delay from payors, $400K device replacement costs) to appeal to senior management’s financial and legal concerns ; 2) Integrate Y2K remediation into ongoing projects (e.g., ensure new systems like Meditech are Y2K-compliant during implementation) ; 3) Advocate for a formal prioritization framework that mandates Y2K compliance as a prerequisite for other initiatives.
Sadlemire likely refers to projects like the $17 million Basic Infrastructure initiative (network upgrades, PC replacements), the IDX project to replace old HIS applications, and the Peoplesoft conversion for payroll and HR systems . These projects consumed resources and attention, sidelining Y2K efforts.
To address this, Sadlemire should prioritize demonstrating Y2K’s criticality. He could present concrete risks: patient care disruptions from failed medical devices, $26–$40M in delayed payments from non-compliant payors, or legal liabilities . He should also integrate Y2K into ongoing projects—e.g., ensuring new hardware/software in the infrastructure upgrade is Y2K-compliant. Finally, urging top management to allocate dedicated resources and mandate cross-departmental accountability would help elevate Y2K’s priority.
“Other projects” likely include:
1.Routine non – critical upgrades: Like general network expansions or hardware updates for non – essential departments, not focused on Y2K compliance.
2.Operational enhancement projects: Such as software feature additions for daily use or facility renovations, seen as more “tangible” but less crucial long – term than Y2K.
Advice for Sadlemire
1.Risk communication:
Make a report on Y2K risks (financial loss, operation disruption) and present it to management, stressing potential disasters.
2.Align with goals:
Use regulations and business continuity (ensuring post – 1999 operation) to show Y2K’s importance over other projects.
3.Prioritization & advocacy:
Create a matrix scoring projects by risk, cost, etc., to prove Y2K should be top – ranked. Team up with IT and compliance heads to advocate for Y2K priority.
The “other projects” mentioned by Sadlemire include a $17 million infrastructure upgrade, the replacement of the IDX/Meditech system, the Peoplesoft migration, and the telemedicine project. These projects were marginalized due to resource competition and the Y2K work was pushed aside. It is suggested to convince the top management by quantifying risks (such as the $4 million cost of equipment replacement) and establishing a cross-departmental resource arbitration committee to allocate personnel from infrastructure projects. Introduce the “risk – benefit matrix” to prioritize projects, bind supplier compliance with contracts, and prioritize the repair of high-frequency modules such as the emergency system. The core reason why the Y2K project was overlooked in this case is that the management prioritized business growth while neglecting systemic risks, and lacked a cross-project coordination mechanism. This situation needs to be reversed through institutional design and data-driven approaches to address the imbalance in resource allocation.
Other Projects Referenced:
$17M Basic Infrastructure Initiative (network upgrades, IDX/Peoplesoft migrations)
$13M Regional Telemedicine Network (video conferencing, expert systems)
Advice
Escalate Risks: Present Y2K delays as operational/legal threats to leadership.
Quick Wins: Focus on testing life-critical devices first (e.g., nuclear medicine equipment).
Resource Trade-offs: Propose pausing non-urgent IT projects temporarily.
Sadlemire should argue that $17M infrastructure projects (network upgrades, telemedicine) and Meditech/PeopleSoft migrations drain resources from Y2K efforts. Emphasize Y2K’s criticality—potential financial/legal risks from non-compliance—to push senior management for resource reallocation or additional staffing, prioritizing system continuity over competing initiatives.
“Other projects” include network upgrades, new PC deployment, internet access, remote medical system development, IDX (patient management) which has been launched but is five months behind schedule, payroll systems, and management adjustments. Some department heads responsible for Y2K compliance have left.
Recommendations: Quantify risks and seek senior management support; temporarily reallocate infrastructure project personnel to support Y2K testing, and suspend investment in non-critical projects (such as non-core functions of remote medical systems); publicly announce departments that fail to submit progress on time; plan alternative solutions in advance for high-risk areas and work with the finance department to reserve emergency funds.
He’s likely referring to the $17 million Basic Infrastructure upgrades (network revamp, new PCs), the IDX system replacement, and the Peoplesoft HR software conversion.
Advice for Sadlemire:
1. Show senior leaders concrete risks with FDA warnings and examples—like the $400k nuclear device needing replacement or $40M in delayed payments from non-compliant payors.
2. Tie Y2K to ongoing projects: when testing new hardware for the infrastructure upgrade, check Y2K compliance simultaneously.
3. Find a tech-savvy board member as an advocate, and regularly remind management of past project delays (like the IDX project being 5 months late) to stress Y2K’s urgency.
The other projects is probably those employees think risks or profit will bigger than The Year 2000 Project, that every director has their respectively prosepctive to consider the priority. For example, the $17 million “Basic Infrastructure” initiative, the $13 million Regional Information Network, Meditech clinical system replacement, IDX billing system upgrade, etc.
I suppose Sadlemire can show executives concrete data to stakeholders, acknowledging them the failure risks. Also, Sadlemire should create a emergency task force which include cross-departemnet employees, to sufficiently include time staff put into Year 2000 Project, and even can ensure critical one involve full time in this project. Last but not least, Sadlemire can turn to board for publishing mandatory requriements, or inform the whole company the substantial liability exposure.
To resolve project priority conflicts, initiatives competing with the Y2K compliance effort include infrastructure upgrades, Meditech clinical system migration, and regional information network deployment. To address these conflicts and elevate the Y2K project’s priority, the first critical step involves presenting to senior leadership the severe potential consequences of Y2K failure—particularly the legal liabilities and financial losses that could materialize in the event of non-compliance. Additionally, the steering committee should conduct monthly resource allocation reviews for all active projects, deliberately deferring non-critical project demands to prioritize Y2K requirements. For vendor-related bottlenecks, the audit department should actively monitor supplier compliance progress through formal reviews and apply contractual pressure when necessary to ensure timelines are met.
The organization faces competing demands from multiple infrastructure initiatives including delayed IDX patient management system implementation, network modernization, enterprise PC refresh, and telehealth platform development – all while experiencing turnover among critical Y2K leadership positions. This resource dispersion necessitates immediate strategic reprioritization to avert millennium-related system failures.
To address these challenges, management should implement a four-point contingency plan: First, conduct quantitative risk assessments to justify executive-level intervention and secure temporary reallocation of IT personnel from non-essential upgrades to accelerate Y2K validation testing. Second, impose a strategic moratorium on discretionary projects, particularly non-core telehealth functionalities that offer minimal Y2K risk reduction benefits. Third, establish accountability through transparent enterprise-wide reporting of departmental compliance status, publicly identifying lagging units. Finally, develop fallback protocols for high-probability failure scenarios while collaborating with finance to earmark contingency funding, creating a financial safety net for last-minute remediation efforts.
“Other Projects” Referenced by Sadlemire
Based on case context, these likely include:
High-Visibility Infrastructure: New outpatient building (prioritized for political visibility).
Short-Term Revenue Projects: Custom EMR development for external hospitals (immediate cash flow).
Compliance-Driven Initiatives: HIPAA privacy upgrades (explicit penalties attract resources).
Executive Pet Projects: Mobile patient scheduling app (CEO’s “innovation showcase”).
Core Conflict: Y2K is a high-risk/low-visibility project (no reward for success, catastrophe for failure), while “other projects” offer political/short-term gains, causing misaligned priorities.
Actionable Advice for Sadlemire
1. Quantify Silent Risks → Speak Leadership Language
Tactic: Translate Y2K failure into decision metrics:
Financial: 1-day outage = $5M loss (using BIA downtime cost models).
Legal: Ventilator failure risk → $20M+ lawsuits (cite FDA cases like Therac-25 deaths).
Tool: Build a risk heatmap dashboard showing real-time system failure probabilities.
2. Align with Strategic Goals → Secure Executive Sponsorship
Method: Tie Y2K to CEO’s KPIs:
Link to patient satisfaction: EMR crash → 30% complaint surge (per case data).
Bind to innovation reputation: Mobile app useless if backend systems fail.
Action: Demand Y2K compliance be included in executive bonus criteria (e.g., 20% weighting).
3. Force Priority Trade-offs → Create Resource Reallocation Mechanisms
Steps:
Monthly Triage Meetings: CFO/CTO review project rankings using BIA data (e.g., Y2K risk score > lobby renovation).
”Lifeboat Fund”: Pause low-risk projects (e.g., cafeteria upgrade → free $800K for Y2K testing).
Outsource Non-Core Work: Contract out EMR customization → free 50% developer time for Y2K.
4. Engineer Visible Wins → Build Political Capital
Tactics:
Issue weekly Y2K Risk Downgrade Alerts (e.g., “Payment system risk: Red → Yellow”).
Stage symbolic victories: Invite CEO to press “Recovery Button” after fixing critical systems + PR campaign.
Partner with auditors to release non-compliance warnings (leverage regulatory pressure).
Based on the case evidence, Sadlemire’s remark about Y2K playing “second fiddle” refers to competing strategic initiatives that consumed resources and leadership attention, diverting focus from the urgent Y2K remediation. The specific projects include:
1.The $17M “Basic Infrastructure” Initiative
2.The $13M “Regional Information Network” (Telemedicine)
3.Major System Replacements (e.g., IDX, PeopleSoft, Meditech)
4.Organizational Restructuring
Advice for Sadlemire to Address Conflicting Priorities:
1.Escalate Risks in Business Terms
2.Demand Executive Prioritization
3.Secure Dedicated Resources
4.Leverage Governance Structures
5.Simplify and Focus