Ideas · systems · requirements

Connect ideas.
Build clarity.

Turn an early software idea or a systems question into a focused project conversation.

project / outline
Software requirementsInformation flowsProject planning
A useful starting point

A better brief
is a useful beginning.

Give your next discussion a clear starting point. Outline the people, workflows, and information involved before choosing an implementation.

01 /

The application idea

Describe the problem, the people it affects, and the outcome you would like to explore.

02 /

The information flow

Map the information involved and systems or tools that may need to work together.

03 /

The project context

Record known requirements, constraints, priorities, and open questions.

The approach

From an idea
to an outline.

  1. 01

    Frame the problem

    Start with the task and the people who need a better way to complete it.

  2. 02

    Make the scope visible

    Separate essential needs, assumptions, and questions.

  3. 03

    Choose a next discussion

    Use the brief as a starting point for review, rather than a promise of a particular solution.

Keep the next step simple

Put the idea on one page.

Create a project outline you can keep locally and share when you have the right contact.

Do not include passwords, API keys, proprietary data, or other sensitive information.

Saved to your device as a text file. No information is submitted.