Too many priorities, none of them yours

Everything is urgent, the backlog grows faster than the team does, and the roadmap is a list of other people’s requests. Ask what the team is for and the answer is a description of what it does: dashboards, pipelines, ad hoc analysis, supporting the business. It works hard, and nobody outside the team, often nobody inside it, could say what it would refuse.

The usual fix is a prioritization framework. Score each request on impact, effort and confidence, rank the list, work from the top. I have used most of them, and they do what they promise: they sort the queue. What none of them does is ask whether an item belongs in the queue at all. A team that scores every request has already agreed that every request is a candidate, and it gets steadily better at ranking other people’s priorities.

The question I ask instead has two halves: what is the team for, in one sentence, and which of this quarter’s work would that sentence decline?

A remit is a sentence that declines something

Most teams can produce a sentence. It usually declines nothing.

Declines nothing

“We deliver trusted data and insight that helps the business make better decisions.”

Every request ever made of a data team passes it.

Declines something

“We keep the twenty numbers the company is run on correct, current and explained. We do not build reports for a single department.”

Narrower than is comfortable, which is the point.

The second sentence names what the team is accountable for, implies what done looks like, and gives a reason to say no to work that is useful, well-intentioned, and somebody else’s to do. Three checks I apply to a draft:

1. Does it decline something real? Walk this quarter’s list against it. If nothing fails, the sentence is a slogan.
2. Would the people it declines recognize it as fair? A remit only the data team believes in is a wall, not a remit.
3. Does it name an outcome the team owns? “Support the business” is a posture. “Keep these numbers correct and explained” is a job, with a way of failing at it.

Why the queue fills with other people’s work

The mechanism is not mysterious. A central data team is a shared service with no price. A request costs the person making it one message, and every request is individually reasonable: this dashboard, that extract, one more cut of the numbers before Thursday. Each yes buys a little goodwill and each no spends some, so without a remit the team’s value is measured by how often it says yes. It says yes until it cannot, and then it says “not yet” to everyone, which does more damage than a clear no to a few.

There is a second mechanism underneath, and it explains the title. The work a central team is uniquely placed to do (shared definitions, data quality, the platform itself) rarely arrives as a request. Nobody files a ticket asking for a metric to have one owner. A roadmap assembled from requests is, by construction, a roadmap with none of the team’s own work in it.

Order matters here. In building a data function from zero, an early move was pulling the engineers already there into a core team with a clear remit and a line to the decisions its work fed, and the tools came last. A team formed without that sentence inherits whatever queue is waiting for it.

Decline one thing, with the sentence

A remit becomes real the first time it declines something a senior person wanted. Until then it is a draft.

The practice I suggest is deliberately small. Write the sentence. This month, use it to decline one piece of work, and give the sentence itself as the reason: this falls outside what the team is for, which is this; here is who could help, or what would bring it inside. Then report what happened.

Three things make the decline land:

• A route. Point to another team, a self-serve option, or the condition under which the work would come inside the remit. A no with a route is a decision. A no without one is a closed door.
• The right altitude. If the requester outranks you, the decline may need to come from your manager, using your sentence. That is not a failure of nerve. It is finding out who owns the remit.
• A record. Keep a short list of what the sentence declined and what happened next. It is the evidence you will want when someone asks, at review time, why the team is not doing more.

What happens next tells you more than the sentence did. If the decline holds, the remit is real. If it is overturned, you have learned who actually sets the team’s priorities, which is often the more useful finding. It also answers a question worth asking separately: is anyone at your level able to decline work, or is this a structure rather than a judgment about you?

When the sentence is not yours to write

Not everyone with this problem runs the team. An analyst whose week is other people’s requests has the same problem one level down, and cannot rewrite the team’s remit alone.

Two moves still work. Write a personal remit inside the team’s: what you are accountable for, and what you would hand back. Take it to your manager as a proposal rather than a complaint. And separate the decisions you can make from the ones you can only influence. Declining a request may not be yours to decide. Proposing the sentence that would decline it usually is.

What it costs

A remit is a trade, and it is worth naming the price before paying it.

Some declined work gets done badly elsewhere. A department told no may build its own spreadsheet, hire its own analyst, or buy a tool. Some of that is healthy. Some of it produces a second version of a number the team exists to keep single. The remit should say which is which, and every decline should point to the healthy route.

The team looks less busy. Fewer requests closed can read as less value to anyone counting tickets. The record of declines, and what the team built with the time instead, is the answer, and it has to be kept on purpose.

Goodwill gets spent. A clear no costs more in the moment than a vague “we’ll look at it,” and some people will remember it. The trade is breadth of goodwill for depth of trust in fewer things. I think it is the right trade for most central teams. It is still a trade.

Some declines will be wrong. A remit written this quarter will decline something that matters next quarter. Review the sentence on a schedule, and treat a wrong decline as evidence about the sentence rather than a reason to abandon it.