Fieldnote, a farm records app

OKR progress slide example with two objectives and six key results

An OKR progress slide is a status document, not a plan, so every row has to carry a current figure against a target and a word that says how it is tracking. This one belongs to Fieldnote, a fictional farm records app, at the end of week nine of a thirteen week quarter.

Create a presentation with OneCraftOne 1920 × 1080 slide on the Metrics: OKR Tracking Table layout

FIELDNOTE

OKR Progress, Q3

Objective	Key Result	Progress	Status
Grow paid farms	412 of 600 paid farms	69%	On track
Grow paid farms	Trial to paid 24% of 30%	80%	On track
Grow paid farms	Annual churn 2.1% of 1.5%	71%	At risk
Cut support load	First reply 4.6h of 4h	87%	On track
Cut support load	Tickets per farm 1.9 of 1.2	63%	Behind
Cut support load	Help centre 41 of 60 guides	68%	On track
Measured at the end of week 9 of the 13 week quarter

The finished slide as it renders, built on the Metrics: OKR Tracking Table layout.

What is on the slide

Headline: FIELDNOTE above OKR Progress, Q3, with the caption noting week nine of the thirteen week quarter.
Objective one: Grow paid farms: 412 of 600 paid farms at 69% on track, trial to paid 24% of 30% at 80% on track, annual churn 2.1% against 1.5% at 71% at risk.
Objective two: Cut support load: first reply 4.6 hours of 4 at 87% on track, tickets per farm 1.9 of 1.2 at 63% behind, help centre 41 of 60 guides at 68% on track.
Columns: Objective, key result, progress and status, with the narrative columns given the width and the two short columns kept tight.

When this is the right slide

A tracking table is right at mid quarter, when the audience already agreed the objectives and now needs to see which key results are moving and which are not.

What to swap it for

Grouping: OKR Two Objectives. Swap to the two objective planning layout when the meeting is about setting or explaining the objectives rather than reporting progress against them.

What this slide shows

The slide is a four column table under an eyebrow and a headline. The eyebrow reads FIELDNOTE and the headline reads OKR Progress, Q3. The columns are objective, key result, progress and status, and the column widths are weighted so the two narrative columns get the room and the two short ones stay tight. Six rows follow, three under each objective. Under grow paid farms: 412 of 600 paid farms at 69% and on track, trial to paid conversion at 24% against a target of 30% at 80% and on track, and annual churn of 2.1% against 1.5% at 71% and at risk. Under cut support load: first reply time of 4.6 hours against 4 at 87% and on track, tickets per farm at 1.9 against 1.2 at 63% and behind, and 41 of 60 help centre guides published at 68% and on track. A caption under the table records that the reading is at the end of week nine of a thirteen week quarter, which is what makes the progress percentages interpretable.

Who this slide is for and when to use it

The audience is the team that owns the objectives plus whoever they report to, at a mid cycle check in. Everyone in the room has seen the objectives before, so the slide spends none of its space justifying them and all of it on movement. Used at the start of a quarter it would be empty, and used at the end it would be a scorecard rather than a check in. The other limit is size. Two objectives with three key results each fits comfortably; four objectives with five key results each does not belong on one slide at all, and the usual fix is one slide per objective with the key results as rows and the owner named.

How to adapt it

First, set a rule for the status word before the slide is built, so that on track, at risk and behind mean the same thing every quarter. A common rule is that a key result is on track when progress is within ten points of the elapsed share of the quarter. Second, add an owner column only if the table stays readable; this layout takes four columns, so an owner column would have to replace progress, and progress is usually the one the room asks for. Third, change the unit in the key result column to match what the team actually tracks, and write both figures in the same unit. Where lower is better, put the current figure first and the target second so the direction stays consistent with every other row. If the meeting is about agreeing next quarter's objectives rather than reporting on this one, leave the table behind and use the two objective planning layout, which gives each objective a panel and room for its key results to be discussed one at a time.

What makes this slide work

Every key result carries both numbers

The key result column reads 412 of 600 paid farms rather than 69%, so the percentage in the next column can be checked rather than believed. Two of the six rows are measures where lower is better, churn and tickets per farm, and writing them as 2.1% of 1.5% makes the direction obvious without a separate legend or an arrow.

The status column is allowed to say behind

One row says behind and one says at risk. A slide where all six rows say on track tells the reader that the targets were soft or that the status is decorative. Because the words come from a fixed set of three, a reader can scan the last column alone and know where to spend the meeting.

The objective repeats so the rows can be scanned

Grow paid farms appears on three consecutive rows and cut support load on the next three. That repetition costs a little ink and saves the reader from tracking a merged cell across a table, which matters when the slide is read from a phone or on a projector at the back of a hall.

Questions people ask

How many objectives should an OKR slide show?

Two or three, with no more than three key results each. This slide shows two objectives and six key results, which fills a four column table without shrinking the type. A team with six objectives has a planning problem rather than a slide problem, and splitting them across slides hides it rather than solving it.

What is the difference between an OKR slide and a KPI slide?

An OKR slide shows progress towards something chosen for this quarter and ends when the quarter does. A KPI slide shows the standing health of the business and never ends. That is why this table carries a target in every row, while a KPI wall carries a figure and a direction and no target at all.

How do you show a key result where lower is better?

Write the current figure first and the target second, in the same unit, as this slide does with churn at 2.1% of 1.5% and tickets per farm at 1.9 of 1.2. The reader sees both numbers and reads the direction from them. Arrows and colour coding tend to conflict with the status column and add a second thing to interpret.

Should progress be a percentage of the target?

Usually, and it should be read against how much of the quarter has gone. The caption here records week nine of thirteen, which is 69% elapsed, so a key result at 69% is exactly on pace. Without that caption every percentage on the slide is ambiguous, because 69% at week two and 69% at week twelve are different stories.

When should this become two slides?

When a key result needs discussion rather than reporting. If the churn row is going to take ten minutes, give it its own slide with a trend chart and leave the table to summarise. A table is a scanning device, and a room that stops to argue about one row has stopped scanning and needs a different layout for that argument.

Is it acceptable to show a key result as behind?

It is the point of the meeting. A slide with six on track rows produces no decisions and quietly teaches the team to set safe targets. Marking one row behind and one at risk directs the discussion to the two rows that need it, and gives the people who are on track their credit in one glance.

Build your own in about a minute

The button below opens the generator with this use case already described. Change the wording to match your own, generate, then edit anything you like.

Make one like this

Sources

Written and checked by the OneCraft team. Last checked 20 September 2026.