A selected collection of leadership principles, operating models, and real-world lessons from leading web platform teams, improving developer productivity, and partnering with business stakeholders.
I use this playbook to document how I think about engineering leadership: building healthy teams, creating platform leverage, improving execution, adopting AI responsibly, and connecting engineering work to measurable business outcomes.
Web Platform Engineering
A web platform is a long-lived product. The choices that compound are editorial experience, who owns maintenance after launch, and whether the architecture stays reusable under pressure.
Engineering Productivity & Delivery
Speed under pressure is real engineering work. The craft is sequencing so tracks do not block each other, and making every quality-for-speed trade visible and agreed before you take it.
AI-Assisted Engineering
AI tooling sticks when engineers choose it, not when they are told to. Start where the risk is low and the time savings are obvious, keep human review as the guardrail, and measure the difference.
Leadership & Team Health
Hiring for how people treat each other, growing engineers into larger roles, and being the steady point when the organization goes uncertain are the same job. Protecting the team is how the work gets delivered.
Leadership & Team Health
A weekly one-on-one is a recurring promise to a person, owned by them and protected like any other commitment. Held that way, it stops being a status meeting and becomes the place where trust is built and where friction surfaces long before it reaches the work.
Leadership & Team Health
Hiring failures rarely come from bad judgment about skill. They come from real behavioral observations getting softened in the debrief. Make every observation count as data, because a muffled flag costs the team far more than a reopened search.
Web Platform Engineering
A web platform is a long-lived product. The choices that compound are editorial experience, who owns maintenance after launch, and whether the architecture stays reusable under pressure.
Web Platform Engineering
When every page needs an engineer, marketing moves at engineering speed and engineers become a content bottleneck. A governed component library lets marketers ship on their own and lets engineering protect quality where it compounds.
Web Platform Engineering
Page speed matters because of what it moves: conversion, bounce, and search visibility. Treat performance as a business investment with diminishing returns, and build it into the component library so it holds without heroics.
Engineering Productivity & Delivery
Speed under pressure is real engineering work. The craft is sequencing so tracks do not block each other, and making every quality-for-speed trade visible and agreed before you take it.
Engineering Productivity & Delivery
A web team earns strategic standing the day its work is prioritized against business impact instead of stakeholder volume. The shift from reactive queue to defensible roadmap is an operating model change, not a tooling change.
Engineering Productivity & Delivery
Whether a web team runs on a roadmap or drowns in requests is decided at intake. Require a business goal and a target metric on the way in, rank with one model applied in the open, and separate self-serve work from engineering work at the door.