Customization sprawl: 800+ custom fields per object, 200+ flows on the same object, dozens of triggers. Eventually unmaintainable.
Governance mechanisms:
1. Architecture Review Board (ARB).
A small group of senior architects/admins reviews proposed changes above a threshold (e.g., new custom object, new integration, more than 10 hours of work). Approves, denies, suggests alternatives.
Cadence: weekly or bi-weekly.
2. Standards documentation.
- Naming conventions — fields, classes, flows.
- Trigger framework — one trigger per object, handler pattern.
- Sharing patterns — when to use what.
- Custom code criteria — when is custom code justified.
- Field deprecation process — how unused fields get retired.
3. Change request process.
Before building: submit a request explaining the business need, alternatives considered, estimated effort. Reviewed and prioritised.
4. Quarterly cleanup sprints.
Once a quarter, dedicate a sprint to:
- Removing unused fields.
- Consolidating redundant flows.
- Updating deprecated patterns.
- Closing out tech-debt items.
5. Metrics dashboard.
- Custom field count per object.
- Active flow count per object.
- Apex class count and total lines of code.
- Test coverage trend.
- Number of validation rules per object.
When metrics cross thresholds (e.g., 200 fields on Account), trigger review.
6. Sunset policy.
- New customisation added with a "review by date" — typically 12-18 months out.
- At review, validate: is this still used? Still needed? Still the best approach?
Cultural enablers:
- Leadership backing — without exec support, governance is ignored.
- Build trust through helpful, not bureaucratic, governance — denying requests without alternatives breeds resentment.
- Visibility of architecture — share the org's data model, integration map, technical debt with stakeholders.
Anti-patterns:
- No governance — accumulate forever.
- Over-bureaucratic governance — everything needs ARB approval; nothing ships.
- Governance without measurement — no data on whether it's working.
- One-time governance — set up, then ignored.
A senior consultant helps clients set up governance proportional to org size — too heavy for small teams; too light for enterprise.
The most senior insight: most "customization" requests don't need customization — they need configuration of existing features, or a different process altogether. Governance is partly about asking "do we really need to build this?"