Projects vs Activities vs Key Results

Ask five people on a team to define "Project," "Activity," and "Key Result," and you'll likely get five different answers, often with the words used interchangeably. That's a problem, because each one plays a different role in getting work done. Mixing them up is how OKRs quietly turn into a task list. This post lays out a simple way to tell them apart, and how they connect under a single Objective.

Three Different Jobs

A Key Result is a measurable outcome. It's a number that moves, and it tells you whether an Objective was actually achieved, not just worked on. "Increase trial-to-paid conversion from 12% to 18%" is a Key Result.

An Activity is a recurring or ongoing action that contributes toward a Key Result, without a fixed end point of its own. "Run weekly customer interviews" or "Publish two blog posts a week" are Activities. You keep doing them for as long as they're useful.

A Project is bounded work with a defined scope and an end date. It has a beginning, a middle, and a finish line. "Redesign the pricing page" or "Migrate to a new billing provider" are Projects. Once it's done, it's done.

The Test That Separates All Three

Ask two questions about anything on your plate. First: does this have a natural finish line, or does it just keep going? If it has a finish line, you're looking at a Project. If it repeats indefinitely, it's an Activity. Second, for either one: can I complete this and still fail to move the number I actually care about? If yes, and the answer to the first question was "either," you're looking at work, not a Key Result. A Key Result is the only one of the three where finishing the thing and achieving the goal are the same event by definition.

A support team can finish the Project "roll out a new ticketing system" and still leave customers waiting just as long. They can run the Activity "reply to every ticket within an hour" every single day and still not know if satisfaction is improving. Neither one proves anything about outcomes on its own, which is exactly why neither belongs in the Key Result slot. Only "reduce average first response time from 8 hours to 2 hours" does that job. This is the same trap we cover in more depth in why Activities are not Key Results.

Why the Project/Activity Split Also Matters

Most teams get as far as "don't put tasks in your Key Results" and stop there, lumping every non-outcome into one bucket called "work." That's close enough for a first pass, but the Project/Activity distinction still earns its keep once you're managing the work day to day.

Projects need a plan, a scope, and someone tracking it to completion; they show up once, get delivered, and disappear from your active list. Activities need a rhythm instead, a cadence you sustain, a habit you either keep or drop. Scheduling a kickoff meeting for a six-week Project makes sense. Scheduling a kickoff meeting for "send a weekly customer digest" does not, because there's no delivery to schedule around, only a routine to start and keep. Treating an Activity like a Project adds process it doesn't need. Treating a Project like an Activity means nobody ever declares it finished, and it lingers on lists long after it should have been closed out.

How the Three Sit Together

Under an Objective, the Key Result defines success. Projects and Activities are both means to that end, just shaped differently. Take the Objective "Become the go-to OKR tool for small consultancies," with the Key Result "grow monthly active accounts from 400 to 700." A Project supporting it might be "build a client-portfolio view for consultancies," a piece of work with a clear scope and a ship date. An Activity supporting the same Key Result might be "publish one case study a month," an ongoing rhythm with no finish line as long as it keeps working. Both matter. Neither is the Key Result. As Harvard Business Review frames the underlying distinction, outputs are what you produce, and outcomes are the difference that output actually makes. A Project is one shape of output, an Activity is another, and a Key Result is the outcome they're both meant to serve.

This is also why forcing everything into a single "initiatives" bucket makes a Key Result harder to manage. A Key Result with three open-ended Activities and one time-boxed Project underneath it needs different check-in questions for each. "Is this still worth doing?" fits an Activity. "Are we still on track to ship by the date we planned?" fits a Project. Blurring the two means you ask the wrong question of the wrong kind of work.

A Quick Way to Sort Your List

Take whatever's sitting under a Key Result right now and sort it into three piles. Anything with a number attached that defines success on its own stays out, it's not supporting work, it's the Key Result itself, or a duplicate of it. Anything with a start date, an end date, and a single deliverable goes in the Project pile. Anything you expect to keep doing on a schedule, with no natural stopping point, goes in the Activity pile. If something doesn't fit cleanly into either pile, it's usually a Project in disguise, most ongoing-sounding tasks turn out to have a natural checkpoint once you look for one.

Where This Lives in Easy OKR

Easy OKR keeps this structure explicit rather than folding everything into one generic list. Key Results carry the number that defines success. Projects and Activities both attach underneath a Key Result, but as distinct entities, one bounded, one recurring, so a team can see at a glance what's scheduled to finish and what's meant to keep running. Read more on how Projects specifically relate to OKRs in Projects vs OKRs: what belongs where.

The Bottom Line

A Key Result tells you if you won. A Project is a piece of work with a finish line. An Activity is a habit you sustain. Confuse any two of them and either your outcomes stop being measurable, or your day-to-day work stops being manageable. Keep all three in their own lane, and your OKRs stay honest while your execution stays organized.

References

• It's Not Just Semantics: Managing Outcomes Vs. Outputs — Harvard Business Review
• John Doerr, Measure What Matters (Portfolio, 2018)