Business Objectives

Captures the measurable goals the project must achieve. Keeps requirements anchored to business value.

AI in this module

How AI suggestions work

Click "Get AI Suggestions" at the top of the module to draft or improve both the Overview and the Objectives table in one pass — grounded in the rest of the DRP's content and any AI Knowledgebase documents for the project. Drafting both together in one call keeps them consistent: the objectives the AI proposes will match the context the Overview describes.

Suggestions appear in the right-hand panel as one card per field, not one long block of text. Each card has its own "Apply" button, so you can accept the Overview suggestion without touching your existing objectives, or vice versa — or use "Apply all" to accept everything at once. Nothing is written to the module until you click Apply.

The AI only proposes objectives it can ground in the DRP's existing content — if the draft looks thin, add more detail to modules like Introduction & Purpose or Solution Scope first, or upload supporting documents to the AI Knowledgebase, then refresh suggestions.

Quality checks

What "Check Quality" looks for here

Real, checkable success metrics. Flags an objective with a vague aspiration instead of a real metric, keeping objectives measurable rather than aspirational.

Priorities that are actually differentiated. Flags every objective marked "Must" — a sign priorities haven't genuinely been thought through.

What it captures

The measurable business goals the project must achieve — what success actually looks like, not just what's being built.

Using this module

This module has two parts: an Overview — a short narrative paragraph on the business context and why the project matters now — and an Objectives table, where each row is one objective with a Success Metric and a MoSCoW priority (Must, Should, or Could).

  1. 1Write the Overview first, even briefly — it gives the AI (and human readers) the context to judge which objectives actually matter.
  2. 2Add one row per objective in the table. Use "+ Add row" to add more, or the ✕ next to a row to remove it.
  3. 3Set a Success Metric for every objective — a real, checkable measure, not a vague aspiration.
  4. 4Assign a MoSCoW priority to each objective from the dropdown.

Review and approval

Reviewed as a whole — Overview and the Objectives table together, not row by row. A Lead Analyst or Analyst assigns this module's reviewer and approver from the project's Modules tab, or overridden on this DRP's Review Assignments tab. Once submitted it is read-only; to change it, press "Reopen to edit", which cancels the round and returns it to In progress.

Tips

  • "Export CSV", at the top of the page, downloads this table as a spreadsheet file — handy for sharing it with someone who works in Excel.
  • Make objectives measurable where possible (a percentage, a time saved, a cost avoided) — "reduce processing time by 30%" is checkable, "improve efficiency" isn't.
  • Every requirement should trace back to at least one objective here — the Traceability Matrix module checks exactly this.