Are You a Designer?

A designer is not defined by one tool, aesthetic or personality. Design becomes visible in a repeated practice: noticing a situation, asking what matters, learning from the people involved, making possibilities tangible, testing consequences and explaining why one direction deserves to continue. Titles and taste may open a conversation; decisions and evidence sustain it.

This means design judgment is neither pure personal preference nor obedience to a famous designer’s rules. It is the ability to connect a choice to purpose, people, context and constraints, then remain willing to revise that choice when a prototype, participant or collaborator reveals something better.

Build an opinion without becoming trapped by it

A design opinion is a provisional judgment: this hierarchy is clearer, this material is more appropriate, this flow protects the user better, or this concept better expresses the intended character. The opinion becomes useful when another person can inspect the reasoning behind it. ‘I like it’ may be honest, but it does not yet explain what the choice accomplishes.

Interaction with other designers and aspirants expands the set of approaches you can see. Given the same research, two designers may frame different problems, combine evidence differently and pursue different ideas. Comparing their work is valuable because it reveals alternatives—not because one voice should replace your own judgment.

• Ask how another designer framed the problem before comparing final forms.
• Look for evidence they noticed that you overlooked.
• Identify the constraint or value that explains a different decision.
• Separate an unfamiliar approach from an ineffective one.
• Decide what the comparison changes in your next attempt.

Treat advice as input, not navigation by committee. If every comment has equal authority, feedback becomes noise. Give more weight to people with relevant lived experience, domain knowledge or responsibility for implementation, and to observations that repeat under testing. Keep the final reasoning visible so accepting or rejecting feedback is a decision rather than a reflex.

Present enough process to make the work legible

Putting work in front of others is part of the practice. A presentation must show enough research, alternatives and development for someone to understand the decision without turning the project into an archive of everything that happened. A short presentation can feel ungrounded; a long one can bury the argument.

1. Begin with the person, setting and goal—not the polished artifact.
2. Show the evidence that made the problem worth addressing.
3. State the important constraint and the criterion for success.
4. Show meaningful alternatives so the chosen direction is not presented as inevitable.
5. Connect the decision to a reason, then show what a prototype or test revealed.
6. End with the current result, its limitation and the next change you would make.

Presentation quality matters because design is collaborative, but presentation cannot rescue weak reasoning. A persuasive story should clarify the evidence and trade-offs, not manufacture certainty the project has not earned.

Borrow philosophies as lenses, not commandments

Influential designers offer different answers to what deserves attention. Studying them broadens the questions you can bring to your own work. The useful exercise is not to imitate a signature style; it is to apply a principle, observe what it reveals and recognize where the principle does not fit.

Other fields add other lenses: comfort and movement in fashion, narrative and atmosphere in interiors, integration and manufacturing precision in product design. Build a diverse reference library and annotate it. What is working, for whom, in which context, under what constraint—and what would fail if the context changed? Annotation turns admiration into a vocabulary for judgment.

Get the idea out of your head

A sketch or render can communicate intent while leaving the most important uncertainty untouched. Print the graphic at its intended size. Make the package from the proposed material. Build the interaction far enough for someone to attempt the core task. A prototype creates contact between an idea and the physical, technical or behavioral conditions it must survive.

Prototyping also teaches knowledge that explanation alone cannot provide: how cardboard bends, how a hinge tolerates repeated movement, how a label reads under poor light, how long a flow feels under pressure, how a control behaves with a keyboard or screen reader. The prototype’s fidelity should follow the learning question, not the desire to impress.

A participant’s difficulty is evidence about the design and context, not a verdict on the participant. One test can reveal a serious issue; repeated patterns provide stronger direction. Domain experts, engineers, craftspeople and critics still matter, but they answer different questions from the people expected to live with the result.

Probe causes without forcing a single root

Why–Why analysis investigates what may sit beneath a visible problem by asking why each condition occurred. The number five is a convention, not a requirement. Stop when the inquiry reaches a cause the project can investigate or influence, and branch when several causes are plausible. Social and service problems rarely have one neat root.

Each question in the diagram is a hypothesis to verify. Blaming ‘the supplier’ after the fifth answer would be premature if late ordering, a specification change or an unrealistic schedule also contributed. Use records, observation and conversations to distinguish causes from a plausible story.

