Turn a business problem into a useful brief.
You don't need to design the entire system before asking for help. Explain the work, show a real example and make the important decisions visible.
Start with the process you understand
Describe what starts the work, who handles it and what a successful result looks like. Include the systems people use and the points where they wait, repeat a task or make a judgment. That context helps an implementation team make better decisions than a feature list alone.
Show one complete example
Provide a representative input and the output you would accept. Explain any information a knowledgeable employee would use along the way. Remove confidential details unless an appropriate handling arrangement is in place.
Make uncertainty useful
If you do not know which integration is available or who should approve an exception, write down the question. An explicit unknown can be investigated. A hidden assumption often becomes rework.
Planning a new workflow?
Follow the guide from the current process to a structured brief and acceptance criteria.
Start with the process ↗Ready to share an app idea?
The app intake walks you through systems, requirements and supporting material.
Build an App ↗What are you
working on?
Looking for a course, help with a difficult problem, or someone to build a solution? Tell us where you are and what you'd like to do next.