Tool Overload
Part of Collaboration software adoption
Measuring whether a collaboration tool reduces duplicated work
Define duplicate work, compare work items before and after rollout, and keep product usage separate from business outcomes.
To assess duplicated work, define a repeat action in one workflow and count how often it occurs before and after the workflow changes. Use comparable work items, record other changes that might affect the result, and inspect the cases behind the count.
Logins, messages and file views show activity; they do not establish that rework fell.
Define the duplicate
Choose one workflow, such as preparing a weekly client report. A qualifying duplicate might be a second person independently rebuilding a section for the same reporting period because they could not find the current copy. Another might be a request entered twice because its first entry was not visible to the next person.
Exclude legitimate parallel review and copies made for a distinct purpose. A dated customer export may be required even when one editable source exists. Write the inclusion and exclusion rules before examining the follow-up results.
Choose the unit you will compare: a report, request, case or handoff. Record both the number of work items with a qualifying duplicate and the number of repeat actions. Several repeats in one unusually difficult item mean something different from a repeat in each of several items.
Key metrics for assessing duplicated work reduction
- Unit of comparison
- Report, request, case or handoff
- Exclusion criteria
- Legitimate parallel review and copies for distinct purposes
- Inclusion example
- Second rebuild of a report section due to unfindable current copy
Establish a baseline
Choose a period and a set of work items that represent normal work. For each, record whether duplication occurred, what was repeated, why it appeared necessary and the effort involved if that can be estimated credibly. Use existing records and ask the people who handled ambiguous cases. A second file alone does not establish unnecessary work; it could be an approved snapshot.
Agree who will classify uncertain cases and apply the same rule after rollout. If past records cannot support a baseline, say so and start tracking prospectively before claiming a reduction.
| Measure | What it answers | What it misses |
|---|---|---|
| Work items with a qualifying duplicate divided by work items reviewed | How often the defined problem appears | The size of each repeat task |
| Duplicate actions per work item | How much repetition the inspected work contains | Time or consequence |
| Credibly recorded time spent repeating work | Effort associated with the problem | Unrecorded effort and differences in complexity |
| Workspace usage | Whether people used the tool | Whether it prevented duplication |
Compare after the change
Review a later set of items using the same definition and unit. Keep the task type, team mix and observation period as comparable as practical. Note changes in workload, staffing, templates, approval rules or customer requirements. If several things changed together, report an observed workflow change rather than attributing it solely to the software.
Inspect individual cases behind the count. A lower rate could conceal a new wait for one owner; a higher rate might reflect better detection of repeats. Ask whether people can find the current work and whether the new route has created extra copying.
Ranked factors affecting duplication in team workflows
- Tool visibility and discoverabilityHigh
- Clarity of ownership and version controlHigh
- Team familiarity with the toolMedium
- Changes in workload or staffingHigh
- Template or approval rule updatesMedium
Keep usage reports in context
Microsoft’s Teams reports include active-user and message activity. Its OneDrive activity report counts file interactions and sharing. Subject to the relevant reporting access and definitions, these can show whether the tools were used.
They cannot identify whether two employees unknowingly completed the same task. Do not turn an activity trend into a saved-hours figure.
Record the duplicate definition, periods, number of comparable items, observed change, alternative explanations and unresolved cases. If the evidence is too thin, keep tracking or revise the workflow. Draw only the conclusion the inspected work supports.
