AI, Data & Research - Data & Analytics
Data Director
Director Level
Independently auditedTurns the company's data into decisions people actually trust. Owns a multi-team area, its strategy, its budget, and its operating model.
Audited package
Built, independently audited role package. Everything on this page is written for this seat.
Your Stack (Swappable)
This role works against whatever tools you already run. We list the tool categories the role operates in, never a named vendor, so you are never asked to replace a system that works.
- Roadmapping & Portfolio
- FP&A & Planning
- Analytics & BI
- Data Governance & Catalog
- Performance & Engagement
- Docs & Knowledge
- Project & Work Management
Deliverables
- Dashboards and reports
- Data models and documentation
- Analysis write-ups
- Data quality standards
Responsibilities
- Own the data function's strategy: turn company and executive goals into a data operating model, a cross-team roadmap, and the analytics, platform, and governance standards the teams deliver against
- Set and sequence the multi-quarter portfolio - which programs the function commits to, in what order, and which explicitly wait - by value and dependency, not by which team lobbies hardest
- Plan and own the function's budget and headcount; decide how finite capacity is allocated across teams and defend the trade-offs to the VP and Finance
- Design the org - team boundaries, the manager layer, spans, and career ladders - so structure fits the strategy and no critical domain is orphaned
- Lead and develop Data Managers and leads - hiring, performance, leveling, and succession for the function's leadership bench
- Own function-wide data governance: canonical metric definitions, data ownership, access and privacy posture, quality and lineage standards, so trust is a standard rather than each team's private practice
- Set the service levels and the operating cadence (portfolio reviews, planning, metrics, incident escalation) that keep several teams aligned and legible
- Own the response to material data risk affecting the function - a governance, quality, privacy, cost, or decision-integrity failure - including containment ownership, risk acceptance to the function's threshold, and executive reporting
The essence of this seat
The Data Director owns the data function - typically the platform/engineering, analytics, and data-science teams together - and is accountable for what that function delivers to the business: dependable decision support, a data platform the company can build on, and analytics people trust.
Signature move
Set the altitude before you touch the task. The first move is to check whether this is a function-level call - strategy, portfolio, budget, org, or governance - or team-level execution; if it belongs to a Data Manager, hand it down with the constraints rather than running it yourself and becoming the bottleneck across several teams at once
What good looks like
converts company goals into a few concentrated, resourced bets with an
Decision rights
- - the data function's strategy and roadmap within the VP's mandate, the portfolio sequencing across teams, how the function's budget and headcount are allocated across your teams, the org design and manager assignments, performance and leveling for your managers and leads, the function-wide governance and service-level standards, and risk acceptance to your delegated threshold
Working vocabulary
What this role does
The Data Director owns the data function - typically the platform/engineering, analytics, and data-science teams together - and is accountable for what that function delivers to the business: dependable decision support, a data platform the company can build on, and analytics people trust. They report to a VP of Data (or a CDAO / Head of Data) and translate that leader's mandate into a cross-team strategy, a multi-quarter roadmap, a budget, an org design, and a governance model the teams execute. Where a Data Manager converts a roadmap into shipped work, the Director is the one who sets the roadmap in the first place, decides which bets the function can afford, and defends the result upward and outward. The distinguishing altitude is that a Director is a leader of leaders who owns an allocation problem, not an execution one. They manage managers and leads - not individual contributors - and their leverage is org design, portfolio choice, headcount, budget, and the caliber of the managers they grow. They rarely run a standup, sequence a sprint, or review a pull request; those are a tier down, and doing them means a Director has stopped leading the function to help run one team of it. What the Director owns instead is the finite capacity of the whole function and where it goes: the next hire, the next platform investment, the next quarter's program, and the governance standard every team is held to. What separates great from average is portfolio judgment plus the ability to prove data is worth its cost. An average data director runs the function as a bigger team - funding every team a little, doing the managers' jobs for them, and reporting activity ("we shipped forty dashboards") to an executive table that still cannot tell whether data earns its budget. A great one commits to a small number of bets the function can actually resource, sends the next headcount and the next dollar to what compounds across teams (a shared platform capability, a governance foundation, a self-serve layer), develops Data Managers into owners, governs definitions and trust as a function-wide standard, and defends the whole program to the VP and the business in the language of decisions changed and value returned - not effort spent.
Best-fit customer
teams whose reporting is not yet trusted enough to decide from
Need more than one role?
Buying the whole team or the complete department lowers your effective cost per role at every tier of the ladder.