Group Decision

You are a mid-level software Developer with five years of experience, specializing in backend systems and cloud architecture. You joined your current company two years ago, drawn by the company’s reputation for innovation and its ambitious projects. And the salary helped. You enjoy the challenge of building scalable, efficient systems and you take pride in your ability to solve complex problems. However, you’ve always steered clear of the soft skills side of development—navigating office politics, managing stakeholder expectations, and advocating for their ideas.

Your time at the company has been a mix of highs and lows. You’ve successfully led smaller projects but often feel overshadowed by more senior Developers and managers. You’re eager to prove yourself but feel stifled by the company’s hierarchical culture and the team’s tendency to avoid making decisions.?

Your organization is a mid-sized tech company that specializes in enterprise software for the healthcare industry. Founded a decade ago, the company initially gained traction with its flagship product, DoctorFlow, a workflow management system for hospitals. DoctorFlow revolutionized how healthcare providers managed patient data, and your company quickly became a rising star in the industry.

However, in recent years, your company has struggled to maintain its competitive edge. The market has become saturated with similar products, and the company’s innovation pipeline has slowed. Leadership is under pressure from investors to deliver new features and expand into new markets, but the company’s traditional, top-down decision-making culture is hindering progress.

Development teams are organized into agile squads, but the transition to agile has been superficial. While teams use Scrum ceremonies like Daily Scrums and sprints, decision-making remains centralized, and Developers often feel disempowered. The company’s leadership talks a lot about “innovation” and “empowerment,” but in practice, they micromanage and resist change.

Your team is tasked with building a new feature for the company’s flagship product. The feature is expected to generate significant revenue, but the requirements are vague, and the stakeholders keep changing their minds. During sprint planning, your team identifies a critical decision that needs to be made: Should you build a custom solution from scratch or integrate a third-party tool that meets 80% of the requirements?

Your team is supposed to be self-organizing, but you’ve noticed a recurring problem: decisions are either delayed, poorly made, or avoided altogether. This indecision is costing the team time, money, and morale. As you reflect on the situation, you realize there are several underlying issues that need to be addressed.

As you observe the team’s dynamics, you notice several factors contributing to the indecision:

Lacking Autonomy

Your team is constantly waiting for approval from higher-ups before making any significant decisions. For example, when you suggested prototyping both options to compare them, the product manager said, “We don’t have time for that. Just pick one.” Without the autonomy to explore options, your team feels paralyzed. The lack of trust from leadership stifles creativity and prevents the team from taking ownership of the decision.

No Authority Within the Organizational Culture

Your company has a hierarchical culture where decisions are typically made by senior managers, not development teams. During a recent meeting, a senior executive overruled the team’s recommendation without explanation. Your team feels disempowered and hesitant to make decisions, knowing they could be overturned.

No One Wants to Take Responsibility

During team discussions, everyone seems to avoid taking ownership of the decision. The product owner says, “You’re the technical experts; you decide.” The Developers say, “We don’t know the business priorities well enough to decide.” The lack of accountability creates a vacuum where no one feels comfortable making the call. This leads to endless debates and delays.

Not Enough Information

The requirements are unclear, and the stakeholders keep changing their minds. When you ask for clarification, you’re told, “We don’t have all the answers yet. Just make it work.” Without clear guidance, your team feels uncomfortable making a decision that could have significant financial and operational consequences.

You realize that something needs to change. As a Developer, you have a unique perspective on the technical and business implications of the decision.

What is your decision?

This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.