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 can use feature flags to decouple deployment from release. They walk through a real example from a mid-size SaaS company that reduced rollback incidents by 70 percent using a structured feature flag strategy. The hosts discuss flag lifecycle management, the dangers of flag debt, and how progressive delivery with flag...

In this episode of Tech Leadership with Fexingo, Lucas and Luna explore how one CTO at a fintech startup used structured observability—specifically, slashing alert noise by 70 percent—to transform on-call rotations from a burnout generator into a learning tool. They walk through the specific metrics, the shift from symptom-based to root-cause alerting, and how observability drove a 40 percent redu...

Lucas and Luna explore how a CTO at a mid-size SaaS company used a 'small bets' approach to test product hypotheses before committing engineering resources. They break down a specific case where the CTO allocated $5000 and two weeks to build a clickable prototype for a new AI feature, validated demand with 200 paying customers, and then greenlit full development — avoiding a six-month, $200,000 bu...

Most engineering teams build features without knowing their true cost. In this episode, Lucas and Luna explore cost-to-serve metrics — a technique used by CTOs to calculate the full infrastructure, maintenance, and support cost of each feature in production. They walk through a concrete example from a mid-stage SaaS company that discovered one of its most popular features was actually losing money...

In episode 100, Lucas and Luna explore how Wardley Mapping helps CTOs visualize strategic landscapes and make better platform investment decisions. Lucas walks through a concrete example from a mid-stage fintech that was debating whether to build or buy a compliance engine. By mapping users, needs, and components onto an evolution axis, the CTO spotted an opportunity to use a managed service for t...

In episode 99 of Tech Leadership with Fexingo, Lucas and Luna explore how CTOs can use internal developer platforms (IDPs) to reduce friction for engineering teams. They break down the concept using the real-world example of a mid-size fintech that built a 'golden path' platform, cutting new service deployment time from three weeks to two days. The hosts discuss the trade-offs between buying versu...

In this episode, Lucas and Luna explore the concept of the technical sparring partner — a practice where engineering leaders invite a trusted peer to stress-test major technical decisions before committing. They unpack how one CTO at a mid-stage SaaS company used a formal sparring partner from a non-competing firm to avoid a costly database migration mistake. The conversation covers the ground rul...

Episode 97 of Tech Leadership with Fexingo explores how engineering leaders use timeboxed experiments to escape analysis paralysis. Lucas and Luna examine a real case from a mid-size SaaS company whose CTO mandated that any architectural decision with no clear winner must be settled by a two-week prototype. They walk through how the team reduced decision cycle time by 60 percent, cut meeting hours...

Episode 96 of Tech Leadership with Fexingo: Lucas and Luna explore how one CTO slashed new-hire onboarding from six weeks to six days by building an internal developer platform. They break down the specific workflows that were automated — local environment setup, CI/CD configuration, access provisioning — and the surprising cultural resistance the CTO encountered from senior engineers who saw the...

Episode 95 of Tech Leadership with Fexingo dives into how a CTO at a mid-size SaaS company uses leading indicators — not lagging ones like velocity — to predict sprint outcomes before they happen. Lucas and Luna unpack the specific dashboard he built: cycle time for open items, work-in-progress count, and scope-change rate. They discuss why measuring 'how many tickets are in flight' beats measurin...

In this episode, Lucas and Luna explore platform engineering through the lens of a real 2025 migration at a mid-sized fintech, where the CTO reduced deployment time from 40 minutes to 4 minutes by building an internal developer platform. They break down the three core layers of a platform — the developer portal, the golden path, and the self-service infrastructure — and discuss why platform engine...

In this episode of Tech Leadership with Fexingo, Lucas and Luna explore how one CTO at a mid-market SaaS company uses the four DORA metrics (deployment frequency, lead time for changes, change failure rate, and time to restore service) to measure and improve engineering team performance. They walk through a specific case: a 40-person engineering org that reduced its change failure rate from 15% to...

In this episode of Tech Leadership with Fexingo, Lucas and Luna explore how one CTO applies behavioral economics — specifically nudge theory — to improve code quality and developer habits without heavy-handed process mandates. The episode centers on a real case: a mid-sized SaaS company whose VP of Engineering, Maria Chen, replaced mandatory code reviews and style guide enforcement with subtle, de...

Episode 91 of Tech Leadership with Fexingo. Lucas and Luna explore how forward-thinking CTOs use a decision log — a simple living document that records every major technical and strategic choice, why it was made, what alternatives were considered, and the expected outcome. They walk through a real example from a mid-stage SaaS company that cut rework by 40 percent after adopting this practice. The...

In this episode of Tech Leadership with Fexingo, Lucas and Luna explore how a CTO at a mid-sized SaaS company uses the cost of delay framework to prioritize features. They break down a real example: deciding between a new integration and a performance upgrade, using cost of delay divided by duration (CD3) to quantify urgency. Lucas explains how this method shifted the team from 'loudest voice wins...

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

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

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

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

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

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

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

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

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

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