Industry Forum Research

What is industry forum research?

Industry forum research means reading the places where people in one profession talk shop with each other: niche web forums, trade association message boards, Stack Exchange sites (the question-and-answer network behind Stack Overflow) and Slack or Discord communities. You look for questions that stay unanswered, workarounds people share and the tools they complain about.

Professionals write differently when they talk to peers. They skip the polite version, name the exact software, mention how many hours a task eats and paste the spreadsheet formula they hacked together. For B2B ideas (business-to-business, where a company pays), this is the closest you get to sitting in their break room without an invitation.

When should you use it?

• B2B and professional tools: software for accountants, lab managers, IT admins, architects, veterinarians, logistics planners, translators.
• Technical audiences: developers, data people and engineers who live on Stack Exchange, GitHub discussions and Discord.
• Trades and specialists: electricians, beekeepers, piano tuners and other groups with long-running forums.
• Skip it for mass-market consumer ideas (use Reddit problem research or reviews) and when you can’t understand the jargon yet. Spend a day learning the vocabulary first, or you will miss every signal.

How do you do it, step by step?

1. Map where the profession talks. Search Google for "[profession] forum", "[profession] slack community", "[profession] discord" and the name of the national trade association plus forum. Check whether a Stack Exchange site covers the field (there are sites for academia, the workplace, server administration, project management and more). Ask one person in the field: “Where do you go when you’re stuck at work?” Aim for 3 to 5 places.

2. Use Stack Exchange’s search operators to find unmet needs. Stack Overflow’s help page documents operators that work across the network. The most useful combination: isanswered:no views:500.. returns questions with no positively scored answer that at least 500 people viewed. Add a tag in square brackets, like [scheduling], and a date range like created:1y.. for the past year. Also try hasaccepted:no score:5.. for popular questions where nobody’s answer was accepted.

3. Join Slack and Discord groups and read before writing. Introduce yourself in the welcome channel with who you are and why you’re there. Then read the help, tools and off-topic channels, and use the workspace search for anyone know, how do you, spreadsheet, manually, hate and the names of the big tools in the field.

4. Log threads with 5 columns that matter for B2B. Thread link, the task described, the tool or workaround used, the time or money mentioned, and the role of the person (owner, manager, junior). The role matters because the person complaining and the person with a budget are not always the same.

5. Follow the workaround trail. When someone shares a template, macro or script, look at the replies. “Can you share that?” and “I’ve been doing this by hand for years” show demand for the workaround. A shared spreadsheet with 30 thank-you replies is a product spec written by the market.

6. Map the tools they mention. Keep a tally of every tool name and the emotion around it. A field where everyone uses the same old tool and grumbles about the same 2 missing features has a clear opening. A field where everyone uses different tools has no standard yet, which is a different opportunity.

7. Pick 1 or 2 problems and find your interviewees. Pick problems that appear in at least 2 communities. Note who answered helpfully on that topic; these people know the problem well and are your best candidates for interviews, approached politely and within community rules.

What does a worked example look like?

Say Elena, a hypothetical former school IT technician, wants to build for IT staff in small schools. She maps a Discord server for school IT people, a long-running forum for education technology staff and Server Fault, the Stack Exchange site for system administrators.

On Server Fault she runs title:"student" isanswered:no views:500.. and finds threads about tracking which student has which laptop and charger. On Discord, searching spreadsheet turns up 9 people sharing their own device check-in sheets over 6 months. One shared template has 26 replies asking for a copy.

The time column is striking: staff mention spending the last 2 weeks of the school year chasing returned devices and missing chargers. The tool tally shows two big device-management systems, and the complaint is the same for both: they manage the software on a laptop, and nobody tracks the physical hand-over between students.

Elena’s problem statement: IT staff in small schools lose up to 2 weeks a year chasing student devices because their management tools ignore physical check-in and check-out. She messages 5 of the most helpful posters and asks for a chat.

Which free tools help?

Stack Overflow lists every search operator on its help page, How do I search?

What mistakes should you avoid?

• Posting a survey on day one. Communities close ranks against outsiders who only take. Read for a week, then help where you can.
• Mistaking the loudest member for the market. Every forum has a handful of members who start a big share of the threads. Count unique posters.
• Ignoring who holds the budget. A junior’s frustration matters, but the problem needs a buyer. Note roles.
• Skipping the jargon. If you don’t know what a term means, you will misread the problem. Keep a glossary as you read.
• Treating old threads as current. Forums keep threads for a decade. Filter to the last 12 months or check whether the tools mentioned still exist.

How do you know it worked?

You have 30+ logged threads from at least 3 communities, a tool tally and 1 or 2 problem statements. Our rule of thumb: a strong B2B problem shows up in 2 or more communities, comes with a homemade workaround that others ask to copy, and mentions time or money in at least a quarter of the threads.

Go: you can name the problem, the role that feels it, the role that pays and 5 people to interview. No-go: threads are mostly about learning the job, with no repeated task-level frustration. Try a different role in the same industry.

What should you do next?

Confirm that companies spend money on the problem with job board signal mining, then watch the work happen through contextual inquiry and run problem interviews with your most helpful posters. Narrow down who to serve first with a beachhead segment. To practise these steps with feedback, Fe/male Switch offers a startup game where an AI co-founder guides your validation.

FAQ

How do I find a professional Slack or Discord community?

Search Google for the profession plus “slack community” or “discord server”, check the links on trade association and conference sites, and ask people in the field directly. Many communities are invite-only and spread through word of mouth.

Is it okay to research a community I’m not part of?

Yes, if you are open about who you are, follow the rules and contribute where you can. Lurking to read public threads is normal. Collecting members’ details or messaging everyone is where you cross the line.

Which Stack Exchange search finds unmet needs fastest?

isanswered:no views:500.. plus a tag in square brackets. It shows questions many people looked at where nobody gave a positively scored answer, which is a direct sign of an unmet need.

Updated 26 October 2026 · Written by the Fe/male Switch team

Mark this method as done