OKR

Objectives and key results: a goal-setting framework pairing a qualitative objective with measurable outcomes that prove it was reached.

OKRs are goals with receipts. An Objective is the qualitative destination, ship a support experience customers praise. Key Results are the measurable proofs, first-response time under two hours, CSAT above 4.6, ticket deflection at 30 percent via self-service. The pair is scored at the end of the cycle, typically quarterly, against the numbers, not the narrative. The method came from Intel's Andy Grove, was scaled by Google, and survives because it forces the fuzzy word to be falsifiable.

Why it matters to an indie builder: solo and tiny teams drift, not from laziness but from the absence of anyone asking what did this month prove. OKRs are that colleague, cheap. Written quarterly, reviewed weekly, they convert a backlog into a bet with defined success, and the discipline of three key results instead of thirteen is itself the strategic act: choosing what not to attempt this quarter.

A concrete example: a founder's quarter reads, Objective: make the free trial a reliable growth engine. KRs: trial-to-paid from 3.2 to 6 percent, time-to-first-value from 11 minutes to under 3, activation, defined as first project created, from 41 to 60 percent. Six weeks in, KRs two and three are green, KR one is flat, and the diagnosis is honest and early: activation improved but the upgraded cohort does not convert at the old rate either, pointing at the pricing page rather than onboarding. The quarter ends with one KR missed and the next quarter's objective already written by evidence instead of mood.

Common mistakes: key results that are tasks in disguise (redesign onboarding is activity; activation at 60 percent is an outcome), ten objectives, which is a backlog with formatting, commitment-level sandbagging versus aspirational moonshots blurred into one mush (pick a type per OKR and say which), setting and forgetting, OKRs reviewed only at quarter's end are a diary of failure, weekly is where they pay, and bolting OKRs onto individual compensation, which converts honest stretch targets into negotiated minimums and kills the information value. The kpi entry covers the metric layer; the productivity blocks on IndieBoot hold the tracking tools.

Progress toward OKRs is often tracked on a scale (e.g., 0.0 to 1.0 or 0% to 100%) to show how much of each key result has been achieved.