The gold data no one is using...silence

Your dashboards are green. Your seat at the table is smaller. You are invited to fewer tables. The silence in your dashboard is the reason.

• The business stopped needing IT to own its technology between 2006 and 2010. The migration is complete — 74% of technology purchases are now funded outside IT, and four out of five technologists in your company do not work in IT.
• When the systems left, the strategic conversations left with them. IT cheered for the handover at the time. The relief was real. The cost was not visible yet.
• The cost is visible now as silence. Business units that file zero tickets are not fine — they have gone quiet for a reason, and the reason has shape.
• The shape is green, amber, or red. Your dashboard cannot tell them apart.
  • Green — genuinely fine. Watch for the look-alike: a BU that says we're good because they built their own world and stopped expecting anything from IT. Different conversation, not this mission.
  • Amber — running on tools IT is not in the loop on, for an outcome IT could help with. The tell is the pause before they answer.
  • Red — stopped trying.
• The first move is three to five 20-minute conversations with BU leads who have gone silent — three at a smaller company, five if you have a sprawling org with many BUs. Not a program. Not a tool. A tracer bullet to find out which kind of silence you are looking at.

Before the silence, the part nobody talks about.

Between 2006 and 2010, three things gave the business an exit it never had before. AWS S3 went live in March 2006. AWS EC2 followed in August. Workday started taking enterprise share. Salesforce was already proving that outcome-shaped SaaS worked. The corporate card became a real procurement channel inside the same window.

The migration was rational. CRM moved from IT to Sales Operations. Marketing technology moved to the CMO. HRIS moved to HR Operations as Workday rolled out. Analytics moved to the Chief Data Officer. Procurement built its own technology function. Sales should own CRM. Finance should own ERP. The teams that own the outcomes should own the systems that serve them. The migration was correct.

The numbers are not contested. 74% of technology purchases are now funded, at least partially, by business units outside IT. Up to 80% of the technology products and services in a modern enterprise are built by non-tech professionals. Gartner's 2021 survey put 41% of the average enterprise workforce in the business technologist category — doing technology work whose reporting line lives outside IT.

When each category left IT, the response inside IT was relief. The queues were overwhelming. The compliance audits were expensive. The escalations ate half the team's calendar. When a BU said we will take it from here, the response was thank you. We meant it. We held all-hands meetings about being lean. We retired the support contracts. One less thing to manage. That sentence was said in operating reviews across the industry, for twenty years, with relief on every face.

What we did not say out loud is that every category that left IT was a category of business-outcome conversation IT was now no longer in the room for. Sales took CRM, and the pipeline acceleration conversation went with it. Marketing took the campaign stack, and the brand performance conversation went with it. HR took HRIS, and the workforce planning conversation went with it.

By 2026, IT supports roughly the same systems with roughly the same headcount it had in 2010, with one critical difference. Six or seven of the most strategic business conversations now happen in rooms IT does not enter. You signed the transfer order yourself. You celebrated it at the time. You were not wrong to be relieved. You were wrong about what the relief meant.

Your service dashboard is the wrong instrument for the question you are trying to answer.

Outcomes rescued rise fast with the first service improvements. Then the curve bends. Past the bend, tightening service targets is adding decimal places to a test you already passed. You pay real money. You get near-zero movement on the thing the user is upset about.

A ticket closes green within all targets. The user could not achieve the outcome. The silence becomes proof nothing is wrong. You conclude the business is being unreasonable. They are not. You are judging them on a measurement they could not care less about while they are losing.

This is the watermelon. Green on the outside, where the dashboard lives. Red on the inside, where the trust erodes.

Somewhere this week, a person in your business hit a problem and did not report it. They priced IT against a clock — this thing is worth X, losing it costs Y, can IT fix it before Y lands. Sometimes IT wins the bid. When IT loses, the task does not become a ticket. A colleague solves it. A spreadsheet absorbs it. The work gets dropped. Your dashboards never see it.

The silence in your dashboard is not the absence of a problem. It is the absence of an instrument that can see one.

The goal is not a program. The goal is a conversation that earns the next conversation.

Forget transforming anything. Do not build a program. A program has a roadmap, a steering committee, a tool evaluation, an RFP. By the time it ships, motivation is dead and the watermelon rind is thicker.

Your first move is a tracer bullet — three to five conversations. Not with IT people. With business unit leads whose teams have gone silent. The point is not to fix anything. The point is to find out what kind of silence you are looking at.

Step 1 — Find the silence

Ticket volume by business unit for the last 90 days is the obvious starting point, and it is correct as far as it goes. It is also one signal among four. Any single signal can mislead. The strongest first-call lists triangulate across two or three.

Two signals stacking is louder than any one alone. Volume and engagement dropped together — likeliest red. Quiet queue plus growing shadow footprint — likeliest green-disguise. Normal engagement but conspicuous narrative absence — possible federation-without-acknowledgment. Pick three to five BUs — three at a smaller company, five if you have a sprawling org. Include one or two wildcards whose silence doesn't fit a clean pattern; the wildcards are where the model itself gets tested.

Entire business units do not have zero or near zero technology friction.

Step 2 — Go ask

Get 15 to 20 minutes on the lead's calendar. Walk in with no slides, no dashboards, no proposal. Do not announce a program. That is the kind of move that earned the silence.

The conversation has shape — an opener, four probes, a close. The shapes are below as ideas, not scripts. The actual language is yours.

Open with a cost paid up front. Three shapes work. Pick the one that maps to what you actually have. The point is asymmetric — pay something only you can pay before the BU has spoken.

