Turn each research round into a starting point
An interview round may end with notes, a report and recommendations. They belong to a particular product question and customer context. When the product changes, the findings may still apply or leave new questions unanswered.
Before closing an interview round, record what the customers actually described, which roles and business situations the evidence covers, and what the team concluded. Note the product version and the decisions the research was intended to support.
Keep open questions separate. Some can be explored without recruiting another participant immediately. Others require firsthand experience before the next commitment.
Build a research rhythm between studies
Use a continuity plan to connect completed fieldwork, ongoing exploration and the next customer study. It should support decisions, not create research activity for its own sake.
| When the question appears | Explore with Virtual Customer | Next customer evidence to consider |
|---|---|---|
| After an interview round: An explanation remains uncertain. | Return to the relevant virtual roles and explore alternative reasons the problem might occur. | Follow up on contradictory accounts or missing experiences when they could change the decision. |
| After a product change: The workflow or service concept now works differently. | Revisit the same virtual customers with the revised proposal and ask what responsibilities or constraints might change. | Test the changed workflow with customers who use or manage it. |
| When a new stakeholder emerges: Another role may influence adoption. | Add a virtual stakeholder in the same business context and investigate its possible concerns and dependencies. | Recruit someone with direct responsibility if that perspective becomes important to the decision. |
| Before a pilot or release: Important uncertainties remain. | Compare the outstanding hypotheses and identify what the next round should investigate. | Use relevant customer interviews, observation or a pilot to examine the consequential assumptions. |
Keep each question’s source, status, next decision and owner in the research notes. Separate simulated possibilities from customer reports and observations.
Return to a business world, not a generic persona
Virtual Customer is designed specifically for B2B discovery. Define the business you need to understand through its industry, region and company size. The platform builds a business world model of the operating environment, market and organizational context. Within that world, virtual customer roles have different responsibilities, goals and knowledge.
An operations manager might focus on service delivery, a CTO on integration and a CFO on ongoing cost. These are perspectives to investigate, not universal claims about job titles.
Talk by text or voice and return when your offering changes. Add roles or explore another customer context without recruiting a new participant for every exploratory question.
Plan customer contact around what changed
Continuous customer research does not require an interview every time a team edits a feature. It requires a clear way to recognize when earlier evidence is no longer enough.
Plan another customer study when workflows change, a stakeholder is missing, evidence conflicts or a decision becomes costly to reverse. New regions, industries or company sizes may also require fresh customer evidence.
Use simulated dialogue to challenge the current explanation and prepare the next questions. Use customers to establish their reported experience, and observation, product data or pilots when the decision depends on behavior. The two sources of input should remain clearly labeled in your research record.
Example: the service workflow changes between interview rounds
Consider a company improving scheduling software for medium-sized B2B service organizations in Northern Europe. Its last interview round covered how operations teams coordinate field visits. Before the next round, the product team proposes automatic reassignment when a service job is delayed.
It returns to a virtual operations manager in the same modeled business context and explores possible questions about ownership and exceptions. It also explores CTO and CFO perspectives on implementation and operating costs. The team records alternative hypotheses rather than treating the simulated responses as findings.
Customer interviews can investigate recent scheduling disruptions and who made the decisions. A pilot can examine whether the new workflow works as intended. The team can return to the model as the design changes again.
Start with the gap between your last study and your next decision
Choose one completed customer study and one product change since it finished. Identify the roles, company context and evidence the study covered. Revisit a matching virtual customer in Virtual Customer with the changed proposal, then compare a second role if its responsibility matters.
Write down one possible alternative explanation and one question that needs customer evidence. Use that distinction to decide what to investigate now and what belongs in your next interview round or pilot.
To keep these inputs separate, see how to build a customer evidence map.