Managing a Tech Team: 5 principles you won't find in any book

How to build a motivated engineering team

In today's sprawling corporate structures, software developers often find themselves bogged down by bureaucracy and stifled creativity. While small companies tend to nurture an environment of freedom and innovation, big companies frequently suffer from a disconnect that leaves their tech talent less engaged and far less happy.

This disparity begs the question: can granting teams more autonomy reverse the trend of a toxic corporate culture? In this article, we'll delve into a management framework built on 5 simple yet powerful rules.

Through these principles, we explore how rethinking traditional leadership could transform not only how teams operate but also how they feel about their work, potentially turning a rigid, demotivating environment into a thriving hub of innovation and fulfilment.

—

This framework isn't something you'll stumble upon in any conventional management book. It was custom-developed by a seasoned technical lead at Google—a professional with a PhD in Computer Science and Distributed Systems (and the most competent boss I had in my career).

Refined through practical, real-world application, these five principles were designed to tackle the unique pitfalls that plague big company environments.

—

These 5 principles offer a fresh, unconventional roadmap to empowering teams and reigniting the passion for innovation that developers in smaller companies often take for granted.

We explore how rethinking traditional leadership could transform not only how teams operate but also how they feel about their work, potentially turning a rigid, demotivating environment into a thriving hub of innovation and fulfilment.

5 principles to empower your software engineers

Principle 1: Open Minded but Consistent

Encourage team to explore diverse ideas, approaches, and solutions. Welcome new perspectives and innovative techniques without being constrained by outdated practices.
Despite being open, the team should maintain steady processes, standards, and values. Decisions are predictable and reliable, ensuring that while creativity is embraced, there is a clear, steady path forward for everyone.

Example

Team is working on a new feature for a React-based product. In a brainstorming session, one developer proposes using Svelte to quickly build a proof-of-concept. The team embraces this innovative idea—open-mindedly exploring new technology—while still adhering to strict coding standards and integration protocols for their main React project.

The Svelte PoC can be scrapped if it doesn't meet expectations, but it sparks valuable insights without disrupting long-term consistency.

Principle 2: Proactive but Aligned

The team members are expected to take initiative, anticipate challenges, and propose solutions rather than simply reacting to problems. This approach helps in reducing bottlenecks and accelerating progress.
While acting proactively, every action or decision must be in sync with the company’s strategic objectives and overall vision. The team remains connected to the broader goals, ensuring that individual efforts contribute effectively to collective success.

Example

During a sprint review, a developer notices recurring delays in the mobile app experience. Proactively, he spends few hours to integrate a robust performance analytics tool which he is familiar with.

He limits the amount of spent time to minimum and gathers the team to review this work and to cross-check this minimum viable demo with the company’s strategic roadmap, which prioritizes mobile user satisfaction.

The developer was proactive to suggest a solution and he provided a minimum viable demo but he immediately notified the team to align if this solution should be further adopted or scrapped.

Principle 3: Transparent but Independent

Open communication is a cornerstone here. Share insights, progress, and even setbacks openly builds trust and enables everyone to stay informed, making collaboration smoother.
At the same time, each team member has the autonomy to make decisions and solve problems within their domain. This independence is key in fostering a sense of ownership and responsibility, as well as speeding up the decision-making process without waiting for constant approvals.

Example

The product roadmap includes a goal to boost app speed by adding a caching layer. Since no one had taken ownership of this task, a senior developer proposed researching potential solutions in the next sprint—on the condition that he completed his other assignments first.

Once he finished his planned tasks, he promptly informed the team that he was moving on to the research phase. Leveraging his expertise, he identified the top two solutions and sent a query to the legal team for a preliminary vetting.

He copied his tech lead on the email to keep the communication transparent and allow for input, yet he didn't wait for the tech lead's go-ahead to initiate the process.

Principle 4: Candid but Respectful

Honest and straightforward communication is vital. Team members are encouraged to provide and receive feedback that is direct, which can be crucial for personal and team growth.
Even when being candid, it’s important to maintain high level of respect and empathy. The goal is to ensure that critiques and feedback are constructive, helping to build a positive culture where every voice is valued and differences are addressed with sensitivity.

Example

During a sprint review, a developer reviews a colleague’s implementation of a new feature. He candidly points out that certain coding patterns could lead to long-term maintenance issues and offers specific suggestions for improvement.

However, he also emphasizes the strengths of the feature and acknowledges the effort put in, ensuring his feedback comes across as constructive rather than critical.

This honest yet respectful dialogue not only helps address potential issues early but also strengthens team trust and fosters a culture of continuous improvement.

Principle 5: Critical but Supportive

Being critical means rigorously analyzing ideas, code, and strategies to identify potential flaws or improvements. It fosters a culture where high standards are maintained through regular and honest evaluation.
However, this criticism is paired with support. The aim is to empower team members to learn from mistakes and continuously improve. Constructive feedback is balanced with encouragement, ensuring that team members feel motivated to grow rather than discouraged by their errors.

Example

During the sprint review, a junior developer presented a new feature he developed. After the meeting, a senior developer invited him for a one-on-one chat to provide detailed feedback. In the discussion, the senior dev highlighted that the presentation should have emphasized three key points.

He also mentioned that certain verbose sections in the demo, like redundant technical details, could have been omitted to keep the message concise.

While giving this critique, the senior dev shared that he had made similar mistakes early in his career. He explained that his ability to refine his communication and streamline his presentations improved over time through practice and experience. This personal insight not only helped frame the feedback constructively but also encouraged the junior developer to view these critiques as stepping stones for growth rather than setbacks.

—

Final Thoughts

This framework isn’t a one-size-fits-all prescription—it’s a versatile blueprint that can be scaled to suit teams of any size. Whether you’re a fast-growing startup or a sprawling corporation, these five principles offer the flexibility to empower your team and cultivate an environment where creativity and collaboration flourish. By blending autonomy with alignment, transparency with independence, and candid feedback with supportive mentorship, organizations can tailor this approach to address their unique challenges and goals.

In small teams, the framework can help rapidly iterate and adapt, fostering a culture where innovation is at the core. In larger companies, it provides a much-needed antidote to bureaucracy by ensuring that every developer feels heard, valued, and equipped to contribute meaningfully to the organization’s vision. Embracing these principles can unlock the full potential of your software development teams—no matter the company size—and pave the way to a more dynamic, engaging, and successful workplace.