The meeting ended with a sentence everyone in the room understood immediately: the tiered pricing model launches next quarter. The question had hung between other topics for three weeks. Now, in one focused conversation, it was settled. The room closed, the way every Grounds Up room does, and the meeting record appeared automatically as a markdown file, ready to download.
What happened over the next few hours was easy to miss, because it was so unremarkable: five people downloaded five separate copies of the same file. The product manager added hers to her own notes. The engineer dropped his into his personal repo as a reference for the sprint. Someone from support fed theirs into their own AI tool to draft an internal FAQ. Nobody had to ask whether that was allowed or where the file lived. It belonged equally to everyone who had been in the room.
A decision is not yet an action
The record answered what had been discussed and decided. What happened next was still an open question. A decision from a meeting rarely moves on its own. Without a concrete next step, it stays a good idea on a list.
For smaller decisions, that step is usually direct. The product manager updated the pricing page in draft mode that same day, ready for approval. For bigger decisions that play out over weeks, one action isn't enough on its own. That's exactly where OKRs fit: a goal with a measurable key result that a team tracks over a longer stretch of time.
From meeting to cockpit
The pricing decision was exactly that kind of case. The one line from the record turned into a goal: launch the tiered pricing model, with the share of new customers on the tiered plan after six weeks as the key result. Someone logged that goal in Startup Business Cockpit, alongside the other running goals the team already tracks there.
From there, the goal resurfaced every week at check-in, with its current status and trend. Six weeks later, the number confirmed it: a third of new customers had chosen the tiered plan, well above what anyone had expected at the start.
Why it worked
The record gave everyone on the team something of their own to work with right away. The goal in the cockpit gave the one decision that mattered a place to stay visible. Together, that built a chain running from one good conversation to a measurable number six weeks later, without anyone having to keep a separate record in between.
What remained once the room closed turned out to be simple: five copies of a file, each put to its own use, and a permanent place in the Startup Business Cockpit, where the decision did not remain in the record but became part of how the company is run.
Which of your next decisions deserves that same path, from record to key result?