Unfinished concepts can help when the designer explains what is being explored and asks for feedback suited to that stage. Share enough context to support a decision, distinguish exploration from recommendation, and avoid asking a client to approve unresolved production artwork.
Agree what the conversation is for
A rough sketch can reveal a promising idea quickly. It can also distract a client who assumes every visible detail is a proposed final decision. Showing unfinished work is therefore less about openness as a principle and more about setting useful expectations for each conversation.
I would begin the review by stating the question. Are we deciding whether a metaphor fits the business, comparing two positioning directions or checking the spacing of a nearly finished wordmark? Each task requires a different level of resolution and a different kind of feedback.
What Studio Cronica’s process contributes
Pushkar Mankar, Design Week: The Equator Company identity by Studio Cronica, 4 November 2026 reports that Studio Cronica shared unfinished work and tested ideas openly during The Equator Company project. The article describes regular collaboration rather than relying on a single polished reveal.
The useful lesson is that alignment can be built during exploration. It is not proof that every client should see every sketch or that presentation craft has no value. Different teams need different amounts of context, and the designer remains responsible for filtering and explaining the work.
Match feedback to the stage
| Stage | Useful question | Decision to defer |
|---|---|---|
| Exploration | Does this idea fit the business and audience? | Final spacing or production color |
| Direction | Which route best answers the agreed brief? | Tiny export differences |
| Refinement | Which specific relationship needs adjustment? | Reopening settled strategy without a reason |
| Production | Do the approved assets work in the required uses? | Adding a new concept at delivery |
For a hypothetical founder-led business, a rough bird silhouette might test an association with guidance. The review should establish whether that association fits. If the bird’s wing is still a placeholder, say so before the client spends the meeting discussing its final curvature.
Explain what is fixed and what is provisional
Label each presentation with its purpose and the decision required. Show the relevant part of the brief beside the work. Distinguish a deliberately unresolved detail from a mistake that needs correction, and make it clear which alternatives are being compared.
A small number of representative applications can help people understand an idea. Use only enough finish to answer the question. A beautiful mockup should not conceal an unresolved name or make a weak concept appear approved because it already looks expensive to change.
Turn preferences into usable observations
Ask a reviewer to describe what they see, what they think it communicates and where that conflicts with the brief. A comment such as the mark feels too informal becomes useful when tied to a specific buyer situation. It is harder to act on a request to make the whole thing more premium without examples.
Gather the client’s feedback through a named decision-maker. Separate conflicting views before the next revision round and record the reason for the chosen direction. This keeps the project from becoming a sequence of unrelated adjustments requested by people who have not seen the same information.
Protect space for the designer’s recommendation
Sharing rough work does not require handing over an unfiltered sketchbook. The designer should still explain which routes deserve development, what trade-offs remain and why one recommendation best serves the brief. The client should have enough information to participate without having to perform the designer’s role.
My design-process guide explains the wider sequence from discovery to delivery. This review framework concerns the conversations within that sequence. The portfolio shows completed work; it should not be read as a record of private client discussions or unfinished approvals.
Before ending a meeting, write down the decision, the remaining open question and the next deliverable. That simple record gives both sides a shared understanding of what happens next, whether the presentation contained a pencil sketch or a finished application.
Frequently Asked Questions
Should clients see every sketch?
No. Share the explorations that help answer an agreed question, explain their limits and keep responsibility for the recommendation with the designer.
What if feedback changes the agreed strategy?
Identify the new information and its effect on the brief, scope and timeline. Resolve that strategic change explicitly before treating it as an ordinary visual revision.
Sources and Credits
Created and sources checked on 9 November 2026. The editorial date places this article in the requested series; it is not a claim of earlier publication. External projects are credited to their creators. The review frameworks and hypothetical examples are design recommendations, not measured client outcomes.
Bring your brief and decision-making structure. We can shape a review process that makes the important choices easier to discuss. Book a free consultation or explore design services.