> ## Documentation Index
> Fetch the complete documentation index at: https://docs.laneapp.co/llms.txt
> Use this file to discover all available pages before exploring further.

# From signal to shipped

> Take one surfaced signal all the way to shipped work — and make sure the customers who asked hear back.

A [Signal](/signals) tells you *what* customers keep asking for. This playbook is what you do next: turn one signal into committed work, get it built, and close the loop with the customers behind it — one continuous thread from customer voice to shipped code.

## 1. Start from a signal

Open a Signal worth acting on — one from your **For You** tab or the top of your [Priority](/agent) list. Its detail view already has everything you need to decide: the Insights behind it, the customers asking, the revenue at stake, and its [priority score](/prioritization).

If it's real, act on it. If it isn't, reject it — that keeps your list honest.

## 2. Draft the Plan

From the Signal, create a [Plan](/docs) with the **Use Lane** action. Lane drafts a structured brief from the Signal's Insights and customer context, so you start from something real instead of a blank page. (Prefer to write it yourself? **Write it myself** opens a Plan seeded with the same context linked.)

Refine it section by section — tell Lane what to sharpen rather than rewriting by hand.

## 3. Commit the feedback it answers

On the Plan, **commit** the specific feedback this work addresses. This is the step that makes closing the loop possible later: committed feedback is what Lane reaches back to when the Plan ships, and what drives customer requests in [Linear](/linear).

## 4. Push it to delivery

When the Plan is ready to build, **Send to** your delivery tool — [Linear](/linear), [Jira](/jira), [Asana](/asana), or [Notion](/notion). Lane creates the issue and links it to the Plan.

On Linear, Asana, and Notion, map the tool's statuses to your Plan statuses so status flows back automatically — Lane always reflects where delivery actually is.

## 5. Ship — and let the loop close itself

When engineering moves the work to a shipped status, the linked Plan flips to that status in Lane, and [closing the loop](/close-the-feedback-loop) fires on its own: every customer behind the Plan's committed feedback is told, in the source they originally used — a reply in their Slack thread, a note on their Intercom or Zendesk conversation.

Nobody has to remember to follow up. The customer who asked hears back, new feedback comes in, and the cycle continues.

## The whole thread

```text theme={null}
Signal  →  Plan  →  Delivery tool  →  Shipped  →  Customer notified
```

That's the loop end to end — the [proactive setup](/stay-ahead) brings the signal to you; this playbook carries it to shipped and back to the customer.