Governance without the theatre
A light governance model that keeps HubSpot clean without slowing anyone down. Naming, permissions, change control and documentation that actually work.
- By
- Joe Birkedale, Founder & CMO
- For
- CRM and revenue operations
- Published
- 1 Jun 2026
- Read
- 2 min
- Source
- project36.io
Short answer
- Governance is not a committee. It is a small set of rules that stop HubSpot decaying between reviews. If it is too heavy to run weekly, it will not run at all.
Key takeaways
- Effective HubSpot governance covers naming and taxonomy, permissions and roles, change control, and a single place for documentation.
- A minimum viable model includes one named object model owner, a visible one-page naming convention and a documented change control path of no more than three steps.
- Review new fields, workflows and dashboards for 20 minutes each week, and retire unused properties, workflows and dashboards quarterly.
- CORE™ tests whether each property, workflow, dashboard or list serves one of its five indicators, with assets that do not becoming candidates for retirement.
Almost every HubSpot portal we audit has some form of governance on paper, and almost none of it in practice. Rules that require a meeting to enforce do not get enforced. The version that works is smaller than most teams expect.
What governance actually needs to cover
Effective HubSpot governance covers four things: naming and taxonomy, permissions and roles, change control, and documentation. Anything beyond that is usually theatre.
- Naming and taxonomy, properties, workflows, lists, dashboards, campaigns.
- Permissions and roles, who can see what, who can change what.
- Change control, how new fields, workflows and reports get added.
- Documentation, one place where the current model lives.
Rules that survive a Monday morning
The test for any governance rule is simple. Does it survive contact with a sales rep who needs to close a deal at 5pm on a Friday? If the answer is no, the rule is theatre.
Good rules are close to the work. Property naming conventions live where properties are created. Permission changes go through the person who owns the object model, not through a monthly forum.
A minimum viable governance model
- One named owner for the HubSpot object model.
- One naming convention document, one page long, visible to everyone.
- A weekly 20-minute review of new fields, workflows and dashboards.
- A quarterly cleanup: retire unused properties, workflows and dashboards.
- One documented change control path, no more than three steps.
What CORE™ adds
Governance without a model to govern is a housekeeping exercise. CORE™ gives governance something to enforce: does this property, workflow, dashboard or list serve one of the five indicators in the CORE™ model?
If yes, it stays and is maintained. If no, it is a candidate for retirement. This single test cuts most HubSpot portals in half within a quarter.
Frequently asked
With revenue operations. IT holds security and integration standards, but the operating model belongs to the business, and the business runs it.
No. You need a named owner, a small standard, and a short weekly review. Committees are where governance goes to die.
Quarterly for retirement of unused assets. Annually for a full audit of the object model. Weekly for review of what has been added.
27 Aug 2026
Your Business Grew. Did Your HubSpot Grow With It?
Read6 Jul 2026
HubSpot reverses its data enrichment and AI terms update. What it means for your portal
Read25 Jun 2026
That Google Warning: Are Your HubSpot Permissions a Ticking Time Bomb?
Read25 Jun 2026