Write the purpose in one sentence
The materials differ depending on whether you need root-cause investigation, technology selection, design review, or integration planning.
- Issue investigation
- Technology selection
- Architecture review
- External service integration
Prepare reproduction steps and logs
For bugs or performance issues, environment, steps, expected result, actual result, and logs help narrow the scope.
Decide sharing scope and access first
NDA needs, code scope, temporary access, and sharing-stop timing should be decided before research starts.
Practice Example: Organizing a Research Request
Research is easier to act on when the decision, shared information, non-scope, and deliverable are clear.
| Decision needed | Shared information | Not in scope | Deliverable |
|---|---|---|---|
| Narrow down a defect cause | Reproduction steps, logs, environment | Broad feature redesign | Likely causes and next checks |
| Decide whether to adopt a library | Requirements, constraints, candidates | Production implementation | Comparison notes and risk list |
| Understand design risk | Architecture diagram and code scope | Full code review | Design review and improvement candidates |
Common Inquiry Examples
Technical research helps when a team needs evidence before choosing a direction or starting implementation.
- Narrow down a bug or performance issue
- Compare libraries or external services
- Review risks in an existing design
What to Decide Before Requesting Work
Keep the research bounded by deciding what decision is needed and what materials can be shared.
- Decision needed after the research
- Environment, reproduction steps, and logs
- Reviewable code scope and NDA rules
Patterns That Often Fail
Broad research requests often produce notes that are hard to turn into implementation decisions.
- Starting with 'please look at everything'
- Missing reproduction steps or logs
- Choosing a solution before checking the facts
How Nobilwing Can Support
Nobilwing can support root-cause investigation, technology selection, design review, and risk listing.
- Bug and performance issue triage
- Technology selection and external service research
- Research notes, risk list, and next actions
Research Request Checklist
- State the decision needed
- Summarize current environment
- Prepare reproduction steps and logs
- Define reviewable code scope
- Confirm NDA and access rules