Customer research for Project management software

Define the question before collecting names

For project management software, investigate whether handoffs are agreed in chat but never appear in the delivery schedule. Research is useful when it explains a workflow, its owner, and an unresolved constraint. A list of companies in a sector cannot establish that those companies have this problem.

Begin with project leads coordinating work across specialists and check how their work relates to a delivery manager accountable for client deadlines. Map the current process around a project spreadsheet alongside several team chat channels. You are looking for the step where the workaround stops being adequate, rather than asking people to validate an abstract product idea.

Search for the language of the problem

Try the queries below in a search engine or the search feature of a relevant professional community. Read the original discussion and its date. Results are starting points for research; these query examples do not claim any particular search volume or the existence of a matching prospect.

Write an evidence note you can revisit

Illustrative source text: “Our designers finish on time, but engineering does not see the handoff until the deadline slips. How do other agencies track dependencies?” Save the actual source URL and date when researching a real example. Keep a short relevant excerpt and your interpretation in separate fields. Do not rewrite your interpretation as something the author said.

The working hypothesis is that the team is running several client projects at once. The missing information includes whether the author is a delivery manager accountable for client deadlines, whether the need is still open, and which implementation requirements remain unverified. Keep this constraint visible: a new tracker fails if teams still maintain their authoritative schedule elsewhere.

• Observed: the original words, the visible date, the task described, and any explicit requirements.
• To verify: whether the current process is a project spreadsheet alongside several team chat channels.
• Disqualify when the need belongs to buyers requiring portfolio accounting when only task coordination is available.
• Next step: one context-appropriate question, or no contact when there is no suitable route.

Use a short discovery interview

Ask about a recent event before showing your product. Let the person explain the sequence in their own words; do not treat agreement with a leading question as validation.

• Which missed handoff changed a delivery date last month?
• Would all participating teams update a shared dependency record?
• What would need to be true for you to model dependencies and owners for one upcoming client milestone?
• How would you verify that a downstream owner acknowledges a dependency before its deadline?

Turn notes into a research decision

Compare independently sourced accounts of the same task. Keep an example that contradicts your hypothesis, such as this ambiguous scenario: A founder asks for a nicer to-do list for personal errands. It may justify more reading, but it is insufficient to label someone a buyer.

At the end of a bounded research session, decide whether to narrow the audience, ask a specific follow-up, change the pilot, or stop. Keep unknowns visible and store only the information needed for that decision. Research quality is measured by a better decision, not by how many names are collected.