Skip to content
← Product management

SHIP / RELEASES & ROLLOUT

Plan the release.
Record what shipped.

Bring versions, launch plans and rollout into the product story. Keep planned work distinct from what your team confirms it delivered.

A complete Product workspace. Connect the wider work when useful.
Releases & rollout workflowPlan → prepare → confirm → learn. An authored illustration with fictional planning examples.HARBOR 0.8External-review releasePlannedRequest + specification + target window 01PrepareScope & acceptance02ReleaseEvidence of delivery03ReviewAdoption & outcomes A PLAN BECOMES A RELEASE WITH EVIDENCE.
Plan → prepare → confirm → learn
Product workflow illustration · Fictional planning examples
01Release records
02Launch & rollout
03Delivery evidence

SEE THE WORK / MAKE A CHOICE

Give the release a plan.
Give learning a place.

Record a manual release without a repository, then define the outcome you will return to after a real release.

Working demo screens · Fictional examples

PRODUCT / INSIDE THE DEMO

Record the intent clearly.

Name the release, choose a target window and retain the links to the customer request and specification.

The planned release connects a target window with the source request and agreed scope.

Try release planningInteractive example · No sign-up
ProcessScout / ProductDEMO WORKSPACE
Harbor working demo: Name the release, choose a target window and retain the links to the customer request and specification.

PRODUCT / INSIDE THE DEMO

Make the outcome testable.

Choose a measure, target, owner and collection method before claiming that the product change helped.

Baseline, actual outcome and realized value stay unknown until real evidence is recorded.

Try outcome planningInteractive example · No sign-up
ProcessScout / ProductDEMO WORKSPACE
Harbor working demo: Choose a measure, target, owner and collection method before claiming that the product change helped.
01

ESTABLISH THE RELEASE

A product release can start with your existing workflow.

Create a manual release with a name, an optional date and the arcs or epics it includes; no repository or commit is required. The record ties the release to its planned work, whether your engineers built it or Build Factory (beta) prepared it for your team to deploy.

Start with
A release name, included work and an optional release date.
Work toward
A product release record connected to the relevant arcs and epics.
Detail of the Product demo with fictional example data
ProcessScout / Productthe scope a release includes · fictional data
02

PREPARE THE INTRODUCTION

Give the launch more shape than a date.

Launch-plan and cohort-rollout views sit beside versions and the changelog, so the introduction lives with the work being released. Plan who sees the change and when to review it, and keep that plan distinct from deployment evidence and later usage data.

Start with
The intended release, launch considerations and rollout cohorts.
Work toward
A shared view of the release and its introduction plan.

An introduction, not just a date

  1. Release noteWhat changed
  2. The right audienceTold in time
  3. Review dateWhen to look again
Illustration · fictional example

HARBOR / THE WORKED EXAMPLE

Release the change. Keep the measurement open.

In the fictional Harbor example, the team plans a manual release for external-review sharing and identifies the work it would include. Deployment and outcome evidence are still pending. The planned release is an intentional next step, with no shipped change or customer result claimed.

Walk through this example

A PLANNED RELEASE, WITH NOTHING CLAIMED.

  1. Included scopeRequest and specification
    SPEC-31
  2. ReleaseHarbor 0.8 · external review
    PLANNED
  3. DeploymentRecorded by your team
    PENDING
  4. OutcomeMedian review time
    NOT MEASURED
Fictional planning example · No result is claimed
03

FOLLOW THE DELIVERED CHANGE

Let the release say what the evidence supports.

Keep planned, manually confirmed and deployed releases as different records, so the changelog says only what the evidence supports. A build that Build Factory (beta) prepared can carry its review record and approved client-note text; your team deploys it and records that step. Then connect the release to outcome review.

Start with
Release records, your team’s deployment record and, where used, the reviewed Build Factory build.
Work toward
A changelog and release view with an identifiable delivery basis.
Detail of the Transform demo with fictional example data
ProcessScout / Transformobserved readings kept apart from the forecast · fictional data

THE PRACTICAL DETAILS

What a release
records.

Talk through your workflow
Do we need a repository to manage releases?

No. A manual release can be recorded with its name, optional date and included arcs or epics. It does not require a repository or commit.

Does the release page deploy our product?

No. The release record and launch plan do not deploy software, and neither does Build Factory (beta): it designs and builds a reviewed change, ready to deploy, and your team deploys it through its own process.

What qualifies a Factory change for the changelog?

A build that Build Factory (beta) prepared, that your team has deployed and recorded, with approved client-note text. A plan or an unconfirmed deployment should not be presented as the same evidence.

YOUR NEXT PRODUCT DECISION

Record one release.
Say what the evidence supports.

Try a fictional example, or bring one question from your product.

Product view

ProcessScout interactive demo · Fictional Harbor data