Shape A — The confession. A specific failure named out loud from IT's own logs, tied to a moment in the BU's recent past. Use when there is a real dropped ball in the data.

I pulled our ticket aging this morning. During your platform migration last quarter, four of your requests sat past ten days before anyone touched them. We never told you we'd dropped them.

Your access requests during the reorg averaged nine business days. The SLA is two. I didn't know that number until last week, which is its own problem.

Shape B — The found-money gift. IT-side telemetry the BU can't see on their own, translated into something useful to them, handed over with no agenda attached. Use when there's IT-only visibility worth giving away.

Twenty-two of your thirty-eight licenses on the analytics platform haven't been touched in 90 days. Roughly forty thousand a year if you want to reclaim it. Your budget, your call.

Your lifecycle email pipeline is calling our directory forty thousand times a month. Not a governance thing. If you're sized to it, ignore me; if not, that's a number worth knowing.

Shape C — The admission of ignorance. A self-aware admission that IT has not done its homework on the BU's actual business. Use when the relationship is cold — no recent failure, no useful intel.

I'm going to embarrass myself — I don't know what's going to keep someone on your team up at night in October. Not the OKR-slide version. I should know that and I don't.

I couldn't tell you the last three pieces of work that mattered most to your team last quarter. I could tell you our ticket queue, but that's clearly not the same question.

Pick the one with the highest cost to you. The opener is a trust deposit and only counts if the depositor felt it. Then a flat follow-up that hands the floor over:

No slides, no program. A few questions and one thing I'm hoping to walk away with.

Then probe. Four shapes, asked in this order. Each surfaces a different kind of silence.

Probe 1 — The last time they didn't ask. Insist on a specific moment, not a pattern — who, what they needed, what they did instead. Stories with names are unforgeable; opinions about IT are not.

Tell me about the last time somebody on your team needed something from us and decided not to ask. Not the general pattern — the specific moment. What were they going to ask for, and what did they do instead?

Walk me through the most recent thing your team needed that didn't become a ticket. Something where the workaround was easier than the conversation with us.

Probe 2 — The vocabulary mirror. Ask what the team calls IT when nobody from IT is in the room. Explicitly devalue the polite version they normally give.

What do your people call us when I'm not in the room? Not the polite version. If I lurked in your team's chat for a day, what would I hear?

When something breaks and someone blames IT in passing — what's the actual phrase? I'd rather know than guess.

Probe 3 — The Chesterton invitation. Ask whether there's something IT does for them that they think is pointless — with IT pre-committing to either stop the thing or explain the wall it was guarding.

Is there something we do for your team that you think is pointless but we keep doing? Even a small one. Real chance I'll agree and we can stop. Real chance I'll be able to tell you what it was protecting against.

Name one thing we make your team do that looks dumb from where you're sitting. I'll either kill it or explain it. I won't defend it without a reason.

Probe 4 — Beside the point. Ask where technology comes up in their planning, and whether IT in those rooms would be useful or just polite. The phrasing has to make the honest answer sayable.

When your team plans the next quarter — capacity, targets, a new product motion — where does technology come up, and is there a version of that room where my showing up would be useful versus just polite?

If your leadership has a planning offsite next month, where on the agenda would I actually add something, and where would I be a courtesy invite? I'd rather know I'd be the courtesy invite than show up as one.

Close with one commitment, on a date. One thing from what they just said that you'll come back on, by when, with what you found — even if what you found is that you can't fix it.

Of what you just told me, here's the one thing I'm going to spend the next two weeks on. I'll come back to you on the 14th with what I found — even if all I have is what I couldn't do. If I miss that date, hold me to it.

I'm not leaving with a roadmap. I'm leaving with one thing — the access-review thing you said was pointless. Give me two weeks. If it really is pointless, we'll kill it. If it's not, I'll tell you what it's actually doing.

Through all of it — listen more than you ask. Take notes. Don't defend. Don't propose a fix. Don't explain the support model. You are not there to solve. You are there to learn what the dashboard can't tell you.

Step 3 — Sort the silence

After your three to five conversations, you'll be able to sort each unit into one of three buckets.

Step 4 — Believe what came back

If all of them land in genuine green — specific about what works, specific about what they would lose — your dashboard was telling the truth for those units. A handful of units is not the whole organization, so repeat the tracer somewhere else before you generalize. If any unit lands in green disguise, amber, or red, the silence has shape. The model holds. The silence is data, and the dashboard was missing it.

The temptation now is to find a comfortable story — that unit is an outlier, those workarounds are user preference, the spreadsheet is fine. Resist. The whole reason you ran the tracer was to find out which story is true. Believe what came back.

After three to five conversations you can walk into the next leadership meeting and say:

Of the X business units, Y are genuinely fine, W have built their own world and we should leave them to it, Z have workarounds we can fold back in or unblock, and A have stopped trying. Here's what I learned. Here's what I'm doing about the Z and the A.

That statement earns you the next meeting. The strategic planning one. The budget one. Not a program.

Three to five conversations will tell you which kind of silence you are looking at. They will not tell you what to do once you have sorted it.

That is the workshop. We teach the instrument that reads the silence once you have found it — how IT shows up at a table it does not own, what you say at the operating review when the win belongs to the BU, and what kills the practice at each stage of maturity. It runs as a two-day intensive built around your org, not around a stack or a vendor.

If the tracer bullet tells you the silence has shape, come. If you ran the tracer and everyone said fine, save your money — you do not have the problem this workshop solves.