75: The Hidden Systems Behind High-Performing Engineering Teams

Dec 23, 2025

In this discussion, Gerald Chablowski, a lead developer and engineering leader with a unique background in archaeology, highlights the vital role of clear systems and documentation in tech. He argues that teams often struggle due to unspoken rules, which lead to chaos instead of creativity. Gerald emphasizes the importance of human-centered practices and how small pull requests can enhance code quality. He also discusses the balance between firm guidelines and flexibility, advocating for trust-building over micromanagement as key to effective leadership.

Ask episode

AI Snips

Chapters

Books

Transcript

Episode notes

INSIGHT

Tech Serves People, Not The Reverse

Gerald emphasizes technology exists to serve people, not the other way around.
Organize teams and systems around human needs to make tech genuinely useful.

ADVICE

Write Rules And Explain Their Purpose

Define clear rules and explain why they exist before expecting good outcomes.
Build shared vocabulary so everyone understands aims and can cooperate effectively.

ADVICE

Make Documentation Practical And Actionable

Document systems and processes as practical tutorials, not abstract policies.
Use documentation as leverage so knowledge outlives individuals and speeds onboarding.

Get the Snipd Podcast app to discover more snips from this episode

Get the app

Build your own CTO Playbook at www.theCTOplaybook.com — the leadership platform built for the full CTO journey. Coaching, podcast, and community to help you lead with clarity, confidence, and strategic impact.

What if your team's biggest problem isn't talent, it's the rules you've never written down?

In this episode, I'm talking with Gerald Chablowski, a lead developer based in Thailand whose journey from archaeology and history into tech leadership gives him a very human lens on engineering. I’m drawn to the way he thinks less about shiny tools and more about how people organize themselves, how rules get explained, and how work actually feels. His experience leading teams across different countries and cultures makes him obsessed with one question: what happens when we use structure to protect humans instead of control them.

Too many engineering teams are playing a game where nobody can see the rulebook, then wondering why everything feels chaotic. Here we get brutally honest about what happens when goals change every week, when leaders “delegate” but still pull every string, and when trust gets treated like a slogan instead of something you earn in tiny daily moments. You’ll hear how simple constraints like clear rules, small pull requests, and real documentation can unlock creativity instead of killing it, especially in environments where people are scared to challenge the plan.

You’ll Learn:

[00:00] Introduction

[03:48] Why tech only matters when it serves people, not the other way around

[06:19] What happens when a team works without clear rules or shared understanding

[09:14] The reason trust is built through tiny daily behavior, not speeches or titles

[11:47] How unclear systems force developers into chaos even when rules technically exist

[14:52] Why documentation becomes leverage when knowledge needs to outlive individuals

[17:01] The leadership mistake that made a senior dev refuse to work with him

[23:08] What learning hard physical skills teaches about leadership discomfort

[28:19] How asking people to rewrite a task in their own words exposes hidden gaps fast

[34:22] Why tiny pull requests transform code quality when systems enforce them

[42:08] How relying on juniors teaches humility and system thinking faster than doing it all yourself

You can connect with Gerald and his work on his LinkedIn.

Find more from Adam on LinkedIn and YouTube, and check out Adam's CTO coaching company here.