{
  "title": "Six examples of unexpected customers and needs",
  "summary": "Six documented cases show how actual use, complaints and workarounds can reveal an overlooked audience or need.",
  "researched_on": "2026-09-13",
  "assistant_guidance": "Read the findings as supporting evidence and proposed methods. Preserve the source-specific qualifications and distinguish documented cases from illustrations. Start a fresh research round only when the user asks.",
  "research_prompt": "Find additional documented cases in which actual use, support requests, complaints, workarounds, or purchasing patterns revealed an overlooked audience or need. Start from several different industries and mechanisms. Where separate agents are available, give them bounded discovery areas before sharing findings; otherwise disclose that sequential passes share context. Prefer original participant accounts, company announcements, original research, or contemporaneous records. Open every source used.\n\nFor each candidate, establish the original offer, observed behavior, people involved, dates, company response, and what the record cannot establish. Distinguish evidence of unexpected use from evidence that the company noticed it, and from evidence that it caused a change. Do not convert a launch announcement into proof of commercial success. State whether a requested feature indicates a distinct audience or simply a need shared by existing customers. Produce a short, lively example, original links, one or two diagnostic questions applicable to the reader's records, and precise limits. Seek cases that add a mechanism missing from the existing bank. Have a separate verifier check the selected claims where available and report the actual methodology.",
  "examples": [],
  "sources": [
    {
      "id": "source-1",
      "title": "The Buy Guide, “The Story of The Cup”",
      "url": "https://thebuyguide.com/home/the-story-of-the-cup/"
    },
    {
      "id": "source-2",
      "title": "Discord, “Your Place to Talk”",
      "url": "https://discord.com/blog/your-place-to-talk"
    },
    {
      "id": "source-3",
      "title": "IKEA, DELAKTIG announcement",
      "url": "https://www.ikea.com/global/en/newsroom/corporate/ikea-delaktig-sofa-platform-receives-red-dot-award-2018-for-product-design-180328/"
    },
    {
      "id": "source-4",
      "title": "IKEA Poland, “Kolekcja DELAKTIG. Zainspirowana Twoim stylem życia.”",
      "url": "https://www.ikea.com/pl/pl/newsroom/range-news/kolekcja-delaktig-zainspirowana-twoim-stylem-zycia-pub66eaf9a7/"
    },
    {
      "id": "source-5",
      "title": "Microsoft, MIX11 announcement",
      "url": "https://news.microsoft.com/source/2011/04/13/windows-phone-kinect-exemplify-new-usage-scenarios-and-device-capabilities-at-mix11/"
    },
    {
      "id": "source-6",
      "title": "Microsoft, SDK beta release",
      "url": "https://news.microsoft.com/source/2011/06/16/microsoft-releases-kinect-for-windows-sdk-beta-for-academics-and-enthusiasts/"
    },
    {
      "id": "source-7",
      "title": "Notion, “Everything we announced at Block by Block 2022”",
      "url": "https://www.notion.com/blog/block-by-block-recap-2022"
    },
    {
      "id": "source-8",
      "title": "GitHub, “How the GitHub legal team used Copilot CLI to streamline their workflows”",
      "url": "https://github.blog/ai-and-ml/github-copilot/how-the-github-legal-team-used-copilot-cli-to-streamline-their-workflows/"
    }
  ],
  "methodology": [
    {
      "title": "Orientation",
      "text": "Research for move 042. Checked September 13, 2026. Supporting research only; this file does not amend the activity or establish approved wording.\n\nThese six cases offer different things to notice in customer records: a purchase occasion the company overlooked, people struggling with a product's identity, owners modifying a finished object, developers wanting access to a consumer device, customers requesting integrations, and people without engineering roles adopting a developer tool. Their evidence differs. Some sources explicitly connect feedback or observed behavior to a company response; others document use without establishing how the company discovered it.\n\nThe diagnostic questions below are our applications of the cases. They are not questions the companies are documented to have asked. None of these examples demonstrates that an AI analysis of complaints discovered the opportunity."
    },
    {
      "title": "• Stanley Quencher: the camping item was already an everyday cup",
      "text": "Documented episode. The Buy Guide founders describe using the 40-ounce Quencher at work, during carpool, for exercise, and beside their beds. They say it was merchandised with camping products, that their followers bought available stock rapidly, and that discontinuation led them to press Stanley for more. They bought 5,000 cups themselves and report selling them in five days. Their account identifies women as an audience Stanley had not considered, dates a meeting with Stanley leadership to 2019, and describes launches in June and November 2020. The Buy Guide, “The Story of The Cup” (https://thebuyguide.com/home/the-story-of-the-cup/).\n\nWhat to notice. A product's existing capabilities can fit a different daily routine before the company's merchandising recognizes it. Here, advocates brought behavioral evidence and purchase commitments.\n\nCompany-specific question. Which reviews describe where a product lives or what part of the day it accompanies—and does that setting appear in the product page, retail placement, or customer segmentation? Who is asking for a discontinued or hard-to-find product, and what do they use it for?\n\nEvidence boundary. This is the commercial partners' firsthand retrospective, not an independent audit of sales or internal resistance. The page inspected has no visible original publication date; the event dates above come from its narrative. “Construction workers to housewives” is not established here. Use “camping merchandise to women's everyday routines,” attributed to The Buy Guide."
    },
    {
      "title": "• Discord: users said the gaming identity was keeping their friends away",
      "text": "Documented episode. In a June 30, 2020 post, founders Jason Citron and Stan Vishnevskiy said a year of asking users about Discord revealed uses extending beyond games, including books, music, art, and everyday conversation. They said the gaming-focused branding made it harder for users to bring broader communities onto the service. Their announced response included simpler onboarding, server templates, fewer gaming-specific references, and the tagline “Your place to talk.” Discord, “Your Place to Talk” (https://discord.com/blog/your-place-to-talk).\n\nWhat to notice. Customers may already value the product while finding its public identity difficult to explain to someone else. The barrier can be who the product appears to welcome.\n\nCompany-specific question. In referral, onboarding, and sales records, where do users explain that the product is useful for a group our branding never names? What objections do invited colleagues or friends express before they have used it?\n\nEvidence boundary. The founders explicitly link reported feedback, broader usage, and the response. The post does not provide a sample, transcript corpus, or causal measurement of the changes. This is a dated 2020 episode, not a claim about Discord's current positioning or proof that broader positioning remained its strategy."
    },
    {
      "title": "• IKEA DELAKTIG: people wanted to keep designing after purchase",
      "text": "Documented episode. IKEA's March 28, 2018 announcement describes DELAKTIG, developed with Tom Dixon, as a customizable sofa platform. It says the development explored how people customized IKEA products and the demand to personalize and adapt furniture. IKEA, DELAKTIG announcement (https://www.ikea.com/global/en/newsroom/corporate/ikea-delaktig-sofa-platform-receives-red-dot-award-2018-for-product-design-180328/). A Polish IKEA release dated January 23, 2018, updated November 22, 2021, records Dixon saying he became aware of the community modifying IKEA furniture around the start of the collaboration and wanted to explore it; it also describes involving 75 design students. IKEA Poland, “Kolekcja DELAKTIG. Zainspirowana Twoim stylem życia.” (https://www.ikea.com/pl/pl/newsroom/range-news/kolekcja-delaktig-zainspirowana-twoim-stylem-zycia-pub66eaf9a7/).\n\nWhat to notice. Modifications reveal customers who want the supplier's product to be a starting point. A fixed offering may be competing with the owner's wish to change its appearance or function.\n\nCompany-specific question. What do customers repeatedly cut, attach, recolor, rearrange, or buy from third parties? Does the pattern suggest a missing standard variant, or a desire to keep changing the product themselves?\n\nEvidence boundary. These are manufacturer accounts of design intent and influences. They establish attention to existing customization, not the representativeness of the observed hackers, a complaint-analysis process, or a commercial success. The Polish passage above is paraphrased in English from the original."
    },
    {
      "title": "• Microsoft Kinect: a consumer game device attracted people wanting a building block",
      "text": "Documented episode. Microsoft's April 13, 2011 MIX announcement says Kinect launched in November 2010 and enthusiasts were already exploring unexpected nongaming uses. It announced forthcoming Windows access to capabilities including skeletal tracking, audio, and camera depth data. Microsoft, MIX11 announcement (https://news.microsoft.com/source/2011/04/13/windows-phone-kinect-exemplify-new-usage-scenarios-and-device-capabilities-at-mix11/). On June 16, 2011, Microsoft released a free Windows SDK beta for noncommercial applications, explicitly addressing developers, academic researchers, and enthusiasts. Microsoft, SDK beta release (https://news.microsoft.com/source/2011/06/16/microsoft-releases-kinect-for-windows-sdk-beta-for-academics-and-enthusiasts/).\n\nWhat to notice. A person can want the underlying capability while having little interest in the packaged consumer experience. Requests for access can indicate an audience that wants to build with the product.\n\nCompany-specific question. Who asks for raw measurements, programmable access, technical specifications, or a way to connect the product to another system? What are they trying to construct that our normal usage categories cannot describe?\n\nEvidence boundary. The chronology and company recognition of unexpected uses are explicit. These sources do not establish that one particular hack or complaint caused the SDK decision. A consumer-facing game device contains sophisticated technology; the relevant distinction is consumer use versus developer extensibility, not “nontechnical technology.” No present-day product availability is implied."
    },
    {
      "title": "• Notion: requests for an API exposed demand to connect and automate",
      "text": "Documented episode. On March 2, 2022, Notion said its API was among its most requested features and announced that it had left beta. It described a new integration gallery showcasing community-built integrations for workflow automation and information synchronization, alongside expanded API support and easier installation and authorization. Notion, “Everything we announced at Block by Block 2022” (https://www.notion.com/blog/block-by-block-recap-2022).\n\nWhat to notice. Requests that sound technical may express an operational need: stop copying information, keep systems synchronized, or make an existing workspace participate in a larger process.\n\nCompany-specific question. In requests for an API, imports, exports, or integrations, which job titles and workflows recur? Which customers want to write the integration, and which simply need someone else's integration to work?\n\nEvidence boundary. Demand for the API and community-developed integrations are documented. This does not establish that Notion was initially intended only for nontechnical people, that developers were an unexpected demographic, or that every requester could program. Treat this as a case of discovering an extensibility need, not a proven discovery of a new technical audience."
    },
    {
      "title": "• GitHub Copilot CLI: lawyers used a developer tool to encode their working methods",
      "text": "Documented episode. An August 4, 2026 firsthand post by GitHub's Bria Ford describes lawyers, program managers, and business professionals using Copilot CLI to build internal tools. Examples include a drafting style guide and legal workflows initially expressed through plain-language instructions, policies, and report templates. One workflow later became a desktop application requiring substantial code, while its workflow instructions remained editable in plain language. GitHub, “How the GitHub legal team used Copilot CLI to streamline their workflows” (https://github.blog/ai-and-ml/github-copilot/how-the-github-legal-team-used-copilot-cli-to-streamline-their-workflows/).\n\nWhat to notice. People outside the expected professional role may adopt a technical tool because they can describe the work it should perform. Their stumbling blocks and successful workarounds can reveal a different support or interface need.\n\nCompany-specific question. Which active users have job titles missing from our target-customer descriptions? Are they asking how to express business rules, organize source material, or check outputs while our help material assumes they want programming advice?\n\nEvidence boundary. This is observed internal use reported by the vendor, not an external customer cohort. It does not establish market size, a discovery from complaint data, or that the users caused a product change. Keep it as a concrete usage example with a weaker claim about audience discovery than Stanley or Discord."
    },
    {
      "title": "How this research was done",
      "text": "This discovery pass was performed by one research agent with the bounded brief and editorial guide, separate from the lead's additional discovery pass. Within this pass, searches shared context and were not independent experiments. The agent searched for company or participant sources across consumer drinkware, community software, developer tools, furniture customization, LEGO robotics, Notion integrations, Kinect, and Intuit. It then opened the pages cited above and used targeted searches within long pages to check relevant passages and dates. All eight cited source pages were opened successfully. No customer dataset or private company records were inspected.\n\nSearch-result snippets supplied leads; claims in the cases were retained from opened sources. LEGO Mindstorms was not selected because the initial results leaned on secondary histories rather than an inspected primary account of the discovery. Intuit results did not establish the desired origin story during the bounded pass. An Adafruit account of the Kinect bounty was found but its page returned a 403; the bounty narrative was therefore omitted. Manufacturer and partner sources are primary accounts with their own interests, not independent corroboration.\n\nThe case writer checked dates and claim boundaries against these sources. A separate verifier subsequently reopened all eight cited pages and checked all six cases; no material factual corrections were needed. The lead also independently inspected LEGO's official adult-fan and customization programs as a possible additional case, but did not add it because that page did not establish the discovery history and added less to this set. This is purposive example selection for breadth, not a systematic review, exhaustive search, or ranking of success stories."
    }
  ],
  "schema_version": 5,
  "id": "042",
  "shared_ai_guidance": "These are general instructions, not a description of this user's particular AI system, tools, access, or circumstances. Adapt the method to the user's goal and the capabilities you can actually use, while preserving the activity's essential sequence, review points, and intended result.\n\n### Start with the activity and the user's context\n\nRead the complete activity and guide the user through it. Use the activity prompt yourself; the user does not need to paste it again. Keep the responsibilities of the user, the AI, and any colleague clear.\n\nBegin with what the user has already supplied. Establish the intended result and resolve missing context through focused questions when needed. Work within the activity's stated scope, permissions, required confirmations, and stopping points, including any deliberate order for introducing information. Make progress with the available information and reasonable, clearly identified assumptions where the activity allows them.\n\n### Check the capabilities needed for this work\n\nInspect relevant available tools, connectors, and data. Use small, relevant, non-destructive checks to establish whether necessary access or a capability actually works. Naming a product does not establish access to it. Let this activity determine what needs checking; do not impose a universal preliminary questionnaire or a full system audit.\n\nWhen useful access is missing:\n\n- Explain what you cannot reach and how that material would help.\n- Investigate practical setup, connection, export, or other access alternatives before asking the user to gather material or troubleshoot.\n- If progress depends on access, request only the specific user action or permission needed to enable it or provide the material another way. Continue useful independent work while awaiting the response.\n- Offer to walk the user through an export or upload. Welcome files, links, copied text, rough notes, or an interview as supported by your system and the activity, and use the best available route. If the missing access is optional, continue with what is available.\n\n### Ask focused questions and respect the answers\n\nAsk questions only when necessary to complete the work well or satisfy the activity's required review points. Build on answers already supplied. Ask one question at a time, or a small group of closely related questions. Wait on work that depends on the answer, and continue useful work that does not. Explain unfamiliar language with examples where helpful.\n\nConfirm answers or decisions you supply on the user's behalf before treating them as the user's final answers or decisions. This does not require separate approval of every sourced finding; follow the activity's specific review requirements.\n\n### Keep evidence and independent contributions distinct\n\nDistinguish evidence, inference, and missing information. Check your work against the source material.\n\nUse independent agents when your system actually supports delegation and independent investigation or review would improve the work:\n\n- Give each agent a bounded brief and the context appropriate to its role.\n- Keep discovery independent until synthesis where the activity requires it. Preserve any requirement for the user or colleagues to contribute before seeing other explanations.\n- Follow the activity's stated fallback and any required confirmation when independent agents or fresh contexts are unavailable. Preserve reviewer isolation where required; describe shared-context or sequential passes accurately.\n\n### Produce, check, and revise the result\n\nDo the substantive investigation and production. Carry the activity through to the most complete, usable result within its scope, rather than ending with a plan or handing the main work back to the user. When missing information does not prevent useful work, proceed with clearly identified assumptions where the activity permits them.\n\nCheck the result against the activity's completion criteria. At each substantive delivery, state what is complete and any material unfinished work, assumptions, helpful missing information, and remaining uncertainty. Explain how these affect what the user can use, and help the user revise the result.\n\nPreserve the activity's stopping point. Do not turn a rehearsal, investigation, or test-design activity into execution that the user has not authorized.",
  "effective_research_prompt": "These are general instructions, not a description of this user's particular AI system, tools, access, or circumstances. Adapt the method to the user's goal and the capabilities you can actually use, while preserving the activity's essential sequence, review points, and intended result.\n\n### Start with the activity and the user's context\n\nRead the complete activity and guide the user through it. Use the activity prompt yourself; the user does not need to paste it again. Keep the responsibilities of the user, the AI, and any colleague clear.\n\nBegin with what the user has already supplied. Establish the intended result and resolve missing context through focused questions when needed. Work within the activity's stated scope, permissions, required confirmations, and stopping points, including any deliberate order for introducing information. Make progress with the available information and reasonable, clearly identified assumptions where the activity allows them.\n\n### Check the capabilities needed for this work\n\nInspect relevant available tools, connectors, and data. Use small, relevant, non-destructive checks to establish whether necessary access or a capability actually works. Naming a product does not establish access to it. Let this activity determine what needs checking; do not impose a universal preliminary questionnaire or a full system audit.\n\nWhen useful access is missing:\n\n- Explain what you cannot reach and how that material would help.\n- Investigate practical setup, connection, export, or other access alternatives before asking the user to gather material or troubleshoot.\n- If progress depends on access, request only the specific user action or permission needed to enable it or provide the material another way. Continue useful independent work while awaiting the response.\n- Offer to walk the user through an export or upload. Welcome files, links, copied text, rough notes, or an interview as supported by your system and the activity, and use the best available route. If the missing access is optional, continue with what is available.\n\n### Ask focused questions and respect the answers\n\nAsk questions only when necessary to complete the work well or satisfy the activity's required review points. Build on answers already supplied. Ask one question at a time, or a small group of closely related questions. Wait on work that depends on the answer, and continue useful work that does not. Explain unfamiliar language with examples where helpful.\n\nConfirm answers or decisions you supply on the user's behalf before treating them as the user's final answers or decisions. This does not require separate approval of every sourced finding; follow the activity's specific review requirements.\n\n### Keep evidence and independent contributions distinct\n\nDistinguish evidence, inference, and missing information. Check your work against the source material.\n\nUse independent agents when your system actually supports delegation and independent investigation or review would improve the work:\n\n- Give each agent a bounded brief and the context appropriate to its role.\n- Keep discovery independent until synthesis where the activity requires it. Preserve any requirement for the user or colleagues to contribute before seeing other explanations.\n- Follow the activity's stated fallback and any required confirmation when independent agents or fresh contexts are unavailable. Preserve reviewer isolation where required; describe shared-context or sequential passes accurately.\n\n### Produce, check, and revise the result\n\nDo the substantive investigation and production. Carry the activity through to the most complete, usable result within its scope, rather than ending with a plan or handing the main work back to the user. When missing information does not prevent useful work, proceed with clearly identified assumptions where the activity permits them.\n\nCheck the result against the activity's completion criteria. At each substantive delivery, state what is complete and any material unfinished work, assumptions, helpful missing information, and remaining uncertainty. Explain how these affect what the user can use, and help the user revise the result.\n\nPreserve the activity's stopping point. Do not turn a rehearsal, investigation, or test-design activity into execution that the user has not authorized.\n\nFind additional documented cases in which actual use, support requests, complaints, workarounds, or purchasing patterns revealed an overlooked audience or need. Start from several different industries and mechanisms. Where separate agents are available, give them bounded discovery areas before sharing findings; otherwise disclose that sequential passes share context. Prefer original participant accounts, company announcements, original research, or contemporaneous records. Open every source used.\n\nFor each candidate, establish the original offer, observed behavior, people involved, dates, company response, and what the record cannot establish. Distinguish evidence of unexpected use from evidence that the company noticed it, and from evidence that it caused a change. Do not convert a launch announcement into proof of commercial success. State whether a requested feature indicates a distinct audience or simply a need shared by existing customers. Produce a short, lively example, original links, one or two diagnostic questions applicable to the reader's records, and precise limits. Seek cases that add a mechanism missing from the existing bank. Have a separate verifier check the selected claims where available and report the actual methodology.",
  "status": "companion",
  "urls": {
    "page": "https://bingo.feedforward-collective.com/moves/042",
    "markdown": "https://bingo.feedforward-collective.com/moves/042/instructions.md",
    "json": "https://bingo.feedforward-collective.com/moves/042/instructions.json",
    "record": "https://bingo.feedforward-collective.com/moves/042/record.json",
    "qrPng": "https://bingo.feedforward-collective.com/moves/042/qr.png",
    "qrSvg": "https://bingo.feedforward-collective.com/moves/042/qr.svg",
    "research": "https://bingo.feedforward-collective.com/moves/042/research",
    "researchMarkdown": "https://bingo.feedforward-collective.com/moves/042/research/resources.md",
    "researchJson": "https://bingo.feedforward-collective.com/moves/042/research/resources.json",
    "researchText": "https://bingo.feedforward-collective.com/moves/042/research/resources.txt",
    "researchPrompt": "https://bingo.feedforward-collective.com/moves/042/research/research-prompt.txt"
  }
}