Both halves of the problem
The technical half of the work is getting easier. The human half — judgment, trust, the call about what’s worth doing — is where the work, and the value, now live.
Where the work is moving
The mechanics of the work keep changing, but what we actually need people for doesn’t. For years, founders were told the idea barely matters — execution is everything, and the whole game is grinding toward product-market fit. That logic is quietly inverting. Execution is precisely the part AI is making cheap: the lines of code, the tickets closed, the throughput people used to be measured on. What’s left — and what’s becoming the most valuable thing a person does — sits at the two ends execution never touched: deciding what is worth doing, and judging whether the result actually matches the intention.
Those are judgment calls, and they carry values. A tool can propose; only people decide, adapt as the situation shifts, and hold the relationships an organization actually runs on. As the how gets automated, the what — and the did we get it right — become the work.
The hard problems aren’t technical
Most of the hard problems in mature engineering organizations are not purely technical. They are problems of trust, coordination, and alignment expressed through technical disagreements, organizational friction, and stalled decision-making. Two staff engineers arguing about a Kafka migration may really be struggling with unresolved tension after an acquisition. A platform team that “can’t get requirements out of product” may be carrying a much older breakdown in trust. These problems do not appear in architecture diagrams, and they rarely get resolved through another reorg, process change, or framework choice alone.
Our premise is that this work — surfacing the organizational dynamics inside technical teams — requires someone who can stay credible in the technical conversation and recognize what is shaping it underneath the surface.
How we work
Both at once. Most advisors in this space are either executive coaches and organizational psychologists who understand people but can’t follow a technical argument, or former VPs of Engineering who understand the work but default to restructuring orgs rather than mediating. The opening between those two is wide, and it is where we live.
Active in the work. We each bring 25+ years of hands-on experience across the tech industry, including distributed systems, embedded/RT, storage, verification, ML, and biotech. Within the past year, our work has been the same as our clients’: writing code, shaping architecture, running teams, and hiring. That keeps the conversation real: engineers can tell within ten minutes whether they’re talking to someone who follows the work, and so can the leaders who hired them.
A real partnership. We pool revenue and effort, share clients, and make decisions together. The way we collaborate is itself part of what we help organizations build.
Two perspectives, one practice. Our backgrounds are different — engineering disciplines, styles, and a gender-diverse pairing — and that range shows up in the room. Different conversations call for different instincts and forms of credibility, so we flex on who leads which one.
We teach more than we pitch. Both of us come out of teaching as well as building. The default move when we are in a room is to ask the question that helps people see the thing themselves, rather than deliver the verdict.
What you’re buying is judgment. We are an advisory practice, not a consultancy. Clients are paying for access to our judgment in conversations, not for documents we produce afterwards. That keeps the work honest and keeps us out of the document-factory trap.