Project / 11

Northbank

A rhythm tool for small product teams.

Category
Concept · Tools
Year
2025
Role
Founder
Status
Fictional concept placeholder
A simple weekly team rhythm board with notes

A weekly rhythm without another meeting.

Northbank is a fictional tool concept for small product teams that need a shared sense of focus, delivery, and reflection.

The experiment asks whether a few durable prompts can replace status theatre with a calmer working record.

A simple weekly product team board with focus and review notes
Team rhythm board concept. Fictional placeholder content.

One rhythm, five moments.

  1. Focus

    Name the priority in one sentence.

  2. Commit

    Choose a small piece to ship.

  3. Signal

    Make uncertainty visible early.

  4. Deliver

    Record what actually changed.

  5. Reflect

    Keep one lesson for the next cycle.

A record of intent and evidence.

The system map is conceptual and does not describe a shipped service.

Team

  • Members
  • Working week
  • Focus

Commitment

  • Owner
  • Scope
  • State

Reflection

  • Change
  • Learning
  • Next step
Cadence
Every record belongs to one working week.
Memory
Completed weeks remain readable rather than disappearing.

Less ceremony means less context.

Less ceremony means less context.
ConstraintChoiceConsequence
Meeting loadAsynchronous promptsMore flexibility with fewer live cues
Status noiseOne weekly focusClear direction with less detail
Unclear ownershipOne named ownerFaster follow-up with less shared ambiguity
Long archivesWeekly summariesReadable history with some information loss

The ritual can become the work.

Prompts can become performative

A short update still fails when people write for approval rather than clarity.

Quiet is not always healthy

Some uncertainty needs a conversation, not another field.

A week is an arbitrary boundary

Different teams need different ways to close and restart work.

Code evidence

The weekly record as pseudocode.

week
  focus: one clear priority
  delivery: one observable change
  reflection: one retained lesson
  next: one open question
Illustrative data shape for this fictional concept. It is not production source code.

What the concept cannot answer yet.

Candour

What makes an asynchronous update feel safe enough to be honest?

Urgency

How should urgent work interrupt the weekly rhythm?

Closure

When does reflection help, and when is it just another task?