Goals

Initiative and workspace goals, the five goal types, key results, and how goals steer document generation.

Goals tell ForceVue why you are building something, not just what. ForceVue reads your goals when it generates, so a document stays pointed at the outcomes you actually care about.

Adding a goal

  1. Open an initiative and go to the Goals tab (or use workspace goals for outcomes that span the whole workspace).
  2. Add a goal.
  3. Choose a goal type, give it a title, and optionally add a description and a measurable key result.

Goal types

There are five goal types:

TypeUse for
Business OutcomeThe business result you want, for example revenue, retention, or cost
User OutcomeThe change you want for users, for example faster onboarding
Success MetricA specific number that tells you it worked
ConstraintA boundary the work must respect, for example a deadline or budget
GeneralAny other goal that does not fit the above

Key results

A goal can carry a measurable key result: the number that tells you whether you hit it. Adding key results makes your goals concrete and gives the AI a clear target to write toward. You can also add a baseline, a timeframe, and a priority.

Initiative goals vs workspace goals

  • Initiative goals are the outcomes for one product effort.
  • Workspace goals are outcomes that apply across the workspace, the higher-level objectives your initiatives roll up to.

How goals steer generation

When ForceVue writes a document, it reads the relevant goals and keeps the draft aligned with them. A PRD generated against a clear set of outcomes reads differently from one generated with none: it justifies decisions against the goals and frames work around the results you want. Some document types, like OKRs and the business case, lean on goals especially heavily.

Adding a goal or two before you generate is one of the cheapest ways to improve a draft. See How generation works.

Where to go next