))
Building Engineering Cultures That Deliver
Manage episode 480766528 series 2833920
Content provided by Elevano. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Elevano or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://ppacc.player.fm/legal.
In this episode of The Tech Trek, Amir sits down with Clark Downum, CTO at Redox, to unpack the deeper dynamics between engineering, product, and business stakeholders. From tech debt and project delays to culture, communication gaps, and delivery trade-offs—this conversation is a candid exploration of how technical teams can drive impact without getting stuck in process perfection.
Whether you're a tech leader or aspiring one, this episode offers a fresh lens on ownership, expectation-setting, and delivering what really matters.
🔑 Key Takeaways:
The cost of tuning out business context: Engineers often rush to solution-mode too early—Clark stresses the need for active listening before architecting.
Tech debt is not a dirty word: Clark challenges traditional thinking—some tech debt is strategic, and discussing it in business terms builds clarity.
Product owners need more support: Agile isn't just about shifting scope; engineering teams should help product leaders clarify and prioritize based on impact.
Delivery ≠ Impact: Shipping on time is not enough. Clark urges teams to elevate conversations toward value, trade-offs, and business impact over output.
⏱️ Timestamped Highlights:
00:48 – What Redox does and the scale of its data exchange operations
02:00 – Onboarding engineers in a complex healthcare ecosystem
03:55 – Why stakeholders often only ask about engineering when things go wrong
07:24 – Do engineers stop listening when they start solutioning too early?
10:20 – Rethinking tech debt: What the business doesn’t know actually helps
13:46 – Can we train engineers to prioritize “getting it done” over “doing it right”?
17:36 – Agile as a response to imperfect plans, not bad estimates
20:53 – Why scope, time, and quality are business trade-offs, not just engineering ones
22:22 – "The burden is on engineering"—and why that might be the right mindset
24:52 – Final thoughts on collaboration, failure, and owning outcomes
💬 Quote of the Episode:
“Don’t just ask, ‘Is this hard?’ Ask, ‘How hard should I work to make this easy?’ That’s where true collaboration starts.” – Clark Downham
451 episodes
Share
