Here’s what I’ve learned along the way:

• Listen before building—users describe symptoms, not systems

• Design for change—nothing you build stays frozen

• Keep it human—good tools should disappear into the workflow

As orgs grow, so does complexity. And nowhere is that more evident than in multi-user ownership and access design.

You can’t just “let everyone see everything” and hope for the best. Over the last year, I’ve developed frameworks that balance:

• Record-level visibility (role hierarchy, sharing rules, manual sharing)

• Process clarity (who acts when, and how automation responds)

• Ownership transitions (consultant leaves, team changes, reassignment flows)

For years, I focused on building solutions. Now I focus on defining the right problems—and sometimes, that means saying no.

Not all requests belong in Salesforce. Not all automations need to exist. The mark of an architect isn’t how much they build—it’s how strategically they build.