Podcast Summary: Scrum Master Toolbox Podcast

Episode: BONUS: Leadership Is Contextual With Daniel Harcek
Host: Vasco Duarte
Guest: Daniel Harcek (Tech executive, CTO, mentor)
Date: March 8, 2026

Episode Overview

In this special CTO bonus episode, Vasco Duarte sits down with tech executive and CTO Daniel Harcek to explore the nuances of leadership in technology organizations—from startups to internet-scale enterprises. They dive into Daniel’s personal journey, the contextual nature of leadership, scaling engineering teams, fostering team ownership, and the rise of AI-first organizations. Daniel also shares actionable advice for Scrum Masters, insights on organizational change, and his book recommendations that have influenced his approach to leading tech organizations.

Key Themes & Insights

1. Leadership is Contextual, Not Absolute

• Daniel’s core lesson: Leadership methods that work for a small team often falter when applied at scale, and vice versa.
• Quote: “Leadership is contextual, not absolute. What works with 10 people breaks at 50.” — Daniel (06:21)

2. Career Milestones & Learning to Scale

• Daniel shares his progression from a part-time developer on international teams to CTO responsibility over thousands.
  • Started with hybrid, distributed teams and was “hungry” for international, high-impact projects.
  • Managed teams ranging in size from 7 to 70 to 2000, learning that scale profoundly changes leadership needs.
  • Quote: "I learned at the time that I want to work on international projects with international teams." — Daniel (03:46)

3. Team Size Impacts Leadership and Processes

Small Teams

• Minimal operational overhead; focus on straightforward ownership and end-to-end responsibility.
• Quote: "You don’t need a lot of operational overhead. You need to be very much straightforward... You are able then to move fast, and the people grow much quicker." — Daniel (06:30)

Large Teams

• Increased regulatory & operational overhead, need for standardization and guardrails.
• Introduction of more formal roles and specialized teams for DevOps, QA, and performance management.
• Example: In small teams, each engineer owns QA and delivery; in big organizations, these responsibilities are often siloed.
• Quote: “We don’t have any QAs... each dev owns quality for the task, and for getting it to production.” — Daniel (09:34)

4. Scaling and Facilitating Growth

• Key challenge: Maintain alignment during rapid growth.
• Strong onboarding, up-to-date documentation (now easier with AI), and open sharing culture are essential.
• The “buddy system” helps new hires integrate smoothly.
  • Quote: “The buddy system, it’s one of the easiest things you can do... One body for a newcomer for 1, 3, 6 months.” — Daniel (14:36)

5. The Organization as an Ecosystem

• Daniel and Vasco discuss the value of treating companies like tech systems: departments as “interfaces” with “APIs,” and using shared technical metaphors to improve communication and transparency.
• Quote: "When people start looking at the whole company, not just the engineering part, and utilize technical principles... there might be huge gain if the people understand it, but you have to share the same language." — Daniel (17:56)

6. AI-First Organizations

• Daniel explains his approach to embedding AI at the core of company operations:
  • Every area (not just engineering) is expected to utilize and upskill in AI/automation tools.
  • Building a “second brain” for the company is critical; data curation is essential.
  • Quote: "AI ability is like a muscle, you have to train it... every person has the capability to use AI." — Daniel (22:37)
  • Exponential benefits realized when the whole company (not just tech) embraces AI-first thinking.
• Practical hiring advice: Look for digital/AI savvy in non-engineering roles (HR, Accounting, etc.).

7. Organizational Change and Agile Transformation

• Biggest challenge: Leading an agile transformation across organizational silos (product, marketing, sales, engineering).
  • Required executive sponsorship and thorough stakeholder buy-in.
  • Quote: “You can have the best tool, but if you use it wrong, it doesn’t work.” — Daniel (28:26)
• Advice on driving change:
  • Use a “financial argument” for leaders: improved ROI, more value with the same resources.
  • For teams: Emphasize increased ownership, transparency, and personal growth.
  • Quote: “Usually they have more ownership, which is very much motivating for everyone to be a part of such change.” — Daniel (34:46)

8. Book Recommendations Influencing the CTO Role

• Site Reliability Engineering (SRE) Series – Google
  • Helped Daniel understand “quality as a feature.”
  • Emphasizes reliability for customers.
• The Lean Startup – Eric Ries
  • Critical for giving technologists a sense of business and customer understanding.
  • Helps balance experimentation with operational excellence.
• Quote: "All tech people should have a sense of business understanding, a sense of customer understanding." — Daniel (36:56)

Notable Quotes & Memorable Moments

• “Leadership is contextual, not absolute. What works with 10 people breaks at 50.” (06:21)
• “I want to hire people that have a digital awareness in terms of automation tools and AI… all people should be tech people in a way.” (26:24)
• “You can have the best tool, but if you use it wrong, it doesn’t work.” (28:26)
• “The AI ability is like a muscle, you have to train it… use it every day.” (22:37)
• “Usually they have more ownership, which is very much motivating for everyone to be a part of such change.” (34:46)

Key Timestamps for Important Segments

• 01:11 — Daniel’s background and pivotal moments
• 05:39 — How experience with varying team sizes shapes leadership approach
• 06:21 — "Leadership is contextual, not absolute"
• 08:31 — Differences in performance management, small vs. large teams
• 12:12 — Strategies for scaling teams and maintaining alignment
• 14:36 — Explaining the buddy system
• 17:22 — The company as a tech ecosystem, shared language
• 19:37 — Approaching AI-first organizations
• 20:57 — Defining "AI-first" in practical terms
• 28:11 — Daniel’s biggest challenge: Agile transformation
• 32:59 — Tips for getting buy-in from leaders and doers
• 36:19 — Most influential books for the CTO role

Summary Takeaways

• Leadership adapts to context: Techniques for leading 7 engineers do not scale to 700; flexibility and awareness are crucial.
• Scaling is about alignment and sharing: Growth requires transparent communication, robust onboarding, and shared ownership.
• AI is not just for engineering: Daniel’s vision is for every department and staff member to become AI- and automation-savvy, multiplying productivity beyond tech teams.
• Tech metaphors unlock organizational clarity: Borrowing from system design to visualize and improve company structure can bridge gaps between tech and business.
• Lasting change rests on personal growth and transparent business cases: Executive buy-in comes from value arguments; teams benefit from autonomy and clear purposes.

Where to Find Daniel Harcek

• LinkedIn: Daniel is occasionally active and shares his learnings there.
• In-person meetups: Runs the WebApp meetup in Žilina, Slovakia, and appears at Central European conferences.

For more, check out the full episode and connect with Daniel via links provided in the show notes.