I’m Writing a Book About Tech Innovation and Team Dynamics
Just in Time for Today’s Challenges
The software industry is at an inflection point. AI won’t fix our fundamental challenges—it’s revealing cracks in the foundation we’ve long ignored about how software is built.
Long before the AI coding agent frenzy, I starting writing a book on how organizations consistently fail at creating software and how to remedy that.
If you believe tech problems (and people problems) will magically vanish because AI bots will solve them, you’re dead wrong. In fact, the opposite is true: aligning people and technology is more crucial than ever because the democratization of software development intensifies your competition. The only thing setting you apart is your ability to bridge the gap between everyone in your organization.
Developers aren’t going away. The future belongs to those who understand what was built and can troubleshoot it when it breaks. You won’t outrun complexity and it’s unsafe to assume someone else will figure it out. The only thing that’s certain to help is to focus on improving your communication.
This new age in software leadership is just beginning.
An Excerpt From the Book
Why do multimillion-dollar software projects fail—even when they are constructed within a rigorous process that is meant to ensure their success?
How do organizations that are filled with highly intelligent people end up making catastrophic mistakes?
Why is building software with others much harder than it seems?
The reasons for the big failures of software teams are numerous and intertwined. It’s a lattice of complexities.
Nevertheless, you can use mutual trust to create a highly engaged, highly efficient, and loyal team of developers. Once trust is present, you can tap into the intelligence of the group—including, quite literally, all of the people building and touching the software product or service, not just developers. If you can do that, success is all but guaranteed.
There are countless well-written books about leadership, yet most organizations still struggle to lead the people who can make their companies successful. Have you noticed that there’s not a lot of information out there that addresses the nuances of working with developers? Have you ever had a project held hostage by a developer over what seems to be a petty disagreement? Your feeling of powerlessness in such a situation might have driven you to react in ways you’d rather not admit.
Many hard skills can be reliably taught, but attitude, character, and culture are not as easy to change. It is possible to change your developers’ culture, but not without first changing your own attitude, character, and approach.
Early Access Reading
Fill out the contact form and include “beta reader” in your message and I can grant you early access when the manuscript is complete.