A team can enjoy its work, appreciate its manager, and have a positive workplace culture while still failing to deliver meaningful results. Projects fall behind, important problems remain unresolved, and the business struggles to achieve its goals. At the same time, a team can be productive but exhausted, afraid to raise concerns, and dependent on a few high-performing individuals who make collaboration difficult.

Neither situation represents effective leadership.

For years, technology organizations have debated what makes an engineering team successful. Some focused heavily on individual brilliance, rewarding people who could solve difficult problems regardless of how they treated colleagues. Others moved toward a more people-centered approach, emphasizing psychological safety, employee happiness, and supportive management.

Both approaches contain important lessons, but neither is sufficient on its own. Strong leadership requires something more demanding: creating an environment where people can speak honestly, learn continuously, take responsibility, and deliver results that matter.

Your responsibility as a leader is not to make every employee happy with every decision. It is to build a team that can do meaningful work, improve through challenges, and contribute to the organization's success without sacrificing the people doing that work.

There was a time when technology companies placed extraordinary value on individual output. The engineer who could solve a complicated problem overnight, rescue a failing project, or work through an entire weekend was often celebrated as indispensable.

In some organizations, difficult personalities were tolerated because their technical abilities appeared exceptional. A person could create tension, dismiss colleagues, or make collaboration unpleasant and still receive recognition as a top performer.

The problem with this approach is that software development rarely depends on one person alone. A technically brilliant engineer may write excellent code, but successful delivery also depends on communication, coordination, reliable processes, testing, documentation, and the ability of others to maintain and build upon that work.

An individual who consistently creates conflict can reduce the effectiveness of everyone around them. Other engineers may avoid asking questions, hesitate to challenge technical decisions, or spend additional time repairing problems caused by poor collaboration. The person's visible output may look impressive while the team's overall performance suffers.

Google's Project Aristotle, a research initiative published in 2015, examined the dynamics associated with effective teams. Its findings highlighted five important factors: psychological safety, dependability, structure and clarity, meaning, and impact.

The significance is that team effectiveness involves more than gathering talented individuals. People need to understand their responsibilities, trust that colleagues will follow through, and recognize why their work matters. They also need an environment where they can raise concerns without fearing humiliation or retaliation.

This does not mean individual performance is unimportant. Technical expertise, initiative, and strong execution remain essential. But individual contributions must support the team's ability to deliver rather than undermine it.

A brilliant engineer who repeatedly blocks collaboration may be creating more organizational cost than their technical output suggests. Likewise, a supportive colleague who consistently fails to meet commitments still needs to improve their performance.

Tip: Evaluate contributions by looking at both individual execution and the effect on the team. Recognize technical excellence, but do not reward behavior that makes everyone else's work harder.

Psychological safety is one of the most frequently discussed concepts in modern management, but it is also one of the easiest to misunderstand.

The concept refers to a shared belief that people can take interpersonal risks within a team. In practical terms, employees should be able to ask questions, admit mistakes, disagree with decisions, and raise concerns without expecting embarrassment or punishment simply for speaking up.

This is particularly important in engineering because problems are often discovered through questioning and experimentation. A developer may notice that an architectural decision creates a security risk. A junior engineer may identify an assumption that nobody else has questioned. A team member may admit that a proposed deadline is unrealistic before the project becomes impossible to deliver.

If people are afraid to speak, these concerns may remain hidden until they become much more expensive problems.

However, psychological safety does not mean that employees should never feel uncomfortable. It does not guarantee that every idea will be accepted, every disagreement will end positively, or every decision will meet everyone's expectations.

Constructive feedback can be uncomfortable. Being told that a technical approach is incorrect may be disappointing. Having a proposal rejected or being asked to improve the quality of your work can create frustration. None of these experiences automatically indicates an unsafe environment.

The distinction is between discomfort that supports learning and behavior that discourages people from participating.

A manager who humiliates someone for making a mistake creates a reason to hide future mistakes. A manager who explains what went wrong, examines the underlying causes, and expects the employee to improve creates an opportunity to prevent the same problem from happening again.

Psychological safety must therefore exist alongside accountability. People should feel able to speak honestly, but they must also take responsibility for their decisions, commitments, and performance.

Without safety, employees may hide problems. Without accountability, teams may discuss problems repeatedly without correcting them.

Tip: Make it acceptable to admit mistakes and challenge decisions, but establish clear expectations for correcting problems. A safe team is not one without difficult conversations; it is one where difficult conversations lead to improvement.

