Evidence-Driven Design Consulting

Advisory work on which design decisions are genuinely open, what evidence would settle each one, and what to do when the evidence disagrees with the plan. We do not run your design team or your analytics stack: we work on the decisions both of them are being asked to resolve.

Hintergrund des Service-Kopfbereichs L

Evidence-driven design consulting is advisory work on a narrow question: which design decisions in a digital product are worth settling with evidence, what evidence would actually settle them, and what the company does when the evidence disagrees with the plan. Vivaldi is a strategy firm. We do not staff your design team, draw your screens or run your analytics stack. We work on the decisions those things are being asked to resolve, and on the gap between the data a product already generates and the choices anyone makes because of it.

  • Since 1999brand, product and experience strategy work
  • Über 200veröffentlichte Fallstudien
  • 10 Niederlassungenauf vier Kontinenten
  • 5xWirtschaftsWoche: Das Beste aus den Bereichen Beratung, Strategie und Innovation

Two boundaries first, because they save a wasted meeting. If your question is how the product behaves when a person acts on it, the states, defaults, feedback and automated behavior inside the interface, that is interaction design (IxD) and it is a different engagement.

If your question is the participant model, the value exchange and the governance of a system that spans several companies, that is digital ecosystem design, and this page is not the one you want.

Wenn Unternehmen uns beauftragen

  • A redesign is funded and nobody can say, in one sentence, what result would prove it was the right call.
  • The product generates more behavioral data every quarter, and the design roadmap has not changed because of any of it.
  • Two senior people disagree about a flow, both cite research, and the research does not actually address the point in dispute.
  • Testing happens late, after the build is committed, so it produces reassurance rather than decisions.
  • An agency or internal team is producing good work against a brief that was never argued with.

Why more research does not make the decision better

Most companies in this position are not short of evidence. They are short of decisions written down clearly enough for evidence to contradict them.

Research gets commissioned against a topic rather than a question. A usability round tells you people struggled on step three, which everyone already suspected, and says nothing about the choice the team was actually arguing over. Analytics report what happened inside the design you already shipped, so they can rank variants of the current idea and cannot see the one you did not build. Meanwhile the decisions that carry the most risk, what the product is for, what it asks of a person and what it decides on their behalf, are usually made in a meeting and never written anywhere that a later finding could reach.

The failure is not rigor. It is sequence. Evidence collected before the decision is named tends to confirm whatever was already planned, because nobody agreed in advance what result would have changed their mind.

What our evidence-driven design consulting includes

1. A decision inventory

We write down the design decisions actually in play, separate the reversible ones from the ones that are expensive to undo, and establish which are already settled by strategy and which are genuinely open. Most lists come back shorter than the team expected, with two or three decisions carrying nearly all the risk. Those are the only ones worth spending evidence on.

2. Evidence that could change the answer

For each open decision, what observation would settle it, and what it costs to get. Sometimes that is a prototype in front of people who could actually buy. Sometimes it is a query against data you already hold. Sometimes the honest answer is that no affordable evidence will settle it, in which case we say so and the decision gets made on judgment, explicitly, by someone accountable for it.

3. The loop the product learns on

A design decision should leave something behind that makes the next one easier. In practice the loop breaks in the same place in most organizations.

  1. DecideWhat we are claimingThe design decision stated plainly, with the result that would contradict itUsually unwritten
  2. InstrumentWhat we will watchThe specific behavior that distinguishes the claim being right from it being wrongUsually partial
  3. ObserveWhat happenedBehavioral data, session work and interviews, gathered after releaseUsually strong
  4. JudgeWhether we were wrongA verdict on the original claim, owned by the person who made itUsually absent
Without the verdict, the next decision starts from the same assumptions as the last one
Most of the budget buys the Observe box. The claim was never written down, so nothing the data says can contradict it, and the organization accumulates evidence without ever changing its mind.

4. Judgment on the work itself

We review design work as it comes back, against the decisions and the evidence rather than against taste, and we stay through the first release. That last part matters, because decisions get quietly renegotiated during implementation and the evidence that justified them is rarely in the room.

Not sure which of your design decisions are actually open?

Start with a working session on one funded design decision. We will write down what is being claimed, and what result would prove it wrong.

Book a design decision session

How an evidence-driven design engagement works

  1. Frame. Interviews with the people who own the product, the people who fund it and the people who support it. A walk through the current experience with the analytics and support data alongside. The output is the decision inventory and a note on which decisions are already closed.
  2. Rank. The open decisions sorted by consequence and reversibility, not by how interesting they are. We agree which two or three are worth evidence and what the evidence budget is.
  3. Settle. Get the observation that resolves each one. Existing data where it answers the question, a prototype or a structured field session where it does not. Each one is agreed in advance as a test of a stated claim.
  4. Hand over. The decisions, the evidence behind each, the verdict rule for the ones still running, and the loop your team keeps using once we leave. Then review the work against it through the first release.

