The Triangle Offense of Team Management
Watching “The Last Dance” with my kids recently has been more than just a nostalgic trip through the Bulls’ dynasty—it’s been a masterclass in leadership that’s surprisingly relevant to modern SaaS organizations. Phil Jackson’s ability to manage diverse personalities while maintaining a systematic approach to success offers valuable lessons for today’s tech leaders.
The Triangle Offense of Team Management
Just as Jackson’s triangle offense created a system where each player knew their role while maintaining flexibility, modern tech teams need a framework that balances structure with adaptability. The beauty of the triangle offense wasn’t just its geometric precision—it was its ability to adapt to defensive pressure while maintaining core principles.
1. System First, Stars Second
Jackson didn’t build his system around Jordan—he integrated Jordan into a system that made everyone better. This principle is particularly relevant in today’s SaaS environment, where we often face the temptation to build processes around our strongest performers.
Strong systems in SaaS should include:
- Architectural patterns that standardize development while allowing for innovation
- Agile ceremonies that promote collaboration without stifling creativity
- Scalable processes that survive team changes
- Documentation that evolves with the team
- Quality controls that maintain standards without creating bottlenecks
The key is creating frameworks that elevate everyone’s performance while giving top performers room to excel. Just as Jordan found ways to dominate within the triangle offense, your star developers and product managers should find ways to innovate within your system’s framework.
2. Understanding Individual Motivations
Jackson’s genius lay in recognizing that Rodman needed different handling than Pippen, who needed different handling than Jordan. In our SaaS teams, this translates to understanding that different roles and personalities require different management approaches:
Engineering Teams:
- Architecture-focused developers thrive on complex technical challenges and design autonomy
- Full-stack engineers often excel with end-to-end ownership of features
- UI specialists need regular user feedback and creative freedom
- DevOps engineers require both system-level access and clear boundaries
Product and Sales Teams:
- Product managers need strategic autonomy while maintaining alignment with company goals
- Sales teams thrive on clear metrics with flexibility in approach
- Customer success requires both process adherence and relationship-building freedom
The key is recognizing these differences and adapting your leadership style accordingly. Some team members need daily check-ins; others perform better with weekly syncs. Some thrive on public recognition; others prefer private acknowledgment.
3. The Power of Shared Purpose
The Bulls weren’t just chasing championships—they were pursuing excellence as a unit. In SaaS, this means:
Vision Alignment:
- Connecting sprint goals to quarterly objectives
- Demonstrating how individual features impact customer success
- Showing how technical improvements enhance product stability
- Linking team achievements to company milestones
Cultural Integration:
- Regular all-hands meetings that showcase cross-team impacts
- Shared objectives that require cross-functional collaboration
- Recognition programs that highlight both individual and team achievements
- Creating spaces for informal collaboration and relationship building
The Zen of SaaS Leadership
Jackson’s “Zen Master” approach offers crucial insights for modern tech leadership:
Crisis Management:
- Maintaining calm during production incidents
- Focusing on learning from failures
- Building resilience through preparation
- Creating a culture where mistakes are learning opportunities
Strategic Thinking:
- Balancing short-term wins with long-term sustainability
- Investing in team capabilities during quiet periods
- Creating space for innovation within stability
- Understanding when to push and when to rest
Practical Implementation
-
Assessment
- Map your team’s current dynamics and pain points
- Identify where your system needs more structure or flexibility
- Understand each team member’s motivations and working style
-
Framework Development
- Create clear roles and responsibilities that allow for growth
- Establish communication patterns that work for different personalities
- Build feedback loops that reinforce both individual and team success
-
Continuous Improvement
- Regular retrospectives to refine processes
- Ongoing individual development conversations
- System adjustments based on team feedback and results
Beyond the Championship Ring
Success in SaaS isn’t just about shipping features or hitting quarterly numbers—it’s about building sustainable excellence. Jackson’s Bulls didn’t just win; they dominated through a system that maximized every player’s potential while maintaining team harmony.
The next time you face a leadership challenge, consider how Jackson would approach it:
- Would he see it as an opportunity to strengthen the system?
- How would he balance individual needs with team goals?
- What long-term benefits could emerge from the current challenge?
Creating a championship-caliber SaaS team isn’t about implementing rigid systems or managing through force of personality. It’s about building frameworks that allow for both structure and creativity, pushing for excellence while maintaining balance, and most importantly, creating an environment where diverse talents can combine into something greater than the sum of their parts.
After all, even Michael Jordan needed a triangle offense to win championships.