What experience reads between the lines.
Software can tell you that three reports disagree. It takes experience to know why, and which disagreement is about to become a problem. These are the patterns I look for first, in any industry.
From Corey Elliott, founder. 15+ years running federal, state, and enterprise programs.
Same six signs. Any industry.
Program governance isn’t tied to one sector. A federal modernization, a hospital system upgrade, an enterprise rollout, a 200-site facilities portfolio: the warning signs look the same. What changes is what they cost you.
Rushed reports
What it looks likeCopied-forward updates, same wording every week, missing dates.
What it usually meansThe owners are stretched thin. The report isn't wrong, just old news dressed as new.
What I ask“Who wrote this, and how much time did they have?”
Example impact · EnterpriseAn ERP cutover reads “on track” right up to the board meeting. Launch slips a quarter, and $6M in planned savings slides out of the fiscal year.
Example impact · FederalA $40M modernization reports green for two quarters on copied-forward updates. The slip surfaces in an Inspector General review, not a status meeting.
Example impact · State & localA state benefits system stays green until go-live. The delay leaves 50,000 claims backlogged, and it makes the evening news.
Example impact · HealthcareAn EHR upgrade's weekly status is copied forward. Testing gaps surface at go-live, and clinics cut patient volume for weeks while billing stalls.
Example impact · Utilities & energyAn outage-system upgrade shows the same status for six weeks. The gap shows up in the first big storm, and restoration reports to the regulator are late.
Example impact · Facilities & real estateA 200-site facilities transition reports green on copied-forward updates. At handover, a third of the sites have no vendor in place, and SLA penalties start on day one.
New faces, partial story
What it looks likeA new owner, PM, or vendor lead partway through.
What it usually meansThey're reporting what they inherited, not what they lived through.
What I ask“What did the last owner know that never got written down?”
Example impact · EnterpriseA new VP inherits a global rollout. Promises made to the largest customer never made it into the plan, and the renewal is in doubt.
Example impact · FederalA new COR takes over mid-contract. The last one's informal direction was never documented, and it turns into a $3M contractor claim.
Example impact · State & localA new administration replaces the program director. A federal matching-fund deadline isn't on anyone's list, and $20M is at risk.
Example impact · HealthcareThe clinical lead leaves mid-implementation. Physician workflows agreed in design were never written down, and adoption collapses after go-live.
Example impact · Utilities & energyThe project engineer rotates off a substation upgrade. An interconnection condition they were tracking is missed, and energization slips a season.
Example impact · Facilities & real estateThe account lead changes mid-transition. Commitments to the client's real estate team were never written down, and the renewal turns into a rebid.
Politics, seasons, and markets
What it looks likeFiscal year end, budget season, elections, leadership changes.
What it usually meansFunding isn't only about performance. A healthy program can lose out in the wrong season.
What I ask“What's happening around this program that isn't in the report?”
Example impact · EnterpriseA soft quarter triggers a spending freeze. A transformation 60% done is cut back to the pilot, and the business case never pays back.
Example impact · FederalA continuing resolution blocks new starts. An on-track program can't exercise its next option, and the team scatters before funding lands.
Example impact · State & localThe legislative session ends without the appropriation. A program that's 80% built loses its final phase.
Example impact · HealthcareA mid-year reimbursement change redirects capital. A project on schedule is deferred 18 months.
Example impact · Utilities & energyThe rate case comes in below the request. Grid-modernization capital is cut, and a healthy program waits for the next filing.
Example impact · Facilities & real estateThe client's new CFO orders a portfolio review. Capital projects on schedule are frozen while leases are renegotiated.
Silence from stakeholders
What it looks likeNo questions, no pushback, meetings quietly declined.
What it usually meansSilence is rarely agreement. Usually they doubt the plan, or nobody wants to say it's off track.
What I ask“When did this stakeholder last disagree with us?”
Example impact · EnterpriseRegional leaders skip the demos. After go-live they stay on spreadsheets, and a $12M platform sits at 20% adoption.
Example impact · FederalThe program office declines three reviews in a row, then rejects the deliverable at acceptance. Rework eats the option-year budget.
Example impact · State & localCounty partners stop joining calls. At rollout, half aren't ready, and the state misses its federal compliance date.
Example impact · HealthcareNursing leadership stops pushing back in design sessions. At go-live, units build workarounds that start showing up in safety reports.
Example impact · Utilities & energyField operations goes quiet on the new work-management system. Crews keep paper tickets, and reliability data to the regulator won't reconcile.
Example impact · Facilities & real estateSite managers go quiet on the new work-order system. Technicians keep phoning requests in, and the client's SLA dashboard reflects none of the real work.
Thin content
What it looks likeOne-line updates, blank notes, statuses with no dates behind them.
What it usually meansThere's no real update, the team isn't engaged, or the reporter doesn't know the full story.
What I ask“Would the person doing the work tell me the same thing?”
Example impact · Enterprise“Integration in progress,” no dates. The acquired systems aren't combined by Day 100, and synergy targets get restated to the board.
Example impact · Federal“Requirements being refined” for months. The program reaches its milestone decision with no approved baseline, and the review board pauses it.
Example impact · State & local“Vendor onboarding underway.” Nobody can say whether the data-sharing agreement is signed, and launch waits on legal for a quarter.
Example impact · Healthcare“Interfaces in testing” every week. Lab results don't flow at go-live, and staff re-enter orders by hand for a month.
Example impact · Utilities & energy“Design at 90%” for three months. The last 10% is a permitting redesign that pushes in-service past peak season.
Example impact · Facilities & real estate“Capital projects progressing” every month. Nobody can say which roof replacements are funded, until one fails and closes a site.
Off the strategic line
What it looks likeMilestones that don't tie to the objectives the organization is measured on.
What it usually meansOn track can still mean heading the wrong way, and it won't protect the program when budgets tighten.
What I ask“Which objective does this move, and who owns it?”
Example impact · EnterpriseEvery module goes live, but cost-to-serve doesn't move. The CFO declines to fund phase two.
Example impact · FederalEvery milestone is met, but none map to the agency's strategic plan. In the next budget request, it's the first program cut.
Example impact · State & localThe system launches on time, but wait times, the governor's headline metric, don't improve.
Example impact · HealthcareThe rollout finishes on schedule, but readmissions, the metric tied to reimbursement, don't change.
Example impact · Utilities & energySmart meters go in on schedule, but outage minutes, the number the regulator grades on, don't improve.
Example impact · Facilities & real estateEvery work order closes on time, but the client's energy and occupancy-cost targets don't move, and those are what the contract is graded on.
These are patterns, not verdicts.
Every program has context a report can't carry. That's what a 30-minute Altitude Check is for.