No data team. Engineers working in a vacuum, product managers asking developers for numbers, and every department with its own analyst producing a different answer to the same question. The platform was the straightforward part.
→Centralize the definitions first, the people second, the tools last
→Analysts join the center for governance and stay close to their department
Org design
Platform strategy
Enablement
Read the case study →
Central platform team federating ownership to domain analysts
A deliberate giveaway of central control, and an org-design decision that looked like a tooling one. Throughput went up and consistency went down. The second half of that sentence is real, and most write-ups omit it.
→A central team that owns every change is a bottleneck in platform clothing
→Federated ownership trades uniform quality for throughput, knowingly
Move the data team out of IT, the take says: it is a ticket desk, far from the decision. The symptom is real and the diagnosis is a blanket. A move helps when it changes what the team is measured on, who may decline a request and who pays for the engineering. The reporting line alone guarantees none of them.
Most data interviews test whether a candidate can answer the question as asked. The job is to change a decision. Hand the candidate a bounded decision with incomplete evidence, ask for a recommendation, an alternative and a condition, and listen to the reasoning.
A data career leaves a visible record of dashboards shipped, pipelines built and tickets closed, and none of it says whether anything changed. The record worth keeping is the decisions you were part of: what you recommended, what was decided, what happened, and what you would change.
The person everyone sends their work to becomes the team’s bottleneck, and for a long time on my team that person was me. How to share the judgment, make room for the work, and recognize the contribution without keeping the dependency.
When a data team’s roadmap is a list of other people’s requests, a better scoring model only sorts the queue. What changes it is one sentence about what the team is for, used to decline something.
Being the strongest technical contributor can make you the team’s default decision maker. How I would develop someone else’s judgment without leaving them unsupported or quietly taking the work back.
Moving data model ownership from engineers to analysts looked like a tooling change. It was a governance change wearing a tooling costume, and once systems started answering questions, ownership stopped being about speed and became authorship.