OKR Planning: How to Understand if Your Team Has Enough Capacity

Setting ambitious OKRs is essential for growth, but they are only as powerful as your ability to execute them. Without a clear understanding of your team’s capacity, even the most inspiring goals can become sources of frustration and burnout.

Now, you might think the answer is to dream smaller — but that’s the quitter’s talk. Instead, you need to learn how to plan smarter.

When hundreds of employees and dozens of departments are working towards a common goal, the risk of failure grows exponentially. Misaligned timelines, inconsistent tracking, and communication silos can dismantle a project piece by piece, leading to scope creep, delays, and mismanagement.

The solution is to create a seamless link between your high-level strategy and your on-the-ground resource planning. And if you are using Jira, you can automate this by using two Jira apps together:

• Oboard for Jira allows you to define, track, and align your company’s objectives directly within Jira. This ensures your strategic “why” is visible to everyone, guiding every decision and task.
• Activity Timeline gives you a real-time view of workloads and resource availability. This provides the crucial “how,” ensuring your ambitious goals are backed by a realistic, data-driven plan.

But talk is cheap — so let me show you how they work in practice to improve your team's productivity. To do this, I will walk you through the entire process of setting up a Department-level OKR, attaching Jira work items to it, and then using ActivityTimeline to assess the team’s capacity and see how much it will take to complete an OKR.

Step 1 — Establish Your OKRs

OKRs consist of Objectives + Key results.

Objective is a big, ambitious goal that you want to achieve. It should come from your project’s Vision and Mission statement and represent the goal of your work for the next OKR cycle.

Key Result is a metric used to measure your progress toward achieving the Objective. While Objectives can be abstract, Key Results should always be represented by hard numbers — a.k.a. be measurable, clear, easy to understand, and actionable. If you are familiar with SMART Goals, the requirements are very similar.

Finally, Objectives and Key Results are about change. If something is already working, then keeping it as is or even slightly improving it should not be an OKR — it does not require much additional effort or extra motivation. For example, if you are already selling 500 software licenses per month, selling 510 is not exactly ambitious. Selling 700, however, is a worthy goal to rally your team around.

So, to sum it all up — OKRs should be clear, measurable, ambitious, yet attainable. For our example, we are going to create an OKR for a Product team in an average SaaS company.

• [Objective] Enhance the user’s file export experience
• [KR1] Reduce the time to generate a report export from 10 to 5 seconds
• [KR2] Implement PDF and PNG export formats
• [KR3] Decrease support tickets related to “export issues” by 50%

This is what our newly created OKR looks like in Oboard:

NOTE: While traditional OKR methodology favors metric-driven outcomes, KR2 (“Introduce 2 new export formats”) is an initiative-based Key Result. This binary “done/not done” approach is common and favored among Product and Engineering teams. It provides an unambiguous target for a critical deliverable, which is often clearer for the team than forcing the work into an artificial metric. To learn more about setting OKRs and the common pitfalls involved, check out How to Write OKRs.

Link Objectives to Execution

The key aspect of Oboard is its ability to connect Jira Work Items and OKRs, directly tracking strategic goal completion as it is being executed. Going back to our OKR, let’s focus on the KR2 and break it down into Jira Work Items under the “PDF & PNG EXPORT” Epic.

This is what I ended with:

• [Task] Investigate and select 3rd-party libraries for PDF generation and PNG rendering
• [Task] Design UX/UI for new export flow
• [User story] As a user, I can export my report as a PDF
  - [Task] Implement the backend service to convert report data into a PDF document
  - [Task] Integrate the PDF service with the front-end export menu
• [User story] As a user, I can export my dashboard as a PNG image
  - [Task] Implement the backend service that renders the dashboard and captures it as a PNG file
  - [Task] Integrate the PNG service with the front-end export menu
• [Task] Create and execute a QA test plan for new export formats
• [Task] Update Help Center documentation with instructions for PDF & PNG exports

And this is what it looks like on the Jira board, with preliminary task assignments for team members:

NOTE: We are using the User Story format for two of those items to better showcase the use case and improve clarity for the developers working on those tasks. You can also use normal Tasks. It doesn’t change much mechanically, but this is the preferred approach for customer-facing issues.

Now that we have this Epic, we can attach it to our Key Result in Oboard, which will allow us to track the Key Result progress automatically:

Now that our Oboard and Jira integration is set up and we have both an OKR and a list of Work Items directly affecting it, let’s see how much it will take to achieve our KR2 in Q4. To do this, we will need Activity Timeline.

Assess Your Resources

Tool: ActivityTimeline

Get Margo Sakova’s stories in your inbox

Join Medium for free to get updates from this writer.

Remember me for faster sign in

Setting ambitious OKRs is one thing; ensuring your team has the capacity to deliver is another. ActivityTimeline transforms your Jira environment into a visual dashboard for team capacity, making it easy to see who’s overutilized, underutilized, or is working just right. It’s a great tool that you can use to quickly assign OKR-related tasks to the team and ensure that their completion within the timeframe is feasible. However, first, it needs to be able to access Oboard data.

How to connect Oboard, Jira, and Activity Timeline

