Logo feedback: useful questions and a review checklist
In short
Useful logo feedback identifies an application, a file version and an observable problem. 'The name cannot be read in the profile image' can be checked. 'Make it more premium' needs a clearer explanation before it becomes a design instruction.
You show a new logo to colleagues, family and friends, and get conflicting reactions. One person wants a different colour; another prefers the old version. The problem may be the question rather than the people answering it.
A logo needs to work for the intended audience and applications. Ask about those tasks before asking whether someone likes it. For a Gulf business, that includes the Arabic name, the English name and any combined version customers will actually see.
Logo feedback: understand the reviewer’s perspective
A friend can be a prospective customer or have relevant production experience. Being close to you makes their view neither automatically right nor irrelevant. Ask what they are qualified to observe.
Do they know the intended audience? Have they seen the brief? Are they describing a problem or a personal preference? Are they looking at the same file and application as the other reviewers? Record those conditions before comparing answers.
Write down the task before asking for opinions
List the sender, the intended impression and the actual applications. Pucca Diana’s identity was developed for an animated intro, a favicon and a business card. Those are different viewing conditions and help explain why the project needed related variants.
For your brief, add the required Arabic and English name forms and any fixed wording. A large isolated mark on a presentation slide is not enough to approve a family that must work on invoices and small profile images.
Who can help with which question?
| Reviewer | Useful perspective |
|---|---|
| Prospective customers | Meaning, expectations and first impressions |
| Existing customers | Connection with the business they already know |
| Industry contacts | Similarities to competing brands |
| Printers or other production partners | Suitability for the intended output |
These are perspectives, not automatic approval rights. A printer can identify a reproduction problem without deciding the positioning. The project owner remains responsible for weighing the evidence against the brief.
Questions that produce more useful answers
Ask the same questions about the same applications:
- What does this mark bring to mind?
- What sort of company would you expect behind it?
- What can you read at this actual size?
- Which version fits the stated audience and why?
- Does it remind you of another business?
Avoid leading with your preferred answer. ‘Does this look expensive?’ invites agreement more readily than an open question about expected price level. A few conversations can reveal problems, but they are not a representative market study.
Separate the observation from the proposed fix
‘In this profile image the full name disappears’ is an observation. ‘Use the monogram instead’ is a possible response. Keep the two separate so another solution can be considered.
Apexor’s documented family includes a wordmark, monogram and icon. That provides different options for different spaces; it does not prove that every option works in every profile. Review the actual export rather than relying on its label.
Show the logo where people will encounter it
Use the website header, a product label, a profile image, a favicon and a quotation or business card where relevant. Put real names and text into the layouts. For bilingual applications, review the Arabic and English files as well as the combination.
Pucca Diana’s intro, favicon and card illustrate why an application list matters. The record establishes those uses; it does not supply measured recognition scores or a universal minimum size.
Compare variants according to their job
A wordmark communicates the name; an icon may need to work in a small square. Comparing them as if they were interchangeable can produce the wrong revision.
Keep the application, size and background constant when comparing versions. Ask whether the sender is identifiable, the necessary wording is readable and the variant fits the available space. Do not invent a minimum size without testing the actual file and output.
Criteria beyond personal taste
| Criterion | Review question |
|---|---|
| Fit | Does it support the offer, audience and intended price level? |
| Distinction | Is it sufficiently different from relevant competitors? |
| Readability | Can the needed information be understood at the intended size? |
| One-colour use | Do the forms remain clear without colour effects? |
| Variants | Are there suitable files for wide, square and small applications? |
| Continued usefulness | Does the decision depend on a short-lived visual fashion? |
A positive answer is tied to the application reviewed. A legible print does not by itself establish brand recognition in the market.
A suggested review record
| Field | What to record |
|---|---|
| Application | Actual profile, website placement or print sample |
| File | Filename and version |
| Size | Measured output dimensions |
| Task | Read the sender or identify the intended brand |
| Observation | What was readable, lost or confused? |
| Decision | Keep, revise or check again |
This is a proposed protocol, not a completed user test. Use it to make corrections traceable rather than presenting informal comments as research findings.
What makes a logo good in practice?
For this review, focus on readable information, distinguishable variants and a credible connection with the business. State the application whenever making a judgement.
The same wordmark might work in a website header and fail on a narrow label. That is a useful design problem. Whether people will remember the brand after repeated exposure requires different evidence from this technical check.
How to handle conflicting feedback
Group recurring observations and check whether reviewers are describing the same application. Several people misunderstanding the business deserves attention. A single dislike of green has a different evidential weight.
Return to the brief before combining suggestions. ‘Make it red’ may express a concern about visibility, energy or differentiation. Clarify the concern instead of treating the colour request as the only available answer.
Record approval as a specific decision
Name one person to consolidate comments. Record the approved variant, applications and remaining checks. Direction approval is not automatically approval of every production export.
Keep the final decision beside the file set. The logo redesign guide explains the difference between correcting a limited problem and commissioning a new direction.
When feedback justifies a redesign
A revision is worth considering when the intended audience repeatedly reads the wrong message, or the necessary information fails in real use. Identify whether the issue is technical, visual or strategic before choosing the scope.
Our Logo and Brand Essentials package starts from $1,400 (≈ AED 5,150). The logo design service and logo cost guide explain the offer; a limited correction is scoped according to the existing files and required applications.
Agree revisions and permissions in writing
Specify the number or scope of directions and corrections in the offer. A published starting price does not imply unlimited redesign work. If an existing mark is being changed, check the relevant agreement and permissions before editing it.
A feedback document records the design decision. It does not replace a rights review or establish that a mark can be registered in every target market. Send us the current files and the problem you want to solve to define the next step.