Disparate roadmaps stalled OKR roll-ups — Jira, Productboard & Workday into Gtmhub

Overview

Post-merger integration at a multi-product SaaS company struggled to align product roadmaps and performance metrics. Product lines tracked work differently in Jira and Productboard, teams defined Key Results inconsistently, and leadership lacked a single view for trade-offs. Intelligex connected Jira, Productboard, and Workday into an Objectives and Key Results (OKR) roll-up in Gtmhub (Quantive Results), and exposed executive dashboards in Sigma. A monthly approval cadence run by the Transformation Office governed goal changes and cross-team dependencies. Teams reduced duplicated projects, gained clear visibility across lines of business, and made portfolio decisions faster because every discussion referenced the same goals, owners, and delivery status.

Client Profile

• Industry: B2B SaaS (multi-product platform)
• Company size (range): Mid-market to enterprise with global product and engineering teams
• Stage: Post-merger integration and operating model consolidation
• Department owner: Strategy, Analytics & Executive Leadership (Transformation Office / Corporate Strategy)
• Other stakeholders: Product Management, Engineering, Program Management/PMO, Finance/FP&A, HR, Sales, Customer Success, IT/Data Engineering, Legal & Compliance

The Challenge

Two product organizations brought different planning rhythms and tooling. One managed initiatives through Jira projects and Advanced Roadmaps, the other planned in Productboard and synced selected items to Jira. Key Results were tracked in spreadsheets or slide decks, and definitions varied by team. When leadership asked for a cross-portfolio view, analysts exported data from multiple systems and reconciled it by hand. Meetings drifted into debating which source was current rather than evaluating options.

Ownership shifts after the merger compounded the problem. Workday reflected new reporting lines and cost centers, but that context was not tied to initiative ownership or OKRs. Teams scoped similar initiatives under different names, dependencies were discovered late, and Steering Committee sessions ran long without a shared, governed picture of progress and trade-offs.

Why It Was Happening

Taxonomies and cadences were fragmented. Jira epics, Productboard features, and Key Results did not share consistent identifiers or naming. Updates happened on different schedules, and there was no system-of-record for objectives or a common rubric for what counted as progress. As a result, metrics drifted and duplicated efforts were hard to spot.

Governance arrived at the end of the cycle. Goal changes and re-scopes were socialized in slides, not in a workflow with approvals and lineage. Without a monthly, executive-led review that tied tools together, teams optimized locally and escalations landed late. The merger amplified these gaps because product lines had different habits and definitions.

The Solution

We created a governed operating layer that unified work and outcomes. Jira and Productboard flowed into an OKR hierarchy in Gtmhub (Quantive Results), with ownership mapped from Workday. Sigma dashboards pulled from the conformed model to give leaders a cross-portfolio view. A monthly approval cadence, owned by the Transformation Office, locked definitions and changes before they reached executive forums. Nothing was replatformed: teams kept their delivery tools, while the orchestration aligned goals, roadmaps, and accountability.

• Jira integration to ingest epics, initiatives, status, and links to issues; work items mapped to Key Results and Objectives (Jira)
• Productboard integration to pull features, priorities, and customer insights, linked to OKRs and Jira records (Productboard)
• Workday feed for org hierarchy, cost centers, and manager relationships to assign ownership and maintain roll-ups (Workday)
• OKR roll-up in Gtmhub (Quantive Results) with a governed objective hierarchy, standardized Key Result definitions, and progress formulas (Quantive Help)
• Executive dashboards in Sigma for portfolio views, dependency heatmaps, and goal attainment by product and function (Sigma Computing Help)
• Monthly change-log and approval workflow run by the Transformation Office with reason codes and impact notes
• Data model that aligns identifiers across Jira and Productboard, with deduplication and lineage tracking
• Role-based permissions and read-backs so teams preview changes before they publish to leadership
• Cadence calendar and definitions repository to keep terminology and measurement consistent across lines of business

Implementation

