Skip to content

engineering-management

8 posts

engineering-management
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

The Expectation Gap: When Hiring Promises Meet Workplace Reality

An analysis of bait-and-switch hiring, power imbalances, and underemployment, with actionable frameworks for employees to protect themselves and employers to build trust.

hiring · career · team-dynamics +3

Post-Acquisition Culture Integration: Why Acquisitions Fail

Why acquirers destroy the value they paid for through cultural absorption, with M&A failure patterns, organizational research, and proven integration strategies.

business-strategy · organizational-culture · leadership +3

Role Expectations in Software Teams: RACI and DACI Frameworks

Unclear ownership stalls software delivery. How RACI and DACI assign decision rights, where each one fits, and the pitfalls that kill adoption.

team-management · engineering-management · productivity +2

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

How to Write a Technical RFC: Section-by-Section Guide

A section-by-section guide to technical RFCs: what each part has to establish, what reviewers look for, and where proposals stall in review.

rfc · documentation · architecture +3

Deep Democracy Between Product and Tech Teams: From Deadline Dictatorship to Collaborative Delivery

Turn adversarial product-engineering standoffs into collaborative delivery with Deep Democracy principles that surface dissent and reduce burnout.

product-management · engineering-management · team-dynamics +4

How to Write an Effective RFC: A Guide for Engineers

Practical guidance on RFC structure, stakeholder review, and turning technical debates into decisions a team actually keeps.

rfc · documentation · architecture +3