An OKR recap post is the most-read OKR post of the quarter. After thirteen weeks of progress updates, the audience reads the recap to find out which objectives shipped, which slipped, and what the team learned. The post body carries that breakdown in detail, often with charts and per-objective writeups. The share image rarely matches the gravity of the post because it is the same banner the team has been using for every weekly update. SleekPixel handles the case with a dedicated recap preset that signals the quarter close visually.

The setup uses three custom fields: quarter for the corner mark like Q2, final_pct for the headline final progress percentage, and objectives_delivered for an optional subhead detail like '2 of 4 fully shipped.' The accent is a slightly deeper purple than the weekly OKR update preset to mark the recap as distinct from the in-flight updates. The card is square at 1200 by 1200 to fit LinkedIn and stack visually with the weekly cards.

The post body carries the full per-objective recap, the lessons learned, and the carry-forwards into the next quarter. The card carries the headline data and signals the quarter close. Over multiple quarters, the recap cards line up as the structural milestones in the team's OKR history, with the weekly cards filling in between them. The two-tier visual hierarchy (weekly card vs recap card) makes the quarter close immediately recognisable.

Public OKR programs build trust over many quarters, but the trust crystallises at the recap. The weekly updates establish the cadence; the recap proves the team can close out what it committed to. Stakeholders read the recap with a different attention than they read the weekly updates, because the recap is the moment when the quarter's promises are reconciled against the quarter's reality.

The share image has to match that attention. A recap that ships with the same banner as week three has nothing to signal the close, so the audience does not realise they should be reading more carefully. SleekPixel solves this by making the recap card visually distinct.

The accent is deeper, the final progress percentage is in the subhead, and the objectives-delivered count is in the footer. The corner mark stays Q2 to anchor the card in the quarter, but the rest of the layout signals 'this is the close, not another in-flight update.' Over multiple quarters, the recap cards become the structural milestones in the team's OKR history. A candidate browsing the team's blog sees four recap cards from the previous year, each marking the end of a quarter with a final percentage and a number of shipped objectives.

That visible track record is more convincing than any single post because it shows the cadence sustained over time. SleekPixel makes the track record almost free to maintain because the recap card composes from the same kind of custom fields the weekly cards use, which means the team can sustain the program for years without ever asking a designer to draw a quarter-close graphic. The cadence and the visual record reinforce each other indefinitely, which is the architecture that public OKR programs need to actually pay off.