Technical Coherence | Jack Danger
I wrote a whole book to help leaders reverse this slowdown and the central point of the book is a process any engineering leader can apply.
I call this process Technical Coherence and you can mostly achieve it in a single meeting with your leaders. You can implement it in your org gradually or all at once.
Answering these requires some kind of working theory of how engineering actually functions, otherwise we’re left copying the ratios and comp bands of other companies. No leader should have to be a copycat to answer basic questions about their org.
Technical Coherence is a theory and a structure to answer these questions about the whole system full of people and software and data.
This post takes as a given that there are three layers of engineering. Check out Infrastructure Gravity and Domain Engineering if that’s unfamiliar.
The first step to applying Technical Coherence is identifying UX domains. This term comes to us from the field of UX research but it’s similar to “bounded contexts” from Domain Drive Design. A UX domain is basically a bounded context of a user experience. Or, more helpfully, a UX domain is the whole set of things a person does while they’re in a specific role.
