You present colleagues with a proposal you have spent days working on. Instead of a discussion, someone says, “It’s too unusual. This won’t work.” You may feel like revising the idea immediately, defending it forcefully, or abandoning it altogether. None of those reactions, by itself, tells you whether the proposal is any good. First, find out exactly what was rejected and why.
This is difficult in creative work because we often see an idea as part of ourselves. Negative feedback can then feel like a judgment of our abilities. It is more useful to treat it as information whose reliability, significance, and implications still need to be assessed. Critical thinking is not about suppressing originality; it is about distinguishing important objections from vague impressions.
A rejected proposal is not proof of failure
“I don’t like it” may be an honest response, but it is not enough to make a decision. Someone may be reacting to the colour, an unusual layout, the way the proposal was presented, or a genuine problem with how it would work. Until you know which, you have no clear reason to change a particular element.
At the same time, an author’s confidence is not proof that a proposal works. The fact that it took a long time to develop, or that its creator believes in it, says nothing about whether it will be clear, safe, feasible, and useful to the people it is intended for. Separate the value of your work from the quality of its current form. A proposal can have a promising core and still contain a serious weakness.
Record the feedback before responding
After hearing criticism, briefly write down what was actually said. Don’t make it sound more reasonable, and don’t add assumptions about why the other person said it. Then break the situation into four parts:
- The exact objection: what the other person actually said.
- What it refers to: which part of the proposal they may have meant.
- A possible reason: what seems to be bothering them, treated only as a working hypothesis.
- What needs checking: the question, example, or information that would help clarify the reason.
Take the comment, “It’s too complicated.” It could mean that users won’t find an important detail, that implementation will be expensive, or that a colleague is unfamiliar with this way of working. Each explanation calls for a different response. Without checking, you might simplify something that is working well while leaving the actual, unnamed problem untouched.
Four types of objections call for different responses
When listening to criticism, don’t ask only whether you agree with it. More important is what kind of claim it is. The distinctions below can help you choose what to do next.
| Type of objection | Example | What to do |
|---|---|---|
| Verifiable constraint | “We don’t have permission to use these photos.” | Check the requirements and adapt the proposal if the objection is confirmed. |
| Problem with the purpose | “Visitors won’t be able to find the opening hours.” | Test whether someone can locate the information they need. |
| Unsubstantiated prediction | “No one will understand this.” | Ask who, specifically, might have a problem and what it might be. |
| Personal preference | “I’d use calmer colours.” | Consider how that preference relates to the proposal’s purpose and audience needs. |
The first two objections can be serious because they concern the conditions for implementation or whether the proposal fulfils its purpose. The third may point to something useful, but it needs clarification. The fourth is not automatically irrelevant: for example, if the person commissioning the work has a say in its final form, their preference may legitimately be part of the brief. But it matters whether that expectation was clear from the start.
Ask about consequences, not just opinions
Depending on the situation, you could ask one of these questions:
- Which specific part seems problematic to you?
- What do you think would go wrong when the proposal is used in practice?
- Who would have a problem, and in what situation?
- What is a requirement of the brief, and what would you simply prefer?
- What small test could help us choose between two versions?
This is not an interrogation. Choose one or two questions that matter most to the decision, and give the other person time to answer. When you can summarise their objection in your own words and they confirm you have understood, you can start discussing possible changes. If you begin listing all the proposal’s strengths after the first sentence, you may miss information you would otherwise have gained.
When to defend, revise, test, or set an idea aside
Once you understand the objections, you have more options than simply giving in or stubbornly carrying on. Make your decision based on the seriousness of the risk, the strength of the evidence, and how cheaply you can find out more.
Defend the core idea when the objection is unrelated to its purpose
If someone prefers a traditional approach simply because it is familiar, you don’t have to give up on an original idea straight away. Explain the specific problem the new approach addresses and the benefit it is intended to bring. But defending the idea should not mean repeating the original presentation indefinitely. If you cannot describe the expected benefit, you need to clarify the proposal first.
Revise an element when the objection identifies a specific flaw
If people cannot find the information they need during a test, address readability or layout. You do not have to abandon the whole concept. Change as few elements at a time as possible so you can tell which adjustment made a difference. A safety or legal obstacle, however, may mean there is no room to test the original version at all.
Test two versions when both arguments are reasonable
If one person says an unconventional visual design will attract attention and another worries it will be hard to follow, prepare a simple comparison. Give people the same task with each version. For example, see whether they can find the key detail without help and where they hesitate. A small test won’t prove that a solution works in every context, but it may reveal a specific weakness.
Set the proposal aside when an essential condition is missing
If you lack the necessary rights, time, capacity, or a clear decision-maker, further creative revisions may not solve the problem. In that case, record what would need to change for the project to resume. Setting a proposal aside is not a judgment on your creativity; it is a decision about the conditions for putting it into practice.
A worked example with an information board
Example scenario: A community centre coordinator proposes a new noticeboard with bold symbols and short headings. She wants visitors to notice upcoming events quickly. A colleague responds, “It looks chaotic, and older visitors will get lost.”
The first mistake would be to dismiss the feedback as resistance to a new style. Removing all the symbols immediately would be just as premature. The coordinator asks whether the problem is the number of colours, the small text, the order of the information, or something else. The colleague points out that the event date and location are less prominent than the decorative symbols.
This turns vague criticism into a specific question: Can a visitor find the date and location without an explanation? The coordinator prepares a second version that keeps the recognisable symbols but makes the practical details more prominent. With both versions, she asks a few visitors to point out where they would find the time of the next talk. She is not asking which noticeboard they like in general, but whether they can complete the same task.
The outcome of this example test is not predetermined. If people find their way more easily in the revised version, there is a reason to keep the change. If they struggle with both versions, the information structure itself needs attention. If there is no clear difference, it may be worth simplifying the designs further and testing them with additional users. What matters is that the decision does not depend on who sounded more persuasive in the meeting.
Watch for weak arguments in criticism
Some comments sound authoritative without giving you enough reason to make a decision. Pay particular attention to three situations:
- Appeals to tradition: “We’ve always done it differently.” Find out what the old approach actually achieved and whether the new proposal can do the same.
- Unsupported predictions: “People will definitely reject this.” Ask what the prediction is based on and whether there is a way to check it.
- Attacks on the author: “You don’t have enough experience for an idea like this.” Experience may matter when it comes to implementation, but by itself it does not determine whether a specific solution works.
Apply the same discipline when defending your own view. “It will definitely attract attention because it’s original” is no stronger an argument than “It definitely won’t work.” Originality can be an advantage when it serves the goal. If it makes the information hard to navigate or increases costs disproportionately, it can become an obstacle instead.
Don’t turn every objection into a personal verdict
Rejection can be discouraging, even for someone who usually works independently. In the moment, it helps to separate two statements: “This proposal has a weakness” and “I’m not a creative person.” The first is about a specific piece of work. The second is a broad judgment about a person that does not follow from one situation.
If you feel intensely frustrated, you don’t have to respond immediately. You can ask for time to think or return to the feedback the next day. But taking a break is not the right answer to every disagreement. A clear, well-supported flaw that needs urgent attention may call for a quick fix; with vague criticism, it is more sensible to gather information first.
Watch for two opposite traps. In the first, you revise the proposal after every disagreement until it loses its purpose. In the second, you reject feedback simply because you don’t want to give ground. Both responses are driven more by your reaction to being judged than by the problem itself. A steady goal and flexibility about the details are often a more useful combination.
So the next time someone responds negatively, don’t make a major change straight away. Write down one specific objection, ask about its consequences, and decide what smallest next step would give you useful information. Sometimes that will be a conversation; sometimes it will be a revision or a test. That is how uncomfortable criticism can become a basis for a thoughtful creative decision.
