Skip to content

Graph · Work graph

Work graph

A task is never alone. WAH reads the graph, not just the title.

Goal

Keep life moving

Project

MBA Presentation

MBA Presentation

Prepare presentation

Due Tomorrow · 9:00 AM45 min

Blocks: Presentation

MBA class · Tomorrow
4 errands
Family · Tonight

Do this next

Prepare presentation

45 minDue tomorrow

Why this?

  • Due tomorrow and fits your 45 minutes before the meeting.
Start task

Same engine → same card, no motion required to understand

That tiny graph — goal, project, dependencies, effort, time — changes the answer.

A task is never alone. WAH reads the graph, not just the title. “Fix authentication” tells you what to do. The graph tells WAH whether you should do it now — what it blocks, how long it takes, and what else is happening around it.

That graph — goals, projects, dependencies, effort, time, and context — changes the answer. Ask “What should I work on today?” and WAH optimizes for leverage and fit. Ask “What’s blocking the launch?” and WAH follows the dependency path.

  1. 01

    Leverage

    Goals + projects tell WAH what matters.

  2. 02

    Dependencies

    Blocking relationships tell WAH what can move now.

  3. 03

    Fit

    Effort + time tell WAH what fits right now.

  4. 04

    Context

    Messages, notes + history explain why the work matters.

The graph

Interview notes
↓
Product brief
↓
Launch
↓
Friday

What should I do now?

Finish the product brief

45 min · Highest leverage · Interview notes ready

Why this?

  • → Unblocks launch
  • → Highest-leverage project
  • → 45 min available
  • → Interview notes already complete

Next: Product brief → Launch → Friday

Don't build the graph. Use it.

You don't manage the graph. You manage your work. WAH builds the graph underneath — connecting goals, projects, dependencies, time, and context. You ask the question. WAH follows the graph.