Feature requests
Start with the decision your team cannot make.
Describe who is blocked, what evidence they need, and what a useful outcome looks like. That context gives product enough to assess the request.
Make the need reviewable
A feature name is not enough to judge the work.
Product needs the operating context behind the idea. A concise brief makes the affected person, current constraint, and success test visible before anyone discusses a solution.
- User and moment
- Who is doing the work, and which decision or handoff is blocked?
- Current workaround
- What do they do today, and where does that process lose time or evidence?
- Required context
- Which cost scope, role, source data, or audit record must be present?
- Success test
- What should the user be able to decide, verify, or complete afterward?
Have the brief ready?
Send the decision, current workaround, required context, and success test through Contact Us.
