Skip to main content

Tavism
All enterprise casesInternal Experimentation

Validating Event Album Customer Demand

Kodak Gallery — Validating Feature Demand

Surveys say customers want the feature. Payment behavior decides whether engineering should build it.

Case overview

The challenge

VP Mark Cook needed to judge customer demand for new photo-sharing features at Kodak Gallery. The easy path was to fund backend work for specialized event albums on survey enthusiasm alone. That would burn enterprise engineering cycles on features nobody might pay for.

The experiment

Test intent before backend cycles

Before committing engineering to specialized event photo albums, the team tested customer intent. The goal was a clear signal—would people pay?—not a polished product that locked budget into unproven demand.

Finding the truth

Surveys vs. payment behavior

Stated survey preferences said customers wanted event albums. Actual payment behavior told a different story. That gap is the validated learning: what people say they want is not what they buy.

Outcome

Kill early, save millions

Killing the unvalidated features early saved millions in enterprise engineering costs. The roadmap got smaller—and more honest—because demand was measured with money, not opinion.

Survey yesPay no

Stated preference vs. real payment intent

For executives

Key takeaways for executives

How to validate feature demand before the backend spend.

  1. Treat survey enthusiasm as a hypothesis—not a build order.
  2. Test payment intent for the feature before committing backend cycles.
  3. Trust the gap between what customers say and what they pay.
  4. Killing unvalidated roadmap items early is a win, not a failure.

Ready to validate before the roadmap spend?

Book 30 minutes. Bring the feature list stuck on survey opinion and the budget you would rather not burn.

Validate Enterprise Feature Roadmaps