# Where Does Your Sales Team Do the Work Twice?

Choose one routine your team already performs. Use observed work and times; this worksheet is not a test result or a promise of savings.

1. **Name the job.** For example, preparing the weekly sales review or handing a customer's requirements to another team. Write down where it starts and what a useful result looks like.
2. **Follow the work.** List who enters, copies, checks or requests information. Include spreadsheets, emails, Salesforce and other systems.
3. **Ask why each repeat exists.** What decision does it support? Who needs it? What would they lose if that step stopped?
4. **Watch where people get stuck.** Do they lack instructions, an answer, access to the right information, or a convenient way to complete the task? Record necessary business requirements too.
5. **Measure one full cycle.** Record seller time, manager preparation and sales-ops assistance. Keep time waiting separate from time spent working. Avoid counting the same work twice.
6. **Choose one change.** Stop an unnecessary request, simplify a step, improve a report, connect systems, or provide focused help. Explain why that choice addresses the problem.
7. **Name the decision maker.** Identify who can change the management requirement and who will implement any Salesforce or integration work.
8. **Agree how to check it.** What should take less time or happen without assistance? What information must remain accurate and complete?
9. **Review a comparable cycle.** Check the workload, work quality and any remaining copies or unofficial workarounds. Ask the users what still takes extra effort.
10. **Decide what follows.** Keep, adjust or stop the change. Agree authorization before altering systems or creating test records.

Read the [Salesforce user adoption guide](https://logicconduit.com/articles/salesforce-user-adoption/) for the examples behind this review.

[Discuss one repeated sales task with Logic Conduit](https://logicconduit.com/#contact).
