14/07/2026
The Physiology of Design: Why Design Begins Before the Visual
For a long time, I believed that becoming a better designer meant becoming more skilled at seeing.
I studied proportion, contrast, hierarchy, proximity, alignment, typography, and white space. I learned how these principles guide the visual system, organize information, and influence where people direct their attention.
When I looked at an interface, I began to notice everything.
The headline lacked contrast. The button was not prominent enough. The spacing between elements felt inconsistent. The page needed more breathing room. The visual hierarchy was unclear.
These observations were not wrong. Yet, over time, I began to feel that something was missing.
I could explain how to make an element more visible, but I could not always explain why that element deserved greater visibility.
I could say that a call-to-action button needed stronger contrast. But why did it need to be highlighted? Because the business wanted the customer to click it. Why did the business want that action? Because it might lead to a sale.
At that point, I was no longer dealing with contrast.
I was dealing with business strategy.
I was dealing with marketing, sales, branding, customer readiness, trust, risk, and long-term value. The visual decision was only the final visible outcome of a much deeper chain of decisions.
This realization changed the way I understood design.
I began to see that proportion, contrast, proximity, hierarchy, and white space are not independent reasons for design choices. They are instruments. They help us express a decision, but they cannot determine whether the underlying decision is correct.
Contrast can tell people where to look.
It cannot tell us what they should be looking at.
The Question Behind the Button
Imagine that I am reviewing a website with a design team.
Someone says, “The call to action needs to be more prominent.”
I ask, “Why?”
“So users can see it.”
“Why do they need to see it immediately?”
“Because we want them to take action.”
“What action?”
“To purchase the product.”
“Why should they purchase at this moment?”
This is where the conversation usually becomes more difficult.
The team may know what the business wants the customer to do, but it may not know whether the customer is prepared to do it.
Perhaps the visitor has only just discovered the company. They do not yet know what the product does, how it is different, whether it can be trusted, or whether it is relevant to their situation.
Yet the interface immediately presents a large, high-contrast button asking them to buy.
From a narrow visual perspective, the button may be successful. It is visible. It attracts attention. It follows common interface conventions.
From a behavioral perspective, however, the decision may be premature.
The customer is being asked to choose before understanding what they are choosing.
This may increase uncertainty rather than reduce it. The customer may begin thinking about what they could lose before they understand what they might gain. They may feel that the business is attempting to accelerate a decision for which they are not yet prepared.
The question is therefore not simply whether the CTA is visible enough.
The more fundamental question is whether this is the appropriate action for this customer at this stage of the experience.
Design Begins With Two Realities
I now believe that every meaningful design process begins with two realities.
The first is the reality of the provider: the business or organization offering the product or service.
The second is the reality of the receiver: the customer for whom the product or service is intended.
The visible design exists between these two realities.
A designer cannot responsibly determine what should be emphasized without understanding both sides.
The Reality of the Business
A business does not make decisions in isolation.
Its choices are shaped by revenue requirements, operational capabilities, market conditions, brand positioning, sales processes, marketing strategy, competitive pressure, legal restrictions, and long-term ambitions.
One company may need immediate sales.
Another may be trying to build awareness in a new market.
A third may want customers to explore its product range before making a purchase.
Another may prioritize trust, education, retention, consultation, or long-term customer relationships.
These are different strategic situations. They should not produce identical interfaces.
Before deciding where to place a CTA, the designer must understand what the business is actually trying to achieve.
Does the business want the customer to purchase immediately?
Does it want them to learn first?
Does it want them to compare products?
Does it want them to contact a representative?
Does it want to introduce the brand before asking for commitment?
Does it want short-term conversion, or does it value long-term trust and customer lifetime value?
These decisions cannot be made through visual intuition alone.
They require participation from management, branding, marketing, sales, product, research, and other relevant functions. Each of these areas contributes information that affects the experience.
The designer should not invent the business strategy by making a button larger.
The visual hierarchy should reflect a strategic decision, not replace one.
The Reality of the Customer
The customer also arrives with a reality of their own.
They do not enter an application or website as a neutral person waiting to be directed. They bring previous experiences, expectations, fears, habits, motivations, social influences, and levels of knowledge.
Some customers already understand the product.
Others do not know why they need it.
Some arrive with a strong intention to purchase.
Others are merely exploring.
Some trust the category but not the company.
Others distrust the entire category because of previous experiences.
The customer may be influenced by where they live, their economic situation, cultural expectations, family, colleagues, social groups, local politics, market conditions, and the way similar products have trained them to behave.
When I design for these customers, I cannot begin only by asking what the business wants them to do.
I must first ask what state they are currently in.
What do they already know?
What do they still need to understand?
What do they believe about this type of product?
What risks do they perceive?
What information would reduce their uncertainty?
What would make the next decision feel reasonable rather than forced?
The appropriate design depends on the answers.
A returning customer who already understands the offer may benefit from an immediate and prominent purchase action.
A first-time visitor considering an expensive or unfamiliar service may need explanation, evidence, comparison, and reassurance before seeing the same action presented as the dominant option.
The CTA has not changed.
The context has.
The Appropriate Next Action
This led me to rethink what a call to action actually is.
A CTA is not merely a button designed to increase conversion. It is an invitation to move from one state to another.
The customer may move from unfamiliarity to understanding.
From uncertainty to confidence.
From comparison to selection.
From interest to commitment.
From purchase to continued use.
Therefore, the important question is not simply:
“What action does the business want?”
It is:
“What is the most appropriate next action for this customer, given their present state and the business objective?”
Sometimes that action is “Buy Now.”
But sometimes it is “Learn More.”
Sometimes it is “Explore Products,” “Compare Options,” “See How It Works,” “Calculate the Cost,” or “Speak to an Adviser.”
A business may ultimately want a sale, but the most effective path to that sale may not begin with an immediate request to purchase.
The experience may first need to create understanding.
It may need to establish identity.
It may need to show evidence.
It may need to reduce perceived risk.
It may need to give the customer enough breathing space to decide whether the offer is relevant.
This does not mean that every customer must be forced through a long educational journey. A highly motivated customer should not be prevented from acting quickly.
The interface may need to support different levels of readiness. An immediate action can remain available, while the main experience helps less-prepared customers develop the confidence required to make an informed decision.
The point is not to hide the CTA.
The point is to ensure that its prominence corresponds to the customer’s readiness and the business’s actual strategy.
When Persuasion Becomes Premature
When a business asks for commitment before creating sufficient understanding, the interface may generate resistance.
The customer may feel pressured. They may sense that the business is attempting to control the pace of the decision.
They may experience uncertainty because they do not understand what will happen after clicking.
They may focus on potential loss because the requested commitment appears before the benefit has become clear.
They may also experience decision anxiety because they are being asked to choose without enough information.
These reactions are often discussed through concepts such as psychological reactance, ambiguity aversion, loss aversion, and cognitive load.
However, I do not think designers should treat these ideas as mechanical laws.
Human behavior cannot be reduced to a checklist in which one principle always creates one predictable result.
The same design pattern can create different reactions in different contexts.
Scarcity may increase urgency for one audience and reduce trust for another.
Minimalism may communicate confidence in one market and insufficient information in another.
Social proof may reassure some customers while appearing artificial or irrelevant to others.
A prominent CTA may feel efficient to a returning customer and aggressive to a first-time visitor.
Behavioral principles help us form hypotheses. They do not remove the need to understand context.
Returning to the Visual Principles
Once the realities of the business and customer are understood, visual principles become meaningful.
At this stage, contrast is no longer an arbitrary styling choice.
It expresses a decision about attention.
If I increase contrast, I should be able to explain why the highlighted element deserves priority.
Is it the most appropriate next action?
Is it essential information?
Is it a risk the customer must understand?
Is it the primary difference between this product and its alternatives?
Would failing to notice it cause confusion or lead to a poor decision?
Contrast is justified when attention has already been strategically justified.
The same applies to proximity.
Proximity tells the customer which elements belong together. A claim should be close to the evidence supporting it. A price should be close to the terms that explain it. An action should be close to the information required to understand its consequences.
White space also has a purpose beyond beauty.
It can regulate the pace of the experience. It can reduce perceived complexity, create moments of reflection, and prevent the interface from feeling psychologically demanding.
Sometimes a customer needs speed.
Sometimes they need clarity.
Sometimes they need room to consider an unfamiliar or consequential decision.
The correct use of space depends on the situation.
Hierarchy, similarly, tells people what matters first, what matters next, and what can wait.
But hierarchy becomes problematic when it reflects only the interests of the provider.
If the purchase action is highly visible while the cost, risk, limitation, or commitment is hidden, the interface may be persuasive without being responsible.
A meaningful hierarchy must consider both business value and customer understanding.
The Wider Context of Choice
As my thinking developed, I began to recognize that the customer’s decision does not occur only inside the interface.
The customer lives within a wider environment.
Their decisions may be affected by economic uncertainty, political events, cultural values, social expectations, technological familiarity, market maturity, and the behavior of people around them.
Their understanding of one product may be shaped by the choice architecture of similar products they already use.
Their family or professional group may influence what is considered acceptable, trustworthy, prestigious, or risky.
This does not mean that every project must study every social, political, and economic variable in existence.
That would make design impossible.
The more practical responsibility is to identify the contextual factors most likely to influence the specific decision being designed.
Research should help the team reduce assumptions.
It should reveal which variables matter, which fears are relevant, which expectations already exist, and which parts of the customer journey require the greatest attention.
The goal is not perfect prediction.
The goal is a more informed design hypothesis.
Design as a Causal Process
I now understand design as a causal process.
The final interface should not contain elements merely because they are common, attractive, or considered best practice.
Every important visible decision should be traceable to an earlier reason.
The process can be expressed as follows:
Context → business objective → customer state → appropriate next behavior → experience sequence → interface hierarchy → visual expression → measurement
This sequence allows the designer to explain not only what has been designed, but why.
For example:
A first-time visitor does not yet understand the value of the service.
Because of this, asking for immediate purchase may increase uncertainty.
The business ultimately needs qualified customers, not simply accidental clicks.
The experience should therefore first establish the company’s identity, explain the value, and provide evidence.
A direct purchase option can remain available for high-intent visitors, but it should not dominate the experience before sufficient understanding has been created.
The visual hierarchy can then reflect this reasoning.
The introduction receives emphasis.
The evidence is connected to the claims.
The exploratory action becomes prominent.
The purchase action becomes more visually dominant later in the journey, when the customer has reached a more appropriate state of readiness.
Now the design is not based on preference.
It is based on a hypothesis that can be examined.
Did customers understand the product?
Did they find the relevant information?
Did they develop greater confidence?
Did qualified conversions increase?
Did regret, cancellation, or support requests decrease?
Did the interface create only a short-term click, or did it support a valuable long-term relationship?
Measurement completes the design process by showing whether the underlying reasoning was credible.
The Visual Is the Final Translation Layer
I once said that visual design should be the last thing that comes to mind.
I would now refine that statement.
Visual exploration does not always need to occur at the final chronological stage. Sketches, interfaces, and prototypes can help teams expose strategic problems. A visual model may reveal that the journey is confusing or that the intended customer action has not been properly defined.
Design is often iterative rather than strictly linear.
However, visual styling should remain the final translation layer.
It should translate knowledge about the business, the customer, the context, and the intended behavior into a form that people can perceive and use.
It should not substitute for that knowledge.
A designer should not begin by making an action persuasive and only later ask whether the action was appropriate.
The appearance of the interface may evolve throughout the project, but its final hierarchy must be accountable to deeper reasoning.
Beyond Making Things Pretty
A beautiful interface may attract attention.
It may appear modern, sophisticated, and professionally executed.
But visual quality alone does not establish that the design is valuable.
A valuable design can explain its decisions.
Why is this information shown first?
Why is this action dominant?
Why is another action secondary?
Why is the customer being asked to decide at this moment?
What does the customer need before proceeding?
What does the business gain from this sequence?
What might the customer lose?
What evidence would demonstrate that the decision is working?
When these questions cannot be answered, design becomes decoration.
When they can be answered, visual design becomes something more significant. It becomes the visible expression of a relationship between a business and the people it serves.
This is what I now think of as the physiology of design.
The visual interface is the part we can see, just as the appearance of a living body is visible. But underneath it is a system of causes, relationships, pressures, and functions that determine how the whole organism behaves.
The button, the contrast, the spacing, and the hierarchy are the surface.
The business reality, the customer reality, and the context connecting them are the system underneath.
To design only the surface is to make something look alive.
To understand the system is to design something that can actually functio
