The Analyst Who Became the Gateway

Refresh fails. Someone messages the analyst.

A VP needs access. Someone messages the analyst.

“What does this include?” Someone messages the analyst.

The tenant has workspaces, apps, and a gateway appliance. The company still has one human routing path. That person is not a steward. They are infrastructure.

A bus-factor of one is not a compliment. It is an unowned product wearing a hero.

Occupied is not the same as owned

This is not folklore inside the file: tribal knowledge in the data model. You can document the model and still route every runtime question to one inbox.

This is not an empty chair: why your Power BI project has no owner. That chair is empty. This one is full. The analyst became the path around the empty seats.

This is not who may change a measure. Change control is the formula. The gateway-person also resets credentials, grants access, explains the pack, and reruns Thursday’s refresh.

Waiting on IT is a different queue: the hidden cost of waiting on IT. Here the queue is one named human who absorbed operations, support, and meaning. The appliance can have a backup: when refresh fails before stand-up. This post is the person every question has to cross.

Hero culture feels efficient until they are out. Then you discover you had a bridge, not a program.

What “the gateway” actually does

They keep the refresh jobs in their head. Access as a favor. The sentence for what Revenue includes. The meeting, because someone has to drive the page. Delivery never split runtime, access, and meaning, so one competent person absorbed all three.

The costs of a person-as-gateway

1. Vacation is an outage. Not a courtesy delay. Refresh, access, and “what does this include” pause. Close week does not pause. The company will still call it a staffing issue. It is an architecture issue with a calendar.

2. The queue is a person, not a backlog. Requests die in chat. There is no intake, no “we are done,” no steward list. The loudest DM wins. Standing questions stay heroic extracts because the hero is available: executive questions that should never be ad-hoc.

3. Definitions live in messages. The measure description is empty because the analyst will explain it live. When they are not in the thread, the room invents a sentence. Trust becomes whoever spoke last.

4. Access is a favor, not a control. Personal shares bypass groups. Row-level security gets waived “just this once.” When the analyst leaves, nobody can say who can see the number—or who should.

5. Refresh is tribal operations. The job succeeds most days. The runbook is a person. Capacity collisions, credential rotation, and close-week order live in one head. Finance learns about staleness from a VP, not from an on-call.

6. Quality drops because one seat does three jobs. The same person builds, supports, and explains. Build loses. Support is endless. Meaning stays oral. You cannot hire a successor because the posting would say “owns Power BI,” which is not a role. It is a confession.

7. Hero culture hides underfunding. Leadership praises responsiveness. That praise postpones a steward, a backup, a group-based access path, and a refresh SLA. The compliment is the cover.

8. The product cannot be inherited. A successor can be walked through the file and still fail on Monday, because Monday is not the file. Monday is the routing: who to call, which workspace is a lie, which refresh to rerun first. People do not scale. Paths do.

A bus-factor of one is a close risk, an access risk, and a meaning risk wearing the same hoodie.

How to stop routing the company through one inbox

1. Split runtime, access, and meaning. Refresh and gateway operations get an on-call and a runbook. Access gets groups and a request path. Meaning gets a named steward who can say the sentence. One human may still do two of these in a small shop. They should not be the only path for all three.

2. Write the three things the DMs currently hold. As-of and refresh order. Who is in which group. The measure sentences the room actually asks. If it only exists in chat, it is not a product.

3. Put refresh on an SLA with a backup. Success is the certified model current through the agreed grain before the first meeting that uses it. A second person must be able to rerun, rotate, and declare stale. If that sentence is impossible, you have a gateway-person, not a gateway.

4. Move access off personal shares. Apps, groups, roles. The analyst should not be a permissioning desk. Exceptions get a named expiry. Row-level security is who sees the number—not who the analyst likes this week.

5. Name a steward who is not the only builder. The steward owns the sentence and the change path. The builder ships. If they are the same person, at least name a backup steward and a backup builder. Occupied chairs still need deputies.

6. Publish “what does this include” where the page lives. Description, glossary, or a certified info page. The next “is freight in this” should not require a human to be online. If the model cannot say it, that is a product gap.

7. Cross-train before the next outage. Not a slide hour. A second person runs close-week refresh, grants a group, and explains Revenue out loud. If they cannot, the bus-factor is still one. You just scheduled it.

8. Measure the inbox. How many requests are refresh, access, or meaning. That mix is your org chart. A pile of meaning questions is a steward problem. A pile of access questions is an identity problem. A pile of refresh questions is an operations problem. Stop hiring “another analyst” as the universal solvent.

9. Stop praising the bottleneck. Thank the person. Fund the path. A compliment without a deputy is how you lose them and the estate in the same quarter.

What a company with a path looks like

Refresh has an SLA and a named backup. Access is a group. The room can read what a measure includes without waiting. The analyst still builds. They are no longer the appliance. Vacation is inconvenient. It is not an outage.

Executive takeaway

If refresh, access, and meaning all route through one person, you do not have a Power BI program. You have a bus-factor.

That is not a compliment. Split the path. Write the runbook. Name a backup. Put the sentence on the product.

Need a 30-minute look at whether one analyst has become the gateway? Contact Alluvium. We’ll map refresh, access, and “what does this include”—and which of those still require a single inbox.