Why companies choose Vivaldi for design decisions

We are a strategy firm sitting in design conversations, which makes us unusually willing to say that a decision is commercial rather than experiential and belongs to someone else in the building. We will not sell you a research program to postpone a judgment call, and we will tell you when the evidence you want is not worth its price.

We also do not produce the design work, which removes the obvious conflict: we have nothing to gain from recommending a larger redesign, because someone else would be doing it.

How to evaluate an evidence-driven design consultant

  • Ask them to state the decision before the method. A firm that opens with a research plan rather than a question is selling a process.
  • Ask what result would make them wrong. If no answer exists in advance, the study will confirm whatever you already intended.
  • Ask what they would not test. Honest practice names the decisions that have to be made on judgment because no affordable evidence reaches them.
  • Ask who owns the loop afterwards. If the measurement only works while the consultancy is engaged, you rented a verdict rather than building a capability.
  • Ask what they would cut. A firm that cannot name research you are already paying for and should stop has not read your situation.

Evidence-driven design consultancy vs user research agency vs product analytics vendor?

Kriterium Evidence-driven design consultancy User research agency Product analytics vendor
Was es beschließt Which design decisions are open, what evidence settles each, and what the verdict was What to study, how to study it, and what people said or did What is happening inside the product you already shipped
Typische Ausgabe A ranked decision inventory, an evidence plan with stated verdict rules, and a judgment on the work A findings report, personas, usability sessions, a research repository Dashboards, funnels, experiment infrastructure
Ausgangspunkt The decision in dispute The research question in the brief The data the product emits
Toter Winkel No production capacity and no research field team, so others do the gathering and the drawing Will answer the brief precisely even when the brief misses the decision Cannot see the option you never built

Verwandte Arbeiten

This work sits inside our Digital Products and Platforms practice at Vivaldi, the strategy firm behind the Demand Landscape and the Interaction Field.

Evidence-driven design consulting in the US and worldwide

Our product and experience strategy work runs out of ten offices on four continents, with the US team in New York. Most engagements of this kind run remotely, with two or three days on site at the points where decisions are actually made. Where a product launches in several markets, we keep one decision inventory and gather the evidence per market, because the behavior that settles a question in one country frequently does not settle it in another, and a verdict quietly imported from the US is the most common way a global rollout goes wrong.

Start with the decision, not the research plan

One working session on a funded design decision: what is being claimed, what evidence would settle it, and what it is worth paying to find out. You leave with the decision written down and a verdict rule attached to it.

Book a design decision session

Häufig gestellte Fragen

What is evidence-driven design consulting?

Advisory work that names the design decisions actually in play, establishes what evidence would settle each one, and judges the resulting work against that evidence. It starts with the decision rather than with a research method, because evidence gathered before the decision is written down tends to confirm whatever was already planned.

How is this different from user research?

User research gathers the evidence. This work decides which decisions deserve evidence at all, what result would count as settling each one, and who owns the verdict afterwards. The two fit together: if the gap in your organization is fieldwork capacity rather than decision discipline, our user insights and research page is the better fit.

Do you run the research yourselves?

We design what needs to be observed and we will run focused sessions where that is the fastest route, but we are a strategy firm rather than a field research operation or a design studio. Large qualitative programs and production design work are done by your team or by specialists, with us setting the question and judging the answer.

What if no evidence can settle a decision?

Then we say so, and the decision gets made on judgment by a named person rather than postponed behind a study. A research program commissioned to avoid a judgment call is the most expensive form of indecision we see.

How do you decide which decisions get evidence?

By consequence and reversibility. A decision that is cheap to reverse should usually be made quickly and corrected later. A decision that commits the architecture, the business model or the brand is worth paying to get right, and in most products there are only two or three of those open at any one time.

Is this the same as A/B testing?

No. A/B testing compares variants of something you already built, which makes it strong on refinement and blind to the option nobody designed. It is one instrument among several, and it answers a narrower question than most roadmap decisions require.

We already have good analytics. What would change?

Usually the claim, not the dashboard. Analytics describe what happened inside the current design. The missing piece is a written statement of what the team believes and what observation would contradict it, so that the data has something to disagree with.

How is this different from your interaction design work?

Interaction design settles how the product behaves when a person acts on it: the states, defaults, feedback and automated behavior. That work lives on our interaction design (IxD) page. This page is about how any of those decisions get settled with evidence.

What if our question spans several companies rather than one product?

Then it is an ecosystem question, not a design evidence question. Participant models, value exchange and governance across a multi-company system are covered on our digital ecosystem design page.