1. The problem is not “not knowing”
Not knowing something is not the problem.
At work, it is perfectly healthy to say:
“I don’t know.” “I will check.” “Ms. X may know.” “I understand this part, but I need to confirm the rest.”
The real problem is different.
The problem is when someone cannot admit they do not know, becomes defensive when asked for assumptions, refuses to define criteria, and then later reviews the output as if they had clear criteria all along.
This person does not merely struggle with the work.
They damage the workflow.
They do not define requirements. They do not provide acceptance criteria. They dislike clarification. They review after the fact. They push deadline failure onto the worker.
This is the dangerous pattern.
2. A useful label: the defensive red-pen reviewer
In a humorous taxonomy, this type could be described as:
Theater Monkey Family
Defensive Red-Pen Genus
Responsibility-Laundering Species
Authority-Silenced Subspecies
The wording is intentionally sharp.
But the point is not personal attack.
The point is to make the structure visible.
Once the pattern has a name, it is easier to stop endlessly replaying the anger in your head.
3. They cannot define requirements but want to be the judge
The core problem is that this person cannot define requirements but still wants to occupy the reviewer position.
A reviewer should provide certain things in advance:
- Purpose
- Desired output
- Acceptance criteria
- Priorities
- What must not be included
- Deadline
- Final decision maker
- Scope of delegation
- Scope of reviewer responsibility
Without these, the worker must guess.
Then, after the worker guesses, the reviewer says:
“This is wrong.” “Not like this.” “Do it differently.” “Redo everything.”
That is not review.
That is retroactive grading.
If someone wants to use a red pen, they should provide the grading sheet first.
4. They become defensive when asked for assumptions
This type often reacts badly to basic clarification.
Questions such as:
“What is the purpose?” “Who will use this?” “Who makes the final decision?” “What is the deadline?” “What scope should I handle?” “What criteria should I use?”
may be met with:
“You are overthinking.” “That is too detailed.” “That is your job.” “Just do it first.” “Why are you asking that?”
But clarifying assumptions is not an attack.
It is how rework is prevented.
People who reject clarification often create the largest rework later.
Refusing clarification is essentially scheduling future chaos.
5. “That is your job” often hides responsibility laundering
A common phrase is:
“That is your job.”
Sometimes this is partly true.
Creating the document may be your job. Making the video may be your job. Organizing the content may be your job. Drafting the proposal may be your job.
But defining decision criteria is not solely the worker’s job.
The decision maker must decide. The reviewer must define what good looks like. The requester must explain the purpose and conditions.
When all of that remains vague, but the worker is still blamed later, the structure becomes responsibility laundering.
The worker receives the execution responsibility. The reviewer keeps the red pen. The decision responsibility remains undefined.
That is not management.
That is a broken process.
6. Do not destroy the deadline and then blame the worker
The worst version is when the worker creates rules to protect the deadline.
For example:
- Clarifying assumptions
- Setting review deadlines
- Defining correction scope
- Creating a schedule to meet the final due date
- Preventing responsibility shifting
These are not unnecessary details.
They are deadline protection.
But a defensive reviewer may break all of them.
They resist clarification. They miss review deadlines. They add massive late corrections. They expand the scope. They delay the schedule. Then they blame the worker.
This is infuriating because the worker did not fail to manage.
The worker tried to prevent failure.
The person who broke the system then pushed the responsibility onto the worker.
7. Late red-pen feedback should be treated as a change request
Corrections are not always bad.
Work often needs revision.
The problem is when late changes are treated as if they were part of the original task.
When a correction changes the premise, scope, or criteria, it is not just a small edit.
It is a change request.
Change management exists because unmanaged extra requirements lead to scope creep, overruns, and deadline problems.
So late feedback should be clarified:
- Is this a change from the original assumption?
- Is it mandatory or optional?
- Does it affect the deadline?
- What is the priority?
- Who decides?
- What should be removed if this is added?
- Can the deadline change?
Without this, the worker’s time disappears into unlimited rework.
Red pen is not free.
It has labor cost. It has deadline impact. It carries responsibility.
8. When authority appears, they suddenly become quiet
The most theatrical part is when the person becomes quiet as soon as an authority figure joins.
Before that, they resist assumptions. They add red marks. They posture. They make noise.
But once a department head, senior manager, or another authority figure is present, they suddenly stop.
The work passes. The objections disappear. The noise disappears.
That suggests the issue may not have been quality.
It may have been status, face, or control.
The person was not responding to logic.
They were responding to authority.
In that case, reasoning with them directly is often ineffective.
A documented decision, deadline, and approving authority are more effective.
9. If the normal line does not function, use documented approval
Ideally, the team should clarify assumptions, criteria, review deadlines, and final approval internally.
But when the direct line does not function, documented approval from a relevant authority may be necessary.
The point is not to use authority as a weapon.
The point is to fix the decision, deadline, and scope.
Once a direction is confirmed, late red-pen comments can be handled as change requests:
“This is an additional change.” “This may affect the deadline.” “Please clarify priority.” “Who will make the final decision?”
Do not fight the monkey with logic.
Use documentation, authority, deadlines, and change control.
10. Do not release wild red-pen monkeys into the office
If this pattern is left unmanaged, it damages the whole workplace.
The person may think they are reviewing. They may think they are improving quality. They may think they are giving guidance.
But what actually happens is:
- Assumption clarification is blocked
- Criteria are not provided
- Rework increases
- Deadlines slip
- Responsibility is shifted
- Psychological safety is damaged
- Meetings become wasteful
- Competent workers burn out
If someone is given a red pen, they must also provide criteria. If someone reviews, they must respect review deadlines. If someone makes decisions, they must own decision responsibility. If someone requests changes, they must acknowledge deadline impact.
Otherwise, do not release wild red-pen monkeys into the office.
11. Countermeasure: turn red-pen feedback into change requests
The solution is not emotional confrontation.
The solution is process control.
Use rules:
- Document the assumptions.
- Ask for criteria in advance.
- Set a review deadline.
- Treat late corrections as change requests.
- Treat major changes as deadline-impacting.
- Convert verbal feedback into written records.
- Ask for priority on additional changes.
- Identify the final decision maker.
- Fix the direction through documented approval.
- Do not absorb unlimited work.
This turns chaotic review into managed change.
12. Email example: asking for criteria before work
Hi [Name],
To prevent rework, I would like to confirm the criteria before proceeding.
Could you please clarify:
- Purpose of this work
- Desired output
- Required content
- Content that does not need to be included
- Priority
- Final reviewer
- Review deadline
Once these points are clear, I will proceed in a way that meets the deadline.
Best regards,
[Name]
13. Email example: treating late feedback as a change request
Hi [Name],
Thank you for the comments.
Some of the requested changes appear to differ from the assumptions we previously confirmed, so they may affect the deadline.
Could you please clarify:
- Which changes are mandatory
- Which changes are optional
- Which items do not need to be handled this time
- Whether the deadline can be adjusted
- Who will make the final decision
Once confirmed, I will organize the scope and schedule.
Best regards,
[Name]
14. Email example: fixing direction with documented approval
Hi [Name],
This matter has been confirmed with [Manager/Department Head], and we will proceed with the current direction by [date].
If there are additional corrections, they may affect the deadline, so please also clarify the priority and whether the deadline can be adjusted.
Best regards,
[Name]
15. Conclusion: If you use a red pen, bring criteria and responsibility
Do not define requirements. Reject clarification. Add late red marks. Delay the deadline. Push responsibility onto the worker. Become quiet when authority appears.
This is not good review.
It is a broken workplace process.
The problem is not not knowing.
The problem is refusing to admit uncertainty, blocking clarification, grading after the fact, and shifting responsibility.
If you use a red pen, bring the grading sheet. If you review, respect the review deadline. If you change the scope, acknowledge the deadline impact. If you decide, own the decision.
Otherwise, do not release wild red-pen monkeys into the office.
Summary
- The problem is not people who say “I don’t know.”
- The problem is defensive reviewers who refuse clarification but grade after the fact.
- Reviewers must provide criteria, priorities, and deadlines.
- Late red-pen feedback should often be treated as a change request.
- If a person only listens when authority is present, the issue may be status rather than quality.
- Countermeasures are documentation, criteria, review deadlines, authority confirmation, and change control.
- Do not release wild red-pen monkeys into the office.
参考資料 / Sources
- Jack R. Gibb, “Defensive Communication” summary archive
https://reagle.org/joseph/2010/conflict/media/gibb-defensive-communication.html - Gibb Categories overview
https://www.shoreline.edu/intranet/operationscommittee/Operations2008-2009/Gibbs_support_defensiveness_grid.doc - UK Government Project Delivery, “Change control”
https://projectdelivery.gov.uk/teal-book/home/part-e-planning-and-control/chapter-22-change-control/ - ProjectManagement.com, “Project Scope Statement”
https://www.projectmanagement.com/wikis/961606/project-scope-statement - Adobe Business, “What is scope creep?”
https://business.adobe.com/blog/basics/scope-creep - Chua and Verner, “Examining Requirements Change Rework Effort: A Study”
https://arxiv.org/abs/1007.5126
