Team + Time + Tasks: Three actions any leader can take to deliver more value, faster

The Infinite Monkey Theorem suggests that given enough monkeys and enough time, almost anything is achievable. Unfortunately, most organizations have neither infinite time nor infinite monkeys. Competition is relentless, customer needs shift constantly, and the operating environment remains volatile, uncertain, complex, and ambiguous.

The mandate for leaders is simple to state and hard to execute: improve as much as possible, as quickly as possible, before customers find someone better able to create value for them. Then repeat.

A range of tools, systems, and processes can help teams deliver more value, faster. Coaching plays an important role too, helping new techniques take root so results persist over time. Three relatively quick actions can get almost any leader, in almost any organization, started:

• Team – Is the team stable and diverse?
• Time – Is a sense of urgency present?
• Tasks – Does everyone know what comes next, and does it actually matter?

Team: Building Stability Into How People Work Together

Most leaders are familiar with the "forming, storming, norming, performing, adjourning" model of team development, created by Bruce Tuckman. Decades after its introduction, the model still holds up. It suggests that every team moves through five stages, even if not all teams move through them at the same pace.

In the forming stage, team members are still getting to know each other, and role clarity is limited. As storming sets in, personalities begin to test group dynamics. Norming brings a shared understanding of acceptable behavior. Performing is the stage every leader is waiting for, where the work actually gets done. Adjourning marks the natural conclusion, as the team disbands and moves on.

Leaders can take deliberate steps to help a team move from forming toward performing faster. Encouraging genuine connection early can shorten the forming stage and ease the transition through storming. A clear, systematic process for setting expectations can help norming progress more smoothly. These efforts all aim to make the journey leaner.

There is a simpler lever available, though: keep the team stable.

Assembling the right mix of people, with a genuine diversity of skills, experience, and thought, and then keeping that team intact, avoids repeated trips through Tuckman's five stages. It saves time and effort that would otherwise be spent rebuilding trust and working rhythms from scratch. Even organizations that consider themselves Agile often get this wrong, shuffling people between teams based on whatever priority is most urgent that week.

The less time spent cycling through the five stages, the more time a team spends performing, and performing is where organizations see the greatest return on their investment in people. The goal is to maximize the time teams spend in that stage, until the point where rotating people into new areas would generate more value through fresh thinking or new skills.

There are softer benefits too. A team that has found its rhythm knows how to work with each other to get results, which makes for a less stressful and more sustainable environment.

Many large organizations, particularly in retail, are transforming how they deliver value by shifting toward Agile ways of working and new operating models, ensuring time, energy, and resources go toward the priorities that matter most to customers. Across this work, a consistent pattern emerges: stable teams consistently outperform those that experience disruption, such as changes in membership. Every disruption effectively resets a team's progress through Tuckman's stages, with a direct impact on its ability to deliver.

The lesson is straightforward: if it isn't broken, don't fix it.

Time: Creating a Healthy Sense of Urgency

The right team in place is no guarantee of success on its own. The next ingredient is a general sense that time is running out, a phenomenon researcher Connie Gersick described as the "midpoint transition," and one we refer to here as the "uh oh" effect.

Gersick's research built on Tuckman's foundation by looking more closely at how teams actually get work done. She found that teams don't progress in a straight line. Instead, their effort follows a stop-and-start pattern.

In the early going, teams operate based on an initial, often incomplete, understanding of what is needed. They spend time reading, discussing, and trying to piece together how everything fits. An outside observer would likely see little visible progress at this stage.

Then, at roughly the calendar midpoint, something shifts. This is the "uh oh" moment: the point at which people take what they've learned so far and begin applying it in earnest toward the goal. Working patterns, designs, to-do lists, and team dynamics all become open for revision. This is where the real work happens. The team continues at this intensified pace until the deadline arrives, for better or worse.

The "uh oh" effect occurs at a specific and pivotal moment: when a team knows enough about what it's doing, time is beginning to feel scarce, but enough of it remains to course-correct. Once that window closes, teams rarely revisit their plans or behavior again. It's a one-time opportunity, triggered by awareness of an approaching deadline.

A familiar analogy is the midlife crisis: at some point people look up, realize they aren't where they expected to be, and adjust course accordingly. Or consider the difference between getting ready for a 7 p.m. dinner starting preparations at 6:30 rather than 6: a flurry of focused activity kicks in around 6:45. It's a necessary jolt that helps deliver results under pressure.

Deliberately increasing the frequency of "uh oh" moments keeps attention focused on the task at hand and maximizes the value gained from each person's time. Rather than a weekly or monthly check-in, try daily meetings with direct reports, each with a clear goal for the next day. This creates a near-term milestone that teams must work toward. Instead of one "uh oh" moment a week, this approach creates five, along with the added benefits of transparency and accountability that come from a shared team rhythm.

