You turn IT, risk, and HR into one governance team by giving them a shared mandate, a single committee with clear decision rights, and common policies they co-own. Instead of three departments protecting their own priorities, your law firm gets one group accountable for how client and staff data is handled.
The shift works best when it is led by senior management and framed around outcomes your partners already care about: client trust, regulatory confidence, and efficient work. Below, we walk through the questions that come up most often when firms build this kind of team as part of a data governance implementation roadmap.
Why do IT, risk, and HR clash on data decisions?
IT, risk, and HR clash because each function measures success differently and sees different dangers in the same data. IT prioritises availability and usability, risk prioritises exposure and compliance, and HR prioritises employee privacy and fairness. Without a shared goal, each team defends its own concern.
A few patterns show up again and again:
- Different definitions of “good”: a fast, flexible system looks great to IT but worrying to risk.
- Unclear ownership: when nobody owns a data set, every team assumes someone else does.
- Separate reporting lines: decisions are made in silos and only meet when something goes wrong.
- Different vocabulary: the same word, such as “retention” or “access”, can mean something different in each team.
None of this is bad faith. It is a structural gap, and a structural gap is fixed with structure: shared goals, shared language, and a shared table to sit at.
Who should sit on a law firm governance committee?
Your governance committee should include a senior partner sponsor, plus representatives from IT, risk and compliance, HR, information governance, and the data protection officer. Keep it small enough to decide quickly, ideally six to nine people, and make sure every member has genuine authority to commit their team.
A practical line-up looks like this:
- Executive sponsor: a partner or C-suite leader who can break ties and signal importance to the whole firm.
- Chair: often the head of data or information governance, who keeps the agenda moving.
- IT and security lead: explains what is technically possible and what it costs in time and effort.
- Risk and compliance lead: represents regulatory and professional obligations.
- HR lead: speaks for staff data, onboarding, leavers, and training.
- Data protection officer: advises on privacy requirements.
- Practice group voice: a fee-earner who reminds everyone how lawyers actually work.
Avoid filling the committee with people who attend but cannot decide. Seniority matters less than the ability to say yes on behalf of a department.
How do you define roles and decision rights?
You define roles and decision rights by writing down who proposes, who decides, who must be consulted, and who is informed for each type of data decision. A simple responsibility chart, agreed in writing by the committee, removes the guesswork and ends most turf disputes before they start.
Work through it in three steps:
- List your recurring decisions. Examples include granting access to sensitive matters, setting retention periods, approving new tools that touch client data, and handling a data incident.
- Assign one accountable owner per decision. Shared accountability sounds fair but usually means no accountability. Others can be consulted, but one person decides.
- Agree on an escalation route. When two functions disagree, the executive sponsor makes the call within a set timeframe.
Also name data owners within the business, such as the practice group head responsible for matter data. Governance sticks when the people closest to the information are accountable for it, not just the support functions.
What shared policies and processes should the team own?
The combined team should jointly own the policies that cut across all three functions: data classification, access and permissions, retention and deletion, incident response, and onboarding and leaver procedures. Owning these together means one consistent rule set instead of three overlapping ones.
Start with the processes where handoffs between teams cause the most friction:
- Joiners, movers, and leavers: HR triggers the process, IT executes it, and risk checks it was done properly.
- Data classification: a common way of labelling information by sensitivity that everyone uses.
- Retention and deletion: clear rules for how long client and staff data is kept and who approves its removal.
- Incident handling: one playbook with defined roles, so nobody debates who leads during a real event.
- Taxonomy and naming: a shared structure so information can be found and governed consistently.
A phased approach works well here. Pick two or three policies for the first quarter, finish them properly, and build from there. This is the heart of a realistic data governance implementation roadmap: fewer policies, fully adopted, beat a long list nobody reads.
How do you get partners and staff to follow the model?
You get partners and staff to follow the model by making it easy, visible, and relevant to their daily work. People comply when the rules save them time or protect their clients, and when leadership follows the same rules. Training, clear communication, and partner sponsorship do more than enforcement ever will.
Some approaches that help:
- Lead from the top. When partners follow the process openly, everyone else notices.
- Explain the why. Link every policy to something lawyers care about, such as client confidence or winning panel work.
- Keep it simple. A one-page guide beats a forty-page manual.
- Train by role. Fee-earners, secretaries, and HR staff each need different examples.
- Listen and adjust. Invite feedback and show people when you changed something because of it.
Treat adoption as a people project, not a technology rollout. The tools matter far less than whether your colleagues understand and trust the approach.
How do you measure whether the combined team works?
You measure the combined team by tracking a small set of indicators covering decision speed, policy adoption, incident handling, and stakeholder confidence. If decisions are made faster, fewer issues are escalated, and partners report greater clarity, the team is working. Review these indicators regularly rather than once a year.
Useful measures include:
- Time to decision: how long it takes to resolve a cross-functional question.
- Policy adoption: the share of teams actively following the agreed processes.
- Incident response: how quickly and smoothly issues are contained and reviewed.
- Completion of training: who has been trained and how confident they feel.
- Stakeholder feedback: a short, regular check-in with partners and department heads.
Share results with the committee and the wider firm in plain language. Visible progress builds momentum and keeps governance on the leadership agenda.
How Iron Carrot helps with building one governance team
We help your law firm bring IT, risk, HR, and your other data-related functions into one aligned governance approach. Through our Global Data Strategy service, we work alongside your Data Governance, Information Governance, IT Security, Innovation, DPO, and Business Intelligence teams to create a firmwide data strategy that works for everyone.
Here is what that looks like in practice:
- Facilitating conversations so each function is heard and shared priorities emerge
- Defining committee membership, roles, and decision rights that fit your law firm’s culture
- Shaping the shared policies and processes your team will co-own
- Supporting adoption through practical training and clear communication
- Building long-term relationships so your governance model keeps improving
If your teams are pulling in different directions, we would be glad to talk. Get in touch with Iron Carrot to start shaping a governance team your whole law firm can rely on.
Related Articles
- What are the signs your data governance roadmap lacks stakeholder support?
- How do you run a data governance workshop with senior stakeholders?
- How do you keep data governance momentum going in 2026?
- What language works best when talking to lawyers about data governance?
- What does change leadership look like in a data governance programme?
