TapCub is live — analytics, insights and live chat, free on one platform
Glossary

What Is Validation? Meaning, Validation vs Verification and a Worked Example

Validation confirms with evidence that something meets its intended use. How it differs from verification, the three kinds, and a pre-set three-check rule for deciding whether a new feature passed, with a worked 14-day example.

Emma Collins Reviewed by Lucas Hayes Also called product validation Last updated Nov 18, 2026 Glossary

Quick answer

Validation is confirming, with evidence, that something meets its intended use. Verification asks whether it was built to spec; validation asks whether it meets a real need. For a feature, validation needs behavior: how many people tried it, used it again, and came back more than before.

What is validation?

Validation is the act of confirming, with evidence, that something does what it is meant to do for its intended use. The word covers several fields (data, software, medicine, research), but they share one test: not "was it built to the plan?" but "does it work for the purpose it exists for?"

In product work the purpose is a person's need, so the evidence has to come from people: what they chose, used and came back to. A feature that the team believes is useful has not been validated. A feature that 30% of active users tried, and 40% of those used again, has started to be. This page defines validation, separates it from verification, lists the three kinds you meet, and gives a rule for deciding from data whether a new feature passed.

Validation vs verification

The two terms are often swapped, but they answer different questions. Barry Boehm's 1981 phrasing, widely quoted, is that verification asks whether you are building the product right and validation asks whether you are building the right product.

VerificationValidation
QuestionDid we build it to the specification?Does it meet the real need for its intended use?
Checked againstThe requirements and design documentsThe user's or customer's needs
Who judgesUsually the team: tests, reviews, inspectionsPeople who use it, or evidence of their behavior
Typical evidencePassing tests, a review sign-offAdoption, repeat use, retention, acceptance
ExampleThe export button produces a correct CSV in under 5 secondsAfter 14 days, people export reports and come back to do it again
Can pass while the other fails?Yes: a perfect build of the wrong thingYes: the right idea, built with bugs

Wikipedia, summarising ISO 9001:2015 and the PMBOK Guide as adopted by IEEE, describes verification as conformity with requirements and validation as assurance that the product meets the needs of the customer and other stakeholders. A product can pass verification and still fail validation if the specification never matched a real need.

The three kinds of validation

KindQuestionEvidenceWhenExample
Need validationIs the problem real, and do people want this solution?Interviews, sign-ups, a painted door testBefore buildingVisitors click a "Coming soon" button for a feature that does not exist yet
Product validationDoes the built thing get used and re-used?Adoption, repeat use, retentionAfter launchOf 1,200 active users, 30% try the new feature
Data validationDoes this data follow the rules?Format, range and consistency checksWhenever data is entered or movedAn email field rejects text without an @ sign

Need validation tests a product hypothesis cheaply before a minimum viable product exists; the full process is in product validation. Data validation is a different meaning of the same word and has its own entry: data validation. One point worth knowing: MDN's guide to form validation notes that client-side checks in the browser are a convenience for users, not a security measure, and that applications must validate again on the server because client-side checks are easy to bypass.

This page concentrates on product validation, because that is where behavior data decides the answer.

A rule for deciding whether a new feature passed

The common failure is to launch, watch the numbers move and decide afterwards that they look good. Use a rule that is fixed before launch, made of three checks over the same window (14 days is a common choice for features meant for weekly use):

  1. Adoption. Users who used the feature at least once ÷ active users who had access to it. Target example: at least 25%.
  2. Repeat use. Of the people who tried it, the share who used it again on a different day in the window. Target example: at least 35%. One trial shows curiosity; a second use shows the feature earned a place.
  3. Return against the users' own baseline. The share of feature users who came back in the following 14 days, compared with the same people's return rate in the 14 days before launch, not with the people who skipped the feature.

The third check exists because people who try new features are usually the more engaged. Comparing them with non-users measures who they are, not what the feature did. All three must pass; the numbers in each target are your call, and the point is that you set them before you look.

Worked example: did "Saved reports" pass?

Sample data: a product ships a "Saved reports" feature. In the first 14 days, 1,200 active users had access. Targets set before launch: adoption at least 25%; repeat use at least 35%; return no lower than the users' own pre-launch rate.

MeasureCalculationResultTargetVerdict
Adoption360 ÷ 1,20030.0%≥ 25%Pass
Repeat use144 ÷ 36040.0%≥ 35%Pass, see below
Return after launch, feature users234 ÷ 36065.0%
Return before launch, same 360 users198 ÷ 36055.0%
Change for feature users65.0% − 55.0%+10.0 pts≥ 0Pass

