Product tour

Decisions library: find the reasoning

Find a decision’s rationale, owner and source in the Decisions library.

2 min 6 sFor: Engineer, product owner or reviewer12 steps

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

Quick steps

  1. Start on DM HomeStart from your DM Home. A decision is more useful when you can see its reason, its owner and its source. Here is how to find them in your team's Decisions library.
    1. Start on DM Home (/).
    2. Review "Knowledge".

    What it means: Start from your DM Home. A decision is more useful when you can see its reason, its owner and its source. Here is how to find them in your team's Decisions library.

  2. Click KnowledgeSelect Knowledge in the main navigation. It holds everything your team has approved.
    1. Click "Knowledge". The next view is "Knowledge" (/knowledge).

    What it means: Select Knowledge in the main navigation. It holds everything your team has approved.

  3. Click DecisionsKnowledge groups approved items by type. Choose Decisions to see your team's approved decisions.
    1. Click "Decisions". The next view is "Decisions" (/knowledge/decisions).

    What it means: Knowledge groups approved items by type. Choose Decisions to see your team's approved decisions.

  4. Review lifecycle statusBy default the list shows current decisions. The status filter lets you look at other lifecycle states, and the date fields narrow the list by meeting date. Switch to Timeline to see decisions in the order they were made.
    1. Review "Lifecycle status": "Current Active In progress Blocked Completed Superseded Cancelled Archived".
    2. Review "Timeline view": "Timeline".

    What it means: By default the list shows current decisions. The status filter lets you look at other lifecycle states, and the date fields narrow the list by meeting date. Switch to Timeline to see decisions in the order they were made.

  5. Click TimelineSelect Timeline. Each entry shows the decision, its date and its owner, oldest first, so you can follow how your team's thinking developed.
    1. Click "Timeline". The next view is "Decisions" (/knowledge/decisions).

    What it means: Select Timeline. Each entry shows the decision, its date and its owner, oldest first, so you can follow how your team's thinking developed.

  6. Click ListSwitch back to List when you want to open one.
    1. Click "List". The next view is "Decisions" (/knowledge/decisions).

    What it means: Switch back to List when you want to open one.

  7. Click Decision All tenant-owned tables use Postgres row-level security keyed on workspSelect a decision to preview it. The preview leads with what was decided, then the reason why. Below, you see its project, thread and repository, and when it was last updated.
    1. Click "Decision All tenant-owned tables use Postgres row-level security keyed on worksp". The next view is "Decisions" (/knowledge/decisions).
    2. You should now see "What was decided": "Isolate tenant data with row-level security".

    What it means: Select a decision to preview it. The preview leads with what was decided, then the reason why. Below, you see its project, thread and repository, and when it was last updated.

  8. Click Open decisionTo go deeper, open the decision. Its own page keeps the full record in one place.
    1. Click "Open decision". The next view is "Isolate tenant data with row-level security" (/decisions/dec-rls).

    What it means: To go deeper, open the decision. Its own page keeps the full record in one place.

  9. Review the decisionThe page leads with the decision statement and the reason behind it. Its lifecycle status is shown next to the title.
    1. Review "The decision": "All tenant-owned tables use Postgres row-level security keyed on workspace_id.".
    2. Review "Why": "Why Application-level filters have missed a query before. Row-level security enforces iso…".

    What it means: The page leads with the decision statement and the reason behind it. Its lifecycle status is shown next to the title.

  10. Click Evidence & LineageTo see where it came from, open the Evidence and Lineage tab.
    1. Click "Evidence & Lineage". The next view is "Isolate tenant data with row-level security" (/decisions/dec-rls).

    What it means: To see where it came from, open the Evidence and Lineage tab.

  11. Review linked evidenceLinked evidence shows the source the decision rests on. Here, it is an excerpt from the meeting where the decision was made. A decision shows evidence only where it has been linked.
    1. Review "Linked evidence": "1 linked item".

    What it means: Linked evidence shows the source the decision rests on. Here, it is an excerpt from the meeting where the decision was made. A decision shows evidence only where it has been linked.

  12. Review ask dmThen put what you find to work. Ask DM and Prepare context, both in the sidebar, can bring approved decisions into your next task. Next, learn how to use Search and Ask DM.
    1. Review "Ask DM".
    2. Review "Prepare context".

    What it means: Then put what you find to work. Ask DM and Prepare context, both in the sidebar, can bring approved decisions into your next task. Next, learn how to use Search and Ask DM.

The decisions, rationale, owners and the meeting excerpt shown are invented for this tour. DM Decision Health describes how complete and traceable a record is, not whether the decision was right.

Searching for a decision is the subject of a separate episode and is not repeated here.

Next lesson

Next: Rules, Skills and Policies: what each means

Descriptive transcript

Read the full transcript, including what happens on screen

