AI · Architecture · Engineering Leadership

Engineering the future of software organizations

AI is changing more than how software is engineered and written. It's changing how the organizations that build it need to be designed, led, and operated.

Read the articles

Areas of Practice

Where two decades of experience meet the future of building.

Enterprise AI & Agentic Engineering

Adopting AI the way real engineering teams work: agentic development, spec-driven builds, and tools that make developers faster instead of slower.

Cloud Engineering

Cloud-native delivery on AWS, from infrastructure automation to the distributed systems it runs on.

Software Engineering

Building and shipping software for more than two decades, across every shift the technology has gone through.

Enterprise Architecture

Architecture that keeps options open instead of locking a team into today's decision.

Engineering Leadership

Leading without the title: mentoring engineers and changing how teams actually work.

Product Leadership

Six years in product management, spent figuring out what customers actually needed instead of just what they asked for.

Central Thesis

The challenge has shifted from building more software to building better technology organizations.

The old engineering approach was built for a different constraint.

For decades, the biggest challenge was building software. It was expensive, and there were only so many engineers who could do it.

AI is changing that equation.

As creating software gets easier, the real constraint shifts. What's left is harder to automate: good judgment, and people who know which problems are worth solving.

Technology alone has never been the competitive advantage. The organizations that learn the fastest and adapt the fastest are the ones that win.

Ideas shaping the future of technology organizations.

View all articles

Strategy

Man Hours Went Down. The Bill Did Not.

AI cut man hours to almost nothing, but token spend didn't shrink with it, and none of it is worth anything if nobody goes back to confirm the user's problem actually got solved.

Operating Model

Small Was Never About How Fast You Could Build It

AI made it fast to build things once called 'small,' but small was always a measure of risk, not build time, and those two stopped being the same thing.

Operating Model

Waterfall With a Better Interface

Spec-driven development promises efficiency, but a long spec written before anyone validates the problem is the same mistake as waterfall, just running at agent speed instead of committee speed.

20+

Years building technology

About

The journey behind the ideas.

I've spent over 20 years in software, engineering, product, architecture, and leadership. None of it made me care about technology for its own sake. What held my attention was different: why some organizations build things people love while others, with just as much talent, don't.

The answer is rarely a skills problem. It's usually the system built up around good people that makes good work harder than it should be.

Along the way I've worked as a consultant, a project manager, an engineering manager, and eventually a coach helping other teams get better at how they build software. Every one of those jobs pointed at the same thing: the best fixes usually happen at the edges, where product, architecture, and engineering actually sit down together instead of staying in their own lanes.

Start a conversation

Contact

Let's rethink how software organizations are built.

If you are an engineering leader rethinking how your organization operates in the age of AI, I would love to talk.

Start a conversation