Personal productivity product
What if a task could change views without changing meaning?
I designed and shipped one task model across capture, list, board, calendar, project, and work or personal contexts.
Open BrainMap Creator, product designer, and builder
Operate the idea
Move one task without creating three versions of it.
Task 014Prepare the release decision
Captured. Context not decided.
Move the task from capture to a planning view.
Product decisions
The feature list was easy. The shared model was the product.
- 01
Capture first. Organize second.
An inbox keeps an unfinished thought cheap to record. Structure arrives when there is enough attention to make a useful decision.
- 02
Views are perspectives, not copies.
List, board, calendar, and project screens read and change the same task state. Moving a task cannot fracture its meaning.
- 03
Separate context without splitting the system.
Work and personal spaces reduce noise while preserving one planning model and one search surface.
0 to 1Problem definition
One modelList, board, calendar
PublicReact, TypeScript, Supabase
The evidence is a shipped product and an end-to-end design process. No adoption or time-saving metric is claimed.