When you share engineering metrics with executives, link each one to a key business goal. First, find out which outcomes matter most to your leaders, such as cutting costs, speeding up delivery, or improving product quality. Next, figure out which engineering work supports those goals and choose metrics that show
Writing
On Writing Well is a book that made it easier for me to write non-technical documents. Writing non-technical documents used to be a significant challenge for me, but William Zinsser’s On Writing Well changed my entire approach. By focusing on clarity and simplicity, I discovered how to better connect
Metrics
After years of leading engineering teams, I’ve noticed that we all aim to build better, faster, and smarter systems. We rely on metrics to guide our decisions. But I’ve also seen these numbers backfire, hurting morale and blocking the innovation we want. There’s an intricate relationship between
Security
A team works best when it can quickly find and fix system issues. Speed and accuracy both matter. Success also depends on how much risk the organization is willing to take and how much technical debt stands in the way of fixing big security problems. 💡The answer is not to
AI
1. Our Core Principle We use AI to help us do more, but we don’t let it replace our own judgment. We are fully responsible for every line of code, every design choice, and every customer interaction, even if AI helped us. 2. Roles & Responsibilities We’ve set
AI
As we built modern, efficient teams, our true goal emerged: work smarter while retaining the personal touch that makes our products special and delights our customers. To address these needs, we created the AI-Human Workflow Matrix. This structured approach helps us decide when to assign tasks to AI rather than
Feedback
Code review has always been a sign of a healthy team and our last line of defense against expensive mistakes, whether we used paper in the 1970s or AI tools today. It reminds me that responsibility and teamwork have always mattered in this process.
Feedback
In the last post, I wrote that creating a common bond helps create a culture of respect and shared goals. In any convertion having a clear structure helps reduce anxiety for everyone in these conversations. Here are two templates I use to keep things focused, supportive, and effective.
Feedback
This blog explores how software engineering leadership is less about rigid status updates and more about building a "Common Bond" to drive growth. A good 1-1 serves as a psychological "growth lab".