How Northwind works

From first idea to shipped, in four steps

Follow a single feature as it travels through a Northwind workspace. Each stage hands off cleanly to the next.

A product team planning together around a table covered with laptops
Planning session, Northwind Berlin

Chapter 01 · Plan

Turn a rough idea into a shared plan

Start with a one-page brief, then break it into milestones with owners and dates. Everyone who touches the work sees the same plan, so scope questions get answered in the doc instead of in a meeting.

  • Briefs with built-in templates
  • Dependency-aware timelines
A laptop on a desk displaying source code
Linked to 120+ developer tools

Chapter 02 · Build

Keep engineers in flow, not in tabs

Branches, pull requests and deploys attach themselves to the task they belong to. Statuses update as code moves, which means nobody has to drag cards around to prove progress.

  • Automatic status from pull requests
  • Documented REST API and webhooks
A designer sketching layouts on a tablet while reviewing a draft
Design review in progress

Chapter 03 · Review

Feedback that lands on the right pixel

Comment directly on designs, documents and builds. Reviewers are pinged once, approvals are recorded with a timestamp, and open questions never get buried in a thread.

  • Inline comments and mentions
  • Timestamped approvals
A smartphone on a desk showing an app that has just been released
Release 4.12 is live

Chapter 04 · Ship

Release with a checklist, not a prayer

Release notes draft themselves from finished work, and go/no-go checks run before anything goes out. When it ships, stakeholders get a clear summary without asking for one.

  • Auto-drafted release notes
  • Go/no-go checks before launch