How-to

Record your first decision and why

A decision candidate with its rationale is saved for review. Write the decision first. Add the reason while it is fresh.

37 sFor: Workspace member who can create decisions7 steps

Read the steps OR watch the video. Both teach the same outcome, and neither is needed for the other.Jump to the video

Guided Quick Start

Six steps from sign-in to useful context

Follow the sequence or jump to any lesson. Every step also works on its own, with written instructions alongside the optional video.

Step 3 of 6

  1. Step 1Sign in and choose your workspaceGoal: Reach the right workspace before doing anything else.33 s
  2. Step 2Know where to startGoal: Know the three places you will use: the Home queue, Add to DM and Knowledge.25 s
  3. Step 3Record your first decision and whyGoal: A decision candidate with its rationale is saved for review.37 s
  4. Step 4Approve it so the team can rely on itGoal: The candidate becomes approved team knowledge.39 s
  5. Step 5Find it again laterGoal: Find the decision, its reason and its evidence.44 s
  6. Step 6Put it to workGoal: Ask DM from the decision, and hand it to an agent task as context.45 s

Quick steps

  1. Click Add to DMTo record a decision, select Add to DM.
    1. Start on DM Home (/).
    2. Click "Add to DM". The next view is "Add to DM" (/add).

    What it means: To record a decision, select Add to DM.

  2. Click Create directlyYou already know the decision, so choose Create directly.
    1. Click "Create directly". The next view is "Create directly" (/add/create).

    What it means: You already know the decision, so choose Create directly.

  3. Click DecisionChoose Decision.
    1. Click "Decision". The next view is "Intake" (/intake).

    What it means: Choose Decision.

  4. Fill in the formWrite the decision as a statement.
    1. Type "Any migration that touches production schema needs approval from two reviewers." into the "Decision statement *" field.
    2. You should now see "The decision".

    What it means: Write the decision as a statement.

  5. Fill in the formThen add the reason behind it.
    1. Type "A single-reviewer migration dropped an index in the spring." into the "Rationale (optional)" field.
    2. You should now see "The reason".

    What it means: Then add the reason behind it.

  6. Click Create proposal →Then submit it.
    1. Click "Create proposal →". The next view is "Production schema changes" (/candidates/cand-two-reviewers/review).

    What it means: Then submit it.

  7. Review your candidateYour decision is saved as a candidate for review. It isn't team knowledge until a person approves it. Next, approve it.
    1. Review "Your candidate": "Any migration that touches production schema needs approval from two reviewers.".

    What it means: Your decision is saved as a candidate for review. It isn't team knowledge until a person approves it. Next, approve it.

Source-based intake (pasting notes or attaching files) is a different route, covered by the Add your first evidence episode.

The Optional details section (owner, follow-up and the other advanced fields) is not opened in this Quick Start; a separate, focused tutorial would explain each field.

Rules, Skills and Action items, the other things Create directly can record, are not shown.

What happens in a real deployment after submitting, including the checks on the candidate, was not verified.

Descriptive transcript

Read the full transcript, including what happens on screen

Demo environment · synthetic workspace and data · backend responses are simulated. Quick Start 3 of 6
The submission is SIMULATED: this guide uses the real DM Create directly form with a synthetic workspace, and the response that creates the review candidate is fixture data, not a deployed backend. Nothing is approved or becomes durable knowledge in this clip. Quick Start clips 1 to 6 follow one example workspace, Acme Platform Team.

A banner reading "Demo environment · synthetic workspace and data · backend responses are simulated" stays on screen for the whole video.

00:00–00:04 · start

On screen: Start on DM Home (/). Click "Add to DM". The next view is "Add to DM" (/add). A highlight marks "Add to DM".

Narrator: To record a decision, select Add to DM.

00:04–00:10 · create

On screen: Click "Create directly". The next view is "Create directly" (/add/create). A highlight labelled "Create directly" marks "Create directly You know exactly what to author — one Decision, Rule,…".

Narrator: You already know the decision, so choose Create directly.

00:10–00:13 · kind

On screen: Click "Decision". The next view is "Intake" (/intake). A highlight labelled "One decision" marks "Decision".

Narrator: Choose Decision.

00:13–00:18 · statement

On screen: Type "Any migration that touches production schema needs approval from two reviewers." into the "Decision statement *" field. A highlight marks "The decision". Afterwards: A highlight marks "The decision".

Narrator: Write the decision as a statement.

00:18–00:24 · reason

On screen: Type "A single-reviewer migration dropped an index in the spring." into the "Rationale (optional)" field. A highlight marks "The reason". Afterwards: A highlight marks "The reason".

Narrator: Then add the reason behind it.

00:24–00:27 · submit

On screen: Click "Create proposal →". The next view is "Production schema changes" (/candidates/cand-two-reviewers/review). A highlight labelled "Submit" marks "Create proposal →".

Narrator: Then submit it.

00:27–00:36 · saved

On screen: A highlight labelled "Your candidate" marks "Any migration that touches production schema needs approval from two…".

Narrator: Your decision is saved as a candidate for review. It isn't team knowledge until a person approves it.

Narrator: Next, approve it.

Last verified against the product on .

How-to 25 s4 steps

Know where to start

Know the three places you will use: the Home queue, Add to DM and Knowledge. Three places are enough to get started.

For: Any signed-in workspace member

How-to 39 s8 steps

Approve it so the team can rely on it

The candidate becomes approved team knowledge. Until a person approves it, it is only a proposal.

For: Reviewer or workspace decision owner

How-to 44 s6 steps

Find it again later

Find the decision, its reason and its evidence. Months later, search beats remembering.

For: Any authorized workspace user

How-to 45 s8 steps

Put it to work

Ask DM from the decision, and hand it to an agent task as context. An approved decision is only useful if it is used.

For: Workspace member and agent user