Every CTO makes dozens of consequential calls per quarter — which platform to bet on, whether to refactor now or later, whether to hire a specialist or grow a generalist. Most of those decisions get absorbed into the team's collective memory and then forgotten, along with the reasoning behind them. This episode drills into a practice that a handful of engineering leaders are adopting: the structured decision log. Lucas and Luna walk through a real example from a mid-stage SaaS CTO who started logging every major architectural and people decision with the context, the alternatives considered, and the expected outcome. They discuss why decision logs are different from meeting notes or postmortems, how they prevent repeated debates, and what happens when the team revisits a six-month-old entry and discovers the original assumptions no longer hold. The conversation also touches on the simplest way to start: a shared document with a template that takes three minutes to fill out after any decision that affects more than one team.

#DecisionLog #CTO #EngineeringLeadership #TechStrategy #DecisionMaking #OrganizationalMemory #ArchitectureDecisions #TeamAlignment #TechDebt #Scalability #Management #Leadership #Technology #Business #FexingoBusiness #BusinessPodcast #TechLeadershipWithFexingo #EngineeringManagers

Keep every episode free: buymeacoffee.com/fexingo

In this episode, Lucas and Luna explore how a CTO at a mid-sized SaaS company uses DORA metrics — Deployment Frequency, Lead Time for Changes, Mean Time to Restore, and Change Failure Rate — to measure and improve engineering velocity. They walk through a real example: the CTO noticed their change failure rate was 15 percent, above the industry elite benchmark of 5 percent, and used that insight to shift the team's focus from shipping speed to reliability. The conversation covers why DORA metrics matter more than vanity metrics like story points, how to avoid the trap of optimizing one metric at the expense of others, and the specific steps the CTO took to bring the change failure rate down to 8 percent in two quarters. Listeners will learn a practical framework for diagnosing engineering bottlenecks and aligning team incentives with business outcomes.

#DORAMetrics #EngineeringVelocity #CTO #TechLeadership #DevOps #DeploymentFrequency #LeadTimeForChanges #MeanTimeToRestore #ChangeFailureRate #EngineeringMetrics #SoftwareDelivery #TeamPerformance #SaaS #ReliabilityEngineering #ContinuousImprovement #FexingoBusiness #BusinessPodcast #Technology

Keep every episode free: buymeacoffee.com/fexingo

Episode 117 of Tech Leadership with Fexingo explores how CTOs use reverse mentorship to bridge the experience gap between veteran engineers and junior talent. Lucas and Luna examine a real case at a mid-size SaaS company where the CTO paired a 25-year industry veteran with a new grad who grew up on serverless and AI-assisted coding. They break down the specific outcomes: the veteran learned to adopt event-driven architecture patterns in one legacy module, cutting latency by 40%, while the new grad got mentoring on system design trade-offs and stakeholder communication. The episode covers how to structure these pairings, set boundaries, and avoid common pitfalls like status friction. Listeners walk away with a concrete playbook for launching a reverse mentorship initiative in their own engineering org.

#ReverseMentorship #CTO #TechLeadership #EngineeringManagement #Serverless #LegacySystems #EventDrivenArchitecture #KnowledgeTransfer #TechnicalDebt #Leadership #Mentorship #SaaS #EngineeringCulture #FexingoBusiness #BusinessPodcast #Technology #SystemDesign #CareerGrowth

Keep every episode free: buymeacoffee.com/fexingo

In this episode of Tech Leadership with Fexingo, Lucas and Luna explore how a CTO at a mid-sized SaaS company uses systemic debriefs—structured post-mortems focused on system-level causes rather than individual blame—to turn every incident into actionable learning. They dissect a real-world example: a database migration that caused a 45-minute outage, and how the debrief uncovered not a coding error but a missing communication protocol between the SRE and product teams. The conversation covers the five-question framework, the difference between systemic and root-cause analysis, and why the CTO insists on writing the debrief within 48 hours. Lucas shares his own experience implementing a similar practice at a previous startup, and Luna challenges whether debriefs can scale across dozens of teams. The episode offers a concrete process any engineering leader can adopt to build a culture of continuous improvement.

#TechLeadership #CTO #EngineeringManagement #SystemicDebrief #Postmortem #IncidentAnalysis #FailureCulture #SaaS #SRE #DatabaseMigration #RootCause #LearningCulture #ContinuousImprovement #TechnicalLeadership #FexingoBusiness #BusinessPodcast #Technology #EngineeringTeams

Keep every episode free: buymeacoffee.com/fexingo

In this episode of Tech Leadership with Fexingo, Lucas and Luna explore how a CTO at a fast-growing fintech uses written memo culture to preserve decision quality as the team scales from 50 to over 200 engineers. They break down the Amazon-style six-pager adapted for a smaller company, including the one-page executive summary, the appendix-only data section, and the silent-read start to meetings. Lucas shares how the CTO cut meeting prep time by 30 percent while improving cross-team alignment, and Luna presses on the risk of creating a culture of performative writing. The episode closes with practical tips for engineering leaders considering memo-based decision-making in their own organizations.

#MemoCulture #CTO #DecisionMaking #ScalingEngineering #TechLeadership #FexingoBusiness #EngineeringManagement #WrittenCommunication #AmazonSixPager #Fintech #CrossTeamAlignment #MeetingCulture #AsyncWork #TechDecisions #LeadershipScaling #BusinessPodcast #Fexingo #TechPodcast

Keep every episode free: buymeacoffee.com/fexingo

