Pre-Code Operator Validation
Interview practitioners before building to expose barriers, workflows, and repeatability gaps.
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 5
- Confidence
- 96%
This validation method delays code until the team understands how practitioners experience the problem. Begin with a focused strategic question, then interview operators across the roles that touch the workflow. Examine what they currently do, where they get stuck, why they hesitate to allocate resources, and how they judge success. Yuliya Bel's research surfaced two different barriers: teams either did not know how an activity affected the bottom line or lacked a roadmap for starting and repeating success. That distinction matters because measurement software and workflow guidance solve different problems. Patterns across a large and varied interview set become evidence for the product's required capabilities. Only then should the team commit to implementation.
Origin
Before writing code for Notice, Yuliya Bel and her team interviewed 300 people working across community, growth, marketing, and content to understand why companies struggled with organic growth.
Core principles
- 01Validate the problem before committing engineering resources.
- 02Practitioners reveal both operational pain and reasons for inaction.
- 03A repeatable solution must address roadmap and measurement gaps.
- 04Diverse roles reduce the risk of mistaking one workflow for the whole market.
How to run it
- 1
Frame the Unknown
State the decision the research must inform and the assumptions that could make the product unnecessary.
Pro tip Include at least one question that could invalidate the idea.
Watch out Do not frame interviews solely to confirm an existing solution.
- 2
Recruit Across the Workflow
Interview people from each function that owns, performs, measures, or depends on the activity.
Pro tip Include both highly successful teams and teams that abandoned the effort.
Watch out One job title may expose only one part of the problem.
- 3
Study Current Behavior
Ask participants to describe recent actions, tools, constraints, and outcomes rather than speculate about future purchases.
Pro tip Request concrete examples of the last time they attempted the task.
Watch out Positive opinions about an idea are weaker evidence than existing behavior.
- 4
Classify the Barriers
Separate missing know-how, unclear attribution, absent roadmaps, resource constraints, and repeatability failures.
Pro tip Count how often each barrier appears across roles.
Watch out Do not merge distinct barriers simply because they affect the same activity.
- 5
Define the Minimum System
Translate recurring barriers into the smallest set of capabilities needed to guide action and demonstrate value.
Pro tip Trace every proposed feature back to repeated interview evidence.
Watch out Avoid coding speculative features that no recurring workflow requires.
In the wild
A founder interviews community leaders, growth marketers, content teams, and finance partners. The interviews show that community leaders know how to engage members but cannot connect activity to business outcomes, while growth teams lack a map of relevant external communities.
→ The product scope separates attribution from landscape discovery instead of presenting one vague community dashboard.
Common mistakes
Interviewing Only Enthusiasts
Category advocates may overstate demand and overlook the barriers that prevent mainstream teams from adopting the workflow.
Counting Interest as Validation
A participant saying an idea sounds useful does not establish a recurring problem, budget, or behavior change.
Is it for you?
Best for
Founders evaluating a new category, workflow, or product before substantial engineering investment.
Not ideal for
Minor implementation choices that can be tested more cheaply with a small prototype.
From the transcript
“even before we like wrote a single line of code, we talked to 300 operators and communities and growth and marketers and contents, like you…”
“Or two, what is that roadmap? Like, how do we get started?”
From the episode
Becoming a Community-Driven Company with Yuliya Bel
Yuliya Bel