Suggested answer

1. Start with the business case, not the backlog. I would ask the sponsor what measurable outcome justified the budget, because that single answer frames every prioritisation decision that follows.
2. Run a stakeholder identification exercise and build a RACI plus an influence/interest grid, so I know who decides, who advises, and who simply needs updates.
3. Review the existing org: objects in use, active automation, report usage, field population, and installed packages. This tells me what I am building on top of and where the technical debt sits.
4. Run focused discovery sessions per business area, mapping the current-state process and capturing pain points with role, frequency, and quantified impact.
5. End the two weeks with a playback session: a current-state summary, a prioritised pain point list, a draft success metric per objective, and an explicit list of assumptions and open questions. The playback is what converts my interpretation into an agreed baseline.

Practice content for interview preparation; not an official vendor answer. Verify details against current product documentation.

Community comments (0)

No comments yet.

Sign in or create a free account to add a comment. Comments are moderated before they appear.

Plain text only, 3–2000 characters. A moderator reviews every comment before it is published.