Study Notes by Niladri & AI

sec15-being-visible

11 min read

Being Visible

selt visibility career-growth organizational-influence

Status: Notes complete

Overview

At Staff-plus levels, excellent work that nobody sees is frequently unrewarded. Promotions above Senior Engineer are rarely purely meritocratic — they depend on the right people having formed an accurate picture of your judgment, impact, and scope. This section addresses how to build genuine visibility ethically, the difference between making your work visible and unhealthy self-promotion, practical techniques for sustained visibility, and the structural inequities that make visibility strategies context-dependent.

Why Visibility Matters

The promotion process for Staff-plus roles is typically not algorithmic. Unlike earlier-career levels, where a manager can point to completed projects and a rubric, Staff-plus promotion requires assembling a coalition of senior stakeholders who are willing to vouch for your readiness. That process is unavailable to people these stakeholders have never seen in action.

Visibility closes this gap. When decision-makers have direct experience of your judgment — in rooms they share with you, documents they’ve read that you wrote, talks they attended — they can form the substantive assessment that promotion decisions require. Without visibility, even a strong case assembled by your manager faces skepticism: the decision-makers are being asked to promote someone they don’t know, based on evidence they haven’t experienced firsthand.

Visibility also matters for access to high-impact work. Projects and partnerships go to people who are known. If influential engineers don’t know what you work on or what you’re good at, you’re unlikely to be pulled into the opportunities where your next growth would happen.

Visibility Is Not Self-Promotion

Larson draws a clear distinction between two orientations:

Making your work visible (healthy): The subject is the work. You share a design doc because others need to understand the decision. You write an incident retrospective because others will learn from it. You speak at an all-hands because your team’s technical context helps the audience make better decisions. The byproduct is that people learn about you through learning about the work.

Personal brand building at the expense of the team (unhealthy): The subject is you. Credit for collective work flows to you in public while attribution is vague. You speak up in rooms not to improve the decision but to be seen by the right people. Visibility is pursued as an end in itself rather than as a natural output of doing and communicating real work.

The practical test: if the visibility artifact disappeared, would anyone — other than you — be worse off? If the design doc improves alignment and the talk helps others make better decisions, those are genuine contributions. If the main effect is that your name appears more prominently in more places, the orientation has drifted.

Practical Strategies for Making Work Visible

Write Design Docs and RFCs

Written artifacts are the highest-leverage visibility mechanism at most companies. A well-written design doc:

  • Circulates to engineers and leaders who weren’t in the original decision
  • Persists indefinitely and continues signaling your thinking after you’ve moved on
  • Is cited, referenced, and linked in future discussions
  • Establishes your position as a technical authority on the problem domain

For Staff engineers, the quality and reach of your written technical artifacts is often a more reliable signal of your thinking than any verbal conversation.

Share Learnings from Incidents and Projects

Postmortems and project retrospectives that are written with genuine depth and shared broadly serve two purposes: they help the organization learn, and they demonstrate your capacity to extract systemic insight from specific events. An incident retrospective that identifies a pattern across multiple failures and proposes structural fixes signals exactly the kind of system-level thinking that Staff work requires.

Speak at Internal Events

All-hands presentations, tech talks, engineering blog posts, and internal newsletters make your work visible to people outside your immediate team. Each appearance builds a data point in the minds of people who will later be asked about you in a promotion or staffing discussion. Recurring presence is more valuable than one-off appearances — a single talk is forgettable; a quarterly tech talk series becomes a standing part of how colleagues know your work.

Build External Presence

Conference talks, public blog posts, and open-source contributions add a layer of external credibility that travels internally. When a senior leader reads an industry post you wrote or sees your name on a conference program, it creates a different kind of signal than internal artifacts alone. External presence also sends the signal that you are engaged with your field at a level beyond your immediate role.

External visibility is more valuable at certain career stages than others. Earlier in a Staff career, internal visibility tends to matter more — the people who decide on your promotion are inside the company. External presence becomes increasingly valuable as you build toward more senior roles, when your scope is expected to extend to the industry.

Recurring Visibility vs. One-Off Events

A single visible action has limited compounding effect. Visibility becomes powerful when it is sustained and consistent. Compare:

  • One-off: Giving a talk at the annual engineering all-hands
  • Recurring: Writing a monthly technical newsletter, hosting a quarterly cross-team architecture review, publishing a blog post each time you complete a significant project

Recurring visibility builds a consistent signal. After several cycles, colleagues and leaders have formed a mental model of you as someone who regularly contributes substantive, useful thinking. That mental model is what gets invoked in promotion discussions, staffing decisions, and room-access choices.

The goal is not frequency for its own sake. Low-quality recurring artifacts are worse than occasional high-quality ones, because they train people to filter out your signal. Recurring visibility should be recurring quality.

The “Write Once, Talk Many” Strategy

A single piece of work can generate multiple visibility touchpoints through sequential reuse:

  1. Write the design doc or retrospective — creates the foundational artifact
  2. Present it at a team meeting, tech talk, or all-hands
  3. Share in Slack or email with commentary calling out the most interesting insight
  4. Include in a newsletter or weekly engineering update
  5. Reference it in future discussions when the topic recurs

Each touchpoint reaches a somewhat different audience and reinforces the signal at a different time. The incremental cost of each step after the first is low; the compounding reach is high.

The “Snail Trail” Concept

