Engineering Culture
Sweating the Bar and Raising the Details
Management meetings were built for an older information system. Poor writing keeps the machinery alive, and one calendar invitation can commit thousands before anybody acts.
Teams that match the system you want, not the org chart you inherited. Mirrored front end and back end crews, centres of excellence when they earn it, release trains for coordination, and ownership that is clear enough to make escalation boring.
Engineering Culture
Management meetings were built for an older information system. Poor writing keeps the machinery alive, and one calendar invitation can commit thousands before anybody acts.
Engineering Culture
Cascading a message through management loses reach, meaning and accountability. Policy owners should publish directly, notify proportionately and put repeated rules into the workflow.
Organisational Design
AI extends the reach of engineering judgement. Product delivery units can become smaller, management spans can become wider, and collective stewardship can remain.
Organisational Design
AI lets one engineer carry work that might once have required a cross-functional product development team. Delivery units can shrink, management spans can widen, and the community can still own the product.
Organisational Design
AI has reduced the cost of coordination across software engineering. Our management structures should probably notice.
Developer Experience
Why code review must be predictable, humane, and measured.
Organisational Design
When muscles and nerves aren’t enough to stand.
Organisational Design
The practices that make companies faster, safer, and engineers more valuable.
Developer Experience
One wardrobe, many uniforms, one team.
Developer Experience
Why weekly release trains and a monorepo culture deliver stability, speed, and less toil.
Developer Experience
Clarity in the address line is clarity in the organisation.
Organisational Design
Balancing integration, adoption, and the lure of best-of-breed.