Glossary

Workstream

A strand of work that keeps going, rather than a project that ends.

Definition

A workstream is a continuous strand of related work within a larger effort, with its own owner, its own outputs and its own rhythm. The term comes from programme management, where a programme is divided into parallel streams that each run to their own schedule. In everyday use it covers anything ongoing that a team wants to see grouped: a project, an area of responsibility, or a client.

Origin: Programme management
Distinguishing feature: Ongoing, not time-boxed
Polaris name in UI: Workstreams, also called buckets

Why teams reach for the word

Project implies a start, an end and a deliverable. Most work in a company has none of those: keeping the help centre current, running recruiting, handling one client's account. Calling these projects forces an artificial end date onto work that will still be happening next year, and teams notice the mismatch even when they cannot name it.

Workstream describes the ongoing thing directly. In programme management the meaning is narrower, covering parallel strands within a defined programme, each with a lead, but the looser usage has spread because it fills a gap the project vocabulary left open.

Commonly confused with

Term	What it is	The difference
Project	A time-boxed effort with a defined end and deliverable	Ends. A workstream continues until the responsibility itself ends.
Programme	A group of related projects managed together	The parent. Workstreams are typically the strands inside a programme.
Epic	A large body of work broken into stories	A backlog-sizing construct that eventually completes.
Team	A group of people	Describes who. A workstream describes what, and one team can run several.

How Polaris uses the term

Polaris calls them workstreams in the interface and buckets in conversation. Both mean the same container.

Any container of work
A project, an area or a client. There is no separate concept for each; one container type handles all three.
Lanes shared between views
The lanes inside a workstream are the same whether you look at it as a list or as a board, so a team organises once and chooses its view afterwards.
Not the home screen
The Focus lane is the home screen, not the workstream list. Workstreams are where work lives; Focus is what you have committed to next.
Created when work needs a home
The Chief of Staff will propose a workstream when tasks are accumulating without one, rather than leaving them loose in an inbox.

Focus lane

A commitment for a horizon, not a filter over everything you have.

All-in-one workspace

One data model behind documents, tasks and conversation, instead of three products and a pile of integrations.

Tool sprawl

The expensive part is not the licences. It is that nothing is authoritative any more.

Acceptance criteria

Written before the work, checkable after it, and binary either way.

What an AI worker actually does, department by department

Twelve functions, sixty recurring jobs, and the exact tool connection each one needs.

Alternatives to the work tools you pay for by the seat

Sixteen pages about tools teams leave, what leaving actually costs, and when leaving is the wrong call.

Questions people ask

+What is the difference between a workstream and a project?

A project is time-boxed and ends when its deliverable is complete. A workstream is ongoing and ends only when the responsibility itself goes away. A launch is a project; keeping the documentation current is a workstream.

+How many workstreams should a team have?

Few enough that someone can name them all without looking. When the list stops being memorable it has usually become a filing system rather than a map of what the team is responsible for, and the fix is merging rather than nesting.

+Do AI workers belong to a workstream?

In Polaris, no. Workers belong to the workspace roster and can be assigned tasks in any workstream, in the same way a colleague is not confined to one project.