In Episode 89 of Tech Leadership with Fexingo, Lucas and Luna explore how one CTO applied cognitive load theory to reorganize engineering teams, reducing context-switching and improving delivery speed. They break down the three types of cognitive load—intrinsic, extraneous, and germane—and show how the CTO used team topology mapping to assign services to squads based on intrinsic load. The episode cites a specific case where a platform team's cognitive load was halved by splitting ownership of a monolith into bounded contexts, cutting lead time for changes from two weeks to two days. Listeners learn practical heuristics like 'if a team's pull request review cycle exceeds 48 hours, the cognitive load is too high' and how to use Wardley mapping and team cognitive load assessments to find bottlenecks. The conversation also touches on how this approach connects to Conway's Law and team topologies, with a real-world example from a mid-sized SaaS company.

#CognitiveLoad #TeamTopologies #ConwaysLaw #EngineeringManagement #SoftwareArchitecture #PlatformEngineering #DevOps #Agile #TechLeadership #FexingoBusiness #BusinessPodcast #CTO #Technology #Leadership #Productivity #ContextSwitching #BoundedContexts #SystemArchitecture

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-size SaaS company uses Cost of Delay to prioritize features. They break down the formula — value divided by duration — and walk through a real example where a login feature was deprioritized because its Cost of Delay was lower than a data export tool. They discuss how the CTO briefed product managers to estimate delay cost in dollar terms, and how the team used weighted shortest job first to sequence work. The conversation covers common pitfalls, like over-weighing urgency vs. value, and the importance of keeping estimates rough. Listeners learn a practical framework to cut through opinion-driven backlog debates.

#CostOfDelay #FeaturePrioritization #WSJF #CTO #EngineeringLeadership #ProductManagement #SaaS #BacklogManagement #Lean #Agile #TechLeadership #FexingoBusiness #BusinessPodcast #TechnologyPodcast #DecisionMaking #Prioritization #ValueStream #DeveloperProductivity

Keep every episode free: buymeacoffee.com/fexingo

Lucas and Luna explore how one CTO at a mid-size SaaS company uses customer journey mapping to align engineering teams around user outcomes instead of output metrics. They break down the specific technique — mapping every touchpoint from signup to renewal, tagging pain points with severity scores, and running monthly 'journey reviews' that replace feature-count standups. The episode walks through a concrete example: how a team used the map to deprioritize a flashy dashboard rebuild and instead fix a seven-step password reset flow that was churning 12 percent of new users. Lucas and Luna discuss the tension between product roadmaps and engineering reality, why journey maps cut cross-team silos, and how the CTO sold the approach to a skeptical VP of Sales. No buzzwords, just a real system that works.

#CustomerJourneyMapping #CTO #EngineeringLeadership #ProductAlignment #UserOutcomes #SaaS #TechLeadership #EngineeringManagement #JourneyMaps #UserExperience #ProductRoadmap #CrossTeamCollaboration #ChurnReduction #OutcomeOverOutput #FexingoBusiness #TechPodcast #BusinessPodcast #Technology

Keep every episode free: buymeacoffee.com/fexingo

Lucas and Luna explore how one CTO implemented energy budgets—a practice borrowed from embedded systems—to cut cloud infrastructure costs by 30 percent without sacrificing performance. The episode walks through the specific method: setting per-service power caps, measuring actual consumption against them, and using the data to retire waste. Lucas shares a case from a mid-stage fintech where each microservice got a monthly energy allowance in kilowatt-hours, the team built a simple dashboard, and within one quarter they shut down 12 underutilized services. Luna raises the natural resistance from engineers who fear performance degradation, and Lucas explains how the CTO addressed this by making budgets adjustable and tying them to team-level reliability reviews. The conversation also touches on how this approach creates a shared language between engineering and finance, and why it works better than traditional cost-tagging. The episode closes with a reflection on whether energy budgets could become a standard practice for cloud-native companies.

#EnergyBudgets #CloudCostReduction #FinOps #CTOStrategy #InfrastructureEfficiency #GreenTech #CostOptimization #Microservices #CloudNative #EngineeringLeadership #TechDebt #Sustainability #TeamAccountability #DashboardDesign #ServiceRetirement #FexingoBusiness #BusinessPodcast #Technology

Keep every episode free: buymeacoffee.com/fexingo

In this episode of Tech Leadership with Fexingo, Lucas and Luna explore chaos engineering with a concrete case: how a CTO at a mid-sized e-commerce platform used controlled fault injection to uncover a critical database failover bug before Black Friday. They walk through the specific experiment design—shutting down one of three Cassandra nodes during low traffic—and the surprising finding that the application's connection pool didn't retry, causing a 12-second timeout cascade. Lucas explains the principles behind chaos engineering (steady-state hypothesis, blast radius, automate experiments), and Luna pushes back on the cultural resistance: 'Our systems are too fragile for chaos.' The hosts discuss how starting with small, scheduled experiments in staging builds confidence, and share a practical framework for prioritizing which failure modes to test first. The episode closes with a reflection on whether chaos engineering is worth the investment for smaller teams.

#ChaosEngineering #ResilienceEngineering #SiteReliabilityEngineering #FaultInjection #TechLeadership #CTOTips #EngineeringManagement #ProductionTesting #FailureModeAnalysis #DatabaseResilience #Cassandra #HighAvailability #DevOps #SRE #SoftwareEngineering #Business #Technology #FexingoBusiness

