It's a reasonable question, and I will attempt to answer it, but only if you promise to remember that "leadership training" itself is a sloshy pile of almost complete and total garbage. It does not "train" you to be a better "leader". It barely even pretends to try.
If I could take the same money and order everyone to therapy to talk about their childhoods instead, I would in a hot second.

(unfortunately this is "frowned on" by the nanny state and other such maskwearing meddlers 🙃)
When such leadership training is effective, it is usually to the extent that it resembles a weak-tea version of therapy, and forces you to regularly reflect on the emotional states of yourself and your teams, and talk thru your shit with a neutral party.

Which is not nothing!
So. The issue isn't that you aren't being given magical training beans to sprout forth your inner leader.

The issue is that your org has defined leadership in a way that excludes most of the actual leaders. Their actions say that "managers == leaders == managers". That sucks.
I would use this as a wedge to try and pry apart that tight coupling a smidge. Start, of course, by simply asking for it with your best curious innocent face firmly on:

"Hey! I just happened to notice this RAD leadership resource -- but it says managers only -- how odd 🤔 --
"-- is that a typo? Is there a reason for that? It is EXACTLY the kind of training I could really use in the context of xyz senior leadership challenges in my current role."

Maybe an appeal to authority: "everybody knows that effective engineering leadership relies on tech--
"--leads as much as people managers. I think it's wonderful that the people managers have beta tested this resource for the rest of us, but if it's effective shouldn't we really be rolling it out to all the senior leadership?"

Few other arguments come to mind.
"It's incredibly critical for people managers and tech leaders to share language, concepts, and training for tight alignment"

It could be an effective and less costly way of creating a trial period or vetting period for folks trying out management for a spell.
Or, if you have too many people clamoring to fill a few scarce manager slots, you can pitch it to them as a consolation prize for people who aren't getting tapped but they do want to retain and keep happy.
Anyway. You have to choose how much to fight this war over symbolism and perks.

If you ACTUALLY want to become a better leader, pay attention to practicing the composite skills of management/leadership instead. For example,

* leading meetings
* translating tech to $ and back
* breaking down large projects into work that challenges without overwhelming a lot of people at once
* having hard conversations, giving hard feedback. Being heard.
* making people enjoy working with you and eager to do more of it
You don't need any title to do this shit. Look for the scut work, the stuff your manager hates or is weak at, and find ways to be helpful. Become indispensable (as in they don't WANT to be without you, not can't function without you).

Rest will come. 💜🖤

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Charity Majors

Charity Majors Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @mipsytipsy

8 Sep
I keep talking to engineers who are antsy to get to senior and beyond, frustrated that it is taking so long. And I've encountered one very, very widespread blind spot around leveling

Which is ...✨not every opportunity exists✨at every company✨at every time.✨
I mean ok; if you're a junior eng you should be able to get to intermediate, pretty much anywhere. But it gets progressively trickier after that.

Even just trying to go from intermediate to senior can get interesting. How many other intermediate or senior engineers are there?
Typically you will get promoted to the next level after you have already been performing at it for six months or the span of a review period or two. So how many other people also require promo-worthy, solidly-senior projects?

Does your ladder include mentoring/leading others?
Read 27 tweets
26 Aug
I've been noodling over this lately.

If you want to ask someone to change how they work, change the tool they use, change their workflow -- it needs to be an order of magnitude better to justify the cognitive and opportunity cost.

Not 50% better, not twice as good. 10x better.
And until fairly recently, I think that most developer tools didn't reach that bar. Yes, you could improve the rate at which you shipped, the speed of your recovery, etc, but the benefits weren't pronounced enough to be unmistakably worth it for many teams.
I believe it's just in the last two, maybe three years that we've crossed that threshold.

The DORA reports have some fascinating clues here. Consider the 2017 report, which compared high performers from 2016 and 2017. Not much change, and mostly convergence.
Read 7 tweets
18 Aug
here's another way to think about it:

monitoring is for understanding infrastructure; instrumentation + observability are for understanding your core business value.

it's how you make your code easy to understand and navigate, long after it's shipped and running in production.
monitoring is about "what's happening" from the perspective of your infrastructure components.

observability is about "what's happening" from the perspective of your users. that's why everything is gathered up around the perspective of the request as it executes.
there's a bright line here. software engineers writing features for users shouldn't have to care about the state of the infrastructure components. right? they should have to care about whether their code is doing what it's supposed to do, and about the user's good experience.
Read 5 tweets
18 Aug
so annoyed by all the "topic: observability!" followed by chatter about logs and monitoring. that is not going to help you with your unknown-unknowns, it's o11y-washing old shit to sell it to you.

i made two checklists. grab a marker, let's figure out what you're listening to --
Technical observability:

❑ high cardinality
❑ high dimensionality
❑ wide, rich events (aka spans)
❑ schemas are inferred and dynamic
❑ no friction to adding more context
❑ unique ids, propagated
❑ SLOs
❑ tracing
❑ column store or autoindexed
❑ very near realtime
Marketing "observability":

❑ pillars (one for each product they're trying to sell you)
❑ metrics
❑ AIOps (sic)
❑ logs
❑ pricing based on hosts or seats
❑ dashboards
❑ magical autoinstrumentation
❑ tags
❑ single pane of glass
❑ ML, AI
❑ aggregates
❑ strings, searching
Read 4 tweets
7 Aug
today i learned about something called "web assembly" and now i feel betrayed by ALL OF YOU
i have also learned some horrifying shit about typed arrays. who the actual fuck is in charge of this language
the only bright spot in this dreadful day is that both javascriptwtf.com and wtfjs.com exist.

... on second thought, OF COURSE THEY DO
Read 8 tweets
3 Aug
This is a very good point. It is every bit as possible, and equally as common, for eng managers to err on the side of under-evaluating as over-evaluating.

If you under-eval, your team misses out on growth opportunities, and your comp and levels won't be fair or meaningful.
How can you distinguish between the helpful, growth-unlocking ways of evaluating engineers from the harmful, metrics-gaming ways that I ranted about here? charity.wtf/2020/07/07/que…

Well.. think about the differences between factories and artisans.
Imagine we're talking about building shoes, not software. You have a shoe factory. How can you tell if it's performing well?

You gather stats on # of pairs manufactured per day, how long it takes to make each pair, uniformity of the components, quality of the finished product.
Read 10 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!

Follow Us on Twitter!