Goal: Reduce surprise purchases, minimize downtime, and keep your team working at full speed.
How we use this: We review your score during QBRs and build a roadmap to improve your IT Health based on your priorities and budget.
Related Standards #
These pages support the IT Health framework and provide deeper standards by category.
What “IT Health” Means #
IT Health is the overall condition of your technology environment. It includes performance, reliability, recoverability, security readiness, and standardization.
A healthy environment is predictable, supportable, and easy to budget.
Outcomes of Healthy IT #
- Fewer outages and fewer urgent emergencies
- Faster systems and happier staff
- Faster recovery when something breaks
- Predictable budgets and planned replacements
- Improved readiness for security events and audits
Common Causes of Poor IT Health #
- Old hardware beyond lifecycle or without support
- Depot warranties on business critical systems
- Single points of failure and no continuity plan
- Unmanaged networks and poor cabling practices
- Backups that are not tested or not monitored
The Biggest Success Identifier: People and Leadership #
IT Health improves fastest when staff and leadership are engaged. Education, support, and participation are the biggest success identifiers in any IT environment. If this area fails, most other improvements will fail or move slowly.
Technology standards are important, but they only work when people consistently follow them. Leadership sets priorities, approves roadmaps, funds lifecycle planning, and reinforces accountability. Staff behaviors determine whether security practices are followed, incidents are reported quickly, and processes are used correctly.
What Healthy Staff Engagement Looks Like #
- Users report issues early and use the support process consistently
- Security awareness is practiced, not only discussed
- Phishing and suspicious activity are reported quickly
- MFA and password manager usage is consistent
- Users understand where files should live and how sharing should work
What Healthy Leadership Engagement Looks Like #
- Leadership approves the roadmap and funds lifecycle replacement planning
- Standards are reinforced as expectations, not suggestions
- Decisions are made quickly when risk or downtime is high
- Security and compliance are treated as business priorities
- Quarterly reviews happen and actions are taken
When people and leadership are aligned, everything becomes easier: fewer incidents, faster improvements, better uptime, and a smoother budget cycle.
Priority note: Leadership engagement and staff education are the strongest predictors of success. Even if your technology is modern, weak engagement will slow or stall progress across every other category.
IT Health Maturity Model #
Use these levels to describe where you are today and where you are headed. Many organizations start at “Stable” and improve to “Resilient” over time. “Continuity” is recommended for environments with low tolerance for downtime.
| Level | Short Description | What You Can Expect |
|---|---|---|
| Stable Minimum Standard |
Basics are in place and the environment is supportable | Fewer repeat issues, better support outcomes, and a clear lifecycle plan |
| Resilient Recommended Standard |
Reduced risk through redundancy, standardization, and planning | Fewer outages, faster recovery, and improved user experience |
| Continuity High Availability Standard |
Business stays operational during major failures | Best uptime, best recoverability, and strongest operational predictability |
Core IT Health Standards #
These standards reduce downtime, improve performance, and create predictable budgets. The more consistently these are applied, the more stable and scalable the environment becomes.
1) Warranty & Vendor Coverage #
- Critical infrastructure: Maintain proper warranty coverage with onsite repair service and parts coverage.
- Priority systems: Faster response warranties are recommended where downtime is expensive.
- Non-critical systems: Depot warranties may be acceptable when downtime tolerance is high.
2) Asset Replacement Lifecycle #
- Workstations: replace every 3 to 5 years to maintain performance and staff satisfaction.
- Servers and network equipment: replace every 5 to 7 years to maintain support, security, and reliability.
- Systems beyond lifecycle are on borrowed time and are more prone to wear and tear failures and support limitations.
- Reference: Hardware Lifecycle Standards
3) Business Continuity Planning #
- Identify and reduce single points of failure during business reviews.
- Spare workstation standard: keep 1 ready to deploy spare per 25 workstations.
- Have a replacement plan for critical network equipment, either stocked spares or next day replacement options.
- Use redundant server designs where appropriate, such as replication, clustering, or hyperconverged solutions.
- Add a backup internet option where downtime risk is meaningful, such as an LTE or secondary provider.
4) Workstation Performance Standard #
- Buy business class workstations designed for longevity and supportability.
- Standardize minimum specs so no user falls below a healthy performance baseline.
- Budget for the full experience, including warranty, docks, monitors, and required accessories.
- Reference: Workstation Standards
5) Server Performance and Reliability #
- Size servers based on growth, application requirements, and downtime tolerance.
- Use redundant server components where possible to reduce failure impact.
- Track server performance trends so bottlenecks are addressed before users feel them.
- Reference: Server Infrastructure Standards
6) Network Performance and Manageability #
- Use managed network equipment. Avoid unmanaged core switches in business environments.
- Design networks for performance, supportability, and reduced single points of failure.
- Use proper wiring standards and ensure cabling is tested and labeled.
- Reference: Network and Internet Standards
7) Power Protection #
- Clean, consistent power reduces equipment damage and data corruption risk.
- Servers and network equipment should have UPS protection sized for load and uptime requirements.
- UPS devices should be remotely monitorable so battery health and shutdown behavior can be managed proactively.
- Reference: Power Protection Standards
8) Backup and Recovery Planning #
- Use a structured backup strategy such as 3-2-1 when appropriate for the business.
- Define RPO and RTO to match business needs and expectations.
- Test restores. Backups are only valuable if recovery works under pressure.
9) Routine and Review #
- Establish a routine for monitoring and inspection. Repeatable routines reduce surprise failures.
- Use monthly reporting and quarterly planning to stay ahead of aging equipment.
- Reference: IT Hardware Budgeting Standards
10) Standardization #
- Standardize hardware models and configurations to reduce support time and improve predictability.
- Standardize core software suites to reduce training burden and compatibility issues.
- Reference: Technology Standards Map
IT Health Scorecard #
This scorecard is designed for QBRs and planning meetings. It creates a clear, proactive way to measure IT Health and hold the environment accountable to agreed standards. Each category is scored from 0 to 2.
Scoring guide
- 0: Not in place or high risk
- 1: Partially in place or inconsistent
- 2: Fully implemented and maintained
Total score: Add points across categories. Higher score means healthier IT.
| Category | What “Healthy” Looks Like | Score (0–2) | Notes / Next Actions |
|---|---|---|---|
| Leadership Engagement | Leadership supports standards, approves the roadmap, reinforces accountability, and aligns budgets to reduce surprises | __ | __ |
| Staff Education and Awareness | Ongoing training exists for IT operations and security, and users follow clear reporting and safe-use expectations | __ | __ |
| Lifecycle Coverage | Workstations and infrastructure are on planned refresh cycles with minimal overdue assets | __ | __ |
| Warranty and Support | Critical infrastructure has active warranties and support aligned to business uptime needs | __ | __ |
| Performance Baseline | Users have consistent, business-class performance and minimum standards are enforced | __ | __ |
| Network Manageability | Managed firewall, switches, and access points with documented standards and visibility | __ | __ |
| Power Protection | Servers and network gear are protected by monitored UPS and proper surge protection | __ | __ |
| Backup and Recovery | Backups are monitored, recovery objectives are defined, and restores are tested | __ | __ |
| Continuity Planning | Single points of failure are identified and a continuity plan exists for key systems and internet | __ | __ |
| Monitoring and Alerting | Proactive monitoring is enabled with meaningful alerting and monthly reporting | __ | __ |
| Standardization | Hardware models, configurations, and core software suites are standardized wherever possible | __ | __ |
| Roadmap and Budget | A replacement roadmap exists and budgets are annualized to reduce surprise purchases | __ | __ |
Priority note: Leadership engagement and staff education are the strongest predictors of success. Even if your technology is modern, weak engagement will slow or stall progress across every other category.
Score Interpretation #
How to read the score
- 0–7: High Risk — frequent surprises and higher downtime likelihood
- 8–14: Improving — some standards are consistent, but gaps still create disruption
- 15–20: Healthy — predictable operations, fewer surprises, and strong user experience
Tip. A rising score quarter over quarter is the goal. Improvements should be tied to a roadmap, budget, and leadership support.
How We Use IT Health Standards in QBRs #
- Step 1: Score the environment and identify the top 3 risks.
- Step 2: Agree on a realistic roadmap based on priorities and budget.
- Step 3: Align lifecycle and budgeting to remove surprise purchases.
- Step 4: Re-score quarterly to show progress and keep momentum.
A healthy environment is not built overnight. It is built through consistent standards, clear planning, and steady improvement.
