Skip to content

Staff+ Council

Status: drafted · Time: 12 min · Audience: staff-plus Outcome: Understand what the Staff+ Council is, what it does, how a builder joins it, and what the chapters cover.

What this is. The standing community of senior contributors who shape the program’s AI direction over multi-year horizons. Members are invited when they are already operating at the level. They sit on the Council, sponsor RFCs, mentor Black Belt candidates, and represent the program externally through writing, speaking, and OSS contributions.

What this is not. A belt to earn. A management layer. A closed circle. A credential. The literature is unanimous on these points and the chapters are explicit about them.

Who reads these chapters. Black Belts who have closed the curriculum and want to understand the next layer. Engineers who have been invited to the Council and need to know what to expect. Anyone who wants to understand how the program governs itself.


The four belts (White, Yellow, Green, Black) describe a learnable progression. A reader walks them, claims them, and crosses into the next. Each belt has quests, evidence, and a badge. The Council is structurally different. It is a community, not a credential. People do not earn their way in; they are invited when peers and engineering leadership recognise that they are already operating at the level.

The literature on senior-IC communities is now extensive. Will Larson’s Staff Engineer (2021), Tanya Reilly’s The Staff Engineer’s Path (2022), and Lara Hogan’s Resilient Management (2019) describe the patterns at organisations such as Stripe, Slack, GitHub, Squarespace, Etsy, and Intercom. The patterns differ in detail; they agree on shape. There is a layered membership structure (a wide channel, a working forum, a smaller decision-shaping group). There is a charter that the community revises annually. There is an RFC archive that doubles as a teaching corpus. There are mentoring and sponsorship norms that recognise senior-IC time as the scarce resource it is. There is an external-voice posture that acknowledges reputation accrues to the engineer, not just the company.

These chapters synthesise that public material into a Council framework the program can adopt and adapt. They are not an invention; they are a faithful application of the public engineering literature to the program’s specific context.


Five things, drawn from the literature and adapted for the program:

  • Technical alignment across organisational boundaries. The Council is the layer where senior contributors notice when teams are diverging on architecture, agent design, or platform choices, and convene the conversation that aligns them.
  • Succession. The Council watches the Black Belt cohort. Members notice the engineers who are operating at the level before anyone else does, and recommend the next invitations.
  • RFC sponsorship and review. The Council is the body that sponsors RFCs against the program’s AI surface and reviews peers’ submissions with seriousness.
  • Mentoring and sponsorship at the senior level. Council members coach Black Belt candidates through their boss fights, advocate for under-recognised engineers in rooms those engineers are not in, and treat mentoring as recognised work.
  • External representation. Council members write, speak, and contribute to OSS in ways that represent both the program and themselves. The chapter on external voice makes the boundary explicit.

The Council does not own headcount. It does not own a budget. It does not set policy that engineering managers must follow. It advises, sponsors, mentors, and represents. Those are large jobs. They are not the job of management.


§ChapterTime
C.1What this is and is not25 min
C.2Structure: charter, cadence, membership35 min
C.3The RFC pipeline and the decision archive40 min
C.4Mentoring and sponsorship at the senior level35 min
C.5External voice: writing, speaking, OSS, brand35 min
C.6The multi-year horizon25 min

Plus a Council charter template that the Council itself ratifies and revises annually. The charter sits outside the linear reading order; C.2 references it in detail.

The total reading is roughly three and a half hours. The Council is a community, not a curriculum. The chapters describe the practice; living the practice is the work.


The literature is consistent: invitation by current members, ratified by engineering leadership, with an explicit non-credentialed framing. The mechanics:

  • A peer or current Council member nominates the candidate based on observed work (RFC sponsorship, mentoring, external representation, technical alignment moves the candidate has already been making).
  • Engineering leadership ratifies the nomination, primarily as a check against the echo-chamber failure mode that Larson and Reilly both warn against.
  • The candidate receives the invitation and accepts or declines. Acceptance carries no titular change and no compensation change. It is membership of a community, not a promotion.
  • Membership is reviewed annually as part of the charter revision (C.2 covers this).

A reader who has just earned Black Belt is not yet a Council member. The patterns of work that lead to invitation are observable, and the Black Belt badge chapter names them: sponsoring RFCs, reviewing peers’ boss fights, mentoring Black Belt candidates, contributing chapters to this playbook, representing the program externally. The Council recognises the moves before it formalises them.


  1. This README.
  2. C.1 (What this is and is not). Sets the framing for everything that follows.
  3. C.2 (Structure). Charter, cadence, membership. References the charter artefact.
  4. C.3 (RFC pipeline). The longest chapter. Decision archive as teaching corpus.
  5. C.4 (Mentoring and sponsorship). Hogan and Reilly’s material; the most under-recognised work at this level.
  6. C.5 (External voice). Writing, speaking, OSS, brand.
  7. C.6 (Multi-year horizon). The long-arc chapter; what the Council shapes that no quarterly artefact captures.
  8. The charter template. Reference document the Council fills in at ratification.

Most readers will spread these across two to three weeks of evening reading. Council candidates and current members typically revisit specific chapters when situations call for them rather than walking the section linearly each time.


The most-cited failure mode in the literature is the Council that becomes a shadow management layer. Engineering managers begin routing decisions through the Council to avoid responsibility. The Council begins owning decisions that belong to teams. Both move the org backward.

The chapters are explicit about this from C.1 onwards. If a reader takes one thing away from this section, it should be that the Council advises, sponsors, mentors, and represents. It does not manage.

Other failure modes the chapters address: the retirement home (members who have stopped doing the work), the echo chamber (recruitment by acclamation that narrows the community), the unminuted room (decisions taken verbally and never written down), capture by a single domain. Each is named where it most directly applies and the failure-mode literature is cited.


  • If you have just claimed Black Belt and want to understand the next horizon, open C.1.
  • If you have been invited to the Council and want to know what membership entails, open C.2 and the charter.
  • If you are interested in a specific aspect (RFCs, mentoring, external voice), the chapter table above points you straight to it.
  • If you are a sponsor or program lead reading this to understand how the curriculum closes, the chapters are short enough to read end-to-end in a single sitting.

Previous: ← Black Belt badge · Next: → C.1 What this is and is not