Kick-off conversations, test ideas, or surface questions!

General

In our latest podcast episode w/ Dhruv Parthasarathy (CTO @ Commure & Athelas), we unpacked scaling decision-making & how to operate with startup-level speed inside a complex, high-stakes industry (like healthcare). Listen to the full episode HERE

Here are a few takeaways that can help you improve decision velocity, reduce org friction, increase ownership & build more resilient and adaptive teams…

Dhruv shares a replicable framework for scaling decision-making without increasing risk:

Identify your org’s “catastrophic risks”

Build guardrails and platform-level protections around those.

—empowering engineers and PMs to move fast without fear.

“If you isolate the 2-3 catastrophic risks, you can let 90% of decisions happen quickly and safely.”

Dhruv reframes scoping as one of the most 

Bad scoping creates hidden debt (coordination, decision fatigue).

Effective scoping unlocks faster iteration, clearer ownership, and more focused velocity.

“Who really needs to be in this decision loop?”

“Reducing scope isn’t about cutting corners—it’s how you go faster with better outcomes.”

3. Polymath Engineering as a Velocity Strategy

Commure intentionally hires or develops polymath engineers (those who can flex across backend, frontend, design, and even customer conversations).

This reduces handoffs and coordination drag.

They encourage all engineers to grow range—“1 through 5” basketball analogy.

Start by integrating adjacent responsibilities (e.g., backend + some frontend or product discussions).

“We tell people—you may not be multi-talented now, but you will be once you join.”

4. Customer Co-Creation as Product Development Model

 them—through live iteration in real-world hospital environments.

This eliminates long feedback loops and reduces risk of misaligned priorities.

It turns real-world constraints into design inputs from day one.

“Customers don’t want to just use software—they want to help design it.”

What’s worked (or backfired) for you when trying to speed up decision-making or reduce coordination debt in your org? What frameworks, tactics, or team design changes have helped you build a faster-moving, more empowered team?

Would love to hear your approaches, questions, or lessons learned.

Scaling decision-making, optimizing eng orgs for speed & scope as leverage

Home

Forum

Events

Content

People

Contributors

Albums

Chapters

Chat

Channels

Sub-Communities

Tools

Help

ELC is a safe, supportive space for engineering leaders to connect, learn, and grow. We value authenticity, sharing, and thoughtfulness, with a mission to unite leaders and advance tech leadership.

Copyright

Terms of Service

Privacy Policy

Code of Conduct

Login to the ELC community to connect with others, attend community events, and more!

Login or Sign Up for even more

To unlock all parts of the community and get the best experience, complete your profile.