Keep every episode free: buymeacoffee.com/fexingo

Episode 84 of Tech Leadership with Fexingo: Lucas and Luna dive into Architecture Decision Records (ADRs) — lightweight documents that capture the context, options, and rationale behind every major architectural choice. They walk through a real example from a fintech CTO who uses ADRs to prevent recurring debates, onboard new engineers faster, and create a searchable history of why the system is built the way it is. They discuss the typical ADR template, how to keep ADRs short enough to actually write, and when an ADR is overkill. Lucas shares a specific story about a team that saved months of rework by documenting a database choice. Luna challenges whether ADRs become shelfware, and they explore how to make ADRs a habit rather than a chore. If you are an engineering leader tired of repeating the same architectural conversation every six months, this episode gives you a concrete tool to stop the cycle.

#ArchitectureDecisionRecords #ADR #TechLeadership #FexingoBusiness #BusinessPodcast #CTO #EngineeringManagement #TechnicalDebt #Documentation #DecisionMaking #SoftwareArchitecture #TechStrategy #Onboarding #KnowledgeManagement #TechCulture #Leadership #Podcast #Technology

Keep every episode free: buymeacoffee.com/fexingo

Most technical decisions disappear into Slack threads and hallway conversations. In this episode, Lucas and Luna explore how one CTO uses a lightweight trade-off log to capture every architectural decision, the alternatives considered, and the reasoning behind the choice. They walk through a real example from a fintech startup that avoided a costly infrastructure pivot by consulting its own log, and discuss why writing down what you didn't choose is just as important as writing down what you did. The conversation covers the log's structure, how to make it stick without adding bureaucracy, and why it turns tribal knowledge into an organizational asset. If you've ever made a technical decision and later wondered 'why did we do that again?', this episode offers a practical fix.

#TradeOffLog #ArchitecturalDecisions #ADR #CTO #EngineeringLeadership #TechDebt #DecisionMaking #KnowledgeManagement #Fintech #Startup #SoftwareArchitecture #TechnicalDebt #EngineeringCulture #AsyncDocumentation #Technology #Leadership #FexingoBusiness #BusinessPodcast

Keep every episode free: buymeacoffee.com/fexingo

In this episode of Tech Leadership with Fexingo, Lucas and Luna explore how one CTO at a mid-stage SaaS company uses RFCs — Request for Comments documents — to drive technical alignment before any code is written. They walk through a real example: a proposed migration from a monolithic payment service to a microservices architecture. The CTO requires every significant technical decision to start with a written RFC that includes context, goals, non-goals, design options, and a clear recommendation. The hosts discuss why this practice prevents wasted engineering cycles, creates an auditable decision trail, and distributes architectural authority across the team. They also touch on common pitfalls like RFCs that are too long or too vague, and how the CTO uses lightweight templates to keep documents focused. Listeners walk away with a concrete framework they can adapt for their own teams — plus a one-line link to how the same documentation discipline applies to listener support.

#RFC #RequestForComments #CTO #EngineeringLeadership #TechDecisions #Architecture #Documentation #TeamAlignment #Microservices #Migration #DecisionMaking #EngineeringCulture #Technology #SaaS #Leadership #FexingoBusiness #BusinessPodcast #TechLeadership

Keep every episode free: buymeacoffee.com/fexingo

Most engineering leaders frame tech debt as a technical problem to be refactored. But what if the root cause is actually a product strategy gap? In this episode, Lucas and Luna look at how one CTO at a mid-sized SaaS company stopped treating tech debt as a code quality issue and started treating it as a product design issue. They walk through the concrete framework he used — mapping every recurring maintenance ticket back to a feature that was built without a product owner, then killing or redesigning those features instead of rewriting the code. The result: 40% less unplanned work in six months, and a product org that finally owned the consequences of scope creep. No abstract architecture theory. Just a specific, replicable decision-making pattern for any engineering leader.

#TechDebt #ProductThinking #EngineeringManagement #CTO #TechLeadership #SoftwareEngineering #ScopeCreep #MaintenanceCost #ProductStrategy #EngineeringCulture #SaaS #TechDebtReduction #FeatureDesign #UnplannedWork #TechPodcast #Technology #FexingoBusiness #BusinessPodcast

Keep every episode free: buymeacoffee.com/fexingo

Episode 80 of Tech Leadership with Fexingo dives into cost of delay — a prioritization framework that turns gut-feel roadmaps into dollar-weighted decisions. Lucas walks through a concrete example from a mid-stage SaaS company: three features, three delay scenarios, one number that blew up the existing roadmap. Luna challenges whether the model works when uncertainty is high, and Lucas shares how one CTO at a Series B fintech applied weighted shortest job first to cut time-to-value by 40 percent. No buzzwords — just the math, the trade-offs, and why your engineering team might hate you for asking 'what's the cost of waiting another quarter?' Recorded June 29, 2026.

#CostOfDelay #WSJF #Prioritization #ProductManagement #EngineeringLeadership #CTO #TechLeadership #DecisionMaking #RoadmapPlanning #LeanProductDevelopment #Agile #ContinuousDelivery #SaaS #Fintech #SeriesB #Technology #FexingoBusiness #BusinessPodcast

Keep every episode free: buymeacoffee.com/fexingo