“We need a design” can mean almost anything. A business might need a finished leaflet, a clearer identity, a page that explains a service or help deciding what information belongs on a sign.
For the designer, those are different assignments. For the customer, they can sound like one request. The business of design begins by making that difference understandable.
Creative skill matters, but it does not settle the brief, confirm the supplied information or decide who approves the work. Those questions need a conversation.
This guide is for people offering design work and small businesses commissioning it. It offers a practical way to clarify a project without promising income, sales growth or a particular return on design.
The first problem may not be the one in the first request
A hypothetical customer asks for “a more modern brochure”. That describes a proposed response, but not necessarily the difficulty.
Perhaps the service has changed. Perhaps readers cannot find the relevant option. Perhaps the existing wording no longer matches what the business can deliver.
Updating the appearance could be useful. It could also leave the important problem untouched.
The Design Council’s Double Diamond provides a helpful reference. It describes discovering the problem rather than assuming it, defining the challenge, developing possible answers and testing solutions through delivery.
That model is not a guarantee of commercial success or an instruction to turn every small job into a lengthy exercise. Its useful reminder is that deciding what to make deserves attention before making it.
Our interpretation is straightforward: ask what the customer needs to change, then check whether the requested design is a suitable response.
Explain the audience in ordinary language
“For everyone” rarely gives a designer much to work with. Explain who needs to use the finished piece and what they need to understand.
Are they already customers or encountering the business for the first time? Are they comparing options, finding instructions or deciding whether to enquire?
A returning customer may recognise terminology that a new visitor does not. An event attendee may need a date and location before the organiser’s background story.
This is not a demand for invented customer profiles. Use information the business actually knows. If an assumption is being made, identify it.
The brief becomes more useful when the audience is connected to a task. “Help a new visitor understand the available formats” gives the design a clearer purpose than “appeal to a broad demographic”.
Separate the result from the deliverables
A business may want more enquiries. The design commission might deliver a service-page layout, revised wording or artwork for a printed piece.
Those are different kinds of statement. The first is a desired business result; the others are things the project can produce.
Do not quietly turn the desired result into a guarantee. Design can contribute to a customer experience without controlling every condition that affects a sale.
Identify the deliverables clearly. Which items, pages or versions are included? Is the assignment to develop an idea, prepare finished artwork or adapt an existing design?
If an element is only a concept, call it a concept. If production or implementation belongs to another stage, make that distinction visible. A persuasive presentation should not imply that unfinished work is ready for use.
Say what is outside the job
A clear scope explains the boundary as well as the included work.
A leaflet layout does not automatically include photography. A logo discussion does not automatically include every application of the identity. A website layout does not establish that integrations or ongoing support are included.
These are examples of questions to clarify, not claims about what a particular supplier excludes.
The purpose is to prevent two reasonable people from approving different versions of the same project in their heads.
If the customer later needs another item, discuss it as an additional requirement. It is more useful to recognise the changed assignment than to pretend the original description covered every possible extension.
Identify what the customer needs to supply
Design work can begin with incomplete material, but the missing information still needs an owner.
List the wording, logos, photographs, specifications and other facts required. Establish which are final and which need work.
A file named “final” is not proof that its contents are current. Confirm important details such as contact information, dates and the offer being described.
If existing artwork is available, explain what it is and whether an original file exists. A screenshot may communicate an appearance without providing the underlying artwork.
Keep unknown facts visible. A designer should not fill an information gap by inventing a product feature or business promise simply because the layout needs another sentence.
Use references to explain a preference, not to request a copy
A reference can help somebody explain an idea they find difficult to describe. It becomes less useful when nobody identifies which part matters.
Is the customer responding to the information order, the colour relationship, the type size or the overall mood?
Discuss those elements separately. Two people can admire the same example for entirely different reasons.
A reference is not permission to reproduce another business’s wording, photography or artwork. Nor should it determine a design that does not suit the actual requirement.
The practical aim is to turn “something like this” into an understandable preference. That gives the designer room to answer the brief rather than recreate a surface.
Make feedback specific enough to use
“I don’t like it” may be an honest reaction, but it does not identify what needs changing.
Try connecting feedback to the agreed purpose. Is the main message unclear? Is an option missing? Does the image suggest the wrong product? Is the next action difficult to find?
A personal preference can also be stated plainly. It does not need to be disguised as a universal design rule.
For the designer, explain the relevant choices without treating every criticism as a misunderstanding. The work should be understandable to its intended audience, not only to the person who made it.
Bring feedback together where possible. Several incompatible instructions from different people can leave the project without an agreed direction.
Decide who can approve the work
A project can involve several contributors while still needing a clear approval route.
Who confirms the wording? Who checks the product facts? Who decides that the design is ready for its intended use?
These responsibilities may belong to different people. Identify them rather than assuming that one approval covers everything.
A designer can review arrangement and presentation without knowing whether a customer’s event date or technical specification is correct. The relevant person must confirm those facts.
Use an identifiable proof or version for final approval. A vague reference to “the latest one” becomes less reliable when several similar files have circulated.
A mock-up is an explanation, not a completed result
A mock-up can show how a proposal might appear. It does not establish that the product has been made, the page implemented or the customer experience tested.
Label concepts and illustrations clearly. If an image includes an unconfirmed material, setting or feature, do not let it become an accidental promise.
The same discipline applies to a portfolio. A visually convincing scene is not evidence that the depicted project happened.
A hypothetical identity can demonstrate thinking when it is identified as hypothetical. A real commission can show completed work when its use is authorised and the description is accurate.
The distinction does not make concept work less useful. It tells the reader what kind of evidence they are looking at.
Clarify permission and the intended use
Files, permission to use a design and ownership of copyright are not questions to leave to assumption.
The Intellectual Property Office of Ireland’s copyright guidance explains that paying for commissioned work does not by itself establish ownership of its copyright. The commissioning arrangement matters.
For a project, clarify the intended uses, supplied assets and agreed rights. Do not assume that an image found online or a file supplied by somebody else is authorised for every proposed application.
This is a prompt to resolve permissions, not legal advice or a substitute for reviewing a particular agreement. Where ownership or use is uncertain, obtain appropriate advice before relying on an assumption.
Likewise, agree portfolio permission before publishing customer work. A finished design does not automatically authorise disclosure of private information or unpublished material.
Show the work without inventing the outcome
A useful portfolio can explain what the assignment involved, what was delivered and why particular decisions were made.
It does not need a fabricated growth statistic to make the work sound important.
If the business reports an outcome, distinguish that report from something independently established. If several things changed together, do not attribute the entire result to the design without evidence.
For example, a clearer information hierarchy can be described as a design decision. Claiming that it caused a particular sales increase requires different evidence.
Be clear about your role. If several people contributed, say what you did rather than claiming the whole project as your own. Readers need to understand the work and what the evidence shows.
A useful handover explains what has been supplied
The customer should understand what arrives at the end of the commission and what it is for.
Identify the agreed files, versions and instructions. Explain which are for the intended output and which are previews or working material.
If further production, implementation or checking remains, state it clearly. A handover should not turn an unresolved requirement into somebody else’s surprise.
Also clarify how later updates will be handled. A file can be correct today while contact details or product information change later.
This is part of completing an understandable assignment. It does not mean every project includes unlimited revisions, future support or every source file. Those are matters for the agreed scope.
A short brief both sides can use
Before commissioning or beginning the work, bring these points together:
- The audience and the task the design should help them complete.
- The problem being addressed, separated from the preferred appearance.
- The deliverables, formats and versions included.
- The facts and assets available, with missing material identified.
- The intended use and permissions requiring confirmation.
- The people responsible for feedback, factual checks and final approval.
- The required date and any dependencies that affect it.
- The handover and any separately agreed follow-on work.
The document does not need elaborate terminology. It needs to describe the same job to everyone involved.
Beginning a design conversation with Time for Designs
Explain what you need the finished work to do and what material you already have. State the intended use, approximate scope and required date.
For website work, see our website design service. Projects are assessed and quoted individually according to the required pages, content, design work, functionality, migration, integrations and support. Annual services are quoted separately.
Call 062 61524 or visit the Cashel shop to discuss the requirement. A conversation establishes whether the proposed work fits; it is not a promise to undertake every specialist design service.
The business is the agreement as well as the artwork
Making something attractive is not the whole assignment. The design must answer an understood requirement, use accurate information and arrive through a clear approval process.
For a designer, that means explaining the work honestly. For a customer, it means giving the project a purpose and resolving the facts only the business can confirm.
Neither side needs to pretend every uncertainty has disappeared at the first conversation. They do need to recognise those uncertainties and agree how to address them.
That is a more useful starting point than a promise that creative skill automatically turns into income—or that a new appearance automatically turns into sales.
Sources and scope
The design-process reference comes from the Design Council. The limited copyright reference links to the Intellectual Property Office of Ireland’s guidance. The project examples and working recommendations are Time for Designs’ interpretation, not claimed client cases or research findings.
This guide does not provide legal, pricing or career-income advice. Particular commissions require their own assessment and agreement.