Start with a task your team performs often. It might be admitting a student, following a patient visit, receiving stock or approving an internal request. Describe what happens today before describing the software you want.
1. Who touches the work?
List the people who create information, check it, make a decision and need to see the result. That list helps define roles and access from the beginning.
2. What record carries the task?
Choose one fictional example and follow it through each step. Ask where its information is entered, how it changes and how someone later finds the correct version.
3. Where does the handoff slow down?
Note where a team member has to call, message or retype information to keep work moving. Those moments often reveal the most useful first improvement.
4. What would a useful first version do?
Choose the task your team should be able to complete. Agree the result you need, who will review it and any systems it must work with.
Ready to make this concrete?
Use the short brief builder to capture your own task and desired outcome.
Describe your needs