Important business data sits behind layers of approvals and costly licenses that the well-connected skip with a phone call, so everyone else waits months or gives up.
An example
A category manager at a home-improvement retailer wanted to test whether paint promotions were eating into full-price sales. The data sat in the company's new cloud warehouse. Her request needed a business case, a security review, a data-steward sign-off, a license from IT finance at four thousand dollars a seat, and a director-level sponsor, and the data council met monthly. She filed in February. In April she learned that the head of the flooring category, who was close to the chief merchant, had the same access within two days of asking, through a "temporary" shared login. Her request was approved in June, a week after the promotion calendar for the second half of the year was locked. The analysis, when she ran it, showed the promotions losing money at a third of stores. It shaped the following year's calendar.
Why it works
Each gate has a reasonable rationale: security, compliance, license cost. Together they make access costly for anyone without political standing, in calendar time and in exposure, since every request has to explain what the requester is looking for. Insiders pay almost nothing, a call to the right executive, so for them the same data is easy to reach. The gap decides whose analysis arrives before the decision. Each gate must be defensible, the bypass must stay selective, and the data must actually matter. It fails when an executive sponsor demands transparency, when license costs become trivial, or when cheaper tools route around the gates.
The thinking behind it
Jeffrey Pfeffer Pfeffer's The External Control of Organizations: A Resource Dependence Perspective (1978) holds that whoever controls a critical, scarce resource gains power over those who depend on it. Gated business data is such a resource, and the gatekeepers decide whose analysis arrives in time. Cheaper tools and published service levels reduce the dependence, which is why they weaken the paywall.
Ronald H. Coase Coase's The Problem of Social Cost (1960) argues that if bargaining were costless, the parties would reach the efficient outcome however rights were assigned; because it is costly, who holds the rights and how expensive it is to negotiate decide what actually happens. Approval chains raise the cost of getting data for some requesters and not others, so access follows political standing. Measuring turnaround by requester makes those costs visible.
Warning signs
Identical access requests clear in days for some units and stall for months for others. Each gate in the approval chain has a sensible explanation, and the chain as a whole has no published timeline. Some people have shared or temporary logins. Analyses from favored units reach decisions while others arrive after the deadline. Requests must state what you plan to look for, which tells the gatekeepers in advance.
How to defend yourself
Numbers about the process itself make the case better than complaints about any single gate.
- Track your own access requests: date filed, each approval, date granted. Ask peers to do the same.
- Compare turnaround by requester. A table showing two days for one group and four months for another speaks for itself.
- Take the table to an executive sponsor or the data council chair and ask for a published service level for access.
- Where policy allows, use cheaper analytics tools or extracts that do not depend on the gated platform.
File early for decisions you know are coming, and say in writing when a delay has made an analysis too late to use.
How a leader shuts it down
Publish the access policy with a service level, and measure turnaround by requester. Remove shared and temporary logins. Match license budgets to the people who need the data. Treat a wide gap in access times between units as a governance problem, because it decides whose analysis reaches each decision in time.