The structure to use
A problem statement should be specific enough for matching but concise enough for first review. Avoid a long background memo. Lead with the decision you need to make and the evidence that would help you make it.
- Problem title: a short, descriptive name.
- Current bottleneck: what is blocking progress internally.
- Desired outcome: what success would enable.
- Technical focus: materials, measurement, optics, chemistry, data, environment, XR, or another domain.
- Inputs: sample type, dataset, prototype, process, or system.
- Timeline and budget readiness.
- Confidentiality level.
What not to include too early
Do not share trade secrets, formulas, source code, full datasets, customer names, or proprietary process parameters before the right confidentiality path is in place. Use a limited summary for matching, then disclose sensitive detail after trust and NDA steps.
Example framing
Instead of writing 'we need help with a polymer issue,' write 'we need to understand why a bio-based polymer film loses barrier performance after thermal cycling, and we need microscopy and material analysis to compare three candidate formulations.' The second version gives a lab enough signal to assess fit.
Common questions
How long should an R&D problem statement be? A first version can be 150 to 400 words. The goal is to give enough context for lab matching, not to replace a full technical brief.
Can I write a useful problem statement if I do not know the method? Yes. Describe the outcome you need and the evidence that would help. A lab can often suggest suitable methods during scoping.