The tempting comparison is feature users against everyone who skipped it: 65.0% against 294 ÷ 840 = 35.0%, a 30-point gap. Most of that gap is who chooses to try things. Their own before-and-after, +10.0 points, is the fairer number, and it is still not proof of cause because something else may have changed in those weeks. For the 840 non-users the rate moved from 300 ÷ 840 = 35.7% to 35.0%, down 0.7 points, so the product as a whole moved from 498 ÷ 1,200 = 41.5% to 528 ÷ 1,200 = 44.0%, an increase of 2.5 points.

Then check the noise. A 95% interval for the repeat-use rate is 40.0% ± 1.96 × √(0.40 × 0.60 ÷ 360) = 40.0% ± 5.1 points, about 34.9% to 45.1%. The point estimate clears the 35% target but the lower end falls just under it, so call this a provisional pass and recheck at 28 days. Adoption, 30.0% ± 2.6 points, clears 25% comfortably.

Common mistakes with validation

  • Treating launch as validation. Shipping shows the team finished. Validation needs evidence that people use it.
  • Treating verification as validation. "All tests pass" says the feature matches its spec. It says nothing about whether anyone wants it.
  • Trusting what people say they would do. Interview answers and survey intent are a start, but behavior is the evidence: a click on a painted door beats "yes, I'd use that".
  • Setting targets after seeing results. A target chosen to fit the data cannot fail.
  • Comparing users with non-users. The people who try features are the ones already engaged; compare people with their own earlier behavior.
  • Calling a total a result. "10,000 clicks" is a count. Divide by who could have clicked.
  • Mixing the meanings. A project can pass data validation (the events arrive correctly) and fail product validation (nobody uses the feature).

How to run this check in TapCub

Here is the "Saved reports" example worked through in TapCub. TapCub measures the behavior; it does not run A/B tests or send surveys.

  1. Send an event for the feature. Send a report_saved event with custom events, and list it in All-platform analytics › Data › Tracking plan with a status. Turn on Live verification (24 h) to see that the event arrives and that required properties are filled, which is data validation for the event itself.
  2. Read adoption. In All-platform analytics › Behavior › Behavior analysis, use the event analysis tabs for report_saved. The unique-users aggregation gives the people who used it, and the active-percent aggregation gives the share of active users.
  3. Count repeat use. In All-platform analytics › Users › Segments & tags, create a rule segment of people who did report_saved at least twice in the last 14 days, and compare its member count with those who did it at least once. Segments need identified users, so call tapcub.login to recognise people; anonymous visitors have no profile.
  4. Compare people with themselves. In the retention view, set report_saved as the start event and any activity as the return event, then run the same users' pre-launch window as a separate date range. Retention has no compare-period switch, so run the two ranges one after the other and note the launch date in Configuration › Annotations.
  5. Write the verdict next to the target. Record the three results against the targets you wrote before launch. For the full process, see measure product adoption.

Sources

Was this explanation clear?

We use your answers to fix and expand this page.

Emma Collins

Product Analyst

Focuses on event analysis, conversion funnels, and retention, using clear metric definitions and structured analysis to explain product performance.

FAQ

Questions people ask

Short answers to the follow-up questions that come up most.

Still have a question?

Chat with the team behind TapCub — we usually reply within a few hours on business days.

What is validation in simple terms?

Validation means checking, with evidence, that something does what it is meant to do for the people who use it. A feature is validated when real behavior, such as people using it again, shows it meets a need. A team believing it is useful, or the tests passing, does not count.

What is the difference between validation and verification?

Verification checks that something was built to its specification: are we building the product right? Validation checks that it meets the real need: are we building the right product? A product can pass verification and still fail validation if the specification never matched what people wanted.

What are examples of validation?

A painted door test where visitors click a button for a feature that does not exist yet; a new feature where 30% of active users try it and 40% of them use it again within 14 days; a web form that rejects an email without an @ sign. The first two validate a need or a product, the third validates data.

How do you validate a new product feature?

Set targets before launch for adoption, repeat use and return rate, then measure them over a fixed window such as 14 days. Compare feature users with their own earlier behavior rather than with non-users, who are less engaged to begin with, and treat a result near a target as provisional.

See this number on your own site

Add one script tag for web and apps, and the first reports fill in within minutes.

See your data clearly. Find your growth.

Every click, backed by data. Install one line of code and see your first numbers in a minute.

No credit card · Free plans for analytics and chat · Cookieless analytics