Deliver What Matters · LinkedIn

Teams Behave Differently When They Stay With the Problem

At CAIP, new applications would continue arriving tomorrow, next month, and next year. Applicants would continue navigating the process. Staff would continue processing submissions. Policies would evolve. User expectations would change.

The need itself wasn’t going away. Yet much of the work surrounding the effort was organized as though it had a finish line .

Funding cycles ended. Priorities shifted. Success was often framed around delivering a capability rather than improving a condition over time.

That distinction matters more than most organizations realize.

Many government challenges are ongoing by nature. Improving an application experience isn’t a one-time event. Reducing processing delays isn’t something you achieve once and declare complete. Building trust, improving data quality, increasing adoption, or reducing friction are not projects with natural endpoints.

They are conditions that require continuous attention.

Yet organizations often respond to these enduring challenges with temporary structures. Teams are assembled, work is planned, funding is approved, and delivery begins. Eventually, the effort concludes, the team moves on, and attention shifts elsewhere.

The problem remains.

What’s interesting is not simply that the problem remains. It’s that teams behave differently when they know they’ll stay connected to it .

Imagine two teams tackling the same challenge.

The first team is told to deliver a set of requirements by the end of the fiscal year. Success will be measured by whether the planned work is completed on time and within budget.

The second team is told to improve the application experience. They will remain responsible for that experience after delivery and will continue measuring whether conditions improve.

Both teams may begin with similar requirements. Both may have talented people. Both may work hard and deliver quality solutions. But they won’t think the same way. The first team is naturally drawn toward completion. The second team is naturally drawn toward improvement.

When teams expect to stay with the problem, they begin asking different questions .

Instead of focusing solely on what needs to be built, they become interested in what users are experiencing. They pay closer attention to adoption, behavior, outcomes, and unintended consequences. They become more invested in understanding whether the work actually helped.

Delivery still matters. But delivery becomes a means to an end rather than the end itself .

At CAIP, meaningful progress accelerated when the team remained connected to the problem long enough to learn from the results of its decisions.

When applicants struggled with a process, the team saw it. When a change improved completion rates, they saw that too. When something didn’t work as expected, the team had an opportunity to learn, adapt, and improve rather than simply move on to the next request.

That continuity changed behavior. The team wasn’t just delivering work. It was learning from outcomes.

Temporary efforts often create a different dynamic.

When success is defined primarily by completing work before funding expires, before a contract ends, or before the team transitions elsewhere, the focus naturally shifts toward delivery. Teams become increasingly concerned with scope, schedules, milestones, and commitments.

Those things matter. But they don’t necessarily create improvement. In many cases, they simply create completion.

This isn’t a criticism of projects. Projects can be effective vehicles for delivering meaningful value. The challenge arises when projects become the primary mechanism for addressing problems that never truly end.

The longer a team expects to live with the consequences of its decisions, the more likely it is to think beyond delivery .

It starts asking:

Did users adopt the change?
Did the experience improve?
Did the outcome move?
What did we learn?
What should we adjust next?

Those questions become more important when the team knows it will still be there tomorrow.

One of the most overlooked drivers of ownership is continuity .

Organizations often try to create ownership through accountability statements, performance objectives, and governance structures. Those things can help. But ownership becomes much more natural when people remain connected to the problem long enough to see the results of their decisions.

Continuity changes incentives. It changes attention. It changes behavior. And over time, it changes outcomes.

Many organizations are trying to improve long-term conditions using short-term structures. They are asking temporary teams to solve enduring problems.

Sometimes the issue isn’t capability. Sometimes it isn’t process. Sometimes it isn’t delivery. Sometimes the missing ingredient is simply giving teams the opportunity to stay with the problem long enough to improve it.