Supportive management is important. Employees need leaders who listen, provide guidance, recognize contributions, and understand the challenges people face. But a manager's responsibility cannot end with maintaining positive relationships.

A team can be happy because its workload is light, its expectations are low, and nobody is being challenged. That may feel comfortable for a while, but it does not necessarily create professional growth or meaningful business results.

Consider a manager who avoids giving critical feedback because an employee might become upset. The employee continues making the same mistakes, colleagues compensate for the problems, and the team's performance gradually declines. The manager may preserve a pleasant relationship in the short term, but the decision does not help the employee or the organization.

The opposite can happen, too. A manager may set demanding expectations, challenge weak proposals, and reject requests that do not support current priorities. Some employees may dislike those decisions, even when they are necessary.

This is where leadership requires judgment. Being considerate does not mean agreeing with everyone. It means explaining decisions honestly, treating people fairly, and helping them understand what needs to change.

A strong manager combines care for people with the ability to operate the business. They must understand performance, priorities, resources, delivery commitments, and the consequences of organizational decisions. They also need to recognize that business success creates the conditions for sustainable opportunities, including career development, compensation, and future growth.

When a company performs well, it may have greater capacity to invest in its employees. When it struggles, even a well-intentioned manager may have limited options. Individual managers deserve recognition for the decisions they control, but they cannot personally guarantee every outcome employees want.

The goal is not to make people feel good at every moment. It is to create an environment where people can do valuable work, receive honest guidance, and have a meaningful opportunity to develop.

Tip: Do not avoid necessary feedback just to preserve short-term happiness. Be respectful and specific, explain the reason behind difficult decisions, and give employees a clear path to improve.

Learning is frequently presented as something positive, but the actual experience is not always pleasant.

Learning means discovering that an assumption was wrong, recognizing a weakness, and accepting that an approach that once worked may no longer be effective. It requires people to expose what they do not know and sometimes change habits they have relied on for years.

For engineering teams, this can happen when a developer receives feedback on a design, a manager discovers that a project plan was unrealistic, or an entire team realizes that its established workflow is creating unnecessary delays.

These moments can feel uncomfortable because they challenge people's sense of competence. But they also create opportunities to improve.

A useful way to build a learning culture is to ask questions that move the conversation beyond blame:

These questions are particularly useful after incidents, failed projects, and missed commitments. Instead of focusing only on who made the mistake, the team examines the conditions that allowed it to happen.

That does not mean removing personal responsibility. If someone ignored a known safeguard or repeatedly failed to follow an agreed process, accountability still matters. But focusing exclusively on individual blame can prevent the organization from identifying deeper problems.

For example, if several engineers repeatedly introduce the same type of defect, the solution may require better automated testing, clearer design standards, or improved review practices. Telling everyone to be more careful may not address the conditions that make the mistake likely.

Learning also builds trust. When leaders admit uncertainty, acknowledge their own mistakes, and respond constructively to difficult feedback, employees see that honesty is valued more than appearing perfect.

The strongest teams are not necessarily those that always know what to do. They are the ones that can recognize when they do not know, investigate the problem, and improve their approach.

Tip: After a difficult project or incident, make time to identify what changed, what the team misunderstood, and what should be improved. Turn lessons into specific changes rather than ending the discussion with general reminders.

Organizations often respond to performance problems by introducing more discussions, workshops, training sessions, and team activities. These initiatives may be useful, but their presence on the calendar does not prove that employees are learning.

A meeting can create valuable understanding, or it can consume an hour without producing a meaningful decision. A workshop can introduce a useful technique, or participants can return to work without applying anything they learned.

The difference is whether the activity addresses a real need and produces an outcome that can be observed.

Suppose a team repeatedly struggles with production incidents. A general training session about better engineering practices may sound helpful, but a more focused approach would identify the specific failure patterns, teach the relevant techniques, and give engineers an opportunity to apply them to the systems they maintain.

The same principle applies to leadership development. A manager who struggles with prioritization may benefit more from working through actual planning decisions than attending another broad presentation about time management.

Learning initiatives should begin with a clear purpose. What problem is the organization trying to solve? What capability needs to improve? How will the team apply the learning? What evidence would indicate that the effort made a difference?

Results may take time to appear. Training does not always produce immediate changes in delivery metrics, and some benefits are difficult to isolate. Still, organizations should look for evidence that learning is influencing behavior, improving decisions, or strengthening the team's ability to handle recurring challenges.

