Software conversation notes
Prepare your
software brief.
Choose a task that takes too long or causes mistakes. Describe what happens now and what would make it easier, so Darren can explore the right tool with you.
1. Follow the information
Take a routine example, such as a sales lead arriving or a stock adjustment being recorded. Use invented names and figures rather than private customer details.
- What arrives first, and where does it arrive?
- Who picks it up?
- Where do they record the details?
- How does the next person know it is their turn?
A rough sketch of those handovers is useful. You can bring an empty form or a redacted spreadsheet to explain them.
2. Include the difficult version
The ordinary route is only part of the picture. Tell Darren what happens when an enquiry has no owner, a stock figure is wrong or a post needs another review.
- What must someone check before continuing?
- Which missing details create extra chasing?
- What should happen if a connected service is unavailable?
- Who can correct a mistake or override a decision?
These details help distinguish a useful tool from a tidy screen that leaves the same problem behind it.
3. Define a small result worth trying
Choose a specific first outcome: an unassigned-enquiry list, a low-stock review or a shared queue of posts awaiting approval.
- Which people need it, and what may each person see?
- What existing accounts or systems would it depend on?
- Which actions need explicit approval?
- How would your team judge the trial version?
The plan must cover permissions, supported connections, provider costs and the person responsible for operating it. Delivery timing and ongoing help depend on the scope and capacity agreed.
Walk Darren through the task
Use the software examples to name a possibility, or the workspace illustration to picture where a tool might sit. Your actual workflow sets the brief.
Discuss a working task