It’s easy to think that skipping this step increases efficiency, but it can actually create more problems in the long run. The problem with this approach is that when business users articulate their requirements in the form of a design solution, they skip talking about the business value driving the requirement. These partners will take the path of least resistance and simply build what they’re being asked to build. Usually, these organizations have self-implemented or worked with a junior implementation partner that relied on the organization to articulate their requirements rather than developing an understanding of the business value behind the requirements. I’ve seen this firsthand, having fielded a lot of requests for advice from organizations that have run into issues. Growing and evolving your organization’s Salesforce environment can unlock enormous opportunities, but getting there often proves challenging.
0 kommentar(er)
