Identifying gaps and needs for automation in requirements

In the earlier chapters on gathering requirements, we talked a lot about how you can't help a client solve their real-world issues without first really understanding their processes and people. For a consultant, that always involves being a good listener, asking the right questions, and suggesting the best solutions. Knowing the system well is a requirement (and yes, there's a lot to know!), but sometimes, you're going to run into situations where either no native feature does what your client needs, or where users don't want to perform a set of steps manually. As a reminder from previous chapters, your solutions to problems like these should always flow in this order:

1. Look for native features. Try to convince the users to use them.
2. If possible, create a SuiteFlow to streamline the work.
3. Look for partner solutions (also known as SuiteApps) that can meet the client's requirements or automate...