Where Focus Goes, Energy Flows

How technology leaders can set their team's focus in the most effective ways.

In the realm of software development, the adage “where focus goes, energy flows” holds profound significance. Leaders of software teams play a pivotal role in determining the direction of their team’s focus. Their influence is so substantial that it can make or break the efficiency and effectiveness of the entire development process.

The Order-Taker Approach

Consider a scenario that’s common across the software industry. The business side of the organization dictates the specifics of what needs to be developed, and to some extent, how it should be developed. The software development team gets treated like order-takers. Once the business side provides the specifications, they trickle down to the development team, who then groom, estimate, and execute a set of tickets/stories. This top-down, one-way communication style has some obvious flaws, yet remains popular.

The Collaborative Approach

Contrast this with high-performing teams that thrive on two-way communication. Here, tech leaders obsess about sharing the underlying “why” certain problems exist, not necessarily the “how” to solve them. They invest time crafting a clear and concise set of outcomes everyone understands. These descriptions leave no room for ambiguity and are easy to measure.

Empowered with a clear understanding of the business context and desired outcomes, software teams brainstorm ideas and potential paths to achieve these outcomes. They weigh the pros and cons of each approach, considering both cost and value alongside the business. Once there’s alignment between the business and development teams on the best path forward, the team proceeds to deliver the software.

But the journey doesn’t end there. As the team progresses, they continually reassess their approach, always seeking better cost-value solutions. They make strategic bets, learn from their successes and failures, and adjust their course accordingly. It’s a dynamic process, not a rigid contract.

The Power of Cross-Functionality

Teams need to be cross-functional for such a collaborative approach to thrive. Members from product, design, development, project management, etc should be in constant communication. This mix of expertise fosters a holistic view of the project and encourages innovative solutions.

Moreover, structures like continuous integration and continuous deployment can significantly shorten the feedback loop. The quicker changes are made and tested by real users, the faster teams can refine their approach and achieve the desired outcomes.

Conclusion

Leaders play a crucial role in shaping the focus of their software teams. By fostering a culture of collaboration, clarity, and continuous feedback, they can ensure that their teams are not just order-takers but innovators. After all, where focus goes, energy flows, and with the right focus, software teams can achieve remarkable outcomes.

← Back to Insights