Start with a working day
Think about the last time someone on your team had to look for the same detail in several places. It might have been an address, an order status or an answer already sent to another customer. That task gives you a useful starting point for understanding the operation.
Before choosing a tool, follow the whole journey. What comes in? Who receives it? What do they need to check? Where does the result go? Include the exceptions: missing information or a change that someone must approve.
The first opportunity may be a small part of the process. For example, preparing the information a person needs to reply, while leaving the final response with them.
Choose a task you can explain
Describe the process in one sentence: When a request arrives, we check these details and prepare this output. If that is difficult to write, clarify the work first.
Compare possible tasks with four questions:
- Does it happen often enough to justify improving it?
- Is the necessary information available and authorized for use?
- Does someone understand the process and have time to review the test?
- What would happen if the output were wrong?
A frequent task with an output that is easy to review can be a useful starting point. An action involving money, sensitive information or a consequential decision needs controls that match its impact.
Write down what should change
Choose something you can observe before and after: review time, transcription errors or complete requests. Keep a quality measure alongside it. Finishing sooner is of little use if someone else has to redo the work.
The first test should help you decide whether to expand, adjust or stop the proposal. All three can be useful decisions when supported by evidence.
Try completing this sentence together: We want to improve [task]; today [situation] happens; we will know it works when [criterion]. If the team cannot complete it yet, that conversation is the next step.