A practical approach is to start with a specific problem, test a focused learning activity, and observe whether the team applies what it learned. If the approach works, expand it. If it does not, examine whether the training was poorly designed, the problem was misunderstood, or employees lacked the opportunity to use the new skills.

Tip: Before scheduling another workshop or recurring meeting, identify the capability it should improve and how that improvement will be applied at work. Measure the usefulness of the activity by what changes afterward, not by attendance alone.

One of the most difficult parts of leadership is understanding how much workplace outcomes are influenced by people and how much comes from the systems around them.

When an employee receives a promotion, colleagues may credit a supportive manager. When a team misses its targets, employees may blame poor leadership. Sometimes those judgments are accurate. But organizational outcomes are rarely determined by one person alone.

A manager may advocate for an employee's promotion, but the available budget, company performance, compensation policies, and approval processes can influence whether it happens. An engineering team may have talented people and a capable leader, yet still struggle because priorities change constantly, critical dependencies are understaffed, or decisions take too long.

These structural conditions shape what individuals can accomplish.

This is why leadership assessments should examine more than employee satisfaction or personal relationships. They should also consider whether the organization provides the conditions needed for effective work.

For example, if several teams repeatedly miss deadlines because they depend on the same overloaded platform group, replacing one project manager may not solve the problem. The organization may need to change how shared resources are allocated or reduce the number of competing priorities.

Similarly, if employees report that they cannot raise concerns, the issue may not be limited to one manager's personality. It could involve promotion incentives that reward silence, decision-making structures that discourage disagreement, or performance systems that punish people for identifying risks.

Leaders should look at patterns across teams and over time. Are certain groups consistently overloaded? Do employees have comparable access to development opportunities? Are decisions applied consistently? Do teams have the authority and resources required to meet their commitments?

Fairness is not simply about treating everyone identically. Different roles and circumstances may require different decisions. But the reasoning behind those decisions should be understandable, consistent, and grounded in legitimate organizational needs.

Tip: When a team succeeds or struggles, examine both individual behavior and the conditions surrounding the work. Look for recurring patterns across teams before deciding that one person is responsible for the outcome.

Employee happiness matters because people are not machines. Their experiences influence motivation, communication, retention, and their willingness to contribute. But happiness alone is not a complete measure of whether a manager is effective.

A better assessment combines several dimensions:

These areas provide a more complete picture than a single employee satisfaction score. A team may report high morale while struggling with delivery, or it may meet its targets while experiencing burnout and communication problems. Both situations deserve attention.

It is also important to understand that metrics should support judgment, not replace it. Delivery measurements cannot explain every human experience, and employee surveys cannot independently establish whether a team is performing well. Leaders need multiple sources of evidence, including conversations, operational results, feedback, and observations of how work actually happens.

The objective is to understand whether the environment supports both people and meaningful performance. If employees are comfortable but not developing, the team may need more challenging work and clearer expectations. If delivery is strong but people are constantly exhausted, the organization may need to address workload, staffing, or unsustainable operating practices.

Tip: Use a combination of team feedback, delivery results, learning indicators, and workload patterns to evaluate leadership. Avoid treating any single metric, including happiness, as proof that everything is working.

Good leadership requires more than being approachable, organizing team activities, or keeping everyone satisfied. It requires the ability to make difficult decisions, communicate honestly, challenge people to improve, and build an environment where strong work can happen.

Psychological safety is valuable because it allows teams to learn. Accountability matters because learning must lead to action. Employee well-being matters because sustainable performance depends on people having the conditions to do their jobs effectively. Business results matter because the organization must deliver something meaningful to remain successful.

These responsibilities are connected, not competing priorities.

A leader who focuses only on results may create a team that delivers through fear and exhaustion. A leader who focuses only on happiness may avoid the difficult conversations and decisions required for growth. Neither approach creates lasting effectiveness.

The real measure of leadership is whether people can do challenging, meaningful work, understand what is expected of them, learn from what goes wrong, and contribute to outcomes the organization can stand behind.

Tip: Do not ask only whether your team is happy. Ask whether people can speak honestly, perform meaningful work, improve their skills, meet clear expectations, and deliver results without relying on unhealthy working conditions. That is a much stronger indication of effective leadership.

Hit reply and tell me: what's one hard conversation that made your team better? I read every answer.

Keep going, one small spark at a time.

Erwin