> For the complete documentation index, see [llms.txt](https://portavi.gitbook.io/portavi-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://portavi.gitbook.io/portavi-docs/strategy/objectives-and-strategy.md). # Objectives and strategy reviews Objectives are what a portfolio is trying to achieve. Strategy reviews are the rhythm of checking whether it is. **Strategy** in the sidebar gathers both across the whole workspace. It has three tabs (**Strategy Map**, **Objectives** and **Reviews**) over a row of figures that stays put as you switch between them, so the totals are always the same totals. Clicking an objective on either of the first two (a card in the list, or a column heading on the map) opens it in full, read-only: its key results, its progress across past reviews, and what is contributing to it. **Reviews** lists every completed strategy review in the workspace, newest first and grouped by portfolio. Each row is the date and three counts (how many were in the room, how many objectives were reviewed, and whether any coverage gaps were found) so a year of reviews stays scannable. Click one to see it in full: every objective it covered with the status and the figures it stood at **on that day**, the committee by name, the gaps by entity, and the decisions as written. Those numbers are the snapshot's own; they do not move when the objective does, which is what makes a review worth keeping. It is a read-only register here; correcting a review is done on the portfolio that held it, from the same panel's ⋯ menu.

{% hint style="info" %} Objectives and the strategy map used to sit on the **Governance** page. They now have their own page. Governance keeps the three registers (risks, lessons and benefits) that record what happened; Strategy is about what you are trying to make happen. {% endhint %} ## Objectives Each portfolio defines its own objectives, managed from its **Overview** tab.

An objective has: * **Title**: the outcome being pursued * **Description**: optional * **Target date**: one date for the objective, shared by everything under it * **Status**: not started, on track, at risk, or achieved * **Key results**: what you actually measure. Any number, including none You can also create one without leaving the Overview dashboard: **+ Create → Objective** opens the same form with a portfolio picker at the top. An objective's card also credits whoever logged it, with their role colour on the avatar; selecting the credit opens their [profile](/portavi-docs/tracking-delivery/member-profile.md). {% hint style="info" %} Objectives created before this was added carry no credit. Portavi did not record an author for them, and it will not guess one: a name against words someone may not have written is worse than no name at all. {% endhint %} ## Key results An objective states an outcome; a key result is the number that says whether you got there. Each one has a title, a **start value**, a **target value**, an optional **current value**, a unit, and a **weight**. How many you add changes how the objective reads: * **One**: the ordinary case. The objective's bar is that key result's bar, showing its current value against its target. * **Several**: an OKR. The objective shows a rolled-up percentage, with each key result listed beneath it at its own percentage. * **None**: a qualitative objective. No bar at all; it tracks by its status alone. Use this when the honest answer is "done or not done" rather than a number. ### How progress is calculated Each key result's progress runs from its start value to its target, not from zero: ``` progress = (current − start) ÷ (target − start) ``` {% hint style="info" %} This is why "reduce churn from 20% to 5%" reads correctly. Measured from zero it would look 400% complete at the start; measured from its own baseline it correctly reads 0%. {% endhint %} The objective's own progress is the **weighted average of its key results' percentages**, not a total of their values, which would be meaningless when one is measured in percent and another in signups. ### Weight Weight is **1, 2 or 3**, and it is how many times a key result counts in that average. Leave it at 1 unless one key result genuinely matters more than the others; the weight only shows on the card when it is above 1, so a list of evenly weighted key results stays quiet. Three choices rather than a free number is deliberate. A weighting anyone can argue about is a weighting nobody maintains. ### On track or behind You set the **status** on the objective; that is a human judgement and stays yours. Each key result's health is worked out for you instead, by comparing how far it has come against how much of the objective's time has gone: * **Achieved**: it has reached its target * **On track**: its progress is at or ahead of the share of time elapsed * **At risk**: it is behind that line Each key result's bar is coloured to match, so the bar and the badge beside it always agree. {% hint style="info" %} An objective with no target date gets no verdict on its key results: just a percentage. There is nothing to pace against, and a guess would read as a fact. {% endhint %} Key results have no dates of their own. They share the objective's target date, which is how OKRs are normally set: a quarter's key results are judged against that quarter. ## The strategy cycle Each portfolio has a **strategy cycle** in months, how often it should be formally reviewed, set when you create it and changeable from its edit modal. The portfolio shows a countdown to the next review. When the cycle is up, the **Strategy review** action unlocks. ## Running a strategy review **New review** on the portfolio's Reviews tab opens a five-step wizard. It walks the current state of each objective, asks you to record where things stand, and saves a **snapshot**. The steps run across the top of the dialog; select a completed step to go back to it. Snapshots build a history: what you believed at each review, so you can see how a portfolio's strategy has moved over time rather than only where it is now. ### Step 1: Review and committee The date of the review, and who was in the room. The committee is a record of who agreed the conclusions, not a permission list; it does not change who can edit anything.

### Step 2: Update objectives Every objective in the portfolio, and under each one a box for every key result: its start value, its target, and where it stands today. Set the objective's status alongside the numbers: the values say what happened, the status says how you read it.

### Step 3: Coverage gaps Any programme or project contributing to no objective at all. This is the step that catches strategic drift: work that is running, and being paid for, with nothing tying it to what the portfolio said it was for. A clean pass says every programme and project contributes to at least one objective.

### Step 4: Decisions What changes as a result. A decision recorded here is attached to the review, so the next one opens with the last one's decisions visible rather than relying on anyone's memory. Each one also goes into the [decisions log](/portavi-docs/governance/decisions-log.md) on Governance, dated the review.

### Step 5: Confirm Everything above in one summary before it is written: date, committee, objectives with their new key result values, and the decisions taken. Publishing fixes the snapshot; the next review starts a new set of numbers rather than overwriting these. {% hint style="info" %} Reviews recorded before key results existed hold a single figure per objective rather than one per key result. They are left exactly as they were (rewriting them would put numbers in a record nobody actually took) so an objective's chart may start with points from the old shape and continue with the new. {% endhint %}

Past reviews are listed on the portfolio, each openable. ## The Strategy Map **Strategy → Strategy Map** plots programmes and projects against portfolio objectives: which work contributes to which outcome, and, more usefully, which objectives have nothing working towards them.

Rows are your programmes and projects, grouped by portfolio; columns are that portfolio's objectives. A filled dot means the row contributes to that objective; a dashed outline means it does not. A row that contributes to **nothing** is marked with a red edge and a **Not mapped** chip. That is the reading the map exists for: work that is running, and being paid for, with nothing tying it to what the portfolio said it was for. {% hint style="info" %} A project's contribution is usually inherited rather than declared. Projects contribute through the programme benefit they deliver, so linking a project to a benefit is what puts it under that benefit's objectives. {% endhint %} ### The figures above the tabs * **Objectives**: how many exist, with a bar splitting them by status * **Programmes & projects**: how many components are in scope * **Contributing**: how many map to at least one objective * **Not mapped**: the rest, which is the number to drive down ### If Strategy is locked Objectives live in portfolios, and portfolios are a Growth and Enterprise feature, so on Starter the whole Strategy page is locked, both tabs. The page and its sidebar entry stay where they are and say what is missing, rather than disappearing. ## Who can edit A portfolio's owner or a PMO manager. Portfolios can only be owned by a PMO manager or portfolio manager: the narrowest owner set of the three tiers. ## Objectives from your goals tool An objective can be written in Portavi or mirrored from a goal in a connected tool. Jira connections offer **Atlassian Goals**, Asana offers **Asana Goals**, ClickUp offers **ClickUp Goals**, MS Planner offers **Planner Goals** (progress there is the share of a goal's linked tasks completed, since Planner goals carry no metric), and **Tability** connects on its own (with a personal API token and your Tability workspace ID, under Integrations → Add integration → Goals / Objectives; it needs a Premium Tability workspace and a Tability user with API access enabled, see [Project management tools](/portavi-docs/connecting-your-tools/project-management-tools.md#tability-connects-with-a-token)); the source row in the objective form and in the portfolio wizard lists whichever are connected, beside **Manual**. A mirrored objective takes its title, description, status, dates and key results from the tool and refreshes them on every sync; the portfolio page shows when that last happened and has a **Resync** button. Contributors are still set in Portavi. To edit a mirrored objective's own fields, **detach** it from the edit form: it keeps its current values and stops refreshing. {% hint style="info" %} Reading goals needs one extra permission on Jira and Asana. A connection made before this existed shows **Reauthenticate** on the Integrations page the first time goals are requested; approving again is all it takes. {% endhint %}