Planning next quarter’s goals
Testimonial KPIs for Quarterly OKRs
A testimonial goal tends to reach the OKR sheet as a single line: collect 50 testimonials. It is easy to hit and says nothing about whether buyers saw proof that answered their doubts. A good key result names a change you can read from real data at the end of the quarter, from a starting point you wrote down at the beginning. Open your draft, run it through the scorecard below, and rewrite the lines that score low.
- Grades a drafted objective and key results
- Flags counts that are easy to game
- Ties each key result to a data source
The problem, solved
Why testimonial OKRs go wrong, and where the numbers come from
Our key result is just a count
Fifty testimonials can be fifty one line ratings from your happiest segment. The number is met and nothing changes on the pages that matter.
With StoryProof: Analytics show how many testimonials you collect, their ratings, where they come from and how often you approve them, so a key result can track quality and source alongside volume.
We never wrote a baseline
At review time nobody can say whether a figure went up, because nobody recorded where it started.
With StoryProof: An analytics dashboard is on every plan. Note this quarter’s starting figures from it on the day the OKR is set.
Collected proof is never seen
The team hits its collection target while the widgets that hold the proof sit on pages few visitors reach.
With StoryProof: The dashboard ranks your widgets by views, so one key result can be about proof being looked at, not only gathered.
Every testimonial comes from one channel
A goal met entirely through one form or one imported platform leaves the rest of the funnel without proof.
With StoryProof: The sources chart splits your testimonials by where they arrived from, which makes a mix target measurable.
Nobody notices a target was reached
A milestone passes in week five and the team keeps pushing the same lever for seven more weeks.
With StoryProof: From Pro, an automation can start when your average rating crosses a threshold or you reach a review count, and notify the team.
Flip the switch to see how StoryProof handles each one.
OKR draft scorecard
Score your testimonial OKR before the quarter starts
Have your drafted objective and key results in front of you. Answer for the set as a whole: yes if every key result meets the criterion, partly if some do.
Your answers stay in this browser tab. Nothing is saved or sent.
Weak lines and stronger rewrites
Each weak line is the kind that reaches an OKR sheet. The rewrites show the shape, not your numbers.
An OKR set in this shape
Illustrative sample, not a StoryProof customer
Objective: buyers comparing plans see proof from a company like theirs.
Key result 1: approved testimonials from mid sized companies go from the baseline on day one to the agreed target, read with a segment tag filter.
Key result 2: the pricing page widget is the most viewed widget in the dashboard ranking by the last week of the quarter.
Key result 3: no more than an agreed share of new testimonials comes from a single source in the sources chart.
- Owner, KR 1
- Customer marketing lead
- Owner, KR 2
- Web lead
- Owner, KR 3
- Customer marketing lead
- Mid quarter check
- Week six
In StoryProof
Pull baselines and progress from StoryProof
- You will need
- Your drafted OKR
- Segment tags on testimonials, if a key result is about a segment
- Your OKR sheet or tool
- 1
Record day one figures
Open the analytics dashboard and note collection count, ratings, source mix and approval figures beside each key result.
- 2
Count segments with tag filters
Filter by the segment tag in the library to count testimonials for a segment key result. Export a CSV if you need the figures in a spreadsheet.
- 3
Check proof in use
Read the widget ranking by views and the sources chart at the mid quarter check.
- 4
Get told when a target lands
Set an insight automation on a review count or rating threshold that notifies the owner of that key result.
What happens next: At the quarter end, score each key result against the figures you recorded, and carry the baselines into next quarter’s draft.
Before you start
What these numbers will not tell you
No revenue attribution
StoryProof analytics do not tie a testimonial to a sale. A revenue key result needs your own analytics or CRM.
Snapshot, not history
Keep your day one figures in the OKR sheet. This page does not claim the dashboard stores quarter by quarter snapshots for you.
Segments need tags
A segment key result can only be counted if testimonials are tagged by segment when they are approved.
Alerts need automations
Insight triggers and team notifications are part of Pro. Without them, check progress at a set weekly time.
FAQ
Questions people ask
Short answers to what usually comes up next.
Should a testimonial goal be an objective or a key result?
If proof is a main focus this quarter, give it an objective of its own. If it supports a bigger goal such as pricing page conversion, make it one key result under that objective.
Is the number of testimonials a bad key result?
Not on its own terms, but it is easy to hit without improving anything. Pair it with a line on mix, segment or use so the count cannot carry the whole OKR.
What target should we set?
Start from your own baseline and what one more quarter of effort could realistically move. Copying a target from another company tells you nothing about yours.
How is this different from tracking testimonial KPIs?
KPIs are the steady health figures you watch every month. An OKR picks the one or two of those you will deliberately move this quarter and sets a target for them.
Still have a question? Ask the StoryProof team or book a demo.
Set a testimonial OKR you can actually score
Read your baselines from the dashboard today, write three key results with sources and owners, and check them mid quarter.
Last updated 2026-11-20.