• Discovery: Cataloged Jira projects and Productboard workspaces, reviewed current Objectives and Key Results and their definitions, mapped Workday org structures, and identified recurring duplication and dependency pain points from recent Steering Committee notes.
• Design: Defined a target OKR hierarchy and naming conventions, mapped work item types to Key Results, and established a common identifier strategy. Designed the Gtmhub model, Sigma executive dashboard views, and the monthly approval workflow including reason codes and read-backs.
• Build: Implemented connectors from Jira, Productboard, and Workday; normalized identifiers; configured Gtmhub for OKR roll-ups and progress formulas; and created Sigma dashboards for portfolio, dependency, and ownership views. Stood up a change-log with approvals and notifications owned by the Transformation Office.
• Testing and QA: Backfilled a prior quarter to reconcile progress against legacy reports; tuned mapping rules and deduplication logic; validated ownership roll-ups against Workday; and ran tabletop exercises of the approval flow with Product, PMO, and Finance stakeholders.
• Rollout: Launched read-only dashboards and a shadow OKR roll-up alongside existing reports. After teams validated mappings and definitions, enabled the monthly approval cadence and made the governed OKR roll-up the source for executive materials. Kept an exception path for urgent changes with post-approval review.
• Training and hand-off: Delivered short guides for PMs and Engineering on linking epics/features to Key Results; briefed Strategy and PMO on the approval cadence; trained Finance on using Sigma views for portfolio planning; and assigned stewardship for definitions and mappings, with a change-control process.

Results

Leadership worked from a single, trusted picture of goals and delivery. Objectives rolled up consistently regardless of tool or product line, and Sigma dashboards made trade-offs visible. The monthly approval cadence brought changes into the open early, so meetings focused on options and sequencing rather than reconciling inputs.

Teams spotted overlap and dependencies sooner. Duplicated initiatives were consolidated, and ownership reflected current reporting lines. PMs and Engineering kept their familiar systems, but shared definitions and a governed roll-up eliminated drift, reduced rework on executive materials, and clarified where to invest next.

What Changed for the Team

• Before: OKRs lived in slides and spreadsheets by team. After: A governed roll-up in Gtmhub reflected the same definitions across product lines.
• Before: Jira and Productboard told different stories. After: Work items mapped to Key Results with lineage, deduplication, and ownership.

li>Before: Org changes broke roll-ups. After: Workday fed owner and hierarchy updates into the model with historical snapshots.

• Before: Steering sessions debated inputs. After: Sigma dashboards framed choices and the approval cadence settled definitions beforehand.
• Before: Projects overlapped across teams. After: Dependency and overlap views prompted consolidation and clearer sequencing.

Key Takeaways

• Standardize goals first; then map work from delivery tools to those goals so progress is comparable.
• Keep Jira and Productboard in place; use an OKR platform to align definitions and roll-ups, with Sigma for executive context.
• Run a predictable approval cadence to govern changes, with reason codes and read-backs for transparency.
• Anchor ownership in HR data so accountability and roll-ups persist through reorganizations.
• Invest in identifier mapping and lineage; it is the only reliable way to reduce duplicates and explain progress.

FAQ

What tools did this integrate with?
We integrated Jira for delivery status, Productboard for roadmap items and priorities, and Workday for org and ownership. OKRs were managed and rolled up in Gtmhub (Quantive Results), and Sigma delivered executive dashboards. For references, see Jira, Productboard, Workday, Quantive Help, and Sigma Computing Help.

How did you handle quality control and governance?
We defined a shared OKR hierarchy and Key Result formulas, enforced by the OKR platform. Identifier mapping and deduplication reconciled work items across Jira and Productboard. A monthly approval cadence, owned by the Transformation Office, captured changes with reason codes and read-backs before publishing to leadership. Ownership and roll-ups synced from Workday, and lineage preserved how each metric was computed.

How did you roll this out without disruption?
We started with shadow roll-ups and read-only dashboards, letting teams validate mappings and definitions against their existing reports. Once trust was established, we enabled the approval cadence and used the governed model for executive materials. Delivery tools and day-to-day workflows did not change; the orchestration layered consistency and governance on top.

How were OKRs mapped to roadmaps and budgets?
Epics and features were linked to Key Results via stable identifiers and tags. Those Key Results rolled to Objectives in the OKR platform. Sigma views joined OKRs with ownership and cost center context from Workday and Finance, so portfolio discussions referenced the same goals, owners, and financial views without duplicating data entry.

How did you handle reorganizations and product line changes?
Workday fed updates to owner, team, and hierarchy. The model preserved historical snapshots so past progress and accountability remained accurate after changes. The approval cadence included a lightweight re-alignment step, ensuring Objectives and Key Results moved to the right owners with visible rationale.