The problems worth solving
Make the next step understandable when a capability is unavailable. Keep a source attached to a research finding. Build interfaces that show what needs approval and let users inspect the result.
A practical contribution
A strong proposal names one user problem, shows the current behavior and explains how the change will be verified. Use the support channel for current opportunities; this reference adaptation does not create a vacancy.
A practical starting point
Research with traceable evidence. These steps describe the GoCux workflow and its permission boundaries.
- Define a research question, the project it belongs to, and the sources that may support the answer. Separate a factual question from the action you might take after reading the result.
- Review the proposed research plan before approving execution. Keep the approved scope stable; a different question deserves a revised plan rather than silent expansion.
- Read each finding alongside its citation and source excerpt. Treat missing evidence as an unresolved question, and keep the final report distinct from any subsequent external action.
What to verify
A useful report connects its conclusions to sources and makes unresolved questions visible. A fluent paragraph alone does not establish that a research task succeeded.
Bring this workflow into your workspace.
Set the scope. Review the evidence. Approve the steps that need it.