This isn't about overworking people. It's about minimizing downtime and keeping focus sharp on what matters most.

Tasks: Connecting Daily Work to What Actually Matters

If a task feels meaningless, there's a good chance it is.

Presentations that go nowhere. Meetings without clear outcomes. Staff carrying too much work, or not enough. These are all symptoms of poor task creation and prioritization, and they show up especially often in large organizations or enabling functions, where distance from the customer makes it harder to know which work will genuinely move the needle on customer experience.

The fix is to connect organizational goals directly to the day's work.

At the organizational level, cascaded Objectives and Key Results (OKRs) remain a powerful tool for creating alignment, breaking large strategic goals into smaller ones, each with measurable results and clear timeframes. Most organizations are reasonably good at setting objectives. Far fewer are good at cascading them effectively or tracking momentum toward results.

Eventually, those organizational objectives need to translate into an individual's actual work, and that's where tension between alignment and autonomy emerges. Leaders want everyone pulling in the same direction, but the people closest to the work are usually the ones who best understand what effort is actually required to get there.

As a team, it helps to regularly assess what tasks are needed to achieve an objective. How much time will it take? Does the team have the right skills? How will everyone know when it's done, and does everyone understand why the work matters in the first place?

A range of exercises can help teams prioritize this work so the highest-value items get delivered first. The answer isn't always obvious, and most options will deliver some value while competing for the same limited time and attention. A useful rule of thumb: prioritize whatever will most improve the customer experience, soonest. This tends to generate a better return for the organization over the long run.

The work pipeline itself can be revisited as often as needed, though at least monthly. It sounds almost too simple to matter, yet very few organizations have an effective, transparent pipeline in place from the outset.

A good pipeline means teams can pull the most valuable task whenever they have capacity, understand what's expected and by when, and get on with delivering it. Little time is lost in the ambiguous decision-making phase, because the team has already agreed, transparently and collectively, on what needs to happen.

At the outset, the exact format of the pipeline matters less than having one at all. A Kanban board, a product backlog, or a simple to-do list can all work well. What matters most is agreement and transparency.

Organizations that manage task pipelines well tend to be more efficient and deliver greater value to stakeholders. Customers experience value sooner, which helps maintain a competitive edge. Just as importantly, staff experience greater motivation, because their work is visibly and directly connected to value that the whole team has agreed matters.

One approach that consistently proves effective in this work is Big Room Planning, an exercise that brings together all stakeholders, leaders and team members alike, to map out what pieces of work are needed to achieve an objective by a given time. Its power lies in the clarity it forces: once every piece of required work is laid out together, it becomes obvious that something has to give. The exercise surfaces what's genuinely important to achieving the goal, and it requires organizations to be just as intentional about what they choose not to do as what they choose to pursue. It's a conversation that needs to happen often, not just once.

Bringing Team, Time, and Tasks Together

None of this requires an organization to formally label itself Agile, and this isn't an exhaustive list of everything that drives high performance. But each of these actions is achievable regardless of environment or positional authority. Rather than tackling all three at once, start with whichever feels most within reach:

• Can the organization hire for, and maintain, a diverse and stable team, maximizing the time it spends performing?
• Can near-term milestones be co-created with the team to build a healthier sense of urgency?
• Is there an agreed, transparent list of work the team can reliably pull from?

Wherever the starting point, the outcome is the same: more value, delivered faster.

Where AI Fits In

Each of these three levers, team stability, a healthy sense of urgency, and clear task prioritization, benefits from the kind of visibility that AI tools are increasingly well suited to provide, without replacing the human judgment and discipline that make Agile ways of working effective in the first place.

For team stability, AI-supported workforce planning tools can help leaders spot when staffing changes are about to disrupt a high-performing team, flagging the tradeoff before a reshuffle happens rather than after performance dips. For maintaining a sense of urgency, AI-assisted async stand-up tools can surface blockers and progress in real time, creating more frequent, lower-effort checkpoints without requiring every team member to be in the same room or time zone. And for task prioritization, AI can support backlog grooming and pipeline management by analyzing historical delivery data and customer signals to help teams stress-test which work will genuinely move the needle, freeing up time for the human conversation about tradeoffs that tools like Big Room Planning are built for.

Used this way, AI becomes a way to reduce friction in the systems that already work, not a substitute for the discipline of building stable teams, creating urgency, and prioritizing well.

References

Tuckman, B.W. & Jensen, M.A.C., 1977. Stages of small-group development revisited. Group & Organization Studies, 2(4), pp. 419-427.

Gersick, C., 1988. Time and transition in work teams: Toward a new model of group development. Academy of Management Journal, 31(1), pp. 9-41.