Hi folks,

This is the weekly digest for my blog, Irrational Exuberance. Reach out with thoughts on Twitter at @lethain, or reply to this email.

Posts from this week:

- Being visible.
- TechWriters community.

Being visible.

Bert Fan’s best advice for those trying to reach a Staff-plus role was,

often reaching Staff is a combination of luck, timing, and work.

Timing is a particular sort of luck, so in some ways you can simplify this even further down to just luck and work.

If you’re fortunate, then you won’t have to pursue a deliberate path to a Staff-plus role.. You’re already working on your company’s top priorities, have a well-positioned manager who cares about supporting your career, and are working from your company’s headquarters office. If you’re starting with none of those things, getting promoted is going to be quite a challenge, but don’t count yourself out: it’s easy to underestimate your own role in getting lucky.

One of the most effective ways to get luckier is to be more visible within your organization. There are of course very quick, very negative ways to increase your visibility, so I’ll refine the statement a bit. Your goal is to be known for good things while minimizing the organizational bandwidth you consume to do so.

Why visibility matters

Katie Sylor-Miller describes visibility as a key piece of getting promoted to Staff,

Something I haven’t talked about enough is communication and transparency. A big part of being promoted to Staff is making sure that your work is visible, that people know your name and you have a good reputation.

Staff-plus roles are leadership roles, and by recognizing you with such a role the company is bringing you into its leadership team. The existing members of that team want to be comfortable that they’re expanding their ranks with folks they believe in, and they can’t believe in you if they don’t know you.

If you’re operating without much visibility within your company, this may likely come across as cliquey or gatekeeping behavior. Conversely, if you are well-known internally, this may feel like the necessary cost for maintaining a consistent set of expectations and criteria for folks taking on leadership roles – how could you maintain consistency if you are unfamiliar with their work?

It’s interesting to briefly reflect on how inclusive organizations mitigate the negative gatekeeping aspects of validating folks are appropriate additions to your leadership team. The answer is that they design mechanisms to ensure the full swath of potential leaders get exposure to the folks who will evaluate them for leadership roles. Conversely, less inclusive organizations inadvertently center access on folks who most aggressively self-advertise.

Internal visibility

The single best way to create internal visibility is to work on the things that matter to your company and company leadership. This path is also the most aligned with how a well-managed company will evaluate your contribution.

Sometimes that isn’t enough though, and some other strategies are:

• Write more long-lived documents, like architecture docs or technical specifications.
• Lead (and to a less extent, participate in) company forums like architecture reviews, company all hands, and learning circles.
• Be a cheerleader for your team’s and peers’ work on Slack.
• You can also cheerlead via email instead of Slack.
• Share weekly notes of your work to your team and stakeholders, in a way that other folks can get access to your notes if they’re interested.
• Contribute to your company’s blog.
• Attend, or potentially even host, office hours for your team or org.

Find the right mix of activities that leverage your strengths, aren’t already overburdened with volume, and feel authentic to you. If you’ve never done much communication of your work, it may feel awkward to self-promote your work. You never want to wholly lose that sense of awkwardness–restraint helps–but you will have to get comfortable with some of it.

External visibility

It’s helpful to complement your internal visibility work with external visibility work. There are a huge number of successful Staff-plus engineers with no external presence, but many find external visibility contributes to their career.

Compared to an exclusively internal focus, one advantage of building an external presence is that there’s a lot more room to create a niche and name for yourself. Internal efforts often end up competing for attention with your peers in a way that external efforts simply don’t.

In terms of how to create this sort of visibility for yourself and your work, it could be writing a blog post like Silvia Botros, giving a conference talk like Keavy McMinn or Dan Na, going on a podcast like Michelle Bu, turning a problem into a website and book like Katie Sylor-Miller’s ohshitgit, or creating a mailing list like Pat Kua’s Level Up.

Should you focus on visibility?

You can always have more visibility within your organization, but at some point increasing your visibility is likely reducing the opportunities for others to create visibility for themselves. Internal visibility is not strictly zero-sum, but it’s constrained by the attention of the folks you want to see your work.

My advice would be to use the promotion packet exercise to identify if lack of visibility is likely to hold you back in the promotion process. If so, work to clear that threshold, but not much further. Visibility is a transient currency, learning and developing yourself is a permanent one; focus on the later once you’ve done the minimum to clear the former’s cliff.

TechWriters community.

In part "stuck away from friends due to pandemic" inspired, I've been wishing there was a tech writing community for semi-serious writers. As an experiment, I'm trying to spin up a Discord server to create such a community.

Read a bit more about the project at techwriters.dev.

My hope is this will become a healthy, positive place to talk about creating tech and tech-adjacent, particularly for folks who do it semi-seriously: frequently bloggers, book authors, public speakers and so on. Creating this sort of community is hard work, and not something I've done before, so I imagine it'll be a bit of a learning curve, and excited to add a few more administrators if there are folks with that experience who'd be interested in participating.

Alright, a few frequently asked questions.

Should I join?

Sure, if you're interested you should join. I'm not really sure what "semi-serious writer" or "semi-serious" content creator means, so if you think you'd enjoy being part of a creative community then you should definitely join.

Why Discord rather than Slack?

To be honest, I've never used Discord before, but a few folks mentioned it as preferable to Slack and figured it would be good to give it a try.

Why not join an existing community instead?

I reached out to a handful of folks and none had found a particularly good fit in an existing Slack or Discord, so decided to try spinning one up. It's totally possible there's already a great existing community that'll emerge from the woodwork and it'll make more sense to fold this effort into that preexisting one.

Can I be an admin?

Maybe! If you're empathetic, kind and engaged then send a note to techwriters-dev@googlegroups.com and we'll see what we can do.

That's all for now! Hope to hear your thoughts on Twitter at @lethain!