Whoa! Are you psychic Tom Leddy?!
Currently working on a global org merge project and I see this timely article from Salesforce Architects: Single- or Multi-Org Architecture? Six Factors to Consider. 😍
Love it so much.
I think many organisations mistake the “Customer 360 view” concept literally and think that everyone should be on the same org/instance, regardless of other factors that might be at play.
Classic ‘integration’ cases for companies involved in mergers and acquisition.
But should we all be on the same ship and dress the same and sing the same songs?
Not if we speak different languages and I get sea-sick! 🚢🤢
(Bet y’all missed my outstanding analogies and metaphors 😁)
Whatever decisions we make with regards to technology and business roadmaps, we need to make them thoughtfully.
Make sure you’ve looked at all the reasons why a specific option feels like the right choice. 🔍
Then you jump over the metaphorical fence and try to see things from the other side, and figure out all the reasons why that option might NOT be the right choice. 🔎
It’s called being a Devil’s Advocate. 👿
When embarking on a big project where decisions like single org vs multi org has such deep implications, it pays to really pay attention and do the hard thinking.
If you’re noodling on this particular topic, get a headstart by reading Tom‘s article.
In my project, we’re merging specifically because of a strong argument for centralied management of support, configuration and development – with all the other reasons for separate orgs not being particularly compelling.
And no, not because of any lazy butt reasons at all 😁
Link to the article in the comment 👇🏻
#OnThePeiroll
#TechnicalLeadership