To connect Oboard, Jira, and Activity Timeline, we will use JQL (Jira Query Language) to quickly filter OKR-related issues. You can reference the Oboard JQL documentation here.

You can also check out our video which guides you through the JQL features available in Oboard itself:

https://www.youtube.com/watch?v=Ep0gnFb1YTg

For this example, I will be using a very simple JQL request: OKRparentTitle ~ “Introduce PDF and PNG export formats”.

Do include the quotes — it won’t work without them. The request lists all work items linked as children of the parent OKR named “Introduce PDF and PNG export formats”. Other filtering options include OKR ID, OKR Cycle, OKR Parent Owner, and other OKR data points.

NOTE: ActivityTimeline’s JQL search feature is in the “Extra” tab of their Planner

Now, let’s add some context to our KR and say that the team wants to focus on it during September/October of 2025 — this will give them more freedom to deal with less-defined OKRs later in the quarter. With that, you can start dragging the filtered Work Items out onto the Planner and adding estimates to them, ending up with something like this:

Our initiative will be kicked off by Damian, who is responsible for finding the most suitable tool, and Klaus, who will devise the best methods for testing our results. Viktor will be needed to create the new UI/UX. The back-end implementation will be handled by Daniel, who will work in tandem with Margo, who is responsible for front-end development. Finally, upon completion, Nikita will write the documentation for the new export tools.

ActivityTimeline’s Planner assesses each team member’s capacity and assigns them a weekly capacity score, as indicated by colored marks under their names. If you hover your cursor over that name, you will see a more detailed breakdown that shows the estimated workload. For example:

With that, you can easily see that Damian and Klaus will be available for non-OKR-related tasks (or maybe even other OKRs) after the first week of September, while Daniel probably shouldn’t be bothered until the month ends. Viktor will need to create a UI/UX design during week 2, but it won’t take him long. Margo will be partially engaged for a few weeks, but could take on more work overall. Nikita will need some time to work on the documentation in October, but is otherwise available. Finally, James is not involved in this particular OKR execution and is available for any work that pops up.

This turns long-term capacity planning from a guessing game into a more data-driven process. Of course, it still doesn’t account for abnormal situations or irregularities, but it should be enough to quickly highlight priority tasks and see how many resources they will need.

Track Progress and Performance

Now that you have your strategic goals and the priority tasks attached to them, you just need a way to track both your progress toward them and the cost to your team of achieving that progress. This leads us to the reporting tools provided by both Oboard and ActivityTimeline.

For Oboard, it is the OKR module in Oboard’s Custom Dashboard. It’s a tool that lets you highlight the OKRs you want to give special attention to, and keep them in front of you 24/7.

Now, let’s simulate the work process and move some of our Jira tasks into the “Done” column. Like this:

Our Dashboard will automatically reflect the change and update your progress toward the OKR in real time. So around the end of the first week, this is what you should be looking at:

Of course, our example uses simplified data, just to give you the idea of how everything works. Real-world Custom Dashboards will contain more data, additional context, and possibly KPIs that have recently become available in Oboard tools. These Dashboards are, essentially, the command center for your team’s strategy — and this is what they look like:

On the execution side of things, ActivityTimeline provides you with the Resource Utilization Forecast. It shows how your team is spending their time, broken down by task, team member, or project. You can also use filters to quickly check how many resources are being spent on different projects. The reports are available for different timeframes — from a week to a quarter. For example, this is what the RUF based on our example team looks like:

Once again, that is just sample data — in real-life teams, with a lot more work planned, you will end up with something like this:

Together, the Oboard Custom Dashboard and ActivityTimeline’s Resource Utilization Report provide a complete picture of your strategic execution. The Oboard dashboard answers the question, “Are we on track to meet our goals?” by showing real-time progress against your OKRs. ActivityTimeline’s report then answers the crucial follow-up question, “Why?” by revealing exactly how your team’s time and resources are being invested.

This dual perspective is far more powerful than what standard Jira tools offer. It transforms your management style from reactive to proactive, enabling you to:

• Identify potential bottlenecks before they derail projects.
• Understand the true cost of strategic initiatives.
• Make data-driven decisions to reallocate resources for the greatest impact.

It’s a new level of insight — connecting high-level strategy directly to daily execution — that gives you the tools needed to turn your goals into achievements.

Conclusion

Achieving ambitious goals doesn’t happen by accident. It requires a deliberate fusion of high-level strategy and on-the-ground execution. As we’ve demonstrated, the gap between a well-defined OKR and its successful completion is often a failure to account for team capacity. By abandoning guesswork and embracing a data-driven approach to resource planning, you can transform your strategic process from a source of stress into a predictable engine for growth.

By integrating Oboard and ActivityTimeline within Jira, you create a single source of truth that connects your “why” to your “how.” This setup provides the clarity needed to not only set ambitious goals but to pursue them with the confidence that they are both challenging and, most importantly, achievable. It allows you to stop choosing between ambition and realism and start building a system that delivers both.

Try OKR Board for Jira (free for 30 days) or use it free for up to 10 users

Try ActivityTimeline for Jira for free during a 30-day trial period

Feel free to ask any clarifying questions in the comments 🤗