Field story 5 min

# No Software, No Sprints, Still a Work System Problem

A small investment firm had no software teams and no sprints. It still needed what agility actually provides: a shared definition of value and a way to see where every piece of work stood.

The condition

Experienced partners spent their prioritization time arguing about what mattered, and the firm's core process lived in one partner's head.

## Plenty of good work, no shared way to choose

A small investment firm had a handful of senior partners supported by a tight operations team. It wrote no code and ran no sprints. It also had no shortage of worthwhile work: evaluating investments, supporting portfolio companies, raising funds, building the brand, and running the firm, all competing for the same limited attention.

The managing partner described the problem plainly in our first discovery session. The partners were all experienced, and each had a strong sense of what mattered. When they got together to prioritize, they spent most of the time debating what mattered instead of deciding what to do. Over time the debates had grown combative.

The firm had grown on the instincts of experienced partners. As it matured, that strength became a limitation, because individual judgment could no longer produce consistent priorities across the partnership. The issue wasn't a lack of judgment. The firm had no shared definition of value.

## Blue for value, green for benefit

We ran one four-hour session, starting with the firm's real work instead of theory. Each partner took a different kind of work, such as fundraising, deal sourcing, portfolio company support, investor relations, or firm operations, and mapped a recent initiative on a whiteboard against four questions: how it was prioritized, how its value was captured, what benefits came from it, and how anyone knew those benefits actually happened.

When every board was done, we gave each partner a blue marker and a green marker and asked them to highlight every description of value in blue and every benefit in green. It sounded simple, but it wasn't. One partner put his marker down and said he had been using value and benefit as if they meant the same thing, and they didn't.

That was what the exercise was designed to surface. Value is the worth the work itself creates, such as a stronger investor pitch or a repeatable process. Benefits are what follow because that value exists, such as a second investor meeting or more capital raised. Once the partners separated the two, their examples grouped into recurring themes. They named eight candidate categories, saw that several were the same idea under different labels, and narrowed them to four.

## Making the hard choice on purpose

Agreeing on the categories was only half the work. For each one, the partners wrote out what a score of one through five meant. A five for return generation meant a high-confidence profit impact with a measurable path to investor returns. A one meant work expected to cost money with no credible path to profit. They argued over wording, as people always do at this step, and one partner said he was glad it was finished.

It wasn't quite done. We asked whether all four categories mattered equally. One partner assumed they should. We pushed back, because weighting everything equally is usually how a framework avoids making the hard decision. The managing partner answered quickly: return generation is why the firm exists, and the other categories matter, just not as much. After working through several scenarios, the partners settled on weights.

The framework then went into the firm's work management tool. Every item got four scoring fields, with the definitions shown beside each so people scored consistently. A weighted formula produced an overall value score, and the partners could sort the backlog by the framework they had built together instead of by whoever argued best.

## The process that lived in one head

The second gap was harder to see. The firm's process for finding, winning, and managing investments came from one partner, who had refined it over years, and most of it lived in his head. He was carrying it largely alone, and the strain was starting to show between the partners. Earlier attempts to load the steps into other tools had produced static lists. He still couldn't tell where each activity stood or who was working on it.

When we suggested a work management tool, he pushed back. Why copy the list into yet another tool? On a virtual whiteboard, though, he laid out the whole flow in about thirty minutes. Fundraising ran from identifying and vetting a target through outreach, pitching, and diligence to the first capital call being funded. Deal sourcing had its own sequence. Then he wanted every step to have its own workflow in the tool, in a fixed order. In his head, the design grew into dozens of custom workflows that nobody on his team would want to use.

The turning point was separating two ideas he had fused. A step in his process is an activity. Where that activity stands is its status. Every step could be a single work item, and every work item moves through the same states: to do, in progress, blocked, in review, done. The firm's value streams became swim lanes for deal sourcing, fundraising, investor relations, and portfolio company support, with the steps flowing inside them and the shared states as columns.

## Arguing about the score, not the work

A few weeks later, the managing partner told us the partners would still disagree sometimes. The difference was that they were now debating whether a score was right instead of whether the work mattered. That was the conversation they should have been having all along.

The process work showed up in the tool. Each value stream had its own lane, and the team was organizing and finishing its work inside it. The partner who owned the process could open fundraising and see where each activity stood, who was working on what, and when the planned weeks of work would finish. He felt better about the partnership, and the others seemed as interested as he was in using the process.

None of this used sprints, story points, or software vocabulary. The firm needed two things agility is supposed to provide: a shared answer to what is worth doing, and one way to see where any piece of work stands. These results are the partners' own reports from the first few weeks, not measured outcomes. They still show what transfers. Outside software, the rituals are optional. The operating system underneath them is not.

Agility outside software is not borrowed ritual. It is a shared answer to two questions: what is worth doing, and where is the work right now.

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%2Foperationalizing-agility-outside-software%3Futm_source%3Dlinkedin%26utm_medium%3Dshare%26utm_campaign%3Dinsight-share%26utm_content%3Doperationalizing-agility-outside-software)

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%2Foperationalizing-agility-outside-software%3Futm_source%3Dlinkedin%26utm_medium%3Dshare%26utm_campaign%3Dinsight-share%26utm_content%3Doperationalizing-agility-outside-software)

Email

Components

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

Seen in practice
[The work that fixes this Portfolio Governance](https://www.agileon.com/professional-services/portfolio-governance)

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)[Rank No Urgency, No Change](https://www.agileon.com/insights/no-urgency-no-change)[Surface From 83 Observations to Five Things to Build](https://www.agileon.com/insights/from-eighty-three-observations-to-five-things-to-build)[Flow Promising One Hundred. Finishing Fifty-Six.](https://www.agileon.com/insights/promising-one-hundred-finishing-fifty-six)
