Hubs: where a body of work lives

Overview

A hub is the place a body of work lives — a client, a project, a hiring round, a release: "Acme — rollout", "Hiring a designer", "Release 2.0". A hub gathers the meetings, the obligations and the tracker board that belong to one piece of work, so that everything a meeting produces has an address to go to.

Without hubs a task created from a meeting suggestion has nowhere specific to land. A hub is not a folder and not a group of participants: the same people run two different pieces of work, and an internal review about a client happens without the client in the room. The question a hub answers is "what is this about", not "who was there".

When to use it

  • You work with several clients or projects at once and meetings about them blur together.
  • Tasks from calls end up in the wrong project.
  • Before a call you want one screen showing what is still open on this work.

Step-by-step

  1. Create a hub in the Hub section and give it a name. Whisperer may suggest one, but the name is yours — a name chosen for you is a structural decision you did not ask for.
  2. Choose its board. Pick the tracker project where work from this hub should be filed. Until a board is chosen, suggestions from its meetings will honestly decline instead of filing tasks somewhere arbitrary.
  3. Let meetings find it. A meeting is routed automatically by a ladder of signals: what you said explicitly, then a calendar series, then the meeting title, then a live thread already running in the hub, then named things the hub knows, then the organisation, and only last the participants — who confirm a guess but never create one.
  4. Correct it once. If a meeting landed in the wrong hub, move it. The correction is remembered as a rule, so you are not asked about the same series again.
  5. Read what is missing. The hub page shows not what happened but what is unresolved: obligations coming due, decisions still open, work with no owner.

Common mistakes

  • Expecting routing by participants. Participants confirm a guess but never create one — routing follows what the conversation is about.
  • Leaving the board empty and wondering why tasks are not created. An empty address is a legal state, and the suggestion declines on purpose.
  • Looking for a delete button. Hubs are archived, not deleted: they hold the history of negotiations and promises.

Best practices

  • Name a hub the way you would say it out loud — that name is also the strongest routing signal.
  • One hub per body of work, not per client, if the same client runs two independent projects.
  • Check the hub before a call rather than after: its value is the list of what is still open.

Related articles