Introduction
Not every workplace problem requires an immediate meeting with every person involved.
A reasonable approach is often to begin with a low-cost intervention, observe the result, and escalate only if the problem continues.
Yet managers sometimes evaluate only the visible action:
You did not speak to the person directly.
You did not understand the current situation.
You lack problem-solving ability.
That judgment becomes especially unfair when the employee could not see the real situation because critical information stopped at the manager.
This article examines a small internal-document incident to show how broken feedback channels, one-sided evaluation, and undefined review standards can turn sound problem-solving into an apparent failure.
The case has been anonymized and generalized for publication.
1. The Initial Problem
Documents addressed to individual employees repeatedly returned to the sending department instead of reaching their intended recipients.
The person handling the process added a cover sheet that:
- clearly stated that the document was for the named individual;
- printed the department and employee name;
- used arrows to identify what should be checked;
- asked for a written reason if delivery was impossible; and
- allowed staff to discard only the cover sheet if delivery succeeded.
This was not merely a polite note. It created an exception-notification mechanism.
If delivery failed, the document should return with a reason. If nothing came back, the process appeared successful.
After this intervention, the main document reached the employee.
2. Objective Events and Available Information Were Different
The employee initially understood the situation as follows:
- Documents had been returned before.
- The destination and handling instructions were clarified.
- A return channel was added for unresolved problems.
- The main document arrived.
- The intervention therefore appeared effective.
Only later, during a critical discussion, did the employee learn that earlier documents had also been returned but that this information had not been shared with the person responsible for the next action.
The employee had sent a follow-up document because there was no visible return signal.
This distinction matters. The employee did not ignore known evidence. The employee made a decision based on the information that the process made observable.
3. “No Return Means Delivered” Was Not a Random Assumption
The working model was simple:
Delivery fails
↓
The document returns
↓
The responsible employee is notified
↓
The next action is selected
No returned document appeared, so delivery was treated as successful. The employee also placed the follow-up date on a calendar rather than abandoning the task.
The process contained:
- a state rule;
- an exception route;
- a scheduled next action; and
- a planned escalation if the first intervention failed.
The real failure was observability: the exception occurred, but the signal did not reach the operator.
Blaming the operator for not reacting to an invisible signal does not repair the process.
4. Stepwise Escalation Is a Form of Problem-Solving
The employee's plan was:
- clarify the destination and handling instructions in writing;
- observe whether the document arrived;
- speak directly with relevant people if it still failed; and
- revise the official routing process if necessary.
Direct conversation was not rejected. It was the next step in a conditional sequence.
Starting with the lowest-cost sufficient intervention can be more efficient and repeatable than immediately organizing a meeting. AHRQ guidance similarly emphasizes distinguishing problem severity and using understood escalation protocols.
The employee did not fail to imagine the manager's proposed route. The route had already been incorporated as the next stage.
The trigger for that stage—knowledge that delivery had failed—never reached the employee.
5. When a Planned Next Step Is Misread as No Plan
The manager criticized the cover sheet and suggested that the employee should have spoken directly with the recipient or other stakeholders.
Some local feedback was reasonable. Printed text would be clearer than handwriting, and wording can always be refined.
But those are document-quality issues, not proof of weak problem-solving.
The main delivery problem had been solved, and a direct-conversation route was already planned if the document failed again.
The employee's frustration came from being treated as someone who had never considered that route.
The evaluation skipped the most important question:
What were you planning to do if this intervention did not work?
Had the manager asked, the entire reasoning process would have become visible.
6. When “Do Not Proceed Based on Assumptions” Is Valid
That criticism is reasonable only when:
- explicit receipt confirmation was required in advance;
- a confirmation method existed;
- return information was shared with the responsible employee; and
- the employee still skipped the required check.
If the organization uses exception-based reporting but also expects a direct confirmation every time, it is running two parallel controls.
That may be appropriate for high-risk documents, but it must be designed and communicated as a process rule. It cannot be introduced retroactively as proof of individual incompetence.
7. One Question Could Have Changed the Conversation
A fair manager could have asked:
If the document still had not arrived, what would your next step have been?
The answer was straightforward:
The process required unsuccessful deliveries to be returned, so no return was treated as successful delivery. I scheduled the follow-up date, and I planned to contact the relevant people directly if the delivery failure became visible.
The remaining improvements would then be specific:
- print the entire cover sheet;
- ensure every return reaches the responsible employee;
- define which documents require explicit receipt confirmation; and
- document the trigger for escalation.
This is process improvement, not a judgment about a person's basic intelligence or character.
8. Procedural Fairness Matters
The employee later explained that the one-sided judgment had visibly affected their attitude.
That reaction should not be analyzed in isolation.
Research on procedural justice shows that people perceive evaluations as fairer when they have an opportunity to explain themselves, especially before a decision is made. Research on leader inclusiveness likewise shows that leaders who invite and appreciate contributions help create psychological safety and improvement behavior.
Telling employees to speak up while interrupting, dismissing, or pre-judging their explanations creates the opposite incentive. Employees respond by limiting contact, relying on written records, and avoiding unnecessary interpersonal risk.
That response may look uncooperative from above, but it can be a rational adaptation to an unsafe feedback environment.
9. The Reversal of Responsibility
The core reversal was this:
The exception occurs
↓
The manager receives or holds the information
↓
The responsible employee does not receive it
↓
The process appears normal to the employee
↓
The employee follows the schedule
↓
The employee is criticized for not understanding the current state
When missing information is converted into an individual capability problem, the organization never repairs the notification route.
The same incident can then happen to the next person.
10. How “Revise It 15 or 20 Times Until It Is Perfect” Creates a Red-Pen Loop
In a separate assignment, the team was told that assessment-test materials on logic and problem-solving would require 15 or 20 rounds of revision before becoming “perfect.”
The number referred to revisions of the materials, not attempts to correct the employee.
Iterative review can be useful. The risk appears when review frequency is defined but acceptance criteria are not.
Without clear answers to the following questions, red-pen review can become endless:
- What capability is the assessment intended to measure?
- Who is the target population?
- What is the passing standard?
- What is in scope for each review round?
- When may an already-approved section be reopened?
- Who has final approval authority?
- What observable condition means “done”?
“Perfect” is not an acceptance criterion. It is a moving target.
11. A Better Review Structure
Separate review into four gates:
- Purpose: audience, capability, use of results, and exclusions.
- Architecture: question count, difficulty, timing, scoring, and passing standard.
- Item validity: unique answers, stated assumptions, and alignment with the target capability.
- Language and layout: clarity, consistency, formatting, and errors.
Once a gate is approved, it should not be reopened unless a material contradiction appears.
This produces a document through controlled iteration rather than endless subjective correction.
12. A Short Factual Response
When a discussion is already one-sided, a concise statement can preserve the essential facts:
The process required unsuccessful deliveries to be returned, so no return was treated as successful delivery. I scheduled the follow-up date and had already planned to contact the relevant people directly if the failure continued. I reacted visibly because I felt I was being evaluated as incapable of problem-solving before that reasoning was heard.
This statement:
- acknowledges the visible reaction;
- preserves the decision basis;
- shows that the work was being monitored;
- makes the planned escalation visible; and
- does not concede the unsupported capability judgment.
Conclusion
Problem-solving ability should be evaluated by examining the process, not merely whether the employee immediately chose the manager's preferred action.
The relevant questions are:
- What information was available?
- What hypothesis was used?
- Why was the first intervention selected?
- What result was observed?
- What was the next step if it failed?
- How was timing managed?
In this case, the employee clarified the process in writing, created an exception route, scheduled follow-up, and planned direct contact as the next stage.
The missing element was not problem-solving ability. It was the failure signal that never reached the person expected to act on it.
Before declaring that someone lacks a basic capability, a manager should ask one question:
What could you see at the time, and what were you planning to do next?
That question separates process improvement from one-sided character judgment.
References (6)
- AHRQ: Problem Solving and Escalation
- ISO: The Process Approach in ISO 9001:2015
- Nembhard & Edmondson (2006): Making It Safe
- Tubre & Collins (2000): Role Ambiguity, Role Conflict, and Job Performance
- Lind, Kanfer & Earley (1990): Voice, Control, and Procedural Justice
- Li et al. (2024): Destructive Leadership and Employee Outcomes
