Episodes

  • How One CTO Replaced Standups With a Status Board

    How One CTO Replaced Standups With a Status Board
    Jun 7 2026
    Lucas and Luna dive into a radical shift in team communication: one CTO at a 40-person SaaS company replaced daily standup meetings with an asynchronous status board. They break down the specific problems the old standups caused — context switching, status-as-theatre, and the 15-minute meeting that actually took 45 — and how a simple shared document changed everything. The episode walks through the concrete implementation: what went on the board, how the team handled blockers without a daily huddle, and the surprising effect on junior engineers who suddenly felt more empowered to speak up. They also discuss when this approach fails, and what the CTO learned from the teams that quietly abandoned the board. No hot takes — just a real case with real numbers: the team cut meeting time by 90 minutes per person per week and incident response time actually improved by 15%. For engineering leaders tired of performative standups, this episode offers a specific alternative worth testing. #StandupMeetings #AsyncCommunication #EngineeringManagement #CTO #TeamProductivity #MeetingCulture #StatusBoard #SaaS #TechLeadership #RemoteWork #DeveloperProductivity #Agile #Scrum #EngineeringCulture #MeetingReduction #Blockers #JuniorDevelopers #FexingoBusiness Keep every episode free: buymeacoffee.com/fexingo
    Show More Show Less
    7 mins
  • How One Team Cut Their Cloud Bill By Changing Nothing

    How One Team Cut Their Cloud Bill By Changing Nothing
    Jun 6 2026
    Episode 35 of Tech Leadership with Fexingo. Lucas and Luna dive into a counterintuitive cost-saving strategy: instead of optimizing infrastructure, a mid-stage startup eliminated cloud waste by killing zombie workloads and enforcing tagging governance. They walk through how a $400,000 annual savings was found by simply turning off forgotten resources and tagging everything else. Along the way they discuss why most cost optimization efforts focus on the wrong layer and how engineering leaders can build a culture of cost awareness without a dedicated FinOps team. Practical, specific, and grounded in a real case from Q2 2026. #CloudCosts #FinOps #ZombieWorkloads #TaggingGovernance #EngineeringLeadership #CostOptimization #CloudInfrastructure #AWS #Azure #GCP #TechLeadership #FexingoBusiness #BusinessPodcast #Technology #CTO #EngineeringManager #Podcast #CloudWaste Keep every episode free: buymeacoffee.com/fexingo
    Show More Show Less
    7 mins
  • How One Engineering Manager Cut Cognitive Load by Adopting Async Communication

    How One Engineering Manager Cut Cognitive Load by Adopting Async Communication
    Jun 6 2026
    In this episode of Tech Leadership with Fexingo, Lucas and Luna explore how asynchronous communication can dramatically reduce cognitive load for engineering teams. They dive into a real-world case from a mid-sized SaaS company that adopted an 'async-first' policy—slashing meeting hours by 40% and boosting deep work time. The hosts dissect the specific tactics used: structured written updates, decision documents replacing hallway chats, and a 'no-meeting Wednesdays' rule that stuck. Lucas argues that async isn't just about efficiency—it's about inclusivity for remote and neurodiverse team members. Luna pushes back on the risks of information silos and delayed feedback loops. Together, they offer a balanced playbook for engineering leaders looking to reclaim focus time without losing alignment. If you've ever felt drained by back-to-back standups and Slack pings, this episode gives you concrete steps to try on Monday. #AsyncCommunication #CognitiveLoad #EngineeringManagement #RemoteWork #DeepWork #MeetingReduction #TeamProductivity #TechLeadership #SoftwareEngineering #WorkplaceCulture #CommunicationStrategy #Neurodiversity #DevEx #EngineeringCulture #FexingoBusiness #BusinessPodcast #Technology #Leadership Keep every episode free: buymeacoffee.com/fexingo
    Show More Show Less
    7 mins
  • Why You Should Write Your RFCs in Public

    Why You Should Write Your RFCs in Public
    Jun 5 2026
    Most engineering teams write RFCs (Request for Comments) behind closed doors. In this episode, Lucas and Luna explore why publishing RFCs to the entire company — not just the engineering org — can catch architectural blind spots early, reduce rework, and build institutional knowledge. They dig into a case where a database migration proposal caught a critical data compliance issue because someone in legal spotted it during the public comment period. They discuss the trade-offs: more eyes means more noise, but also more signal. Lucas argues that the transparency forces authors to write more clearly, while Luna points out that it also democratizes decision-making beyond the senior engineers. They wrap with practical advice: start with one team, use a weekly digest to avoid notification fatigue, and treat RFCs as living documents, not one-and-done proposals. If you're a CTO or engineering manager looking to cut decision debt, this one's for you. #RFCs #RequestForComments #EngineeringManagement #TechnicalLeadership #CTO #TechDecisions #DecisionDebt #Transparency #EngineeringCulture #DatabaseMigration #Compliance #KnowledgeManagement #InternalCommunications #Architecture #Collaboration #Technology #FexingoBusiness #BusinessPodcast Keep every episode free: buymeacoffee.com/fexingo
    Show More Show Less
    9 mins
  • How One Team Uses Decision Logs to Stop Repeating Mistakes

    How One Team Uses Decision Logs to Stop Repeating Mistakes
    Jun 5 2026
    In Episode 32 of Tech Leadership with Fexingo, Lucas and Luna dive into the practice of decision logs—a lightweight documentation technique that helps engineering teams avoid repeating costly mistakes. Lucas shares a concrete example from a mid-stage startup that used decision logs to cut recurring incidents by 60 percent over six months. They discuss how to start a decision log, what to include (context, decision, rationale, outcomes), and common pitfalls like over-documentation. Luna brings up the counterpoint of decision fatigue and how logs can actually reduce it. They also touch on the link between decision logs and psychological safety. A practical episode for any engineering manager or CTO looking to build institutional memory without bureaucracy. #DecisionLogs #EngineeringLeadership #TechManagement #CTO #EngineeringManager #InstitutionalMemory #TechnicalDebt #DecisionFatigue #PsychologicalSafety #PostMortem #ContinuousImprovement #SoftwareEngineering #Leadership #StartupEngineering #Documentation #Technology #FexingoBusiness #BusinessPodcast Keep every episode free: buymeacoffee.com/fexingo
    Show More Show Less
    6 mins
  • How One CTO Uses Decision Logs to Stop Repeating Mistakes

    How One CTO Uses Decision Logs to Stop Repeating Mistakes
    Jun 4 2026
    Lucas and Luna explore the concept of a decision log — a lightweight practice where engineering leaders document every major technical decision, including the context, alternatives considered, and the actual outcome. Lucas shares a case from a mid-stage fintech where a CTO introduced a decision log after the team accidentally rebuilt a data pipeline three times in eighteen months because nobody remembered why the previous architecture was chosen. They break down what goes into a good entry, how often to review the log, and why the exercise forces clarity in distributed teams. The episode closes with a practical suggestion: start next week with just one decision, write it down in a shared doc, and see what happens. Listeners walk away with a specific, implementable habit that costs nothing and compounds over time. #DecisionLog #EngineeringLeadership #CTO #TechDebt #KnowledgeManagement #EngineeringCulture #TechnicalDecisions #TeamProcess #Fintech #DistributedTeams #TechLeadership #EngineeringManager #Documentation #DecisionMaking #Technology #FexingoBusiness #BusinessPodcast #Leadership Keep every episode free: buymeacoffee.com/fexingo
    Show More Show Less
    7 mins
  • How One Team Decided Their Database Was the Wrong Database

    How One Team Decided Their Database Was the Wrong Database
    Jun 4 2026
    Episode 30 of Tech Leadership with Fexingo dives into the hardest infrastructure decision a CTO can face: when to migrate off a database that's been running in production for years. Lucas and Luna unpack the story of a mid-stage SaaS company that switched from MongoDB to PostgreSQL after three years of accumulating workarounds, query timeouts, and data inconsistency bugs. They walk through the technical triggers — specifically a cascading replica failure during a routine backup — that forced the engineering team to admit their document store was the wrong fit for their relational domain. The episode covers how the team sized the migration, why they chose a strangler fig pattern over a big-bang cutover, and the one metric that told them the migration had succeeded: p99 query latency dropped from 1.2 seconds to 40 milliseconds. No hype, no vendor pitches — just a real engineering leadership story about admitting a mistake and executing a fix at scale. #DatabaseMigration #MongoDBtoPostgreSQL #StranglerFigPattern #EngineeringLeadership #CTODecisions #Infrastructure #TechDebt #DataConsistency #QueryLatency #PostgreSQL #MongoDB #MigrationStrategy #ProductionIncident #SaaS #TechnicalLeadership #FexingoBusiness #BusinessPodcast #Technology Keep every episode free: buymeacoffee.com/fexingo
    Show More Show Less
    8 mins
  • How to Build an Internal API Platform That Developers Actually Use

    How to Build an Internal API Platform That Developers Actually Use
    Jun 3 2026
    Many engineering teams build internal developer platforms that nobody adopts. In this episode, Lucas and Luna unpack why — and what one team did differently. They walk through a real case: a mid-size SaaS company whose API platform team spent eight months building a developer portal with every feature the team could imagine, only to find that six months after launch, fewer than 20 percent of services were using it. The hosts trace the root cause: the platform team built for their own ideal developer, not the actual developer — cargo-culting patterns from big tech without understanding their own engineers' pain points. Lucas explains the specific missteps: too many abstractions, a mandatory migration deadline that scared teams, and a lack of dogfooding. Luna pushes back on whether those mistakes are avoidable when you're a small team. The conversation drills into the one metric that matters for platform adoption — time to first deploy — and how one CTO cut it from four days to two hours by letting teams opt in gradually. No hot takes, just a concrete playbook for anyone building a platform their colleagues won't ignore. #InternalDeveloperPlatform #PlatformEngineering #DeveloperExperience #APIManagement #EngineeringLeadership #TechDebt #DeveloperProductivity #CTO #VPE #EngineeringManager #Technology #FexingoBusiness #BusinessPodcast #TechLeadership #Kubernetes #Microservices #DeveloperPortal #Backstage Keep every episode free: buymeacoffee.com/fexingo
    Show More Show Less
    8 mins