Field story 4 min

# When Goals Run Parallel to Work

A healthcare technology company set goals every quarter in a spreadsheet the work never touched. Replacing it with one shared backlog, a pull system, and a cap on active goals told leadership, for the first time, how much it could actually finish.

The condition

The chief operating officer had the quarter's goals open in a spreadsheet and could not tell how many of them were done.

## A Spreadsheet Nobody Could Read

The chief operating officer of a healthcare technology company had the quarter's goals open in a spreadsheet and could not work out how many of them were finished. Some rows said in progress. Some said nothing at all. A few she believed were done, but the sheet had not been updated, so she could not be sure.

She got up from her desk and walked from person to person asking about status. The answers were honest and of no use: probably close, that one changed a while ago, you would have to ask someone else. The company set its goals every quarter in this file, and there was no way to measure progress against the strategy from it.

She and a fellow senior executive asked us to look closely at the goal-setting process and recommend what should change.

## Why the Goals Never Reached the Work

Interviews with employees explained the spreadsheet. Goals arrived late in the quarter and felt like surprises. Teams had no way to contribute before goals were finalized, so dependencies, capacity, and staffing were never worked out in advance, and people found themselves committed to goals they were seeing for the first time. Once the quarter began, the spreadsheet was forgotten in the pull of daily work. When a goal slipped, nobody updated it, so leadership learned late. When leadership changed priorities, people were often not told and kept working on the old ones.

There were quieter problems too. Goals were written inconsistently, some in detail and some in a few words. Ownership was unclear, which made accountability hard to hold. Managers in different functions ranked the same shared goal differently, which stalled any goal that needed several teams. One employee said there were hundreds of goals in the file that meant nothing to their own work.

The diagnosis was simple to state. The goal process lived in one place and the work lived in another, and nothing carried intent from the first to the second. Each finding became a design principle for what would replace the spreadsheet: one place where everyone could see the same priorities and status, shared contribution to goals, a shared planning process, sustained focus and alignment, and an explicit way to manage change against capacity.

## A Backlog Teams Pull From

The replacement was presented step by step to the whole company. It started at the top. Customer demand, board demand, and multi-year goals would be translated by the executive team into strategic guardrails, which would inform the annual goals. Annual goals would be decomposed into shared goals of roughly a quarter's worth of work. Planning would roll rather than reset each quarter: new shared goals could enter the backlog at any time, so the plan could stay close to reality.

Shared goals would then be broken into backlog items small enough for a single team to finish. Teams would not be assigned work. They would pull it from the top of the shared backlog onto their own boards, move it from To Do through Ready, In Progress, and In Review to Done, and then pull the next highest priority item.

When one leader asked what would stop teams from pulling everything in at once, as they did now, the answer was a limit. The executive team had agreed that no more than twenty shared goals would be active at any one time. Teams would pull only when they had capacity to deliver, focus on finishing what they had started, and move items across their boards at least once a week.

## The Keep-the-Lights-On Objection

The guardrail that drew the sharpest reaction was the simplest one: if someone asks you to do work that does not align with the strategy, the annual goals, or the shared goals, do not do it. A leader challenged it at once. Some of his team's work existed only to keep the lights on, and none of it was on the list. The chief operating officer answered before we could. Then it needs to be made visible and prioritized.

That exchange defined the system. The point was not to forbid unlisted work. It was to stop unlisted work from being invisible. Another leader raised a different concern: a shared goal does not mean the same thing to every function. It does not have to. Take a goal to make an existing product usable on a mobile device. Clinical staff identify where a clinician actually needs it, finance tracks the return, the client team defines adoption measures, engineering builds it, and sales and marketing target the audience. Different tasks, one goal, all visible in one place.

The design ran in two directions. From the top, the executive team set guardrails, a cross-functional forum made shared goals visible, and a prioritization council set the order. From the bottom, teams reported progress, changes, issues, and impediments, and leaders adjusted priorities and coordinated across teams in response.

## Twelve Goals and a Number Leadership Had Never Had

Two months later we walked leadership through a full cycle. The executive team had set guardrails for scope. The council had turned them into a clear order of work. Incoming work had been triaged into shared goals, pulled by delivery teams, and broken down into backlog items. Movement across the team boards had produced reporting on progress, issues, and impediments, and that reporting had fed back into changes to the priority order.

The two senior executives went into their next board meeting able to present progress with confidence. More important, they knew how many shared goals the organization could complete in a quarter. Twelve had been completed while the company was still adopting the new way of working. That was not a target or a benchmark. It was the first honest measure of capacity the company had ever had, and the next round of planning could start from it.

Goals govern work only when they live where the work lives. Until then, they are a record of intent.

Know someone running into this? Send it to them.

[Share on LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=http%3A%2F%2Fagileon.test%3A64380%2Finsights%2Fwhen-goals-run-parallel-to-work%3Futm_source%3Dlinkedin%26utm_medium%3Dshare%26utm_campaign%3Dinsight-share%26utm_content%3Dwhen-goals-run-parallel-to-work)

Email

### Share With Your Team

Choose who it is for. You send it yourself from your own email; Agileon never writes to your colleagues.

Your Message

Open in Email

Share

[Share on LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=http%3A%2F%2Fagileon.test%3A64380%2Finsights%2Fwhen-goals-run-parallel-to-work%3Futm_source%3Dlinkedin%26utm_medium%3Dshare%26utm_campaign%3Dinsight-share%26utm_content%3Dwhen-goals-run-parallel-to-work)

Email

Components

[Cascade](https://www.agileon.com/insights?component=Cascade)[Flow](https://www.agileon.com/insights?component=Flow)[Signal](https://www.agileon.com/insights?component=Signal)

Industry
Health Tech

Seen in practice
[The work that fixes this Upstream Leadership Alignment](https://www.agileon.com/professional-services/leadership-alignment)

Keep reading
[Surface The Next Reorg Will Be AI-Driven. Most Will Do It Wrong.](https://www.agileon.com/insights/the-next-reorg-will-be-ai-driven)[Surface The Seven Components of Work](https://www.agileon.com/insights/the-seven-components-of-work)[Rank Health Tech No Urgency, No Change](https://www.agileon.com/insights/no-urgency-no-change)[Cascade Your Goals Never Reach the Work](https://www.agileon.com/insights/field-note-044-goals-never-reach-work)
