ANYONE who has worked on a report, business proposal, board paper, policy document or even a presentation knows the feeling. A document returns with dozens of comments. At first, it is reassuring. Someone has taken the time to review your work. Then you begin reading. One comment says a paragraph could be clearer. Another asks whether a heading should be changed. A third points out an inconsistency. By the time you reach the last page, you realize the document has not necessarily become better. It has simply become your next project.
That experience is not unique to writing. It happens in organizations every day.
Managers review proposals. Consultants review business processes. Auditors review controls. Lawyers review contracts. Editors review manuscripts. Board members review strategic plans. Every review has the same purpose: to improve the quality of the final output before important decisions are made.
Some feedback accelerates progress. Other feedback unintentionally creates another round of work. The distinction lies in a simple question: Does the feedback merely identify a problem, or does it help solve one?
There is an important difference between criticism and contribution. Criticism identifies what is wrong. Contribution helps move the work closer to completion.
Finding problems is an essential professional skill. Auditors identify control weaknesses before they become financial losses. Researchers expose gaps in existing knowledge. Quality assurance teams detect defects before products reach customers. Editors ensure that manuscripts meet publication standards. These functions exist because fresh eyes often see what authors, managers or project teams no longer notice.
The challenge begins when identifying problems becomes the end of the review rather than the beginning.
Consider two reviewers examining the same paragraph. The first writes, “This section needs to be clearer.” The second writes, “Here is a suggested revision that may improve clarity.”
Both reviewers noticed the same weakness. Only one has reduced the effort required to resolve it. That distinction extends far beyond writing.
A manager who says customer complaints are increasing has identified a problem. A manager who proposes a revised customer service workflow gives the team something tangible to evaluate, improve and implement.
A consultant who concludes that a company’s digital strategy is outdated has offered an assessment. A consultant who develops a phased implementation roadmap has created a practical starting point for discussion.
Even meetings reflect this pattern. Many discussions revolve around what is wrong, what is missing or what should change. Progress usually begins when someone says, “I’ve prepared a draft for us to improve.”
People generally find it easier to refine an existing idea than to create one from a blank page.
Over the years, this principle has shaped the way I review the work of others. Whenever my role allows it, I try not to stop at identifying the issue. If I believe a paragraph can be strengthened, I draft an alternative version. If I think a table communicates the findings more effectively than several paragraphs, I prepare a sample table. If terminology is inconsistent, I standardize it as a proposed revision rather than simply highlighting the inconsistency.
The important word is “proposed.”
The author, client or project owner always retains the final decision. The objective is not to impose a solution but to reduce the effort required for others to evaluate one. It is often easier to react to a concrete proposal than to interpret an abstract observation.
This does not mean every reviewer should rewrite someone else’s work. Professional judgment includes knowing where your responsibility begins and where it ends.
Editors should not alter technical conclusions without the author’s approval. Auditors must preserve their independence rather than making management decisions. Lawyers identify legal risks without dictating business strategy. Technical reviewers working outside their area of expertise may be more responsible for asking questions than proposing changes that could unintentionally alter meaning.
Respecting those boundaries protects both the quality of the work and the integrity of the review. At the same time, professionals should create as much value as they reasonably can within those boundaries.
A copy editor can resolve obvious grammatical issues instead of merely pointing them out. A reviewer can consolidate repetitive comments instead of scattering similar observations throughout a document. A consultant can draft an implementation framework instead of limiting the engagement to identifying gaps. Every profession has a point beyond which decisions belong to someone else. Before reaching that point, however, there is usually considerable opportunity to reduce uncertainty and make the next person’s job easier.
This distinction is becoming even more important in the age of artificial intelligence. AI can already detect grammatical errors, inconsistent terminology, duplicated text, missing citations, formatting issues and even weaknesses in logical flow within seconds. Finding problems is rapidly becoming less difficult. What remains distinctly human is understanding context.
Human professionals understand organizational culture, competing priorities, stakeholder expectations, legal implications, political realities, resource constraints and the trade-offs that shape real-world decisions. They know when a technically correct answer is unlikely to succeed in practice and when several acceptable options deserve consideration.
As AI becomes better at identifying issues, human expertise will increasingly be measured by the ability to reduce uncertainty and help others move toward practical solutions.
Feedback has a cost.
Every comment requires someone to stop, read, think, interpret, discuss, revise and often seek another round of approval. Individually, these costs appear small. Across an organization, they accumulate into longer review cycles, repeated meetings, delayed decisions and unnecessary frustration.
Good feedback reduces these transaction costs. Poorly designed feedback transfers them. Perhaps we should evaluate reviews differently. Instead of asking how many issues a reviewer identified, we might ask a more meaningful question.
How much easier did the review make it for the work to move forward? We often describe feedback as a gift. Like any gift, its value depends on whether it helps the recipient. Good feedback should leave people with greater clarity, not greater confusion. It should reduce the effort required to improve the work, not simply transfer the burden to someone else.
The professionals who create the greatest value are rarely those who identify the most problems. They are the ones who combine sound judgment with practical assistance, knowing when to ask questions, when to offer solutions and when to step back.
Their reviews do more than criticize. They remove uncertainty, accelerate progress and help others produce their best work.
