Podcast Summary: BONUS Guardrails Over Processes—How to Scale Teams Without Killing Creativity

Scrum Master Toolbox Podcast
Host: Vasco Duarte
Guest: Prashanth Tondapu
Date: March 17, 2026

Episode Overview

This bonus episode explores the real-world breakdowns in delivery as tech organizations scale. Vasco Duarte talks with Prashanth Tondapu—a founder and experienced tech leader—about lessons learned from global failures, the pitfalls of “process theater,” and why true scalability depends on moving from rigid process to adaptable “guardrails.” The discussion centers on fostering team creativity, ensuring accountability without excessive control, and balancing discipline with autonomy as teams grow.

Key Discussion Points & Insights

1. The Myth of the Well-Oiled Machine

(02:29–03:50)

• Prashanth recounts early career expectations that large companies are error-proof, only to learn the reality: “Things go wrong when there is too much diffusion in accountability. Like when too many people are responsible for something, that always translates to nobody being responsible.”
• Failure is often rooted in structural issues, not a lack of talent: “It comes down to proper guardrails and proper structure, decision making, clarity in the team, accountability. That is what determines whether the team is going to be successful or not.” (Prashanth, 03:35)

2. Accountability vs. Ownership

(03:52–09:55)

• Vasco pushes back on the “everyone responsible means no one is responsible” adage, referencing General McChrystal’s “Team of Teams” and Jocko Willink’s “Extreme Ownership.”
• Prashanth distinguishes between team and individual accountability: “Every subtask has a particular outcome that is expected. For everything, the person who is working or the team needs to have very, very clear demarcation.”
• Emotional commitment is essential: “Outcome can only come with 100% emotional commitment to that particular problem. But when five people are committed to a particular problem as accountable, each one shares only 20% of that emotional, you know, the commitment. That is where the diffusion of responsibility happens and the breakdown happens.” (Prashanth, 07:36)

3. Real-World Example: The Release Failure

(11:35–13:39)

• Prashanth describes a catastrophic release due to ambiguous accountability in a production QA team: “There is a group of individuals who are responsible for that particular piece… Somebody dropped the ball because it was supposed to be a group task rather than a particular person who was supposed to sign off.” (12:44)

4. From Process to People-First Organization

(15:20–17:21)

• As organizations grow, what works at small scale (personal oversight or individual trust) breaks down.
• Three stages are described:
  • Founder can oversee everything (up to ~7 people).
  • Standard Operating Procedures (SOPs) work up to about 30 people.
  • Beyond that, “you have to become a people first company. And people first company kind of outlives process...because process says you have to do this exactly this particular way...you are not able to really leverage the creative side of people.” (Prashanth, 15:50)
• The crucial move is to set “guardrails” rather than rigid processes to free up creativity while maintaining direction and accountability.

5. What Are Guardrails?

(18:46–25:44)
Prashanth describes his company’s evolution:

• Initially, he tried to control quality via rigid SOPs—even for code—but soon clients noted that developers stopped questioning requirements and withheld their insights.
• Moving to “people first” meant:
  • Defining outcomes not just processes (“This is the API that needs to come out. This is what we need to come out.” 20:55)
  • Guardrails such as:
    • If a task takes too long, ask for help.
    • Daily summary of work for team leads, who watch for rabbit-holing.
    • “Don’t try to be a hero”: Ask for help when stuck, especially on client ambiguity.
    • If intent is right but result failed, leadership absorbs the consequence.
    • If intent is wrong or skills insufficient, coach or reconsider role.

Notable Quote:
“If something goes wrong, our guardrail is, we will just ask you one question: What was your intent behind doing this?...If the intent was right and the step that he took was also right but it failed, then the problem is company’s problem.” (Prashanth, 25:00)

6. How Guardrails Are Built and Shared

(22:43–23:41)

• Practices that work are standardized across teams—e.g., task time guidelines, daily reporting.
• Focus on collecting proven guardrails from one project and spreading them to similar contexts.

7. Balancing Accountability, Empowerment, and Learning

(25:44–26:52)

• Leadership’s role is to expose people to consequences without creating fear: “We need to expose [reality] in a way that creates empowerment and ability to make decisions. Because just as you said, if you would just punish everyone every time something goes wrong…people would hide the information until it's too late.”
• The aim: Create an environment where people are safe to experiment—but aware and responsible for intent and learning from misses.

Notable Quotes & Memorable Moments

• On accountability and emotional investment:
  “Outcome can only come with 100% emotional commitment to that particular problem. But when five people are committed...each one shares only 20%... That is where the diffusion of responsibility happens and the breakdown happens.” (Prashanth, 07:36)

• On why SOPs alone don’t work as companies grow:
  “Our client said, ‘Your guys do not even ask any questions. They're not questioning requirements at all.’ ...They said, ‘We hire for IQ. By the way, we can tell that your guys are very smart, but they're holding back.’” (Prashanth, 20:10)

• On the leader’s shift from rigidity:
  “I imagined that humans are also going to be as predictable as computers. And until six or seven people, it works well because you can be everywhere.” (Prashanth, 18:46)

• On helping people navigate ambiguity:
  “If you don’t understand something—like it’s not 100% clear, there is ambiguity—don’t proceed.” (Prashanth, 24:06)

Timestamps for Important Segments

| Segment | Timestamp | |---------------------------------------------|-------------| | Episode introduction & theme | 01:11–02:28 | | Early failure story & accountability | 02:29–08:00 | | Real-world release failure | 11:35–13:39 | | Scaling: process-to-people first | 15:20–17:21 | | Defining and implementing guardrails | 18:46–25:44 | | Organizational learning & empowerment | 25:44–26:52 | | Book recommendations & continuous growth | 27:05–28:51 |

Recommended Resources

• Book: Mindset by Carol Dweck
  • “That actually changed [me]. It told me, oh man, I am not built for growth. It cracked something in me.” (Prashanth, 27:13)
• Book: Emotional Intelligence by Daniel Goleman
  • Prashanth credits this book for helping to set effective guardrails.
• LinkedIn / Innostax.com
  • Connect with Prashanth or learn about his work and insights.

Summary Flow & Tone

Prashanth’s candid storytelling, humility (“I was a very rigid guy...”) and emphasis on learning—both personal and organizational—sets a tone of continuous improvement through self-awareness. Vasco steers the conversation with challenging questions and relevant agile literature, making the discussion practical, transparent, and focused on real impact.

Key Takeaways

• Diffused accountability and lack of clear responsibility can be fatal as organizations scale.
• Over-reliance on process kills creativity and engagement; guardrails empower innovation while maintaining direction.
• Accountability should be laser-focused, visible, and always tied to intent and outcome—not just blame.
• Leaders must evolve from micromanagement to enabling safe spaces for risk, learning, and team growth.
• Continuous learning (growth mindset, emotional intelligence) is essential for building resilient, adaptable organizations.

For deeper dives and real stories from agile trenches, listen to the full episode or connect with the Scrum Master Toolbox community.