CRM Governance Guide: Ownership and Change Control

List required and reporting-critical fields. Each needs a business owner (defines meaning and when it must be filled) and an admin implementer (configures validation and views). Stage definitions get the same treatment: exit criteria written, owner named, managers trained to reject dishonest jumps.

Example: Blue Harbor Logistics discovers fourteen custom fields with no owner after six months. Ops lead Devon deletes nine unused fields, assigns owners to five that feed Friday reviews, and freezes new fields until a change request exists.

Treat stage edits, required-field changes, permission model changes, and automations as controlled changes. Flow: request → impact review (who breaks, what reports change) → approve/reject → configure in a controlled window → communicate → short audit that the change behaved.

Example: Meridian Specialty Finance wants a new “Credit Review” stage. Ana rejects a same-day config ask, runs a fifteen-minute impact review with sales and credit, updates exit criteria docs, then configures and announces in the Monday briefing before the stage appears.

Privilege creep is normal: contractors linger, managers inherit broad roles, export rights spread. Schedule reviews of roles, exception grants, inactive seats, and sensitive-field visibility. Document exceptions with expiry and approver.

Example: Harborline Advisory’s quarterly review finds two former contractors still in a reporting role and a temporary “see all households” grant without expiry. Keisha revokes both, adds expiry to future exceptions, and logs the review date on the governance checklist.

Unlimited “can you add a field?” queues destroy focus. Cap work-in-progress, triage weekly, and prioritize items that protect hygiene, adoption, or security over cosmetic requests. Publish what is parked and why.

Example: Crestview Wealth’s admin backlog had forty-two open asks. Priya caps WIP at five, groups duplicates, and parks AI-scoring experiments until Day-60 adoption gates pass. Requesters see the queue status in a shared note.

Weekly: admin triage + hygiene glance. Monthly: field/stage audit and backlog reorder. Quarterly: access review and RACI refresh. Tie governance to adoption and data-quality rituals so it stays operational, not ceremonial.

Example: Blue Harbor’s monthly audit finds three stages nobody can define. They merge two via change control and retrain managers — governance preventing another quarter of dishonest forecasts.