← All case studies Banking

Turning strategic OKRs into business value delivered every quarter at a leading credit union

Agile Brains helped a nearly $1 billion credit union establish an OKR-driven Agile delivery framework connecting strategic priorities to Epics, User Stories, sprint execution, and measurable business outcomes.

A diverse credit union leadership team arranging planning cards on a table, with snow-capped mountains through the windows

Agile Brains helped a nearly $1 billion credit union establish an OKR-driven Agile delivery framework connecting strategic priorities to Epics, User Stories, sprint execution and measurable business outcomes.

About the client

The client is a member-owned federal credit union headquartered in Alaska, serving more than 64,000 members and managing approximately $1 billion in assets. With roots going back more than 75 years, it has grown from a small community cooperative into one of Alaska's leading financial institutions, with a footprint that now extends beyond the state.

Its origin is part of its character: the credit union was established in 1948 when 20 local farmers pooled just $395 to create a financial cooperative for their community. That community-oriented philosophy still guides the organization as it modernizes its technology, operating model and approach to delivering value to members. As it grew, leadership saw an opportunity to strengthen the connection between strategic priorities, technology investments, business initiatives and the work being delivered by teams.

The challenge

The credit union had established strategic priorities and was introducing Objectives and Key Results (OKRs) to create greater clarity around organizational goals. The next challenge was translating those high-level objectives into work that teams could prioritize, execute and measure.

Traditional project planning focused heavily on activities, milestones and completion dates. The credit union wanted an operating model in which teams could connect their work directly to measurable business outcomes and deliver value incrementally, with consistent answers to a few questions: what are we trying to achieve, how will we measure success, what work will achieve it, what should teams deliver first, and did that work create value? That took more than implementing OKRs or introducing Agile ceremonies. It needed one integrated framework connecting strategy, prioritization, planning, Agile execution and measurement.

How we helped

A shared understanding, built on practice. Agile Brains began by working with leaders and delivery teams to build a shared understanding of OKRs, Agile principles, iterative delivery, prioritization, backlog management and value-based planning, with training designed around practical application rather than methodology alone. An Objective describes what the organization wants to achieve; Key Results establish measurable evidence that the outcome has been achieved. Agile delivery became the mechanism for translating those outcomes into prioritized work teams could execute incrementally.

A line of sight from strategy to sprint. We established a practical delivery hierarchy running from strategic priorities to Objectives and Key Results, then to Epics, User Stories, sprints and business value. Instead of treating OKRs as a leadership planning exercise disconnected from delivery, teams learned to use them as the starting point for what enters the backlog. Each strategic objective was examined for the capabilities, changes or improvements needed to achieve it. Those larger bodies of work became Epics, which were broken into User Stories that could be prioritized, estimated, delivered and validated within short iterations, creating clear traceability from sprint work back to the objective and Key Result it was meant to influence.

Backlogs that execute strategy. Agile Brains coaches worked directly with teams to put the framework into live practice: translating OKRs into delivery initiatives and Epics, breaking Epics into executable User Stories, writing effective acceptance criteria, building and continuously refining prioritized backlogs, connecting backlog items to Key Results, prioritizing by expected business value, identifying dependencies and delivery risks, estimating against available capacity, establishing a Definition of Ready and Definition of Done, and preparing high-priority work for upcoming sprints. The backlog changed from a collection of requests into a strategy execution mechanism. Teams could explain not only what they were working on, but why the work mattered and which business outcome it supported.

Sprints measured by value, not volume. We coached teams through iterative delivery with a consistent rhythm: plan, execute, demonstrate, measure, learn and adapt. Sprint planning set near-term priorities, daily coordination surfaced blockers and dependencies, backlog refinement prepared upcoming work, sprint reviews gave stakeholders regular chances to inspect completed work and give feedback, and retrospectives let teams continuously improve how they worked. Most importantly, the emphasis shifted away from how much work teams completed. At the end of each sprint, teams asked what they delivered, what business value it created, which Key Result it advanced, what they learned and what should come next, creating a continuous feedback loop between strategy and execution.

Leaders and teams coached together. Sustainable Agile adoption required change at both the leadership and team levels. Leaders were coached to focus on strategic priorities, objectives and measurable outcomes, business value, prioritization, capacity constraints, dependencies, delivery progress and outcome measurement. Teams were coached on backlog management, Epic and Story decomposition, sprint planning, iterative execution, stakeholder feedback, delivery metrics and continuous improvement. The result was clearer decision rights, with teams given greater autonomy over how best to achieve the outcomes leadership had prioritized.

The result

The credit union established a more structured and transparent way to connect strategic priorities with day-to-day delivery. The fundamental management conversation changed from "Did we complete the project?" to "Did the work we delivered move the business outcome we committed to?" That distinction moved the organization from managing activities toward managing value and outcomes.

For a growing financial institution, the ability to execute strategy is just as important as the ability to define it. By combining OKRs, Agile training, hands-on coaching, backlog development and iterative delivery, the credit union now has a sustainable, repeatable framework that gives leadership greater visibility into strategic execution and gives teams a practical way to turn business priorities into value delivered every sprint.

What the framework delivered

  • A common OKR-driven delivery model connecting strategy with execution
  • A repeatable approach for translating Objectives and Key Results into Epics and User Stories
  • Teams trained in Agile, OKRs, backlog management and iterative delivery
  • Hands-on coaching that moved Agile concepts from training into live execution
  • Prioritized backlogs aligned with strategic business outcomes
  • Sprint-based delivery focused on incremental business value
  • Improved visibility from leadership priorities to team-level execution, including capacity, dependencies and delivery priorities
  • Regular stakeholder feedback through sprint reviews, and continuous learning through retrospectives and outcome measurement
  • Greater emphasis on measuring outcomes rather than simply completing activities

Next step

Bring us the problem as it actually is.

A direct conversation about where you stand and what will actually work. No deck required.

Book a consultation