One of the most important steps in a Salesforce implementation project is User Acceptance Testing (UAT).
This is the moment in which the client and end users can finally test the build and raise issues or concerns as needed.
Nothing is built perfectly, so there will always be some bugs or concerns. Here are a few considerations to make the best use of this time.
1. Set expectations
Before UAT begins, make sure your client knows their role and responsibilities. Who should test what, when, and how. Have them create test scenarios, or help them create some. They should know how much of a time commitment is needed, and what to expect before, during, and after this brief period.
2. Setup the full system
If Salesforce is connected to external systems, make sure those are setup and connected as well. The goal is to provide a scenario which looks virtually identical to what will be received in production. So if Marketing Cloud or Zapier will be used in production, make sure they are working in UAT.
3. Have accurate data
This is especially important when doing data migrations from legacy systems. Whenever possible, load all legacy data. If not possible, inform the client in advance what data they will not see. Your client needs to see the source system and Salesforce side-by-side. Data accuracy is one of the most important elements of trusting the overall build.
The takeaway
UAT is a magical moment in which you get to show off all your hard work. By setting the client’s expectations, providing a glimpse of what the future holds, and fully loading data, you’re much more likely to have a successful project and a happy client.