Clarify a design feedback owner at Singapore business networking events

The problem

A Singapore freelance designer meets a prospective client whose team gives conflicting design comments, but no one can identify who will resolve them or approve the project brief.

Start with the task the brief must describe

Ask what someone needs the proposed design to help a person do, what output they are considering and which condition matters to that task. Keep their stated need separate from a solution you suggest. DesignSingapore’s business resource provides design resources, case studies and initiatives; use it as learning context for a business conversation. It establishes no particular client project or review entitlement. A request to make something look more professional can leave the working task unclear. Ask for one concrete use, such as comparing two product options, before sorting comments about appearance. Choose a relevant discussion and permitted work example, then establish which client information and approval route are needed before detailed brief work.

• DesignSingapore Design for Business ↗ · Source checked 20 October 2026

Make a role record from actual answers

Use four rows: supplies the relevant information; gathers feedback into a usable account; resolves competing priorities; and accepts the brief for its intended next step. Add the named person or team, what they said they handle, the item or decision it covers, the answer’s source and the question still open. One person can occupy several rows when the responsible reply establishes that arrangement. Leave a missing row unknown rather than assigning it to the most senior title or the person who introduced you. Ask whether technical wording, business priorities or another required decision has a separate owner. Use the record to clarify the prospective client’s process; it does not appoint their decision-makers or establish authority from attendance at a networking event.

Translate conflicting comments into the choice they imply

Take one pair of comments and ask which task, requirement or assumption each expresses. A request for more detail may concern missing information, while a request for a shorter card may concern the available reading space. Preserve both explanations until the responsible team states which condition governs this particular output. DesignSingapore’s customer-research article discusses observation, interviewing, research questions and prototype testing. That context supports asking what is known about customers; it supplies no customer finding for your prospective project. Record an observation someone actually reports, a preference they express and a test they propose as separate kinds of information. Counting comments or choosing the more confident speaker leaves the underlying priority decision unanswered.

• DesignSingapore: understanding customers through design ↗ · Source checked 20 October 2026

Work through a wholly fictional product-card brief

Every person, comment and project detail in this example is invented. A prospective client wants a card helping customers compare two product sizes. Person R can supply the product facts. Person C gathers the team’s comments. One comment requests a longer brand story; another requests a size table in the limited space. The designer has no customer research showing what those readers need, and nobody has yet named the final brief approver. A useful record states the proposed task, the competing content priorities, R’s information role, C’s consolidation role and the unanswered decision rows. The next question is who decides the card’s priority and accepts the resulting brief. The example does not show that either layout works or that the client has commissioned a design.

Close only the role a reply actually resolves

In the fictional case, a reply says, “C will collect and combine the comments.” That fills the consolidation row while leaving priority resolution and final brief acceptance open. A later fictional reply says T decides which product-comparison requirement governs; record that decision role and ask what T needs from R. It still leaves the final brief row unanswered. A subsequent fictional reply names A to accept the brief, and A then replies, “I accept the stated task of helping customers compare the two sizes.” Keep that limited acceptance with this invented version. The layout, final wording, later design review and commission remain unanswered. Keep the earlier reply and the new answer distinguishable. Use the actual client’s process for a real enquiry, rather than treating these invented names and stages as a standard organisation chart.

Keep the initial contribution within the conversation agreed

Offer a bounded observation or question when the exchange welcomes it: “These comments seem to describe two different priorities; which customer decision should this card support?” That can expose the missing brief question without producing a complete layout or strategy. If someone requests several alternatives, a research exercise or a detailed proposal, clarify the requested output, required inputs, responsible review and the process for agreeing that further work. Preserve what was actually requested and what you have agreed to consider. You can use a clearly fictional sample when the operating question needs discussion but real material cannot be shared. A friendly exchange supplies no permission to publish the client’s comments or promise ongoing reviews. This is a scope conversation aid, not a price recommendation or interpretation of an agreement.

Retain the accepted brief decision and the next open action

Keep the current task, relevant constraints, role record, decision or brief version accepted, information still required and agreed next action together. In the invented case, A’s reply accepts the stated two-size comparison task; the particular layout, actual content and next review remain open. Ask who will supply the missing item and which route will confirm it. Record a proposed follow-up as proposed until the relevant person agrees. If a new comment changes the task or adds work, identify what changed and ask which existing decision needs reconsideration. A previous answer about one card does not settle the new request. Keep any commission, detailed scope and material-sharing arrangement within their separately agreed process. The record helps prepare that conversation without reporting accepted work that has not been established.

Choose a session that can support the question

For a prospective-client conversation, check the actual described participants and networking opportunity. For peer practice, ask whether the session offers time to examine a fictional role or brief example. A talk about design can support learning while leaving individual case review unavailable. An unsent enquiry could say: “I offer [design service] and want to examine how a brief handles conflicting comments. Does this session permit [relevant discussion or case exercise], and what material may participants bring?” Adapt it to the organiser’s stated format. Use Boardzip’s free design-business search to find current candidates, then confirm their actual participation and sharing arrangements. Bring the blank role record and one permitted question. Keep an unanswered review or client-access condition visible when choosing the next useful opportunity.