In this episode of Tech Leadership with Fexingo, Lucas and Luna explore how CTOs can apply the Dreyfus model of skill acquisition to tailor mentorship and team development. Using the example of a mid-stage startup CTO who mapped her thirteen-person engineering team from novice to expert, they discuss why treating everyone the same stunts growth, how to identify the 'competent' plateau, and what practical nudges help engineers move from rule-following to intuitive decision-making. Lucas cites a specific case: a payments startup where the CTO reduced junior-to-mid-level ramp time by 40 percent by assigning context-rich debugging tasks instead of prescribed tickets. Luna pushes back on whether the model overfits to individualistic cultures. They also touch on how the Dreyfus framework applies to hiring, pair programming, and on-call rotation design. The episode closes with a reflection on why the most experienced engineers often need the least management — and why that's hard for engineering managers to accept.

#DreyfusModel #SkillAcquisition #EngineeringMentorship #CTO #TechLeadership #TeamDevelopment #EngineeringManagement #Mentorship #NoviceToExpert #PaymentsStartup #Onboarding #PairProgramming #OnCall #IntuitiveDecisionMaking #Hiring #Technology #FexingoBusiness #BusinessPodcast

Keep every episode free: buymeacoffee.com/fexingo

Episode 113 of Tech Leadership with Fexingo unpacks how engineering leaders use 'technical debt budgets' — explicit allocations of team capacity for reducing complexity — rather than relying on gut feel or crisis-driven rewrites. Lucas and Luna examine a real-world case: a mid-market SaaS company whose CTO set a 20-percent capacity rule, tracked a single 'debt score' per service, and cut production incidents by 40 percent over two quarters. The hosts contrast this with the common trap of treating debt as a moral failing, and discuss how to communicate a budget approach to non-technical stakeholders. They also touch on the role of automated tooling (e.g., SonarQube, CodeClimate) and the importance of tying debt reduction to measurable outcomes like deploy frequency and MTTR. No fluff — just a concrete framework any engineering manager can adapt.

#TechnicalDebt #EngineeringManagement #CTO #TechLeadership #SoftwareEngineering #CodeQuality #RiskManagement #CapacityPlanning #DevOps #SonarQube #CodeClimate #MTTR #DeployFrequency #IncidentManagement #FexingoBusiness #BusinessPodcast #Technology #Leadership

Keep every episode free: buymeacoffee.com/fexingo

In this episode of Tech Leadership with Fexingo, Lucas and Luna explore how a CTO can use cognitive load theory to design engineering teams that ship faster and with fewer bugs. They dive into a real-world case: a mid-stage SaaS company that reorganized its 40-person engineering org around domain boundaries rather than frontend/backend silos. Lucas explains the three types of cognitive load — intrinsic, extraneous, and germane — and shows how reducing extraneous load through clear team ownership cut context-switching by 30 percent and reduced bugs by 18 percent in three months. Luna brings data on how team size affects cognitive load, citing a 2025 study from the Software Engineering Institute that found teams of 6–8 people had 22 percent lower defect density than teams of 10–12. The hosts also discuss practical tools: using 'team API surfaces' and 'decision logs' to reduce coordination overhead. The episode closes with a reflection on how cognitive load thinking can prevent burnout and improve code quality simultaneously.

#CognitiveLoadTheory #EngineeringTeams #CTO #TechLeadership #TeamStructure #SoftwareEngineering #DomainDrivenDesign #ContextSwitching #BurnoutPrevention #CodeQuality #TeamSize #SoftwareEngineeringInstitute #DecisionLogs #APIDesign #FexingoBusiness #BusinessPodcast #Technology #EngineeringManagement

Keep every episode free: buymeacoffee.com/fexingo

In this episode, Lucas and Luna explore how CTOs use the Cost of Delay framework to make prioritization decisions that actually drive business value. Lucas walks through a real-world example from a mid-stage fintech startup that faced a classic dilemma: build a new compliance feature demanded by regulators, or invest in a performance optimization that would reduce cloud costs. Using the Cost of Delay model, the CTO quantified the urgency of each option by calculating the value lost per week of delay. Lucas breaks down the three components of Cost of Delay — user value, time value, and opportunity cost — and explains how this approach helps technical leaders move beyond 'loudest voice wins' or arbitrary deadlines. Luna pushes back on whether this works when data is scarce, and Lucas shares a practical heuristic for rough estimates. You'll learn how to apply Cost of Delay to your own backlog, including a simple one-page template the guest CTO uses in every sprint planning session. No fluff, just a concrete decision-making tool you can use tomorrow.

#CostOfDelay #CTO #Prioritization #EngineeringManagement #TechLeadership #ProductDecisions #ValueDrivenDevelopment #StartupStrategy #Fintech #DecisionMaking #LeanProductDevelopment #AgilePlanning #BusinessValue #OpportunityCost #SprintPlanning #Technology #FexingoBusiness #BusinessPodcast

Keep every episode free: buymeacoffee.com/fexingo

In this episode of Tech Leadership with Fexingo, Lucas and Luna explore how a CTO uses stability metrics — specifically change failure rate and mean time to recover — to decide when to refactor code. They discuss the case of a mid-stage fintech that cut its incident rate by 40 percent by tying refactoring decisions to data rather than hunches. The hosts walk through the metrics dashboard, the threshold that triggered action, and the cultural shift from 'fix it because it's ugly' to 'fix it because it breaks'. They also touch on how the team avoided the trap of never refactoring by setting a maximum acceptable failure rate. A practical look at using measurement to balance velocity and reliability.

#StabilityMetrics #Refactoring #ChangeFailureRate #MeanTimeToRecover #EngineeringLeadership #CTO #TechLeadership #FincTech #IncidentManagement #SoftwareEngineering #DataDriven #TechnicalDebt #DORAMetrics #EngineeringCulture #Reliability #Technology #FexingoBusiness #BusinessPodcast

Keep every episode free: buymeacoffee.com/fexingo