A direction for every idea.

Founders

Start with one audience and one problem. Describe the smallest experience that helps someone, then separate the must-haves from the “one day” list.

• Name the user and their first useful action.
• Write down the assumption you most need to test.
• Create a project with a focused, editable brief.

Product teams

Use a project description as a shared starting point: the problem, primary workflow and acceptance criteria. Project records are available; real-time collaboration is not.

• Describe the current workflow before proposing a new one.
• Include empty, loading and error states.
• Keep the first version deliberately small.

Designers

Give your idea a point of view. Explain the visual hierarchy, content and interactions that make the experience specific, not merely attractive.

• Identify what people need to notice first.
• Describe accessible interaction states.
• Use original references and materials you can legally use.

Operations

The most useful tool often starts with the task everyone repeats. Map the people, data and decisions involved before choosing a screen.

• Document the steps you want to simplify.
• Define who can read or change each record.
• List the existing systems; integrations are not yet connected.

Prototyping

A prototype begins with a testable question. Today you can organize a brief and project; interactive generation is still on the roadmap.

• Choose one hypothesis.
• Define the shortest path through the experience.
• Plan how you’ll learn whether it helps.