Tech Leadership with Fexingo: Engineering Managers, CTOs, and Technical Leadership Conversations

In episode 60 of Tech Leadership, Lucas and Luna explore how one CTO used the Team Topologies framework to reorganize a 200-person engineering department suffering from chronic handoff delays and knowledge silos. They walk through the four fundamental team types — stream-aligned, enabling, complicated-subsystem, and platform — and explain how a financial services company applied them to cut feature delivery time by 40 percent in six months. Lucas shares specific examples of how they identified 'communication dead zones' using dependency mapping, and why they chose to create two enabling teams instead of one platform team. The episode also covers common pitfalls, like over-rotating on team structure without addressing the interaction modes (collaboration, X-as-a-Service, and facilitating). Listeners will come away with a practical lens for diagnosing their own org's bottlenecks and a concrete next step for starting the reorg conversation. #TeamTopologies #EngineeringManagement #CTO #TechLeadership #OrgDesign #StreamAligned #PlatformTeam #EnablingTeam #ComplicatedSubsystem #DependencyMapping #DevEx #Agile #TechDebt #KnowledgeSilos #ScaleUp #FexingoBusiness #BusinessPodcast #Technology Keep every episode free: buymeacoffee.com/fexingo

In this episode of Tech Leadership with Fexingo, Lucas and Luna explore how one CTO at a B2B SaaS company used Cost of Delay to transform feature prioritization. They break down the real-world case: a team drowning in competing requests from sales and product, using Cost of Delay and Weighted Shortest Job First to reduce time-to-value by 40 percent. Lucas explains the math behind Cost of Delay—a combination of business value, time criticality, and risk reduction—and how it replaces subjective scoring. Luna challenges whether this works outside product companies, and they discuss pitfalls like over-quantifying. Key takeaway: Cost of Delay aligns engineering with business outcomes without micromanaging. A concrete tool for CTOs and engineering managers tired of the HiPPO (Highest Paid Person's Opinion) prioritization trap. #CostOfDelay #WSJF #Prioritization #ProductManagement #TechLeadership #CTO #EngineeringManager #B2BSaaS #LeanSoftware #Agile #DecisionMaking #TechStrategy #FexingoBusiness #BusinessPodcast #Technology #Leadership #SoftwareEngineering #Kanban Keep every episode free: buymeacoffee.com/fexingo

Lucas and Luna dive into Wardley Maps, a strategic planning tool that CTOs use to visualize dependencies, anticipate market shifts, and avoid being blindsided by commoditization. They walk through a real example from a mid-stage SaaS company that used mapping to decide when to stop building custom infrastructure and buy off-the-shelf solutions. Lucas explains the core concepts — value chain, evolution axis, and the doctrine of 'pioneer, settle, colonize' — while Luna pushes back on where maps can mislead. The episode includes a practical template for engineering leaders to start their own map in under an hour. #WardleyMaps #StrategicPlanning #CTO #TechnicalLeadership #EngineeringManagement #TechnologyStrategy #Commoditization #ValueChain #PioneerSettleColonize #SaaS #InfrastructureDecisions #BuildVsBuy #SimonWardley #TechStrategy #FexingoBusiness #BusinessPodcast #TechLeadership #SystemMapping Keep every episode free: buymeacoffee.com/fexingo

In this episode, Lucas and Luna explore how engineering leaders can use developer productivity metrics to detect burnout before it becomes a crisis. They examine a real case from a mid-sized SaaS company where a CTO noticed a sudden drop in code velocity and commit quality, traced it to a team that had been quietly overworking for months, and used data — not intuition — to intervene. The conversation covers specific signals to watch for (increased bug rate, reduced commit diversity, longer pull request cycles), how to distinguish burnout from other performance dips, and why leading teams treat metrics as a diagnostic tool rather than a whip. Lucas shares a framework for building a 'team health dashboard' that combines output metrics with sentiment signals. The episode closes with a reflection on the limits of data: no metric replaces a manager who actually talks to their people. #BurnoutDetection #DeveloperMetrics #EngineeringManager #CTO #TeamHealth #CodeVelocity #PullRequestCycles #BugRate #DeveloperProductivity #EngineeringLeadership #TechManagement #SaaSCaseStudy #PeopleAnalytics #TeamRetention #TechLeadership #FexingoBusiness #BusinessPodcast #Technology Keep every episode free: buymeacoffee.com/fexingo

Most engineering teams are sized by headcount, not by cognitive load. In this episode, Lucas and Luna explore how one CTO at a mid-stage SaaS company used cognitive load theory to break up an overwhelmed team of 14 into smaller, autonomy-sized units — and saw throughput increase by 37% within two months. They walk through the specific signals that indicated cognitive overload: code review latency, WIP age, and the bus factor score. They also discuss how the CTO applied Team Topologies concepts to map team boundaries to business domain complexity rather than org chart convenience. The episode includes a real example of how shifting from a 14-person monolithic team to three six-person stream-aligned teams reduced cycle time by 40% and cut onboarding drag by half. If your team feels slow and you can't figure out why, this episode gives you a framework to diagnose the problem and a specific intervention to fix it. #CognitiveLoadTheory #TeamTopologies #EngineeringManagement #CTOStrategies #TeamResizing #StreamAlignedTeams #DeveloperProductivity #Throughput #CycleTime #CodeReviewLatency #BusFactor #Onboarding #SaaS #MidStage #TechLeadership #FexingoBusiness #BusinessPodcast #Technology Keep every episode free: buymeacoffee.com/fexingo

In this episode of Tech Leadership with Fexingo, Lucas and Luna explore a practical incident analysis technique: the Five Whys. They look at how one CTO, Sarah Chen at a mid-size fintech company, applies this method not just to technical failures but also to process breakdowns. Lucas breaks down a real example from Sarah's team where a database outage traced back to a missing peer review in a deployment script—revealing that the real root cause was a cultural norm around urgent fixes. Luna challenges whether the Five Whys can oversimplify complex systems, and Lucas shares countermeasures like branching into multiple causal chains. The hosts discuss how the technique pairs with blameless postmortems, why it's most effective when done in writing, and how one question—'What would prevent this from happening again?'—keeps the exercise focused on action. A concrete, tool-agnostic episode for engineering leaders looking to improve incident response. #FiveWhys #RootCauseAnalysis #IncidentManagement #EngineeringLeadership #CTO #TechLeadership #BlamelessPostmortem #SRE #ReliabilityEngineering #FexingoBusiness #BusinessPodcast #Technology #TechLeadershipWithFexingo #IncidentAnalysis #ContinuousImprovement #DevOps #SystemThinking #EngineeringCulture Keep every episode free: buymeacoffee.com/fexingo

Every engineering leader eventually faces the build-versus-buy decision. In this episode, Lucas and Luna unpack a concrete case: a mid-stage fintech CTO who set up a lightweight internal platform team that turned the build-versus-buy question on its head. Instead of choosing between buying an off-the-shelf vendor product or building a custom solution from scratch, the team built a reusable internal component that served three different product teams. By measuring cycle time and developer satisfaction before and after, they found a 40% reduction in time-to-ship for new features and a 30-point jump in developer NPS. Lucas walks through how the CTO convinced the board, what the platform actually looked like, and why this approach avoids the classic pitfall of building everything in-house. Luna pushes back on when this doesn't make sense and adds a counterexample from a legacy enterprise that failed with a similar strategy. The episode closes with the hosts reflecting on how to know if your org is ready for internal platforms — and a quick note on how listener support keeps Fexingo ad-free. #BuildVsBuy #InternalPlatform #PlatformTeam #DeveloperExperience #CTO #Fintech #TechLeadership #CycleTime #DeveloperNPS #EngineeringManagement #ReusableComponents #ProductTeams #LeanEngineering #OrgDesign #Technology #FexingoBusiness #BusinessPodcast #TechPodcast Keep every episode free: buymeacoffee.com/fexingo

Episode 53 of Tech Leadership with Fexingo explores a radical experiment: one CTO at a mid-sized SaaS company banned all recurring meetings for two weeks. Lucas and Luna break down the setup, the surprising outcomes—engineering velocity up 40%, but cross-team coordination suffered—and what the CTO kept permanently. They discuss the role of async documentation, the hidden cost of calendar clutter, and how to run a meeting detox without breaking your org. If you've ever felt meetings were eating your productive hours, this episode offers a concrete blueprint and the real trade-offs. #MeetingFree #NoMeetingExperiment #CTOLife #EngineeringLeadership #AsyncWork #DeepWork #CalendarManagement #MeetingDetox #TechLeadershipWithFexingo #Technology #FexingoBusiness #BusinessPodcast #SaaS #EngineeringVelocity #LeadershipExperiment #Productivity #OrgDesign #RemoteWork Keep every episode free: buymeacoffee.com/fexingo

In this episode of Tech Leadership with Fexingo, Lucas and Luna unpack the under-discussed middle ground between building internal tools and buying off-the-shelf software. They explore how one CTO at a mid-stage SaaS company avoided the 'buy regret' cycle by investing in a lightweight internal platform for developer workflows. The conversation digs into the decision framework: when to build, when to buy, and when to adapt an open-source solution. They discuss the hidden costs of integration, the trap of vendor lock-in, and how a small investment in internal tooling can pay off in developer productivity and autonomy. Specific examples include a case where a team built a custom deployment pipeline that saved 200 engineer-hours per quarter versus a licensed alternative. The episode also touches on the cultural shift required to maintain internal tools without creating a separate platform team. By the end, listeners will have a practical rubric to evaluate build-vs-buy decisions in their own engineering organizations. #BuildVsBuy #InternalTooling #CTO #EngineeringLeadership #DeveloperProductivity #TechStrategy #PlatformEngineering #OpenSource #VendorLockIn #SaaS #DevOps #DecisionFramework #EngineeringCulture #TechLeadership #FexingoBusiness #BusinessPodcast #Technology #Podcast Keep every episode free: buymeacoffee.com/fexingo

Episode 51 of Tech Leadership with Fexingo: Lucas and Luna explore a surprising tool for breaking down information silos in engineering teams: internal podcasts. They dive into the case of a CTO at a 300-person fintech who launched a weekly 15-minute internal show where senior engineers explain one architecture decision, outage, or new pattern. The result? Cross-team awareness improved, onboarding time dropped by 30 percent, and the number of repeated questions in Slack fell sharply. Lucas breaks down the production cost (two hours per week for one engineer), the format that worked (no slides, no script, just structured storytelling), and why the CTO believes audio beats written docs for tacit knowledge transfer. Luna pushes back on the 'yet another tool' concern and asks whether this scales beyond mid-size companies. They also discuss when an internal podcast makes sense versus a wiki or an RFC process. If you lead a team that struggles with information asymmetry, this episode is for you. #InternalPodcast #KnowledgeManagement #EngineeringLeadership #CTO #TechDebt #Onboarding #TacitKnowledge #Docs #Slack #Fintech #Scaling #Architecture #Postmortem #Storytelling #AsyncCommunication #Technology #FexingoBusiness #BusinessPodcast Keep every episode free: buymeacoffee.com/fexingo

Lucas and Luna dive into the hidden signals buried in your version control history. Instead of code reviews or metrics dashboards, your team's collaboration patterns — merging frequency, PR sizes, commit message quality — reveal whether your engineering culture is healthy or silently failing. They examine a real case: a mid-stage startup whose weekly git log exposed a bottleneck in the deployment pipeline that no one had spotted. Lucas walks through the specific commit patterns that indicate cognitive overload, siloed work, and poor code ownership. Luna pushes back on survivorship bias — can small teams really trust these signals? By the end, you'll know how to read your own repo's health in under 30 minutes, and why one CTO now runs a 'git audit' every quarter instead of a retro. #GitHistory #EngineeringCulture #DevOps #CodeReview #TechDebt #TeamHealth #DeveloperProductivity #VersionControl #Collaboration #SoftwareEngineering #CTO #EngineeringManager #TechLeadership #CommitMessages #PRSize #FexingoBusiness #BusinessPodcast #Technology Keep every episode free: buymeacoffee.com/fexingo

Episode 49 of Tech Leadership with Fexingo explores architecture fitness functions—automated guardrails that catch architectural drift before it becomes tech debt. Lucas and Luna break down a real example from a mid-stage fintech that used fitness functions to enforce its hexagonal architecture boundaries. They discuss how one CTO defined rules around layer violations, dependency direction, and cyclic dependencies, then automated them as CI pipeline checks. The episode covers why traditional architecture reviews fail at scale, how fitness functions shift enforcement left, and what happens when a team accidentally breaks a critical constraint. No abstract theory—just a concrete playbook for turning architectural principles into testable, automated rules. Perfect for engineering managers and CTOs who want to stop saying 'we need to refactor' and start preventing drift in real time. #ArchitectureFitnessFunctions #TechDebt #ContinuousArchitecture #SoftwareEngineering #CTO #EngineeringManagement #HexagonalArchitecture #CIPipeline #AutomatedGuardrails #TechLeadership #FexingoBusiness #BusinessPodcast #Technology #Leadership #Refactoring #CodeQuality #ArchitectureGovernance #DevOps Keep every episode free: buymeacoffee.com/fexingo

Lucas and Luna dive into a real-world story from a mid-sized SaaS company where the CTO used observability data — not intuition — to locate a subtle memory leak that was silently inflating their cloud bill by $40,000 a month. They walk through the specific signals: a gradual tail-latency creep, a steady rise in container restarts, and a single anomalous metric in their Prometheus dashboard that everyone had dismissed as noise. The hosts explain how the team built a custom alert based on RSS (residual sum of squares) to detect the leak before it impacted customers, and why this case proves that observability isn't just for reliability — it's a cost-control lever. They also discuss the cultural shift required to get engineers to treat metrics as money, and how the CTO tied observability to the P&L without creating a blame culture. #Observability #MemoryLeak #CloudCost #SaaS #Prometheus #CTO #EngineeringLeadership #SiteReliability #SRE #Monitoring #Alerting #CostOptimization #TailLatency #ContainerRestarts #ResidualSumOfSquares #FexingoBusiness #BusinessPodcast #Technology Keep every episode free: buymeacoffee.com/fexingo

Episode 47 of Tech Leadership with Fexingo explores how a CTO at a mid-size SaaS company abandoned two-week sprints in favor of flow-based planning. Lucas and Luna dig into the concrete numbers: cycle times dropped from 12 days to under 3, throughput rose by 60 percent, and developer satisfaction scores hit an all-time high. They discuss the key mechanics—limiting work in progress, using explicit queue limits, and shifting from story points to cycle time metrics—and the specific failure modes that led the team to make the switch. The episode also covers the hardest part: convincing product stakeholders to let go of sprint commitments. If you have ever felt that your team's sprint process serves the calendar more than the customer, this episode will give you a real-world alternative. #FlowBasedPlanning #SprintReplacement #Kanban #CycleTime #WorkInProgress #DeveloperProductivity #Agile #CTO #EngineeringManagement #TechLeadership #SoftwareEngineering #Lean #ProductDevelopment #TeamTopologies #FexingoBusiness #BusinessPodcast #TechPodcast #AgileDevelopment Keep every episode free: buymeacoffee.com/fexingo

In this episode, Lucas and Luna dive into Uber's self-driving car program, a project that burned through over $2.5 billion before being sold off in 2020. They explore why even a company with seemingly unlimited resources failed to deliver autonomous vehicles, the strategic mistakes that doomed the project, and three concrete lessons for CTOs and engineering leaders about moonshot investments, organizational incentives, and technology readiness. Drawing on public financial disclosures, the episode offers a grounded case study in managing high-risk R&D without destroying shareholder value. Whether you're a startup CTO or a corporate engineering manager, you'll walk away with a framework for evaluating ambitious technical bets. #Uber #SelfDrivingCars #AutonomousVehicles #MoonshotProjects #CTO #EngineeringLeadership #TechStrategy #RiskManagement #Innovation #FailedProjects #LessonsLearned #Technology #Business #FexingoBusiness #BusinessPodcast #TechLeadership #RAndD #CapitalAllocation Keep every episode free: buymeacoffee.com/fexingo

In Episode 45 of Tech Leadership with Fexingo, hosts Lucas and Luna explore a specific organizational shift that one CTO at a mid-sized fintech company made to double developer throughput without adding headcount. The episode dives into the decision to create three dedicated platform teams—API gateway, data pipeline, and CI/CD—and how that restructuring reduced cognitive load for product teams from an average of seven context switches per day to just two. Lucas walks through the concrete metrics: deployment frequency went from twice a week to four times a day, and mean time to recovery dropped by 60 percent. Luna challenges the framing, asking about the upfront cost of spinning up those teams and the risk of over-abstracting. The episode includes a short, organic mention of listener support at buy me a coffee dot com slash fexingo. No theory, no platitudes—just one real example of organizational design as leverage. #PlatformTeams #DeveloperThroughput #CTO #EngineeringLeadership #TeamTopologies #CognitiveLoad #Fintech #DeploymentFrequency #MTTR #OrganizationalDesign #APIGateway #DataPipeline #CICD #TechDebt #Technology #FexingoBusiness #BusinessPodcast #TechLeadershipWithFexingo Keep every episode free: buymeacoffee.com/fexingo

Lucas and Luna explore how architecture decision records (ADRs) help engineering teams avoid accumulating tech debt. They walk through a real case from a mid-stage fintech company that adopted ADRs after a costly database migration failure. The episode covers what an ADR looks like, why lightweight templates beat heavyweight documentation, and how one CTO used ADRs to shave two months off a major refactor. Hosts discuss common pitfalls like over-documenting and how to keep ADRs actionable. A practical episode for engineering managers and senior engineers looking to institutionalize technical decision-making without bureaucracy. #ArchitectureDecisionRecords #TechDebt #EngineeringLeadership #CTO #TechnicalDocumentation #SoftwareArchitecture #Fintech #DatabaseMigration #Refactoring #DecisionLogs #EngineeringCulture #Technology #FexingoBusiness #BusinessPodcast #TechLeadership #SoftwareEngineering #BestPractices #Documentation Keep every episode free: buymeacoffee.com/fexingo

Lucas and Luna explore how a CTO at a 200-person fintech company scrapped annual performance reviews in favor of continuous feedback loops. They break down the specific system the company adopted: weekly lightweight check-ins, a shared document for tracking growth areas, and a quarterly calibration meeting that replaced the dreaded stack ranking. The conversation digs into the metrics that improved — retention of senior engineers went up 18 percent, and time-to-feedback dropped from months to days. They also discuss the pitfalls: managers initially resisted the unstructured format, and the company had to invest in training to make the feedback constructive. By the end, listeners get a concrete template for how to pilot a similar shift without blowing up their own org. #ContinuousFeedback #PerformanceReviews #EngineeringManagement #CTO #TechLeadership #Retention #FeedbackCulture #ManagerTraining #Fintech #OrgDesign #PeopleOps #AgileHR #EngineeringCulture #Leadership #FexingoBusiness #BusinessPodcast #Technology #TechLeadershipPodcast Keep every episode free: buymeacoffee.com/fexingo

In this episode of Tech Leadership with Fexingo, Lucas and Luna dissect a real-world case of a death march project that nearly destroyed a team at a mid-size SaaS company. They walk through the warning signs—crunch mode lasting more than two sprints, diminishing returns on overtime, and silenced dissent—and then discuss the intervention that reversed it: a radical scope-shedding exercise called 'trim the tree.' Lucas explains how the engineering manager used a simple prioritization matrix to cut 60% of planned features without losing the core customer promise, and how she rebuilt trust with stakeholders by making trade-offs visible. The episode also touches on the sunk-cost fallacy, the difference between heroic effort and effective work, and why the best leadership move is sometimes to say 'we cannot do this by the deadline.' For engineering managers facing their own death march, this episode offers a playbook for stopping the spiral. #DeathMarch #EngineeringManager #ScopeCreep #CrunchMode #TeamBurnout #Prioritization #TrimTheTree #SunkCostFallacy #StakeholderManagement #TechLeadership #SoftwareEngineering #ProjectManagement #EngineeringCulture #ManagerTools #FexingoBusiness #BusinessPodcast #Technology #Leadership Keep every episode free: buymeacoffee.com/fexingo

In this episode, Lucas and Luna explore how one CTO transformed her engineering team's approach to incidents by institutionalizing blameless postmortems. They discuss a specific case where a major payment outage led not to finger-pointing but to systemic fixes, reducing similar incidents by 60 percent over six months. The hosts unpack the five-part postmortem template that the CTO introduced, the cultural resistance she faced from senior engineers, and the surprising side effect: improved cross-team collaboration. Lucas shares data from a 2024 survey showing that teams with blameless postmortems resolve incidents 40 percent faster. Luna questions whether blamelessness can coexist with accountability, and they explore the distinction between individual error and systemic vulnerability. The conversation is anchored in real practices that listeners can adapt to their own engineering organizations. #BlamelessPostmortems #IncidentResponse #EngineeringLeadership #ReliabilityEngineering #SiteReliabilityEngineering #CTO #TechLeadership #PostmortemCulture #LearningFromFailure #IncidentAnalysis #EngineeringCulture #SystemsThinking #RootCauseAnalysis #DevOps #Technology #FexingoBusiness #BusinessPodcast #TechLeadershipShow Keep every episode free: buymeacoffee.com/fexingo

Lucas and Luna dissect the Technical Decision Record (TDR) — a lightweight practice that captures the rationale behind tough engineering choices. They walk through a real case where a CTO's team avoided repeating a costly database migration mistake by documenting their reasoning. The episode covers what makes a good TDR (title, context, decision, consequences), how it differs from RFCs and ADRs, and why a two-paragraph TDR can save months of rework. Plus, a practical tip on making TDRs a habit without creating bureaucracy. #TechnicalDecisionRecord #TDR #EngineeringManagement #CTO #TechLeadership #DecisionDebt #Documentation #DatabaseMigration #SoftwareArchitecture #EngineeringCulture #KnowledgeManagement #Business #Technology #FexingoBusiness #BusinessPodcast #TechLeadershipWithFexingo #EngineeringManagers #TechnicalLeadership Keep every episode free: buymeacoffee.com/fexingo

In this episode of Tech Leadership, Lucas and Luna explore a surprising diagnostic tool for organizational design: the code review. Drawing on a real case from a 200-engineer company that was struggling with slow feature velocity, Lucas explains how a new CTO analyzed pull request patterns to uncover hidden team coupling, misaligned incentives, and unclear ownership. They walk through specific signals—like excessive reviewers per PR, recurring nitpick comments, and PRs that sit idle for days—and what each reveals about team structure. Luna pushes back on the idea that code review is a reliable org signal, and Lucas cites data from a 2024 study on PR latency and Conway's Law. The hosts also discuss how the CTO used these findings to merge two teams and redefine ownership boundaries, cutting average PR cycle time from five days to under two. Filled with concrete examples and actionable heuristics, this episode gives engineering leaders a new lens for diagnosing friction without running a single survey. #CodeReview #OrgDesign #EngineeringManagement #CTO #ConwaysLaw #PullRequests #TeamStructure #DeveloperProductivity #TechLeadership #PRLatency #SoftwareEngineering #Coupling #Ownership #EngineeringCulture #FexingoBusiness #BusinessPodcast #Technology #Leadership Keep every episode free: buymeacoffee.com/fexingo

Episode 38 of Tech Leadership with Fexingo. Lucas and Luna explore how a real CTO saved forty percent on cloud bills by replacing reserved instances with convertible commitments and usage forecasting. They walk through the actual math: moving from a one-year fixed reservation to a dynamic portfolio of convertible RIs and Savings Plans, using a rolling forecast of compute demand. Lucas explains the three levers the CTO pulled: converting underutilized reservations, layering Savings Plans on top, and rightsizing instances based on six months of data. Luna pushes back on whether this works for startups with spiky traffic. They land on a framework: the 'commitment delta' — the gap between what you reserved and what you actually use. If that delta is under ten percent, you're doing well. Over thirty percent, you're losing money. The episode gives listeners a specific, actionable number to audit their own cloud commitments this quarter. No fluff, no theory — just a real decision from a real engineering leader. #CloudCosts #CTO #ReservedInstances #SavingsPlans #CostOptimization #FinOps #AWS #Azure #GCP #EngineeringLeadership #TechLeadership #CloudFinance #Infrastructure #DevOps #FexingoBusiness #BusinessPodcast #Technology #Podcast Keep every episode free: buymeacoffee.com/fexingo

In this episode of Tech Leadership with Fexingo, Lucas and Luna explore a radical shift in on-call philosophy. They examine how one CTO at a mid-sized SaaS company transformed on-call from a dreaded rotation into a structured learning and ownership tool. The key insight: rotating developers through a dedicated 'incident triage' role for two-week sprints, paired with a strict no-escalation policy unless the issue meets a severity threshold, actually reduced burnout and improved system understanding. Lucas breaks down the metrics: a 40 percent drop in after-hours pages, a 22 percent increase in code contributions from engineers who'd completed the triage rotation, and a measurable uptick in team confidence during incident response drills. Luna pushes back on the 'no escalation' rule, but the data shows that when engineers own the full lifecycle of minor incidents, they naturally prioritize fixes that prevent recurrence. Listeners will walk away with a concrete model to trial in their own teams — and a sense that on-call doesn't have to be a misery tax. #OnCall #IncidentManagement #DeveloperProductivity #EngineeringLeadership #BurnoutPrevention #SaaS #CTO #TechLeadership #FexingoBusiness #BusinessPodcast #Technology #EngineeringManagement #SRE #DevOps #IncidentResponse #TeamCulture #TechnicalDebt #DeveloperExperience Keep every episode free: buymeacoffee.com/fexingo

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

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

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

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

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

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

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

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

In this episode, Lucas and Luna discuss how an internal developer platform (IDP) can dramatically reduce deployment times and cognitive load for engineering teams. Lucas shares a specific case study from a mid-stage startup that built a lightweight IDP using backstage and custom scaffolder templates, cutting average deploy time from 45 minutes to 8 minutes and reducing onboarding from two weeks to two days. They explore the trade-offs between buying versus building, the role of platform teams, and why a good IDP isn't just about tooling — it's about treating developers as customers. If you're an engineering leader wondering whether an IDP is worth the investment, this episode gives you a concrete model to evaluate. #InternalDeveloperPlatform #PlatformEngineering #DevOps #Backstage #DeployTimes #DeveloperExperience #EngineeringProductivity #CTO #TechLeadership #EngineeringManager #SiteReliabilityEngineering #InfrastructureAsCode #SoftwareDelivery #DeveloperTools #Technology #FexingoBusiness #BusinessPodcast #TechLeadershipWithFexingo Keep every episode free: buymeacoffee.com/fexingo

In this episode of Tech Leadership with Fexingo, Lucas and Luna dive into a real-world case study of how a mid-sized SaaS team reduced their AWS bill by 40% over six months — without sacrificing latency or developer velocity. They unpack the specific tactics that worked: from right-sizing instances and committing to reserved capacity, to implementing a 'cost per feature' tracking process that made engineers think twice before provisioning resources. Lucas explains why most cost-cutting advice fails because it treats cloud spend as a finance problem instead of an engineering culture problem. Luna brings data on how the team used a simple tagging policy linked to their OKRs to create accountability. They also discuss the trade-offs of using spot instances for production workloads and why one engineer's script to auto-shutdown staging environments on weekends became the team's highest-ROI project. By the end, you'll have a concrete framework for starting your own cloud cost optimization initiative — one that doesn't slow down your teams or require a dedicated FinOps hire. Ideal for CTOs, engineering managers, and senior engineers who want to align cloud spend with business value. #CloudCosts #FinOps #AWSCosts #EngineeringManagement #TechLeadership #CostOptimization #SaaS #DeveloperProductivity #ReservedInstances #SpotInstances #RightSizing #TaggingPolicy #OKRs #DevOps #CloudInfrastructure #TechPodcast #FexingoBusiness #BusinessPodcast Keep every episode free: buymeacoffee.com/fexingo

Lucas and Luna break down how a CTO at a mid-stage SaaS company used lightweight Request for Comments (RFCs) to eliminate decision debt. They walk through a real example from a team that was paralyzed by recurring architecture debates until they enforced a written proposal process. The hosts discuss why RFCs force clarity, how to keep them short (under 500 words), and why the best RFCs include a concrete 'no' section. They also share a simple rule: any decision involving more than two engineers requires an RFC. No consultants, no tools — just a habit that saved one engineering org roughly 200 hours of meeting time per quarter. #RFC #DecisionDebt #EngineeringManagement #TechnicalLeadership #CTO #ArchitectureDecisions #WrittenProposals #MeetingEfficiency #TeamHabits #TechDebt #EngineeringCulture #Scalability #Leadership #Technology #FexingoBusiness #BusinessPodcast #TechLeadership #DecisionFatigue Keep every episode free: buymeacoffee.com/fexingo

In this episode of Tech Leadership with Fexingo, Lucas and Luna dive into a case study of a mid-stage SaaS company that slashed its mean time to acknowledge (MTTA) from 12 minutes to under 4 minutes — a 70% improvement — without adding headcount or buying expensive tools. They break down the three specific changes the team made: redesigning the on-call rotation to use a 'follow-the-sun' model, implementing a tiered escalation protocol that routes alerts based on severity, and introducing a 'swarming' practice where the first responder owns the incident until resolution. Lucas shares why most incident response improvements fail because teams optimize for alert volume instead of alert quality, and Luna pushes back on whether these practices scale beyond small teams. They also discuss how the team used a simple pre-mortem exercise to identify their biggest bottlenecks before making changes. This episode is packed with actionable advice for engineering leaders looking to reduce burnout and improve reliability. #IncidentResponse #OnCall #EngineeringLeadership #SiteReliabilityEngineering #DevOps #IncidentManagement #FollowTheSun #Swarming #AlertFatigue #MeanTimeToAcknowledge #MTTA #PreMortem #BurnoutPrevention #Observability #TechLeadershipWithFexingo #FexingoBusiness #BusinessPodcast #Technology Keep every episode free: buymeacoffee.com/fexingo

Lucas and Luna break down why traditional on-call rotations damage engineering culture and what to do instead. Using concrete examples from a mid-sized SaaS company that cut burnout by 40 percent and increased incident response speed by 30 percent by switching to a dedicated response team model. They discuss the hidden costs of interrupt-driven work, the myth of equal rotation, and how to build an on-call system that respects engineering time without sacrificing reliability. Practical takeaways for CTOs and engineering managers. #OnCall #EngineeringCulture #Burnout #IncidentResponse #TechLeadership #SRE #DevOps #EngineeringManagement #CTO #Reliability #TeamMorale #InterruptDriven #DedicatedResponseTeam #SaaS #SoftwareEngineering #Technology #FexingoBusiness #BusinessPodcast Keep every episode free: buymeacoffee.com/fexingo

Episode 23 of Tech Leadership with Fexingo dives into the surprisingly high-stakes world of API style guides. Lucas and Luna discuss why a well-crafted guide is more than just naming conventions — it's a tool for reducing cognitive load, speeding up onboarding, and preventing production incidents. They break down specific examples: the difference between RESTful and RPC-style endpoints, the hidden cost of inconsistent error responses, and how one team at a mid-size fintech cut integration time by 40% after adopting a shared guide. The conversation also touches on the tension between strict rules and developer autonomy, and why a style guide should be a living document, not a PDF that collects dust. Whether you're a CTO, an engineering manager, or a senior IC trying to persuade your team to standardize, this episode offers concrete arguments and practical starting points. #API #StyleGuide #EngineeringLeadership #TechnicalDebt #DeveloperExperience #REST #RPC #Consistency #Onboarding #IncidentPrevention #LivingDocument #Versioning #ErrorHandling #URLDesign #CamelCase #SnakeCase #Fintech #PlatformEngineering Keep every episode free: buymeacoffee.com/fexingo

Episode 22 of Tech Leadership with Fexingo explores the concept of a congestion budget for engineering teams — a powerful tool to prevent bottlenecks before they form. Lucas and Luna unpack a real case: a mid-stage fintech company that used congestion budgets to cut deployment wait times by 60 percent and unblock feature velocity. They discuss how to measure congestion using cycle time, work-in-progress limits, and queue depth, and why this approach beats traditional capacity planning. The episode dives into implementation tactics: setting budget thresholds, making trade-offs visible, and creating a culture where teams own their flow. If your engineers are waiting more than they're shipping, this episode offers a concrete framework to reclaim throughput. #CongestionBudget #EngineeringManagement #TechLeadership #Bottlenecks #CycleTime #QueueTheory #WIPLimits #FlowEfficiency #DevOps #SoftwareEngineering #TeamThroughput #CapacityPlanning #FeatureVelocity #FexingoBusiness #BusinessPodcast #Technology #EngineeringCulture #LeanSoftware Keep every episode free: buymeacoffee.com/fexingo

In this episode, Lucas and Luna explore the concept of a congestion budget for engineering teams—inspired by traffic flow theory. They discuss how a $12 million Series A startup used a congestion budget to slash deployment time from 45 minutes to 12 and reduce rollbacks by 60 percent. The conversation covers the three metrics of a congestion budget: WIP limits, queue depth, and batch size. Lucas shares a real example from a client who mapped their CI/CD pipeline as a network of queues, while Luna challenges whether this works for teams with unpredictable workloads. They also touch on how the principle maps to other systems like code review and on-call rotations. #CongestionBudget #EngineeringManagement #QueueingTheory #WIPLimits #BatchSize #QueueDepth #CICDPipeline #DeploymentOptimization #LeanEngineering #FlowEfficiency #TechLeadership #EngineeringTeams #StartupEngineering #DevOps #SiteReliabilityEngineering #SoftwareDelivery #FexingoBusiness #BusinessPodcast Keep every episode free: buymeacoffee.com/fexingo

Lucas and Luna explore the story of a single senior engineer who transformed a struggling team's deployment pipeline from a painful two-hour manual process to a fully automated ten-minute rollout. They discuss the cultural resistance, the decision to let one person redesign the system, and the unexpected ripple effects on team morale and on-call burnout. Specific metrics: deployment frequency went from once a week to seven times a day; rollback time dropped from 45 minutes to under two. The episode digs into when it makes sense to give a single engineer ownership of a critical system, how to protect that person from scope creep, and what happens when the pipeline becomes a bottleneck again after that engineer leaves. A concrete case study for anyone leading a team that ships software. #DeploymentPipeline #CI/CD #EngineeringLeadership #DevOps #Automation #DeploymentFrequency #RollbackStrategy #Burnout #OnCall #TechnicalDebt #PlatformEngineering #SeniorEngineer #Ownership #TeamCulture #FexingoBusiness #BusinessPodcast #Technology #TechLeadership Keep every episode free: buymeacoffee.com/fexingo

Episode 19 of Tech Leadership with Fexingo: Lucas and Luna dive into Architectural Decision Records (ADRs) — lightweight documents that capture the context and rationale behind technical choices. They walk through a real example from a mid-stage startup that used ADRs to avoid repeating a costly database migration mistake. Lucas explains the five essential sections of an ADR: title, status, context, decision, and consequences. Luna pushes back on the overhead concern, and they discuss how ADRs evolve from a draft to deprecated status. The episode includes practical tips for getting started with a single template and a git-based workflow. A natural donation segment ties listener support to keeping the show ad-free. By the end, listeners will understand why ADRs are the simplest tool to preserve institutional knowledge and why skipping them leads to the same debates every six months. #ArchitecturalDecisionRecords #ADR #TechLeadership #EngineeringManagement #CTO #TechnicalDebt #Documentation #SoftwareArchitecture #DecisionLog #EngineeringCulture #KnowledgeManagement #GitBasedDocumentation #StartupLessons #DatabaseMigration #InstitutionalKnowledge #TechPodcast #FexingoBusiness #BusinessPodcast Keep every episode free: buymeacoffee.com/fexingo

Lucas and Luna explore the role of an Incident Commander (IC) during major outages. Using the example of a real e-commerce platform outage that cost $300,000 in lost revenue per hour, they explain how a designated IC prevents chaos, reduces mean time to resolution, and empowers engineers to focus on fixing. Lucas breaks down the IC responsibilities: triaging, communicating, and making rapid decisions. Luna questions whether smaller teams need this role. They cover training ICs from senior engineers and rotating the role to build resilience. The episode includes a sincere mention that listener support via buy me a coffee dot com slash fexingo keeps the show ad-free and running. #IncidentCommander #EngineeringManagement #TechLeadership #IncidentResponse #SiteReliability #OutageManagement #DevOps #EngineeringCulture #OnCall #Postmortem #MTTR #Leadership #Technology #Business #FexingoBusiness #BusinessPodcast #TechPodcast #EngineeringPodcast Keep every episode free: buymeacoffee.com/fexingo

Most engineering teams spend their hackathons building features that never ship. Lucas and Luna explore a different approach: the structured glitch day where teams intentionally break their own systems to expose fragility, test incident response, and build muscle memory for real outages. Drawing parallels to Netflix's Chaos Monkey and a medical-device company that found a race condition in its factory-floor firmware, they walk through how three hours of controlled chaos can surface more reliability bugs than a month of traditional testing. No slide decks, no product demos, just engineers trying to crash the thing they built. The episode covers how to set safety boundaries, why the post-glitch write-up matters more than the glitch itself, and how one CTO used glitch-day findings to justify a platform team reorg. For teams tired of incident-driven reliability improvements, this is a concrete alternative that turns reactive firefighting into a proactive practice. #GlitchDay #ChaosEngineering #Reliability #TechLeadership #EngineeringCulture #IncidentResponse #SiteReliabilityEngineering #SoftwareEngineering #DevOps #BlamelessCulture #FragilityTesting #ProactiveReliability #FexingoBusiness #BusinessPodcast #Technology #Leadership #EngineeringManager #CTO Keep every episode free: buymeacoffee.com/fexingo

In this episode of Tech Leadership, Lucas and Luna explore how proactive observability can prevent outages rather than just help you debug them. They unpack a real case: a mid-size fintech company whose SRE team built a canary-based anomaly detection system that caught a memory leak in staging, two hours before a scheduled production deploy. The conversation covers the difference between monitoring and observability, why most teams only react to alerts they already understand, and how canary deployments combined with high-cardinality metrics create a safety net that engineers actually trust. They also discuss the cultural shift required — from celebrating firefighting to celebrating prevention — and why the best observability investment might be giving your team time to build custom dashboards. Listeners walk away with one concrete framework: the 'three-tier observability stack' that keeps incidents small, rare, and boring. #Observability #SiteReliabilityEngineering #IncidentPrevention #CanaryDeployments #AnomalyDetection #Monitoring #SRE #TechLeadership #EngineeringCulture #MemoryLeak #HighCardinalityMetrics #Fintech #ProactiveEngineering #DevOps #FexingoBusiness #BusinessPodcast #Technology #EngineeringManagement Keep every episode free: buymeacoffee.com/fexingo

Episode 15 of Tech Leadership with Fexingo explores the rise of platform engineering. Lucas and Luna discuss why companies like Spotify and Zalando have invested in platform teams to accelerate development, reduce cognitive load, and standardize infrastructure. They break down the key principles: treating internal developers as customers, measuring platform adoption, and avoiding the trap of building a 'platform that solves every problem.' The hosts also share a concrete success story: how a mid-size fintech company reduced new service setup time from two weeks to two hours using a well-designed platform. If you're a CTO or engineering manager debating whether to spin up a platform team, this episode offers a practical framework for deciding when and how to start. #PlatformEngineering #InternalDeveloperPlatform #CTO #EngineeringManagement #DevOps #DeveloperExperience #Productivity #Infrastructure #Spotify #Zalando #TechLeadership #SoftwareEngineering #CognitiveLoad #DeveloperTools #PlatformTeam #FexingoBusiness #BusinessPodcast #Technology Keep every episode free: buymeacoffee.com/fexingo

Episode 14 of Tech Leadership with Fexingo explores the concept of a code-freeze day — one regular day per week or sprint where no production code is written. Lucas and Luna discuss how companies like GitHub and Basecamp have used this practice to reduce cycle time, improve code quality, and give engineers breathing room. They cite a 2025 study from Stripe showing that teams with a code-freeze day shipped 18% fewer bugs and had 12% higher developer satisfaction scores. The conversation covers implementation tactics, common pushback, and how to avoid the freeze becoming a paperwork day. A practical episode for CTOs and engineering managers looking for low-cost, high-impact process changes. #CodeFreezeDay #EngineeringManagement #TechLeadership #DeveloperProductivity #CodeQuality #SoftwareEngineering #ProcessImprovement #GitHub #Basecamp #Stripe #TechnicalDebt #SprintPlanning #DevEx #EngineeringCulture #Technology #FexingoBusiness #BusinessPodcast #Leadership Keep every episode free: buymeacoffee.com/fexingo

Lucas and Luna dive into the pre-mortem technique—a structured exercise where an engineering team imagines a project has failed six months in the future and reverse-engineers what went wrong. Lucas shares how a pre-mortem at his former company caught a critical scaling flaw in a new payment service before launch, saving $2 million in potential rework. Luna contrasts this with standard post-mortems and argues that pre-mortems surface hidden assumptions without blame. They discuss how top tech teams at companies like Amazon and Google have used pre-mortems to avoid catastrophic failures, and offer a practical template for running one in 45 minutes. The episode also touches on cognitive biases like overconfidence and groupthink that pre-mortems counteract. A concrete, actionable episode for engineering leaders who want to prevent failure rather than just learn from it. #TechLeadership #EngineeringManagement #PreMortem #RiskManagement #CognitiveBiases #ProjectManagement #SoftwareEngineering #CTO #EngineeringManager #FexingoBusiness #BusinessPodcast #TechStrategy #Amazon #Google #Scaling #FailureAnalysis #TeamCulture #DecisionMaking Keep every episode free: buymeacoffee.com/fexingo

Episode 12 of Tech Leadership with Fexingo dives into why technical writing is a superpower for senior engineers. Lucas and Luna discuss how one CTO at a mid-stage SaaS company used a mandatory three-page technical design doc to surface architecture issues that were invisible in code reviews. They explain why writing forces clarity, how to evaluate writing without being a grammar snob, and a surprising stat: teams that require design documents ship 20% fewer critical bugs. Plus, a quick honest moment about how listener support keeps this show ad-free. If you've ever struggled to get an engineer to write a coherent RFC, this episode is for you. #TechnicalWriting #EngineeringCommunication #TechLeadership #SoftwareEngineering #CTO #DesignDocs #RFC #CodeQuality #SeniorEngineer #EngineeringCulture #TechnicalDebt #TechPodcast #FexingoBusiness #BusinessPodcast #Technology #EngineeringManagement #DevEx #Architecture Keep every episode free: buymeacoffee.com/fexingo

Lucas and Luna explore how technical debt accumulates in engineering teams and, more importantly, how to measure and prioritize it. Drawing on a real case from a Series B fintech startup, they discuss the 'debt-to-asset ratio' for codebases, why most teams measure the wrong things, and how one CTO convinced her board to allocate 20% of engineering capacity to reducing debt — without slowing down product velocity. The episode covers the difference between deliberate and inadvertent debt, the 'interest rate' analogy applied to legacy systems, and a concrete framework for deciding when to refactor versus when to ship. Practical for any engineering leader or CTO managing growing systems. #TechnicalDebt #EngineeringManagement #CTO #TechLeadership #SoftwareEngineering #CodeQuality #Refactoring #EngineeringStrategy #Fintech #SeriesB #DebtToAssetRatio #LegacySystems #EngineeringProductivity #SystemArchitecture #FexingoBusiness #BusinessPodcast #Technology #EngineeringCulture Keep every episode free: buymeacoffee.com/fexingo