Earn the Ask

Read access to our data lake was the first ask, and nobody had actually said no to it. Full codebase access was different. It carried real risk: support didn’t own the services, and a bad change would become engineering’s problem. “This would make us better at our jobs” wasn’t going to be enough.

We got it anyway, because by then engineering had been watching us work for a long time.

Trust is a record

“Build your network” has never been useful advice to me. It treats trust as a visibility problem: meet more people, get into the right rooms, make sure leaders know your name.

I think of it as a record. Do you follow through? Is your information accurate? When you bring someone a problem, have you already done the part you could do yourself? People read the whole record every time you ask them for something.

By the time we asked for the codebase, ours was good. Our escalations came with a reproduction and the relevant data, so engineering didn’t have to start over. When a diagnosis changed, we corrected it. We sent the useful context instead of a long customer thread, and we followed up so the people who helped knew how it ended.

Asking for the codebase

We could say exactly what the access would change. Support could read the implementation, follow an investigation past the symptom, and contribute through the same pull request process as anyone else. We weren’t asking engineering to lower its review bar or route around code owners.

Engineering could still have said no. But they weren’t deciding on “trust us.” They were deciding on everything we’d already sent them.

You can’t see the balance

The mistakes that wear a record down are small, and nothing marks them when they happen.

Call every bug urgent, and engineering learns to discount your urgency. Forward complaints without checking them, and they learn to redo your work. Miss a commitment without saying anything, and your next promise is worth less. Promise a customer a timeline you don’t own, and you’ve spent authority you never had. An SLA says what the company owes the customer. It doesn’t give support control of engineering’s roadmap.

None of these start an argument. They show up later, when another team starts rechecking your facts or asking for more proof than it used to.

Spend it

The opposite mistake is being so careful with your credibility that you never use it. The point of building the record is to make the ask possible.

Good asks pay for themselves. Codebase access let support ship small fixes that would otherwise have sat in the backlog, and each one went through normal review and added to the record. Code owners still review every PR. The team just gets to take an investigation further than it used to.