Project Management

Triads in Agile: The Path to Efficient Decision Making

From the Voices on Project Management Blog
by , , , , , , , , , , , , , , , , , ,
Voices on Project Management offers insights, tips, advice and personal stories from project managers in different regions and industries. The goal is to get you thinking, and spark a discussion. So, if you read something that you agree with--or even disagree with--leave a comment.

About this Blog


View Posts By:

Cameron McGaughy
Lynda Bourne
Kevin Korterud
Conrado Morlan
Peter Tarhanidis
Mario Trentim
Jen Skrabak
David Wakeman
Christian Bisson
Yasmina Khelifi
Sree Rao
Soma Bhattacharya
Emily Luijbregts
Lenka Pincot
cyndee miller
Jorge Martin Valdes Garciatorres
Marat Oyvetsky
Ramiro Rodrigues
Wanda Curlee

Past Contributors:

Rex Holmlin
Vivek Prakash
Dan Goldfischer
Linda Agyapong
Jim De Piante
Siti Hajar Abdul Hamid
Bernadine Douglas
Michael Hatfield
Deanna Landers
Kelley Hunsberger
Taralyn Frasqueri-Molina
Alfonso Bucero Torres
Marian Haus
Shobhna Raghupathy
Peter Taylor
Joanna Newman
Saira Karim
Jess Tayel
Lung-Hung Chou
Rebecca Braglio
Roberto Toledo
Geoff Mattie

Recent Posts

3 Signs Your Organization Isn’t PM Ready

Task Conflict vs. Relationship Conflict

Stop Patching: 5 Steps to Find the Core Problem

3 Ways to Level up Your Leadership

Commercializing Agile

Categories: Agile

By Soma Bhattacharya

When it comes to working on larger projects that combine multiple teams spread across locations with a tight timeline, formalizing a triad is one of the easiest ways to streamline the process. While working with everyone is required in all projects, a triad can help you and your team irrespective of the role you play in the project.

The simplest things create the most impact. A triad involves bringing together the product, UX and development teams. You can change the composition of your triad based on your project and invite various functions to the core team.

Once that’s finalized, the triad is responsible for the project moving forward in a timely manner. It adds accountability at all levels and requires unanimous decision making, thus removing uncertainty and the multiple approvals that often lead to a back-and-forth dialogue.

When done at all levels, decision making in a triad takes care of strategic, tactical and operational issues for the project. To ensure that the triad is efficient at all levels (from planning to implementation), it can be created at multiple levels (from governance bodies to scrum teams). This ensures the right group is involved with making decisions.

Here are few ways to involve the triad throughout the release:

  1. Release/Big Room planning: The goal is to ensure that the triad is available at all levels for planning. This ensures that all requirements and risks are covered and ready while we initiate the project and continue with planning. For quarterly planning, triad leadership is involved to ensure requirements for the upcoming quarter are discussed beforehand—and everyone comes ready with the work done for the teams to start pulling in features and stories for the quarter.
  2. Discovery calls: These calls can help the triad come together to plan for the upcoming quarter. They can be attended by the leadership triad as well because it involves decision making on prioritizing and reviewing features like design and architecture.
  3. Team meetings: Ensuring the triad is available at the team level keeps everyone onboard and prevents unwelcome surprises. This involves the scrum team-level triad and leads to better acceptance and demos because the triad is constantly working and reviewing things together—and not waiting on last-second feedback or blockers that need discussion or escalation. These include anything from design reviews to regular standups.
  4. Retrospectives: These provide a good way to understand the pain points from everyone—and start working on them through the sprints, especially when you are constantly learning and innovating as a team (whether it’s the process or technology).

Of course, there are problems that can happen throughout, but the triad allows everyone not to just function as a team, but also feel like a team. And as we all know, happier teams can better resolve complex problems.

Do you think a triad can help your teams?

Posted by Soma Bhattacharya on: February 19, 2023 12:10 PM | Permalink

Comments (7)

Please login or join to subscribe to this item
Estimated Sum
Very interesting the theme that brought to our reflection and for debate
Thank you for sharing and for your opinions.

Triads, like Scrum teams, is about taking a multidisciplinary approach to decision-making. Having more than one perspective is always a good thing.

Absolutely, thanks for sharing Soma!

Hello Soma - thank you for your article. I read and re-read it but I'm still unclear about what you refer to as a "triad" in this context. Can you please provide your definition of triad as it applies to your article.

Soma - Nice Article. but some of them not clear what your are talking about and referring.

Thanks everyone for the comments.
Ignacio- By Triad I meant bringing in the group of stakeholders from different domain. This could be Business, Development and UX or any stakeholders that you might want to add where your product will derive value from. This should happen seamlessly, but when teams are large and perhaps distributed bringing in those are more important and allows faster decision making and minimise time in giving feedback. For example- having a triad call can allow the leadership triad to make decisions on design or a flow faster and right there instead of going via emails and doing it in silos.
Does this help?

Please Login/Register to leave a comment.


"You cannot prevent the birds of sorrow from flying over your head, but you can prevent them from building nests in your hair."

- Chinese Proverb