Better questions for connected work.
Practical prompts to prepare for a scoping conversation. These are general discussion notes, not a substitute for an agreed assessment.
Describe a recent example.
Choose one request that followed the usual route. In a few sentences, describe what started it and what counted as finished.
- What information arrived at the beginning?
- Which decision allowed the work to move forward?
- Who needed the output next?
- Where was the final record stored?
Replace names and identifiers with role descriptions. Do not include passwords, access tokens or personal data.
Look for the return journey.
Work rarely travels in only one direction. Note where it comes back for clarification, where it waits and who notices that it has stopped.
Ask whether the return is an expected review, a missing input or a different kind of request. Those situations may need different routes.
Explore the example dependency mapPrepare a small scope note.
- Question: What would you like to understand?
- Boundary: Which workflow is included, and what sits outside it?
- People: Who does the work and who can decide?
- Evidence: What anonymized example can you discuss?
- Constraints: What dates, access limits or commitments matter?
A short note is enough for an initial conversation. The consultant and your team should confirm the final scope together.