Writing for visibility
- A staff‑engineering thread argued written artifacts are key to scaling influence and making work visible across an organization. - It lists design docs, post‑mortems, and strategy memos as high‑leverage practices for senior ICs moving toward director roles. - The thread frames writing as a primary lever for organization‑wide clarity and leadership resonance. (x.com)
A staff-engineering thread argues that writing, not just shipping code, is how senior individual contributors make decisions visible across a company. (x.com) The post points to three written artifacts in particular: design docs before work starts, post-mortems after failures, and strategy memos that connect technical choices to business direction. The author published the thread on X under the handle Anirudhology. (x.com) That framing lines up with how large engineering organizations already operate. Google’s public engineering-practices repository says its documents capture “collective experience” developed across projects, and Google’s Site Reliability Engineering workbook says post-mortems should be written, acted on, and widely shared. (google.github.io) (sre.google) The argument lands in a career band where scope expands faster than direct control. Staffeng.com, a guide based on interviews with senior engineers, says Staff-plus roles often span multiple teams, and its “Right Hand” archetype appears in organizations with hundreds or thousands of engineers. (staffeng.com) In that model, documents become a way to move decisions without attending every meeting. A design doc records tradeoffs before a build, a post-mortem records what failed and why, and a strategy memo gives leaders a durable explanation they can reuse. (x.com) (sre.google) Google’s postmortem guidance makes the same organizational point in more formal language. It says a blameless postmortem culture improves reliability and that widely shared writeups can drive change beyond the team that handled the incident. (sre.google) Will Larson’s staff-archetype taxonomy also helps explain why writing carries extra weight at senior levels. The Tech Lead, Architect, Solver, and Right Hand archetypes all operate beyond a single ticket queue, and the Right Hand role explicitly extends an executive’s attention across a complex engineering organization. (staffeng.com) The thread’s core claim is that visibility comes from artifacts other people can read later, not from being present in the room once. In organizations large enough to need Staff-plus roles, the written record often becomes the work product that outlasts the meeting and travels furthest. (x.com) (staffeng.com)
