Wider or Deeper? Choosing Where to Invest Your Next Downtime Dollar

9 November 2026

AUTHORED BY: Chloe Williams

At some point in the life of a downtime preparedness program, a budget conversation turns into a strategy question. Leadership has approved some funding. The initial deployment is working. Now the team has to decide where the next dollar and the next hour of effort should go.

There are two broad directions. Going wider means extending coverage to more departments, facilities, and service lines. Going deeper means strengthening what is already deployed: better training, a more current forms library, tougher testing, faster reconciliation, and stronger governance. Both are valuable. Choosing the wrong one at the wrong time is how organizations end up with broad coverage that does not work under pressure, or an excellent program that leaves a high-risk department completely unprotected.

What Wider and Deeper Actually Mean

Going wider usually includes:

  • Adding downtime workstations in departments that have none
  • Bringing newly acquired or newly opened facilities into the program
  • Adding forms and workflows for service lines that were not covered at launch
  • Extending procedures to affiliated practices and outpatient sites

Going deeper usually includes:

  • Closing the gap between stated and actual activation times
  • Raising the share of staff who can demonstrate the procedure, not just describe it
  • Reviewing and updating the forms library against current clinical workflows
  • Testing the full workflow, including post-outage reconciliation, at realistic volume
  • Strengthening ownership, reporting, and follow-through on action items

Signals That It Is Time to Go Wider

Coverage gaps are the right priority when the evidence points to unprotected risk rather than weak performance:

  • A high-acuity or high-volume department has no downtime workstation or procedure. Use the framework in our post on prioritizing which departments get workstations first to rank them
  • The organization acquired or opened facilities that were never integrated into the program. Our post on whether your program is keeping pace with growth describes the typical gaps
  • A survey, audit, or internal review flagged missing coverage rather than weak execution
  • Drills in covered departments are consistently strong, and the weak spots are the departments that were left out
  • A new service line launched that has documentation requirements no existing form supports

Signals That It Is Time to Go Deeper

Depth is the right priority when covered departments are not performing the way the program assumes:

  • Activation takes much longer in exercises than the target allows
  • Spot checks show that staff, especially newer hires and agency staff, cannot describe or demonstrate the procedure
  • Staff default to paper during planned maintenance windows even though electronic workflows are available
  • The forms library has not been reviewed in more than 12 months, or forms no longer match current workflows
  • Reconciliation has never been timed with real data, or it takes far longer than expected
  • Action items from earlier drills and events remain open with no owner
  • Workstation sync or integration problems have appeared in monitoring more than once

A useful test: if you ran an unannounced exercise in your best-covered department today, would you be confident in the result? If not, depth comes before breadth.

A Simple Scoring Method

When both lists have entries, score them rather than arguing from instinct.

  • For each candidate investment, rate patient safety impact, regulatory exposure, and operational impact on a simple 1 to 5 scale
  • Rate how confident you are that the current program would perform in the affected area, with 1 meaning very confident and 5 meaning not confident at all
  • Multiply impact by uncertainty to find the largest unaddressed risks
  • Estimate effort and cost for each, then compare the risk reduction per unit of effort

This often reveals that a small depth investment, such as a forms review or a timed reconciliation exercise, reduces more risk than a large expansion. It also reveals the reverse: an unprotected ED or pharmacy outweighs almost any amount of polish elsewhere.

Sequencing Rules That Work in Practice

  • Never leave a top-tier department uncovered while polishing a lower-tier one. Safety-critical coverage comes first
  • Do not expand into a new site until the first sites can pass an unannounced activation test. Otherwise you copy weak practices
  • Pair every expansion with its depth requirements: training, forms, procedure cards, and a verification step before declaring the area live
  • Alternate quarters when possible. A quarter of expansion followed by a quarter of consolidation prevents the program from stretching faster than it can be maintained
  • Reserve a fixed share of capacity every quarter for fixing what drills reveal, so depth work is not crowded out by new projects

How Pricing Interacts With the Decision

Expansion has a cost structure worth understanding before you commit. dbtech’s published tiers price per station per month, with Tier 1 at $299 for 3 to 5 stations, Tier 2 at $149 for 6 to 10, and Tier 3 at $99 for 11 or more. Details are on the pricing page, and your dbtech team can confirm how the tiers apply to your configuration. Because per-station cost falls as coverage grows, wider deployment can lower the blended cost per workstation over time, as described in our post on how the program becomes easier and cheaper as it matures. Depth investments such as training, drills, and governance mostly consume staff time rather than subscription dollars, which means they compete for attention rather than budget.

Measuring Whether You Chose Well

Decide in advance how you will know the investment worked:

  • For expansion: the new area is live, verified, and passes an activation exercise within a defined number of weeks
  • For depth: activation times, electronic workflow completion, and reconciliation time improve against the baseline from your last exercise
  • For both: open action items decrease and the next drill produces fewer repeated findings

The tracking approach in our post on using downtime data to drive continuous improvement and the maturity dimensions in how to measure the maturity of your program provide the measures to use.

Common Mistakes

  • Treating expansion as progress by default because it is visible, while weak performance goes unaddressed
  • Treating polish as progress by default because it is comfortable, while an entire department is exposed
  • Deciding once and never revisiting. The right answer changes as the program matures
  • Funding expansion without funding the training and maintenance it creates

To get an objective read on whether your program needs breadth or depth, schedule a dbtech Downtime Audit Assessment or request a demo.

Want to learn more? Fill out the form below and a representative will call you ASAP!