Staff engineers should deliberately leave artifacts behind as they work: design documents, architecture diagrams, decision records, incident analyses, runbooks. These artifacts persist after you’ve moved on from the project, the team, or even the company. They continue to:

  • Demonstrate the quality of your thinking to people who encounter the problem later
  • Surface your name in searches and references long after the work is done
  • Build an accessible portfolio of your technical judgment over time

The snail trail is the durable record of your impact. Oral contributions — things said in meetings that aren’t recorded — leave no trail. Written artifacts, diagrams, and decision records do. For Staff engineers whose scope crosses teams and whose projects span years, the snail trail is often the primary evidence base for their impact.

Visibility Without Execution Damages Trust

The important constraint on visibility strategy is that it must accurately represent real impact. Visibility pursued ahead of execution — claiming credit for ideas before delivering results, describing planned work as completed work, building a public presence for contributions not yet made — degrades trust rapidly once the gap becomes visible.

The visibility that helps you is the visibility that prompts someone to think “yes, I’ve seen their work and it’s excellent.” Visibility that prompts “they talk a big game but I’m not sure they deliver” is negative. Delivery must precede or accompany visibility, not follow it.

How Your Manager Can Help Amplify Visibility

Managers have access to visibility channels that individual contributors typically don’t:

  • They attend leadership meetings and can mention your work naturally in context
  • They write performance reviews that are read by senior leaders in calibration sessions
  • They can nominate you for projects, talks, or opportunities that expand your exposure
  • They can broker introductions to senior stakeholders who should know your work

The most effective way to leverage your manager’s visibility channel is to make it easy for them to advocate for you. This means: keeping them informed of your work in a form they can summarize and relay, flagging the specific impacts you’d like them to highlight, and having explicit conversations about the people whose awareness of your work matters to your next career step.

Don’t assume your manager is automatically amplifying your visibility. Have the explicit conversation.

Internal vs. External Visibility

Internal visibility means being known within your company — by your immediate team, adjacent teams, and senior leadership. It is the primary driver of promotion decisions, project access, and organizational influence within your current employer.

External visibility means being known in the industry — through conference talks, blog posts, open-source work, or public writing. It signals credibility inside the company (especially to leaders who follow the field) and is a primary input for future job opportunities.

Prioritization by career stage:

  • Early Staff career: Prioritize internal visibility heavily. The people deciding on your promotion and your next project are inside the company. External presence is valuable but secondary.
  • Senior Staff and Principal career: External visibility becomes more important as the expected scope extends to industry influence. It also becomes more feasible — you have more distinctive thinking to share.
  • Throughout: Internal and external visibility are mutually reinforcing. External credibility boosts how internal stakeholders perceive you; internal credibility gives you the substantive work to write and speak about externally.

Equity Considerations

Visibility strategies are not equally available to or costly for all engineers. Larson acknowledges that visibility work has structural inequities:

Higher penalties for some: Engineers from underrepresented groups — particularly women and people of color — often face higher social penalties for perceived self-promotion. The same visibility behavior that reads as “sharing your work” from one engineer can read as “bragging” from another, due to ambient bias.

Lower default visibility: Some engineers start with lower baseline visibility because they are less likely to be in the rooms where names circulate, less likely to be mentioned in leadership discussions, and less likely to be remembered when opportunities arise.

Mitigation strategies: For engineers navigating these dynamics, the most robust visibility approaches are ones where the artifact does the work — written documents, published posts, and recorded talks that can be evaluated on their merits independently of the person’s identity in a given moment. Relying heavily on verbal/room-based visibility is higher-cost when the social dynamics of rooms are less favorable.

This does not mean visibility is optional for underrepresented engineers — it remains necessary. It means that the specific tactics and the support structures (sponsors, advocates, managers who actively amplify) need to account for the uneven baseline.

Key Takeaways

  1. Excellent invisible work is frequently unrewarded at Staff-plus levels. Promotion requires that the right people have experienced your judgment, not just heard about it.
  2. Visibility is not self-promotion. Making your work visible is healthy; personal brand-building at the team’s expense is not. The test: if the artifact disappeared, would anyone other than you be worse off?
  3. Written artifacts are the highest-leverage visibility mechanism — design docs, RFCs, retrospectives, and decision records circulate widely, persist indefinitely, and continue signaling your thinking after you’ve moved on.
  4. Recurring visibility compounds. A monthly newsletter or quarterly talk series builds a mental model in colleagues’ minds that a single one-off event never will.
  5. The “write once, talk many” strategy maximizes reach from a single piece of work: write, present, share in Slack, include in a newsletter, reference in future discussions.
  6. The snail trail — the persistent written artifacts you leave behind — is often the primary evidence base for your impact. Oral contributions leave no trail.
  7. Visibility must accurately represent real impact. Visibility pursued ahead of execution damages trust rapidly once the gap becomes visible.
  8. Your manager is a visibility amplifier. Make it easy for them to advocate for you by keeping them informed in a form they can relay, and have explicit conversations about whose awareness matters.
  9. Prioritize internal visibility early in your Staff career. External visibility becomes more important — and more feasible — at Senior Staff and Principal levels.
  10. Visibility has structural inequities. For underrepresented engineers, artifact-based visibility is often more robust than room-based visibility, and sponsors/advocates who actively amplify are especially important.

Last Updated: 2026-05-30

Graph View

Backlinks