







I have ended up managing people at the last three places I’ve worked, over the last 18 years. I can honestly say that only in the last few years have I really started to embrace the job of managing. Here’s a collection of thoughts and observations: Growth: Ideas and Opinions and Failures Expose your team to new ideas and help them create their own voice. When people get bored or feel they aren’t growing, they’ll look elsewhere. Give people time to explore new concepts, while trying to keep results and outcomes relevant to the project.
Solving the Engineering Strategy crisis.
These are speaking notes for my October 4th, QCon talk in San Francisco. See a video of this talk. Slides for this talk. Over the course of my career, I’ve frequently heard from colleagues, team members and random internet strangers with the same frustration: the company doesn’t have an Engineering strategy. I don’t think this problem is unique to Engineering: it’s also common to hear folks complain that they’re missing a strategy for Product, Design or Business. But, whereas I don’t feel particularly confident speaking to why so many companies are missing a clear Business or Product strategy, I’ve come to have some clear opinions about why so many engineering organizations don’t have a written strategy.

Measuring an engineering organization.
For the past several years, I’ve run a learning circle with engineering executives. The most frequent topic that comes up is career management–what should I do next? The second most frequent topic is measuring engineering teams and organizations–my CEO has asked me to report monthly engineering metrics, what should I actually include in the report? Any discussion about measuring engineering organizations quickly unearths strong opinions. Anything but sprint points! Just use SPACE! Track incident frequency! Wait, absolutely do not track incident frequency! Just make a pretty chart, they won’t look at it anyway! All of these answers, even the last one, have a grain of truth to them, but they skip past an important caveat: there are many reasons to measure engineering, many stakeholders asking for metrics, and addressing each requires a different approach.

Engineering managers have a new job description
Why engineering managers are expected to be hands-on again and how AI tools are making it possible to stay technically sharp while still leading.

Don't Feed the Thought Leaders
In this article, the author shares their experience as an engineering manager and the challenges they faced when trying to reach alignment and prev...

Write five, then synthesize: good engineering strategy is boring.
Few companies understand their engineering strategy and vision. One consequence of this uncertainty is the industry belief that these documents are difficult to write. In some conversations it can feel like you’re talking about something mystical, but these are just mundane documents. The reality is that good engineering strategy is boring, and that it’s easier to write an effective strategy than a bad one.

Scaling Engineering Teams: Lessons from Google, Facebook, and Netflix
After spending over a decade in engineering leadership roles at some of the world’s most chaotic innovation factories—Google, Facebook, and Netflix—I’ve learned one universal truth: scaling e…

Writing an engineering strategy.
Once you become an engineering executive, an invisible timer starts ticking in the background. Tick tick tick. At some point that timer will go off, at which point someone will rush up to you demanding an engineering strategy. It won’t be clear what they mean, but they will want it, really, really badly. If we just had an engineering strategy, their eyes will implore you, things would be okay. For a long time, those imploring eyes haunted me, because I simply didn’t know what to give them: what is an engineering strategy?

Unintuitive Things I’ve Learned about Management (Part 1)
I first started managing people seven years ago, three years after I graduated and got my first design job. At the time, I was woefully…

All the best engineering advice I stole from non-technical people
As I focus on becoming a better manager of engineers, I have been reflecting more and more on the advice that produced a 10X boost in my…

Bring a Product Manager Mindset to Your Next Engineering Job
The age of AI demands strong ideas, data driven methods, and experimentation

Is Project Management Killing Good Products, Teams and Software? - Slashdot
New submitter mikeatTB writes: "For software development, no significant developer activity is predictable or repetitive; if it were, the developers would have automated it already," writes Steven A. Lowe, Principal Consultant Developer at ThoughtWorks, via TechBeacon. "In addition, learning is esse...

Hiring (and Retaining) a Diverse Engineering Team
Stories from six engineering leaders who succeeded in building and growing diverse teams. Hiring approaches, retention tactics and strategies.

Engineering strategy notes.
Recently, I am thinking quite a bit about engineering strategy, and as part of that, I have started re-reading previous resources on the topic, and looking for new things to read while I refine my point of view on what makes for good engineering strategy. The best introduction to my current theory of engineering strategy is Solving the Engineering Strategy Crisis, which has both written and video versions. You can also read my other strategy writing via the strategy tag.

How to build a generative engineering culture
A generative engineering culture is one where nothing seems to fall through the cracks, “we should” gets prioritized and becomes reality, and original ideas and value come primarily from engineers, rather than management. A culture like this is an engine for building capacity, quality, innovation, and sophistication.
The Engineering Leadership Report 2026
Our survey of 600 engineering leaders exploring how the role is evolving, where the challenges lie, and what the future holds for the job.
