In this session, Pallavi Agarwal shares a practical approach to mastering discovery and requirements gathering in Salesforce projects. She explains why teams should start with the business rather than the technology, ask better “why” questions, identify the right stakeholders, document not just what was decided but why, and understand both current-state and future-state processes before solutioning begins.

Pallavi also discusses how poor discovery can lead to costly rework, low user adoption, and solutions that miss the real business need. She covers process mapping, personas, user stories, managing scope, distinguishing needs from nice-to-haves, and designing Salesforce solutions that are usable, scalable, and easier to maintain over time.