Describe the problem in observable terms
Replace “we need something better” with a task you can examine. Examples include preparing individual messages, helping employees locate statements, maintaining recipients or retrieving records.
Do not attribute a problem to every employee without checking. A current route may work for most people but fail for a particular access condition.
Compare three valid options
| Option | When it may be suitable | What to examine |
|---|---|---|
| Keep | The process meets the actual requirement and workload is acceptable | Whether any unresolved issue is important enough to change the decision |
| Improve | A small control, clearer instruction or better handover addresses the gap | Who maintains the improvement and whether it removes the problem |
| Replace a defined part | A new workflow can meet essential needs with acceptable total effort | Prerequisites, migration work, recurring work and evidence |
These options are not a progression in which replacement is automatically best.
Identify hard conditions
A reliable personal receiving channel, an approved data source or a required permission boundary may be essential. Record them separately from preferences such as a visual layout.
Do not allow attractive features to compensate for an unmet hard condition. A faster send action cannot resolve a channel employees cannot access.
Compare employee and administrator effort
Include preparing data, distributing statements, answering access questions, handling corrections and maintaining records. Count first-use training separately from recurring work.
A link and confirmation can add steps compared with a message that displays information immediately. Assess whether the extra action supports a real requirement. Do not require handwriting simply because a demonstration includes it.
Write a decision with conditions
Use a short statement: “We propose to improve the current route because…”, “We propose to evaluate a replacement for this stage because…”, or “We will retain the process while this prerequisite is resolved.”
Include the evidence, scope, owner and next review point. If you need more information, record that result rather than inventing certainty.
Compare workload · Record the alternatives · Review the software evaluation checklist