Ariel Yadin _ Bazz OKR Atlassian Partner

Great poll, @Hamza_Elevatic I agree that Jira is great at tracking activity. Where things usually break is connecting that activity to outcomes. Most teams can see what’s moving, but not what’s actually impacting their OKRs. We’ve been working on this exact gap with Bazz OKR, layering on top of Jira to connect work → goals…

Hi @Ingo WenkeI get where you’re coming from, and I agree that in pure OKR theory, an Objective and a Key Result serve different purposes. That said, in practice (especially in engineering orgs), the boundary often becomes operational rather than philosophical. Using your example: “Get a ship” as a KR at the company level…

You’re describing exactly the friction we’re seeing. Even if I ignore progress aggregation entirely, I still can’t model the logical relationship between a company KR and the team-level work that actually drives it. What we’re aiming for is: Clear coverage: which teams are contributing to a specific company KR Clear…

Hey @vikram, glad the article clicked with you.

Hi @Bill Sheboy, thanks for the guidance. I appreciate it. I’ve moved the post to App Central. I’m still fairly new to the community, so I’m learning the boundaries between Community posts and App Central content. I’ll definitely keep this in mind for future posts and make sure I post in the right place. Thanks again for…

Hi @Bill Sheboy, thanks for pointing this out. I appreciate it. I’m relatively new to the community, so still getting familiar with the guidelines and where different types of posts should go. The intention here was to share some hands-on experience and lessons learned, not to post marketing content. I did reference Bazz…

That makes sense. sounds like you already have a solid prioritization flow in place. The tricky part (and what I’ve seen break in similar setups) is that once you introduce: Priority, Estimated effort, and Work already in progress, you’re basically trying to solve a capacity planning problem, not just a visibility one. The…

@Nic H_, workload distribution visibility is a real pain, but I'd push you to ask a harder question first: are you distributing the right work, or just distributing work evenly? A few things that helped my teams: * Map tasks to strategic priorities before looking at who has capacity. If a task doesn't connect to a goal, it…

@Dario Sanatkar, impressive that you got 150+ users into a custom visibility layer. That's real engineering commitment. One thing I've seen trip teams up after solving visibility: you can now see what everyone is working on, but not whether it matters. The work looks busy, the board looks full, and then quarter-end…

@Rachel Peterson, what you're describing is actually a classic OKR pattern in disguise. Your team is already thinking correctly, just missing the vocabulary.The tension you're feeling:* SLA metrics tell you if you hit a number * OKRs ask why that number matters and what outcome it drives A few things that helped us: * Map…

Hey @deseymour, this is a really common pain point, and it usually comes down to one thing: Epics don't belong to a Space, they belong to a goal. A few things that helped us get this straight: * Epics are delivery containers, not org chart boxes. If your Epic spans two teams, that's fine. That's actually the point. * The…

Hi @Blake Hall , Spot-on framing. “We held three meetings” is exactly the kind of reporting that gets CUGs defunded. One tip: tie metrics directly to the exec’s OKRs. A “30% faster onboarding” lands way differently if it connects to their Q3 goal. The gap I see is that most teams track CUGs in Jira but keep OKRs elsewhere,…

Hi @Jet , Awesome guide. That ‘Share > Publish’ tip is underrated. Leadership stops asking for updates once they have a live view. Quick note on Step 1: the Theme/Objective field only works if it’s tied to goals that leadership actually tracks. We fixed misalignment by having a single source of truth for OKRs first, then…

Hi @Daria Spizheva_Reliex_, Love your point about Jira’s tracking being “basic”. It really misses the gap between past hours and future sprint capacity. What’s helped our team: use time data as input for planning, not just reporting. When logged hours feed velocity and capacity views, developers actually maintain them…

Hi @Yuri Kudin _Release Management_, Great breakdown. You captured the swimlane issue really well. It’s usually a symptom of a deeper gap: Jira handles how work is structured, but not why it exists at the OKR level. What I’ve seen work is separating the two: treat swimlanes as a display problem, and OKR linkage as a data…

Hi @Peggy Graham, Really well put — especially the Stage 2→3 transition and how ownership starts to blur. I’ve seen the same: “one space per team” works for execution, but creates a gap at the goal level, where someone still has to connect work to company objectives. What helps is a lightweight OKR layer tied directly to…

Hi @Olha Yevdokymova_SaaSJet, This is exactly the right approach: keeping Jira as the source of truth without forcing everyone into it. I’ve seen a similar pattern work well for OKRs too: instead of pushing people into Jira or Confluence, you add a layer that connects strategic goals to Jira work behind the scenes. That…

Hi @Mariia_Domska_SaaSJet , Interesting direction, but with Jira-heavy teams the core issue remains: connecting daily work to goals is still manual. Dashboards help, but without a live OKR link, you’re back to spreadsheets. Teams that get this right treat goals as a data layer with automations tied to Jira. Atlassian Goals…

Hi @Caity Belta, The prompt library is solid, but I keep seeing the same gap with Confluence + Jira: strategy lives in Confluence, execution in Jira, and someone ends up manually connecting the dots. What’s worked better in my experience is treating OKRs as a separate layer with a proper Jira integration, rather than…

@Valeriia_Havrylenko_SaaSJet The framing here around 'lagging vs leading' indicators really resonates. Cycle time and time-in-status are genuinely useful for delivery forecasting, but there's a layer most teams miss: connecting those workflow metrics to *why* the work exists in the first place. When a ticket sits in 'In…

@Viktoriia Golovtseva _TitanApps_The gap you're describing — OKRs living in PowerPoint while actual work happens in Jira is real, and the 'repurpose epics as goal containers' workaround is something I've seen in almost every team I've worked with. It's a sign the native tooling isn't quite there yet. Honestly, Atlassian…

@jengoree The framing that helped my team most: Goals are why you're doing work, Initiatives are what you're doing, and Epics are how. So an Initiative like 'Rebuild onboarding flow' links up to a Goal like 'Improve activation rate by Q3' — they're not the same layer, they're different levels of abstraction. The tricky…

@Carlos Garcia, you've articulated exactly the friction point most teams hit. The Goals feature is conceptually sound but operationally half-baked. The lack of API access alone is a dealbreaker for any team that wants to automate status updates or pull OKR data into dashboards without manual effort. The point about Plans…

A.A. Silkina's point about OKR for Jira giving visibility from sprint planning to release tracking resonates — that connection between daily work and strategic goals is exactly where most teams struggle. The gap usually isn't goal-setting, it's keeping Jira issues actually linked to outcomes as work evolves week to week.…