In your first 90 days as data governance manager, aim for one visible result, not a complete framework. Spend the first 30 days listening and picking one scope: a report leadership reads every week. Use days 31 to 60 to agree its key definitions and name an owner for each. By day 90, show those definitions on the report, share what changed, and use that result to ask for the next scope.
At a glance
- A governance framework written in your first months mostly gets read by the people who wrote it.
- One report that people already use, with agreed definitions and named owners, is a result the business can see.
- What you learn on that first scope is the evidence you need to ask for the next budget.
Why a complete framework is the wrong first deliverable
Most new governance managers think their first job is to design the programme. Policies, roles, a council, a maturity model. It feels responsible, and it's what many roadmaps recommend.
The problem is that nobody outside the data team notices a framework. Your sponsor hired you to fix something they can feel: numbers that don't match, reports nobody trusts, the same question asked in every meeting. If day 90 arrives and that hasn't changed, the programme starts to look like overhead.
For example: the commercial director sees two revenue figures in two reports every Monday. A policy document doesn't change that. One agreed definition, shown on the report she reads, does.
Days 1 to 30: listen, map and pick one scope
Your first month is for understanding, not building. Talk to the people who use data to make decisions, not only the people who produce it.
- Meet your sponsor and five or six business leads. Ask one question: which number do you doubt most often, and in which report?
- Map what exists. Which reports, data sources and glossaries are already there, who built them, and which are still used. Don't fix anything yet.
- Find the existing owners. Someone already answers questions about most data sets, formally or not. Write their names down.
- Pick one scope. One report, or a small set, that leadership reads every week and argues about.
A good first scope is read often and disputed often. A report that's rarely opened won't show your result. A report nobody disputes doesn't need you yet.
Days 31 to 60: agree definitions and name owners
Now work on the scope you picked. Keep it small enough to finish.
- List the measures on the report that people actually discuss. Usually that's a handful, not every field.
- Write one plain-language definition per measure. No DAX, no SQL. A sentence a sales manager would understand.
- Get the definition agreed. Put Finance and the business owner in one room for the disputed ones. Write down what you agree and what you don't.
- Name one owner per measure. A person, not a team, who can change the definition and answers questions about it.
- Note the known problems. If a source is late or incomplete, write that down too. Honesty about weak spots builds more trust than a clean story.
In practice, step 3 is where most of your time goes. That's normal. The disagreement was always there; you're just making it visible.
Days 61 to 90: make it visible and show the result
A definition people can't see is a definition people won't use. This month is about putting your work where readers already are.
- Show definitions and owners on the report itself, not only in a separate document. Readers won't leave a report to look something up.
- Tell the readers. A short note to the people who use the report: what's defined, who owns what, where to ask.
- Collect what changed. Fewer questions to the BI team, a meeting that didn't stall on a number, a dispute settled. Use concrete examples, not a score.
- Present the result to your sponsor with a proposal for the next scope, built on what you learned.
What to leave until after day 90
Some things matter, but they work better once you have a result to point to.
| Comparison | Framework first | Scope first |
|---|---|---|
| First deliverable | Policies, roles and a governance council | One report with agreed definitions and owners |
| Who notices at day 90 | The data team and the sponsor | The people who read the report |
| What you can show | Documents | Questions answered and disputes settled |
| Risk | The programme looks like overhead | The scope is too small to impress, if chosen badly |
| When it fits best | Regulated areas where a policy is required first | Most business reporting |
A formal council, an organisation-wide policy and a full catalog rollout can all come later. They'll be easier to agree once people have seen what governance changes for them.
How do I get the business to take data governance seriously?
Show them something they care about, early. Business leaders take governance seriously when it fixes a problem they've complained about. Start with their report, their number and their argument, and talk about definitions and owners rather than governance.
A practical framework: Listen, Scope, Define, Own, Show
- Listen: ask business leads which number they doubt most, and where they see it.
- Scope: pick one report that is read often and disputed often.
- Define: write one plain sentence per measure that people discuss, and get it agreed.
- Own: name one person per measure who can change the definition.
- Show: put definitions and owners on the report, then present what changed.
Prove governance is worth doing
Your first 90 days won't fix governance. They can prove it's worth doing. Pick one report people already argue about, agree what its numbers mean, name who answers for them and show it where people read. Then ask for the next scope, with a result behind you.
Frequently asked questions
What should a new data governance manager do in the first week?
Meet your sponsor and ask what they expect to be different in three months. Then start meeting business leads and asking which numbers they doubt. Don't start writing policies yet.
How do I choose the first scope for data governance?
Pick a report that leadership reads often and disputes often. It should be small enough to finish in about two months and visible enough that people notice when it improves.
Should I buy a data catalog in my first 90 days?
Not necessarily. Start with the scope and the definitions, then decide what tool helps you keep them current and visible. If you do pick a tool early, check that it shows definitions where people read, not only in its own portal.
How do I measure the success of my first 90 days?
Use concrete examples rather than a maturity score: a meeting that no longer stalls on a number, fewer questions to the BI team, a definition both Finance and Sales now use. Your sponsor will remember those.
Do I need a data governance council from day one?
Usually not. A council works better once there's a result to steer and owners to bring together. Start with the people who own the measures in your first scope.