Bring the challenge.
Start with the context.
An early discussion does not need a finished specification. A few practical details help the team understand the requirement and the most useful next step.
Email the team directly- 01The problem
- What happens today, who experiences the difficulty, and what should work better?
- 02The environment
- Which devices, applications, websites, business platforms, or data sources are involved?
- 03The intended outcome
- What would a useful first version or a successful pilot allow the team to do?
- 04The delivery context
- Are there existing deadlines, a budget range, decision-makers, or dependencies to consider?
Before you get in touch.
Clear answers help define the right next step. Your project scope and responsibilities are agreed before delivery.
Ask the teamExplain the problem, who experiences it, the systems involved, and what a useful outcome would look like. A high-level budget or timing context is helpful if it is available.
