Our approach
Both halves of the problem
The technical half of the work is getting easier. The human half is where the work and the value now live.
Where the work is moving
The mechanics keep changing. What we need people for hasn’t budged. Execution used to carry most of the weight. It’s also the part AI is making cheap: the throughput people used to be measured on, like lines of code and tickets closed. What’s left 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.
Surfacing organizational dynamics
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 are problems of trust and alignment, expressed through technical disagreements and stalled decision-making, which rarely get resolved through another reorg or process change alone.
Surfacing those dynamics takes someone the engineers will argue with on the merits.
How we work
Both at once. Staying credible in a technical argument and understanding the human side of it are different skills, and the work needs both in the same conversation. That combination 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 quickly 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. We share clients and make decisions together. The way we collaborate is itself part of what we help organizations build.
Built-in range. Our backgrounds are different: different engineering disciplines, different working styles. We’re also 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.
What you’re buying is judgment. We are an advisory practice. Our deliverable is honest judgment in conversations you can act on. Not documents you’ll file away.
Want to talk it through?
Let's talk