Imagine cutting a task from an hour to twenty minutes. All the required figures are there, and you meet the deadline. Yet the response is, “Be more thorough,” or, “You don’t seem committed.” If you put thought into reducing unnecessary work, feedback like this leaves you with little idea of what to change.
Start by asking whose workload changed, and how. You may have saved yourself effort while giving the reviewer more to do. Or perhaps quality and handoffs are intact, but visible hours of struggle are what gets rewarded. These situations call for different responses.
Wanting to deliver what you promised without making work the center of your life is a reasonable aim. Protecting that approach starts with making the finish line clear to everyone involved.
What disappeared when the work got faster?
Consider a hypothetical weekly sales report. You replace it with a single, automatically generated table and save forty minutes. But readers may need more than figures: what changed since last week, and where is a decision needed? If removing the explanation means they have to ask you every time, that extra work belongs in the assessment too.
Conversely, if you retained comparisons, checks for unusual values, and clear decision points, but hear only, “You used to spend longer on this,” ask which aspect of quality the criticism concerns.
Separate three questions:
- Results: Does the work meet requirements for information, accuracy, deadlines, and safety checks?
- Handoff: Can the next person use it? Have you passed omitted explanations or checks on to somebody else?
- Appearances: Even when the first two are satisfied, are long hours or cosmetic details what gets rewarded?
A better handoff is a worthwhile improvement. An ever-growing requirement to look busy creates a stranger task: becoming efficient, then secretly staging the effort you no longer need.
Agree on “enough” before you begin
If you alone decide what is sufficient, mismatched expectations may emerge only after delivery. Even for a small task, clarify four things first: purpose, intended user, essential requirements, and deadline. That makes it easier to see what can be removed.
For the sales report, you might say:
“My understanding is that this will help Friday’s meeting decide which products need additional action. Would one page with week-on-week changes, inventory, and comments on the three biggest changes be enough? This time, I’d like to prioritize checking the figures over refining the design.”
That gives the other person more room to identify a specific gap than simply asking, “Is all that necessary?” If the answer is, “The executives also need a trend chart,” you have an additional requirement to incorporate.
Agreement on scope does not authorize you to remove safety, legal, contractual, or mandatory internal checks on your own. “Nothing has gone wrong before” is weak justification for skipping a check. If you do not know its purpose, ask the responsible person what it protects and what can be changed.
Offer options without closing the discussion
Options help, but two choices that both suit you, or a demand for an immediate answer, can come across as forcing the decision.
Go a little further than “A or B?”
“With option A, I can deliver the verified figures today. Option B includes additional analysis and would be ready tomorrow. I think A is sufficient for the meeting’s decision, but is there a requirement I’ve missed? It would help to agree on the direction by 3 p.m.”
Give the purpose, trade-off, your recommendation, and room for correction together. When another request arrives, clarify priorities before automatically accepting: “If I add this today, which of my two current tasks should move to tomorrow?”
Communicating your position clearly while respecting the other person is often called assertive communication. Mayo Clinic describes expressing requests specifically and respecting each other’s rights and views. Adjusting your wording should clarify what is negotiable, not erase your limits.
Bring vague criticism back to the task
“Careless,” “one-sided,” and “people don’t normally do that” do not tell you how to improve next time. Deciding that the other person is “avoiding accountability” does not help either: you cannot verify their private motives.
Ask about observable work: “Was the gap in checking the figures, the amount of explanation, or consulting you before submitting?” Correct specific shortcomings. The calculations might be right, for example, but a change affecting another department may have needed advance notice. Add that notice to the process.
“Use the usual format” also needs context. Does that format support audits or comparisons, or is it simply familiar? Instead of changing everything at once, run one small trial: place the old and shortened versions side by side for one reporting cycle, then compare review time and the number of questions.
Record more than “preparation time decreased.” “No increase in requests for rework” and “another colleague could use it” help establish the value. Focusing only on speed can leave hidden burdens out of the conversation.
If questions bring blame, wording is not the only issue
Suppose efforts to clarify requirements repeatedly lead to personal criticism. Approved methods are rejected later, without an explanation of what needs changing. Trying to solve that pattern entirely through better communication can become exhausting.
Amy Edmondson’s research treats psychological safety as a shared belief that a team is safe for interpersonal risks such as asking questions or reporting mistakes. Her 1999 study of 51 teams within one manufacturing company found an association between psychological safety and learning behavior. It does not establish that one causes the other, nor is it a tool for diagnosing an individual manager. It does offer a way to consider whether saying “I don’t understand” is possible in the working environment.
Careful wording cannot guarantee agreement. Shift toward keeping brief records:
“My understanding from today’s discussion is that I’ll submit option A by Friday and leave the additional analysis for the next round. If that changes, please confirm the revised scope and deadline.”
Record requests, conditions, decisions, changes, and their effects. Leave out character judgments and angry essays. Do not treat silence as approval; get explicit confirmation for important decisions. The aim is to prevent recurring misunderstandings rather than assemble evidence for a later confrontation.
Does efficiency actually leave you breathing room?
Saving forty minutes may not reduce your workload if every minute is immediately filled with another task. Discuss whether the time saved will support quality checks, preparation for busy periods, or less overtime. Otherwise, the purpose of efficiency can disappear.
Keep time to recover outside work, and people you can talk to. Capable, resilient people can end up absorbing unreasonable demands through endless personal adjustments. Being able to endure an arrangement is not, by itself, a reason to keep it.
One harsh comment does not define an entire workplace. But if standards keep shifting after you clarify conditions, test small changes, and seek another person’s perspective, exploring a change of responsibilities, an internal move, or another job is reasonable. If work is seriously affecting your health or daily life, getting support matters more than continuing improvement experiments.
Wanting less work can become a practical improvement proposal when you specify what to remove and what to protect. Start with one task: agree on acceptance criteria and the handoff. If visible struggle continues to matter more than results, workplace fit belongs in your assessment too. Efficiency should let some of your own time return when the work is done.
