Plan a delivery cycle

Deciding that a feature belongs in your product and starting work on it are two separate steps in Vector. First you record the decision: the feature is planned. Then you start a delivery cycle — a piece of work that takes the feature through the stages of Delivery preparation toward artifacts a development team can pick up. A cycle is one pass of work on one feature, so a feature can have several: v1 for the first version, v2 for the improvements once customers have used it. Each cycle works from the feature’s dossier — the research, competitor evidence and customer voice collected there are what the AI at each stage reads.

​

Mark a feature as planned

On the feature’s page, under Do we have this?, click Plan delivery. Your status for the feature moves to on our roadmap. The button appears only while your status says you don’t have the feature, or haven’t assessed it. This records the decision everywhere your status shows — the catalog, the comparison, the product map — but it doesn’t start any work or put anything on the board. It’s reversible: change the status back at any time.

​

Start the work

To start a cycle, use either place: A new cycle starts in the first stage of your pipeline — Backlog by default — and moves on from there.

​

Come back to a feature for another round

When v1 is done and you want to improve the feature, start another cycle the same way. It becomes v2 and moves through the stages on its own; v1 and its artifacts stay as they were.

​

Track a feature’s cycles

A feature’s Overview → Delivery tab lists all its cycles with their number, title and status, and whether one is waiting for your approval at a gate. Click a cycle to open it on the board. Once a cycle is scheduled, it also appears on the roadmap, one row per cycle.

​

Stop a cycle you no longer need

Open the cycle and choose Cancel or Archive. Both take it off the active board and keep its artifacts, so the work done so far isn’t lost.

​

Where to go next