A tool is being used differently than intended. That alone is not proof that employees are using it incorrectly or not making enough effort. First check whether the task, access, and expected use are actually clear and possible.
Your goal for this post
You investigate a specific problem without prematurely attributing its cause to an individual.
Understand: Categorize the work-related question correctly
A feature may be available but not enabled for the person responsible or not explained clearly enough. Similarly, a technical solution may simply not adequately support the task at hand. “Use it better” would not be a complete answer.
The WHO lists unclear roles, lack of support, and insufficient skills for assigned tasks among the possible risks. An appropriate response may require training, changed permissions, or a different allocation of tasks. The title is not evidence of how often errors occur.
An example of your own: Responses are missing from the shared workspace
In a shared workspace, responses are missing. The initial assumption is that some people are not following the process. The discussion reveals that one person cannot edit the relevant field and another received different instructions.
First, clarify the permissions and expected use. Only then can you check whether there is a technical limitation or another point of confusion. An additional reminder message alone would not have changed the lack of access.
Decide: Which requirement is missing?
The expected action is unclear
Describe, using an example, what is needed, when, and from whom. Check whether everyone understands it in the same way.
The action is known, but technically impossible
Have the relevant department check the access or feature. Do not create private workarounds for permissions.
The action is possible, but the process remains unsuitable
Check task allocation, training, and technical suitability. Assigning blame again does not provide any new requirements.
Reviewing a case together
Choose a specific process without unnecessary personal or confidential details. Go through together which step was expected and what was actually possible. Distinguish between observation and assumption.
Agree on an appropriate change and test the same type of task again. Document the clarified process in the designated place. If the task cannot be completed within the available time, the workload must also be addressed.
Your usage check
Understanding: Is the expected action explained clearly?
Capability: Are the function and necessary access available?
Support: Is suitable training or a contact person available?
Suitability: Does the workflow support the actual task?
Next: Review the agreement in everyday work
A fair assessment is only possible once the prerequisites have been clarified. A technical or organizational limitation cannot automatically be overcome through greater personal effort. Identify the right change for the work situation.
Limits and support
This article offers general guidance for work, not a technical approval standard. Changes to shared systems, permissions, or workflows should be reviewed with the people responsible. Maintain access to necessary functions, information, and communication. If the workload remains unmanageable despite clear workflows, a decision is needed about scope, resources, or support.
Frequently asked questions
Is an incomplete status always a user error?
No. Access, training, context, and task allocation can also play a role.
Should I get missing access through other accounts?
No. The responsible teams must check and configure the necessary permissions appropriately.
Is the application itself never the problem?
Yes. A missing or unsuitable function must be checked just as carefully as usage and agreements.
Expert source and context
WHO: Mental health at work →
As of September 15, 2026; accessed October 16, 2026. English-language source.
The WHO supports considering roles, skills, and support. The usage check is a practical template of our own, not a frequency study of misuse.
The practical example and template are practical interpretations of their own, not a scientifically validated program.
Continue reading
Digital tools in everyday work - why more apps rarely mean more productivityFind the right question about tools: function, choice, use, or change
Read article →
Too many tools in everyday work - why more apps don't bring more clarityEvaluate tools based on the functions needed and shared responsibilities, not their number
Read article →Your next step
Choose a specific open question about work and clarify it with the right people. Find more articles on structure, focus, and mindful digital work in the FitStart Work Guide.