Demo environment · synthetic workspace and data · backend responses are simulated. See the reason, owner and source behind a decision
This guide tours the real DM Decisions library and a decision's detail page with a synthetic workspace and simulated backend responses. Which decisions, filters and views you see in your own workspace depend on your data and role.

Disclosure (kept in this transcript and the video description, not drawn on the frames): Demo environment · synthetic workspace and data · backend responses are simulated.

00:00–00:13 · home

On screen: Start on DM Home (/). A highlight marks "Knowledge".

Narrator: Start from your DM Home.

Narrator: A decision is more useful when you can see its reason, its owner and its source.

Narrator: Here is how to find them in your team's Decisions library.

00:13–00:20 · open-knowledge

On screen: Click "Knowledge". The next view is "Knowledge" (/knowledge). A highlight marks "Knowledge".

Narrator: Select Knowledge in the main navigation.

Narrator: It holds everything your team has approved.

00:20–00:28 · open-decisions

On screen: Click "Decisions". The next view is "Decisions" (/knowledge/decisions). A highlight marks "Decisions".

Narrator: Knowledge groups approved items by type.

Narrator: Choose Decisions to see your team's approved decisions.

00:28–00:45 · browse

On screen: A highlight labelled "Lifecycle status" marks "Current Active In progress Blocked Completed Superseded Cancelled Arc…". A highlight labelled "Timeline view" marks "Timeline".

Narrator: By default the list shows current decisions.

Narrator: The status filter lets you look at other lifecycle states, and the date fields narrow the list by meeting date.

Narrator: Switch to Timeline to see decisions in the order they were made.

00:45–00:56 · timeline

On screen: Click "Timeline". The next view is "Decisions" (/knowledge/decisions). A highlight labelled "Timeline view" marks "Timeline".

Narrator: Select Timeline.

Narrator: Each entry shows the decision, its date and its owner, oldest first, so you can follow how your team's thinking developed.

00:56–01:00 · back-to-list

On screen: Click "List". The next view is "Decisions" (/knowledge/decisions). A highlight labelled "List view" marks "List".

Narrator: Switch back to List when you want to open one.

01:00–01:15 · preview

On screen: Click "Decision All tenant-owned tables use Postgres row-level security keyed on worksp". The next view is "Decisions" (/knowledge/decisions). A highlight labelled "Select a decision" marks "Decision All tenant-owned tables use Postgres row-level security keye…". Afterwards: A highlight labelled "What was decided" marks "Isolate tenant data with row-level security".

Narrator: Select a decision to preview it.

Narrator: The preview leads with what was decided, then the reason why.

Narrator: Below, you see its project, thread and repository, and when it was last updated.

01:15–01:23 · open-detail

On screen: Click "Open decision". The next view is "Isolate tenant data with row-level security" (/decisions/dec-rls). A highlight labelled "Open the decision" marks "Open decision".

Narrator: To go deeper, open the decision.

Narrator: Its own page keeps the full record in one place.

01:23–01:32 · detail

On screen: A highlight labelled "The decision" marks "All tenant-owned tables use Postgres row-level security keyed on work…". A highlight labelled "Why" marks "Why Application-level filters have missed a query before. Row-level s…".

Narrator: The page leads with the decision statement and the reason behind it.

Narrator: Its lifecycle status is shown next to the title.

01:32–01:38 · evidence-tab

On screen: Click "Evidence & Lineage". The next view is "Isolate tenant data with row-level security" (/decisions/dec-rls). A highlight labelled "Evidence and lineage" marks "Evidence & Lineage".

Narrator: To see where it came from, open the Evidence and Lineage tab.

01:38–01:50 · evidence

On screen: A highlight labelled "Linked evidence" marks "1 linked item".

Narrator: Linked evidence shows the source the decision rests on. Here, it is an excerpt from the meeting where the decision was made.

Narrator: A decision shows evidence only where it has been linked.

01:50–02:06 · use-it

On screen: A highlight marks "Ask DM". A highlight marks "Prepare context".

Narrator: Then put what you find to work.

Narrator: Ask DM and Prepare context, both in the sidebar, can bring approved decisions into your next task.

Narrator: Next, learn how to use Search and Ask DM.

Last verified against the product on .

Product tour 1 min 57 s13 steps

Rules, Skills and Policies: what each means

Explain the differences between the main Knowledge types and where to inspect them. Not everything your team remembers is the same kind of knowledge.

For: Member and admin

Product tour 55 s5 steps

Review Inbox: what needs your decision

Show how to interpret the review queue before diving into detailed approval. The Review Inbox is where proposed knowledge waits for someone to judge it.

For: Reviewer or workspace decision owner

Product tour 1 min 40 s9 steps

Search and Ask DM: two ways to find context

Orient users to search/navigation versus natural-language answer with citations. You do not need to remember a document title to find the decision behind it.

For: Any authorized workspace user