“Data governance” usually conjures images of committees, policies and dedicated staff. Large organizations do need that. But the underlying questions — who is responsible for this data, what does it mean, who can see it, and how does it change — apply to a ten-person business just as much as a ten-thousand-person one.
The good news is that a small team can answer them with a handful of habits rather than a program.
Habit 1: Every kind of data has an owner
For each important kind of information — customers, locations, open jobs — name the team that answers for it. The owner doesn’t enter every value; they decide what “correct” means and fix things when they’re wrong.
Assign teams, not individuals. People go on holiday and change roles; a team’s responsibility survives both.
Make unowned data visible. Records with no owner should be easy to find, so they can be assigned rather than forgotten.
Habit 2: Write definitions down
The most common governance failure in small teams isn’t a breach — it’s disagreement. Two people count “active customers” differently, and every meeting starts with reconciling numbers.
Keep a short list of definitions for the terms that matter: what an “active customer” is, what counts as a “completed job”, which address is the service address. Better still, build the definitions into your systems, so forms and records enforce them.
Habit 3: Grant access by need
Decide access by asking what each role needs to do: know that information exists, look it up, change it, retire it, or be responsible for it. Start narrow and widen when a need appears. It’s much easier to grant access someone turns out to need than to take back access they shouldn’t have had. See Least-privilege access for business data.
Habit 4: Control how definitions change
Forms and fields will change as the business evolves. The governance question is whether those changes are deliberate and visible.
- Draft, then publish. Separate working on a change from making it official.
- Version, don’t overwrite. Old answers should keep the meaning they were collected with.
- Tell people. A one-line note when a form changes prevents a week of confusion.
Habit 5: Review regularly
Governance isn’t set-and-forget. A short monthly review works for most small teams:
- Are there records without an owner?
- Has anyone been given access they no longer need?
- Are there duplicate or near-duplicate forms or fields that should be merged?
- Did any definition change, and did everyone hear about it?
Thirty minutes a month is enough to keep small problems from becoming large ones.
What good governance feels like
When these habits are in place, data stops being something people argue about and becomes something they use. New team members know where to look. Reports are trusted. Customers get consistent answers. And audits, investor questions or due diligence become far less painful.
A one-page governance charter
Small teams don’t need a policy library. One page covers it:
- Owners. A table of information types and the team responsible for each.
- Definitions. The ten terms that cause the most confusion, defined in a sentence each.
- Access. Which roles get which level of access to which information.
- Change process. How definitions change: who proposes, who approves, how people are told.
- Review. When the monthly check happens and who runs it.
Keep it where people work, not in a folder nobody opens.
Governance as the business grows
| Stage | What governance looks like |
|---|---|
| 1–10 people | Shared understanding; one page; owners named informally |
| 10–50 people | Written definitions; roles and groups; deliberate change process |
| 50+ people | Formal policies, audit trails, regular access reviews |
The trap is jumping to stage three’s paperwork at stage one, or staying at stage one when the team has tripled.
Signs governance is missing
- Two reports of the same number disagree, and nobody can say which is right.
- People ask in chat where information lives.
- A former employee’s access is still active.
- Nobody knows who decided a field should be required.
- The same customer exists three times.
Each maps to one of the five habits: definitions, one home, access, change control, ownership.
Making it stick
- Attach governance to work people already do. A monthly review during an existing meeting beats a new one.
- Prefer systems that enforce the rules. A definition the software applies beats a definition in a document.
- Make the right path the easy path. If the governed way to submit information is the fastest way, people use it.
- Record decisions briefly. One line explaining why a field is required saves an argument later.
Frequently asked questions
Do we need a data steward? Not a full-time one. Name someone responsible for each kind of information; it’s usually part of an existing role.
How does this relate to privacy regulations? Good governance — knowing what you hold, who can see it and why — is the foundation for any regulatory obligation you may have. Specific requirements depend on your jurisdiction and industry.
What’s the smallest useful step? Write down who owns customer data and what “active customer” means. Everything else builds from there.
Tools that help
Governance is easier when your tools express it directly. Stratosphere Atlas builds several of these habits into the product: topics are owned by user groups and unowned topics are collected under Unassigned Topics; security policies grant Discover, Read, Write, Archive and Manage access to roles and groups; and schemas are drafted, published and versioned rather than edited in place. See Why every topic needs an owner.
