Evidence-Informed Design

An argument about a color, a button, or a piece of copy can begin before the team has agreed on its purpose.

What should someone notice? What do they need to understand? What action should be possible? What would make the experience feel appropriate to the situation? What are we hoping will change for the business?

Those questions make the decision more useful to discuss. They turn a preference into something we can examine without pretending that every aspect of an experience can be reduced to a number.

The client's knowledge matters. So do the designer's expertise and the implementation team's understanding of what is possible. We want those contributions in the conversation, while remaining clear about what each can establish and where the people using the result may experience something different.

A chart can show a pattern in recorded activity. A conversation can reveal what that activity meant to someone. Observation can expose a difficulty people do not think to mention. Operational knowledge can explain why a problem keeps returning after the interface has been changed.

Useful material may come from research, feedback, testing, support records, content reviews, analytics, technical investigation, and the experience of people close to the business. Existing work can also contain valuable evidence; beginning a new engagement does not make the organization's history irrelevant.

We consider the source and its relationship to the question. A stakeholder's account of customer needs is valuable, but it is not the same as direct customer research. A designer's concern can identify something worth examining without being presented as an observed user failure.

Professional judgment helps interpret the evidence and decide what to do with it. We make that contribution visible rather than disguise it as a fact the data delivered.

Evidence informs the choice; imagination gives it form.

Someone leaves a page. We may know where their recorded activity ended. We may not know whether they were confused, interrupted, satisfied, or looking for something the business does not offer.

Those are possible explanations, not interchangeable findings.

We distinguish observations, interpretations, assumptions, and proposals. That separation makes it easier to challenge the reasoning without dismissing the person contributing it. It also helps identify the next useful question.

If we believe a person left because an explanation was unclear, what supports that interpretation? What else could account for the behavior? What could we examine before treating a rewritten page as the answer?

Not every uncertainty requires another research project. Some can be resolved through a focused review or an existing record. Others matter enough to justify deeper investigation. The distinction should follow the consequences of getting the decision wrong, not our desire to defend the first explanation.

Evidence has a context. Who contributed it? Under what conditions? How recently? What was asked or measured? What is missing?

A small set of conversations can reveal an important difficulty without establishing how common it is. A large volume of activity can look persuasive while reflecting an incomplete tracking setup. Feedback from enthusiastic customers may tell us little about people who never became customers.

We consider relevance and limitations before turning a finding into a general claim. When the experience or audience changes, older evidence may need another look.

Different sources can strengthen an interpretation or reveal a tension. If people describe something as straightforward but repeatedly need help completing it, that disagreement is worth understanding. It is not a reason to automatically discard either their account or the observed behavior.

We also look for evidence that could change our minds. An investigation built only to confirm a preferred direction offers less opportunity to learn.

Understanding a need does not produce the design response by itself.

Research may show that people feel uncertain. It does not automatically determine the image, language, interaction, service arrangement, or visual rhythm that would help. There may be several thoughtful responses, with different emotional effects and practical consequences.

This is where empathy, originality, taste, and creative judgment matter. We make connections, explore possibilities, anticipate needs, and give an idea a form that can be encountered and discussed.

Evidence can help us understand the conditions and evaluate a response. It should not become an excuse to copy what already exists or reject an unfamiliar idea because there is no historical result for it yet.

A sketch, prototype, piece of content, or small-scale trial can help make a new possibility examinable. We choose the form around the question rather than require every idea to become a complete product before anyone can learn from it.

When a service business brings us concern about unfinished consultation requests, we work through the explanation before agreeing on the remedy. Shortening the form or making its button more prominent might help, but a recorded completion rate does not establish the cause.

We examine what the measure includes, whether submissions are recorded reliably and what the surrounding page asks people to understand. The team contributes the questions prospective clients actually bring to a conversation.

Together, we ask whether the invitation sets the right expectation. Is someone being welcomed into an initial discussion, or does the language suggest they must arrive with a finished brief and a commitment to proceed? We treat that as a question to investigate, not an instant conclusion about everyone who leaves.

The response can then follow the evidence: clearer explanation, different information requirements, another contact route, technical repair or reconsideration of the offer itself. We agree what the next evaluation can tell us rather than promise that one page change will resolve every cause.

That process changes the conversation from making more people press a button to understanding what makes an inquiry a useful, comfortable step for them.

There is rarely time or budget to investigate every possibility. The work still has to move.

We consider what is known, what remains uncertain, and how much the decision matters. A reversible content adjustment and a major change to a service's operating model call for different levels of confidence and preparation.

We may proceed with a reasoned hypothesis, a limited release, or a clearly recorded assumption. We may recommend further research before making a costly commitment. Some conditions may justify stopping or rethinking an idea rather than polishing it further.

The important thing is to be honest about the basis of the decision and how we will revisit it. A deadline does not turn an assumption into evidence, and a lack of perfect evidence does not make careful action impossible.

Confidence grows when we can explain both the reason and its limits.

Where direct participant research or specialist testing is useful, we can co-create that work with appropriate partners. The complete framework makes those options visible without claiming that every engagement must use every method.

We want the discussion to move beyond whose preference carries the most authority. A shared question and a traceable reason give the client, designer, developer, and other collaborators something more useful to examine together.

That does not mean decisions become a vote. Abstraction contributes synthesis and recommendations; other people bring knowledge and responsibilities that need to be respected. We agree who decides and make the consequences of the choice understandable.

Nor does a favorable number settle every ethical question. An increase in completed actions does not justify misleading people, concealing a commitment, or making it harder to withdraw. A less frequently reported barrier may still have serious consequences for the person encountering it.

Empathy asks us to pay attention. Ethical responsibility helps establish what we will not do, even if a narrow measure makes it look effective.

Measurement Strategy helps establish useful goals, signals, definitions, and limitations. Evaluation then needs to consider the circumstances around the result.

A change after launch can coincide with different traffic, seasonality, new content, operational changes, or other influences. A before-and-after comparison may be useful without proving that one design decision caused the difference.

Controlled experiments can address some questions when the conditions support them. Other questions are better explored through observation, interviews, expert review, or a different form of investigation. Inconclusive evidence is still a result to record, not a gap to fill with the outcome we hoped for.

Learning may support a refinement, a larger redesign, or abandoning the direction. The willingness to make that distinction is part of being invested in the client's success rather than only in completing our original idea.

Product Intelligence brings the question, evidence, interpretation, decision, and subsequent learning into a useful shared record.

We want the client to understand why a recommendation is being made and feel more confident contributing to the next one. Participating in that reasoning can build an ability to recognize opportunities, ask better questions, and invest in improvements with a clearer understanding of their purpose.

The record also makes revisiting a decision less personal. We can ask whether its original conditions still apply rather than argue about whether it was permanently right or wrong.

Take a recommendation you feel strongly about and ask: What would we need to learn for me to change my mind?

Then ask what you already know, what you are assuming, and what the smallest useful next investigation could be. This is a prompt for inquiry, not a requirement to test every aesthetic preference or a substitute for a research plan.

Within Design Thinking, evidence contributes throughout Discover → Define → Explore → Design / Develop / Market → Learn → Advance → Discover. It can inform a website, brand, service, environment, campaign, or operational system; its form should suit the subject.

Evidence-Informed Design is a principle of how we work, not an isolated package. If you have an idea you believe in, a result you cannot explain, or a decision that keeps becoming a matter of opinion, bring it to us. We can make the reasoning visible and work out what is worth learning next.

Contact Us