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

In this episode of Tech Leadership with Fexingo, Lucas and Luna explore how a CTO uses Wardley Mapping to visualize strategic trade-offs and find competitive advantage. They break down a real example from a fintech startup that mapped its payment flow to discover a hidden dependency on a legacy fraud provider, leading to a build-vs-buy decision that saved millions. You'll learn the basics of Wardl...

In this episode, Lucas and Luna explore the pre-mortem technique—a structured exercise where engineering teams imagine a project has already failed and work backward to identify what went wrong. Lucas walks through a real example from a CTO at a mid-sized SaaS company who ran a pre-mortem before a major platform migration, uncovering hidden assumptions about database load and third-party API rate...

In this episode of Tech Leadership with Fexingo, Lucas and Luna explore how a CTO at a mid-size SaaS company uses feature flags to decouple deployment from release. They walk through a concrete example: a payment flow redesign that was hidden behind a flag for six weeks while the team iterated on error states. The conversation covers toggle hygiene, the risk of flag debt, and why trunk-based devel...

When the site goes down, most teams panic. This episode examines how one CTO implemented a structured incident commander role modeled on emergency response protocols. Lucas and Luna walk through a real outage at a mid-sized SaaS company where the commander's clear decision-making reduced mean time to resolution by over 50 percent. They discuss the five key responsibilities of the role, how to trai...

Episode 75 of Tech Leadership with Fexingo dives into how one CTO used an internal developer platform (IDP) to reduce cognitive load for his engineering team. Lucas and Luna break down the real-world case of a mid-stage SaaS company where the CTO built a thin platform layer that abstracted away infrastructure complexity, allowing developers to deploy code without navigating Kubernetes, CI/CD pipel...

In this episode of Tech Leadership with Fexingo, Lucas and Luna explore how engineering leaders can move beyond finger-pointing by institutionalizing blameless postmortems. They examine the case of a fintech startup whose CTO transformed incident response after a costly production outage, reducing repeat incidents by 60 percent in six months. The hosts break down the step-by-step process: writing...

In this episode of Tech Leadership, Lucas and Luna explore a counterintuitive approach to reliability: putting a dollar figure on every incident. They walk through how a CTO at a mid-size fintech built a simple 'incident cost calculator' — estimating engineering time, customer churn risk, and reputational damage — and used that data to convince the board to invest in proactive fixes instead of alw...

Episode 72 of Tech Leadership with Fexingo. Lucas and Luna dive into the practice of API versioning as a strategy to prevent breaking changes in production. They discuss the pragmatic approach taken by Sarah Chen, CTO of a mid-size fintech, who implemented a URL-based versioning scheme with a sunset policy. Lucas explains how her team uses semantic versioning for APIs, communicates deprecations vi...

In episode 71 of Tech Leadership with Fexingo, Lucas and Luna explore platform engineering through the lens of a real-world case: a fintech CTO who reduced new-developer onboarding from three weeks to under four hours. They break down the internal developer platform (IDP) built around Backstage, the golden path templates that automate environments and CI/CD, and the cultural shift required to get...

Lucas and Luna explore the concept of error budgets, a tool borrowed from Google's Site Reliability Engineering that helps engineering leaders decide when to push features and when to protect reliability. They discuss how one CTO at a mid-sized fintech company implemented a monthly error budget of 0.1 percent downtime per service, and how the team used that budget to make trade-offs explicit. The...

In this episode of Tech Leadership with Fexingo, Lucas and Luna explore how a CTO at a 200-person SaaS company replaced traditional standup meetings with an async daily update system—and got better alignment, fewer interruptions, and faster decision-making. They walk through the specific tooling (Slack + a lightweight bot), the three-question format that replaced 'what did you do yesterday,' and t...

Lucas and Luna dive into the surprisingly powerful practice of decision logging for engineering teams. They explore how one CTO at a mid-size SaaS company implemented a structured decision log to capture every major technical and product decision—including the context, alternatives considered, and the reasoning behind the final choice. The hosts discuss how this simple practice prevented repeated...

Lucas and Luna explore a surprisingly low-tech tool used by high-performing CTOs: the decision log. They examine how a CTO at a mid-size SaaS company started documenting every architectural and strategy decision in a shared, timestamped document — including the context, alternatives considered, and the expected outcome. The hosts discuss why this practice prevents 'decision amnesia,' reduces re-li...

Episode 66 of Tech Leadership with Fexingo. Lucas and Luna dive into a specific cost-to-serve analysis at a mid-market SaaS company that revealed 12% of features consumed 40% of engineering maintenance but generated zero revenue. They walk through how the CTO identified the hidden costs, made the case to the CEO, and sunset the features without losing customers. A concrete playbook for any enginee...

In this episode, we unpack the story of a CTO at a mid-size e-commerce company who ran a series of load tests six weeks before Black Friday and discovered that a single database query would have taken down the entire checkout system under expected traffic. Lucas walks through the engineering choices — why they used k6 for scripting, how they simulated realistic user journeys, and the specific bott...

In episode 64 of Tech Leadership with Fexingo, Lucas and Luna explore the concept of long-running product experiments—controlled tests that run for weeks or months to validate strategic bets before committing engineering resources. They dive into a case study from a mid-sized SaaS company whose CTO ran a 90-day experiment on a new pricing tier, measuring not just revenue but also support tickets,...

In this episode of Tech Leadership with Fexingo, Lucas and Luna unpack a concrete approach to engineering career ladders: the public rubric used by a mid-stage SaaS CTO. They discuss how he replaced vague titles with a matrix covering four dimensions — scope, complexity, autonomy, and impact — and tied each level to specific, measurable behaviors. Lucas shares how the rubric cut promotion disputes...

In this episode, Lucas and Luna explore how a CTO at a mid-sized fintech company uses chaos engineering to proactively test system resilience in production. They break down a specific case where injecting latency into a payment service uncovered a cascading failure that would have caused a major outage. The discussion covers the principles of chaos engineering, how to start small with game days an...

In this episode, Lucas and Luna explore how a CTO at a mid-sized SaaS company replaced manual tech decision processes with automated decision records. They discuss the problem of decision fatigue in engineering teams, how the CTO built a lightweight system using RFCs and automated linting to enforce architecture standards, and the surprising outcomes: faster onboarding, reduced tech debt, and fewe...

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 featur...

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 c...

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, evolu...

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 conversat...

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,...

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 depl...