Skip to content
~/sph.sh

organizational-design

4 posts

organizational-design
Engineering Team Documentation: Working Agreements, Definition of Done, and On-Call Docs

The team documents a mature engineering team owns: onboarding, working agreements, Definition of Done, on-call, knowledge transfer, and what makes each one good.

engineering-culture · hiring · documentation +4

The Staff Engineer Solver Archetype: An Operating Model

A handbook for the informal fast track: recognise the Solver role, codify its operating model before the role calcifies, and time it against the title-and-pay talk.

career · engineering-management · organizational-design +1

Documentation as Infrastructure: Scaling Knowledge Across Engineering Teams

Documentation debt can slow teams faster than technical debt. A guide to treating docs as critical infrastructure and scaling knowledge across engineering teams.

documentation · rfc · team-management +3

Holacracy vs Team Topologies: Team Autonomy Models Compared

Practical structures and guardrails that raise team autonomy without chaos, drawing on Holacracy, the Spotify model, and Team Topologies.

organizational-design · leadership · dora-metrics