Inheriting an Engineering Team You Did Not Hire

New engineering leader walking into the open-plan office of an engineering team she inherited and did not hire

By Kris Drouet, Engineering Executive, in partnership with KORE1 When you inherit an engineering team you did not hire, diagnose the system before you judge the people. Most of what reads as individual underperformance is your predecessor’s operating model still running, and it will produce the same results with anyone sitting in those seats. The … Read more

Team Topologies in Practice: Stream-Aligned, Platform, and When to Split

Engineering leaders mapping team topologies boundaries with printed cards during an org design session

By Kris Drouet, Engineering Executive, in partnership with KORE1 Team Topologies is an org-design model with four team types, stream-aligned, platform, enabling, and complicated-subsystem, plus three interaction modes. Most companies need two of them. You split a team when its cognitive load outgrows one complex domain, not when its headcount crosses a number. A CTO … Read more

The Four Delivery Metrics That Predict Engineering Velocity (And the Two That Mislead You)

Two engineering leaders discussing which delivery metrics predict engineering velocity before an executive review

By Kris Drouet, Engineering Executive, in partnership with KORE1 Four delivery metrics predict engineering velocity: change lead time, deployment frequency, change fail rate, and failed deployment recovery time. Story-point velocity and sprint completion rate predict almost nothing, because both are calculated from the estimate rather than from the delivery. I sat in a quarterly business … Read more

Why “Tech Debt” Is the Wrong Frame: Renaming the Problem to Get the Resources

Engineering executive presenting a technical debt funding request to three seated executives in a boardroom

By Kris Drouet, Engineering Executive, in partnership with KORE1 Selling tech debt to executives fails because the phrase names four unrelated problems at once. Split it into security exposure, delivery cost, key-person risk, and a growth ceiling, then bring the one your CFO already funds. I have watched the same request get denied and then … Read more

AI Code Review for Engineering Teams: A VP’s Guide to Not Becoming the Bottleneck

Vice President of Engineering standing in a modern office hallway, representing engineering leadership on AI code review governance

By Kris Drouet, Engineering Executive, in partnership with KORE1 AI code review works for engineering teams when a VP assigns a named human owner to every risk tier, sets a review SLA the team tracks weekly, and reserves final judgment for changes touching trust boundaries, money, or production access. That’s the entire operating model in … Read more

When to Buy and Then Build On Top: The Most Underused AI Pattern in Mortgage Tech

Engineering executive weighing how much of a vendor AI platform to trust versus build custom on top

By Kris Drouet, Engineering Executive, in partnership with KORE1 Buy the vendor’s AI for the seventy percent every lender needs, document intake, underwriting signals, compliance logging, and build custom only at the one exception queue that is actually yours. Most engineering leaders pick one extreme or the other. The pattern that actually works sits in … Read more

Fintech Engineering Velocity Without Audit Pain: 3 Patterns That Actually Work

Fintech engineering VP who keeps release velocity high through audits with a risk-tiered change process

By Kris Drouet, Engineering Executive, in partnership with KORE1 Fintech engineering teams keep velocity through an audit by making evidence a byproduct of the pipeline, tiering changes by risk instead of reviewing everything equally, and documenting a break-glass path before they need it. Three patterns. I have shipped under all three, auditors have signed off … Read more