Skip to content

Leadership · Business & Insights

Industry insights, business analysis, and real-world experiences

Wider Responsibility, Thinner Belonging: Pick Your First Team

At staff and manager level, responsibility spans teams while belonging thins. Pick a first team, tie belonging to a shared outcome, and keep the group open.

leadership · engineering-management · team-dynamics +1

Engineering Progression Frameworks: Shape Follows Company Size, and in the EU, Pay Law2/2

How engineering progression frameworks change with company size and type, how the EU Pay Transparency Directive treats level criteria, and what US range laws ask.

career · engineering-management · organizational-design +2

Build an Engineering Progression Framework: A Worked Example for a 40-Engineer EU Company1/2

Build an engineering progression framework from a worked example: level criteria per factor, pay bands, a promotion packet, works council steps, and placement.

career · engineering-management · organizational-design +2

AI Shame in Software Teams: Why Engineers Hide AI Use

Engineers hide AI use because teams still price visible effort and penalize disclosure. The ethical lines are accountability, data boundaries, and honest evaluation.

engineering-culture · psychological-safety · ai-tools +1

Communication Is the Gate to Your Next Engineering Level

Technically solid but stuck at one level? What engineering communication means as concrete artefacts, why ladders gate the next step on it, and where to start.

career · leadership · documentation +4

AI Made Code Cheap and Review Expensive

AI-assisted coding made generation cheap and verification heavy. Why CTOs should pace adoption to review capacity, and what to measure beyond velocity.

leadership · engineering-management · ai-adoption-strategy +3

Who Owns This Code Now: Accountability vs Blame

Stop asking who wrote the legacy code. Separate responsibility, accountability, and blame, and make inherited code owned rather than orphaned.

engineering-culture · leadership · team-management +3

Blameless Postmortems: A Model and a Copy-Paste Template

A blameless postmortem model that fixes the system instead of finding a culprit, with a copy-paste template and where individual accountability still applies.

engineering-culture · incident-response · psychological-safety +4

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

RACI and DACI for Software Teams: Fixing Role Ambiguity

Unclear role expectations quietly drain software team productivity; here are proven RACI, swim-lane, and escalation frameworks to remove the waste and lift performance.

leadership · team-management · best-practices +4

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