WHAT THE TEAM BRINGS
Raw survey responses, question definitions, confirmed product information, launch communication needs and the bundle assumptions used at the time. Add the final launch offer for the review.
Iris—
An imaging device that could switch between modes of use was approaching launch. The brand team had collected survey responses, but still needed to decide which audience to address first, how to explain the product and how to discuss product bundles. Iris organized use cases, purchase intent and concerns from the raw responses, then delivered a research report, content directions and commercial recommendations. After launch, Iris compared the actual offer with the research and turned its unanswered questions into topics for the next survey.

WHY THIS WORK MATTERS
Give the team the findings, assumptions behind the judgments and the researcher’s corrections together. Content teams know which situations to explain, product teams know which bundles to test, and the next study can continue from the questions already uncovered.
WHAT THE TEAM BRINGS
Raw survey responses, question definitions, confirmed product information, launch communication needs and the bundle assumptions used at the time. Add the final launch offer for the review.
WHAT THE WORK LEAVES BEHIND
HOW TO ASSESS A PILOT
Start with a collected survey that has not yet informed a decision. Choose one important purchase question, deliver a table of findings, judgments, content actions and items to validate, and have the team that will use it review it in practice.
See the actual processTHE METHOD IN A WORKING EXAMPLE
Iris separates interest, use contexts, purchase intent and concerns, then brings the findings into content and business discussions. The post-launch review asks what the original questions missed.
A working board connecting user research to action. It contains no real survey, prices or preference distributions.
Survey analysis first produces content tasks and conditional bundle recommendations. After launch, the actual offer reveals purchase paths omitted from the original questions, informing the next round of research.
Iris analyzes an existing survey and translates findings into messaging priorities and research recommendations. After launch, the actual offer is used to revisit assumptions and formulate more precise questions.
01 / THE ASSIGNMENT
For brand and product marketing teams that have collected user feedback and are preparing a product launch. The survey contains feature rankings and attitudes toward purchase, but the team still needs to know how those findings should change the page, content and product bundles.
A new format attracts attention, but a purchase still depends on where someone would use it, whether an existing device could do the job and whether they need the full set of features.
The sample was more familiar with the brand and category, and skewed toward particular groups. Ignoring that composition could turn existing customers’ reasons to upgrade into assumed reasons for new customers to buy.
Treating the complete kit as the only purchase option misses the route of buying the core capability first and adding extensions later. A single price range cannot answer the bundle question.
02 / THE CONTINUOUS WORK
Expand each stage to see its inputs, decisions, actions, outputs and handoff. Each step explains how the next person could continue.
A checklist linking each question to its definitions and sample composition.
A four-layer view of purchase decisions and a summary of audience opportunities.
Research report, content directions and creative recommendations.
Commercial recommendations with explicit premises and items to confirm.
Post-launch comparison and questions for the next study.
03 / THE DECISIONS
When a draft, a source or the actual behavior differed from expectations, how did the Agent locate the problem and choose the next step?
A user’s interest is where research begins. Understanding why they have not bought yet brings it closer to the business decision.
04 / WHAT CHANGED
Compare the starting situation, the Agent’s actions and the resulting change. Read these alongside the working examples to see what was actually delivered.
Put the most popular feature at the top of the page and assume it is the strongest reason to buy.
Analyze use cases, purchase attitudes and hesitation together.
Explain value through situations and address concerns through content. Each finding has an explicit downstream task.
The study largely formed price expectations around the complete kit.
Compare the launch bundles and separate the core capability from extensions.
The next study can compare buying the core product first, choosing a bundle and upgrading later.
Treat sending the report as the end of the research.
Use the public launch offer to examine the assumptions and reasoning used at the time.
Retain useful directions and turn weaknesses in question design into checks for the next study.
05 / FEEDBACK INTO THE WORK
Feedback was no longer presented as a rule for the whole category. The report retained audience scope and question definitions.
Abstract selling points needed to become actions that could be filmed and situations people could understand.
The original pricing recommendation should not be reused on its own. It needs to be considered alongside the final product bundles.
06 / THE DELIVERY
The brand team designed and collected the survey. Iris handled cleaning, analysis, recommendations, report delivery and the subsequent review. Similar wording on public pages is not treated as proof that the recommendations were adopted, and public crowdfunding performance is not attributed to this report.
Question definitions, sample composition, preferences, intent and hesitation organized by question.
User tasks, communication opportunities and research limitations brought together in one report.
Survey findings extended into page messaging, content topics and video scenarios.
Pricing and bundle recommendations state their assumptions, with unresolved items shown separately.
Comparison with the final offer separates alignment in direction from unproven attribution.
Bundle choice, interest in extensions and alternatives become part of the next round of questions.
BUSINESS CONTEXT
Design and collect the survey, provide product facts, and decide the product bundles and final launch offer.
AGENT CONTRIBUTION
Cleans and analyzes the data, organizes the report and content recommendations, then reviews the reasoning after launch.
TEAM COLLABORATION
Produce pages and content and execute the launch using the final offer.
Explore interactive methods and supporting handoff detail. The business process and deliverables are presented above.
+EXPLORE THE METHOD
Iris separates interest, use contexts, purchase intent and concerns, then brings the findings into content and business discussions. The post-launch review asks what the original questions missed.
A review-method board, not a statistical chart from the original survey.
Feature interest informs the messaging entry point; use contexts inform content tasks; intent and concerns inform validation and business discussions.
Keep the denominators and meanings of different questions separate. Attention cannot be treated directly as sales.
An example question structure for the next research round, not a validated pricing plan.
Replace one question about the whole package with three purchase paths: the core product, an extension and the complete bundle.
The improvement is in the questions: people willing to buy the core product may not need every extension.
07 / THE REUSABLE WORK
Brand and product marketing teams launching a product and looking to turn user feedback into positioning, bundles and content tasks.
A PRACTICAL START
Begin with a collected survey that has not yet been translated into decisions. Build a table of findings, judgments and next actions, then decide what further research is needed.
Explore AIelsen Agent and FDE services ↗Apply this case’s methods to your own work
Download the workbook ↓Editable Markdown · No original client material