Explain the work
Describe who performs the process, what they need and where the current approach causes difficulty. A real example is more useful than a long list of features.
Name the constraints
Identify existing systems, data responsibilities, access rules, deadlines and procurement requirements. Be clear about which constraints are fixed and which can be discussed.
Define acceptance
Write observable examples of a successful result, including failure cases. Include maintenance, documentation, handover and ongoing support in the conversation.
Build in useful stages
Start with a coherent outcome that can be reviewed by real users. Use what you learn to shape the next stage, while keeping ownership and technical decisions documented.