Use SMART to sharpen commitments

Specific, Measurable, Achievable, Relevant and Time-bound—SMART—is most useful for defining goals and commitments. It does not make every research question good: early discovery may need an open question before the outcome is measurable. Use the framework when a team needs clarity about what it will change and how progress will be judged.

Talk with the people who shape the outcome

Stakeholders are people or groups who affect a project or are affected by it. Users are stakeholders, but the group may also include clients, operators, support staff, engineers, marketers, executives, regulators, community organizations and people exposed to indirect consequences. Their goals can conflict, which makes communication a design activity rather than a final presentation task.

Translate a design decision into an outcome and a reason: ‘Moving recent projects to the top should make updates easier because people returning to the system can reach the records most likely to need attention.’ This is stronger than ‘the new layout is cleaner’ because the claim can be challenged and tested.

Frame the use case from the situation toward the design. Establish the setting, person, goal and friction before introducing the response. Beginning with the product and working backward can make the user feel like evidence invented to justify a preferred solution.

Seek critique, not validation

Validation asks other people to confirm that the work—or the designer—is good. Critique asks what the work accomplishes, where it fails and what could improve. Constructive critique targets the artifact, decision and effect rather than the worth of the person who made it. It is specific enough to act on and open enough to discuss.

1. State what kind of feedback you need and which decision is still open.
2. Listen without defending the work before you understand the observation.
3. Ask for the moment, condition or criterion behind a broad reaction.
4. Separate a problem the critic observed from the solution they proposed.
5. Look for patterns, then decide which evidence changes the design and why.
6. Tell collaborators what changed—or explain the constraint behind a different choice.

When feedback conflicts

Take one decision. You design a poster for a campus recycling drive and set the date and venue small at the bottom, so the illustration can carry the message. Three people respond. A friend says the illustration is the best part and should be bigger still. A teacher says the date is too small. The organiser asks for the college logo at the top, larger.

Do not average the three. Return each one to the poster’s job: to bring people to one place at one time. The teacher’s comment points to something you can check: hold the poster at the distance people will read it from and see whether the date is legible. If it is not, the work changes, even though the illustration gives up some space. The friend’s comment is a preference about the part that already works; it changes nothing unless the illustration fails to draw attention. The organiser’s request names a solution, so ask what problem it solves. If people need to know who is running the drive, a smaller logo beside the details may do that without displacing them.

One comment changed the work because it was tested against the goal and the poster failed. One did not, because it restated a taste. One changed in form, because its problem was real but its proposed solution was not the only one. Write that reasoning beside the revision, so the next round of feedback starts from it.

Develop a style through repeated decisions

Personal style is not a visual effect to select in advance. It emerges from the subjects you notice, references you collect, materials and methods you return to, values you defend and decisions that survive repeated work. Exploration widens the vocabulary; reflection reveals patterns; consistency makes a point of view recognizable; new evidence keeps it from becoming a cage.

• Study work across periods, cultures and disciplines rather than copying one current reference set.
• Annotate why a composition, interaction, object or space affects you.
• Practise regularly across different tools and constraints.
• Keep rejected directions and document why the decision changed.
• Review several projects together to find recurring questions and choices.
• Bring personal experience into the work without assuming it represents everyone.

Questions for self-assessment

1. What subjects, situations and forms repeatedly hold my attention?
2. Which visual, material or behavioral qualities do I naturally notice first?
3. What do I want the people encountering my work to understand, feel or be able to do?
4. How do my interests and lived experience enrich the work—and where do they limit my view?
5. Which designers, makers or communities do I admire, and which specific decisions earn that admiration?
6. Which projects gave me energy, and what kind of problem or process did they share?
7. Which abilities can I demonstrate, and which weaknesses repeatedly constrain my ideas?
8. How do I respond when critique challenges a choice I identify with personally?
9. Which patterns appear across my work, and are they purposeful or merely habitual?
10. What practice, environment and collaboration help me stay curious enough to continue?

You do not become a designer by arriving at permanent answers to these questions. The practice is visible in the loop: you notice more, make a claim, materialize it, invite scrutiny, learn from the result and make the next decision with greater care. Changing your mind for a reason is not a failure of vision. It is design judgment becoming accountable.