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

# From map to delivery

> Turn a redesign gap on the operating model into a real Opportunity, then a Deliverable, and watch the process KPIs move.

The operating model is where AI work starts, and the rest of the platform is where it gets done. This page shows how a gap on the map becomes delivered work with measurable value.

## The redesign backlog

Wherever a step's **target** disposition differs from its **current** one, you have a redesign gap. Across a unit, those gaps form a **redesign backlog**, ranked by constraint and coordination burden so the highest-value work rises to the top. You see this backlog in your unit cockpit.

A gap answers three questions at once:

* **Where** in the business the work sits (the step, its process, its unit).
* **What** the change is (from this disposition to that one).
* **Why** it matters (it is a constraint, or heavy on coordination, in a high-criticality process).

## From gap to Opportunity

When a gap is worth pursuing, it becomes an **[Opportunity](/platform/opportunities)**, the platform's captured, ICE-scored idea. Because the Opportunity is linked to the step it came from, it carries its address in the business with it. This is what turns a suggestion box into a targeted pipeline: you are not collecting generic AI ideas, you are collecting changes to specific, valued processes.

Individual contributors and managers raise these ideas too, in the app or by mentioning the [Kowalah Agent](/integrations/agent/overview) in Teams, Slack, or Google Chat. When an idea maps to a step, it lands against that step rather than floating free.

## From Opportunity to Deliverable

Once triaged, an Opportunity can be promoted into a **[Deliverable](/platform/projects/deliverables)** inside a Kowalah-managed [project](/platform/projects/overview), or into an [Expert Request](/platform/expert-requests). This is the committed work that actually changes the step: building the agent, wiring up the accelerator, or redesigning how the work flows.

The Deliverable stays linked to the process, so at any point you can see which initiatives are changing a given process, and where in the business any initiative lands.

<Steps>
  <Step title="Spot the gap">
    A step's current and target dispositions differ, and it ranks high on the redesign backlog.
  </Step>

  <Step title="Capture the Opportunity">
    Raise it as an Opportunity linked to the step, or promote an idea your team already raised.
  </Step>

  <Step title="Promote to delivery">
    Triage and promote the Opportunity into a Deliverable or an Expert Request.
  </Step>

  <Step title="Deliver the change">
    Kowalah and your team build and ship the change. The step's implementation is recorded against it.
  </Step>

  <Step title="Watch the value move">
    As the step's disposition shifts, coverage updates and the process KPIs move against their baseline.
  </Step>
</Steps>

## Proving the value

This is the loop that makes AI value legible. A redesign gap becomes an initiative, the initiative ships, the step's disposition changes, and the process KPI moves. Because the KPI is attributed through the linked initiative, you can tell a clear story: *these steps went autonomous, this number improved by this much*. That is the sentence a leader carries to the board.

<Tip>
  Keep the loop tight by keeping the map current. When a Deliverable ships, update the step's disposition and the process KPI so the value shows up on the map. See [owning and improving a process](/platform/operating-model/owning-and-improving).
</Tip>

## What's next

<CardGroup cols={2}>
  <Card title="Opportunities" icon="lightbulb" href="/platform/opportunities">
    How ideas are captured and scored
  </Card>

  <Card title="Deliverables" icon="package" href="/platform/projects/deliverables">
    Committed work inside a Kowalah-managed project
  </Card>
</CardGroup>