Having spent a career avoiding management like the plague, this was the year I took the plunge. I did so right before end of year cross-calibrations (that is, reviews) which was a great way to remind myself of all the reasons I didn't want to do this stuff.
Having survived cross cals I did walk away with a very palpable lesson about what sort of work I need to do to help insure the success of the people who work for me (And of why it's so important I prioritize that).
Logically, the thing to do is to look to my own lessons of success and try to impart that wisdom upon them. However, as it turns out, "Be a middle aged white guy and things will work out" is not actually a fantastic lesson plan.
Also, honestly, having now gotten to watch the sausage get made, I have an appreciation for how lucky I've been. This is not to undercut my competency or effectiveness - I'm pretty good at what I do - but I was very lucky that my inclinations lined up with what the system wants.
So, to some extent, I'm obliged to look to the roots of that "luck", which is humbling but also informative. I'm also obliged to be realistic about what tactics work for me (White, bearded, large well spoken dude) that might not be universally applicable.
Most obviously? I have had a lot more leeway to fail fast than some might because I have that combination of attributes that make failure less sticky. Which is great for me, but makes it terrible advice to give without awareness.
(I'm pretty mindful of this one, because I *love* failing fast as an approach to problems, and I was a vocal advocate of it for a time, and thought objections to it were coming from people who were "just" afraid to take risks. I had not considered the blind spot was mine)
Anyway, this has me thinking about how to help my team succeed, and as I think on it, it boils down to three things (as it so often does) which I'll loosely call knowledge, capability & purpose. I say loosely because there are a LOT of models like this, all roughly overlapping.
Knowledge & Capability are not easy, but they are straightforward. Do you have the skills and information to succeed? Knowledge. Do you have the tools and opportunity to succeed? Capability. If there are gaps with these things, there are tools for addressing them.
Those are problems I can solve.

Purpose, however, is definitely knottier. I look at my own journey through it, and it raises more questions than answers.
For me, Skills and Capability are things that have steadily leveled up as I've learned and done things, but purpose has sort of skittered and jumped. And I think that's probably as it should be.
Improving skills is a progression. It moves in one direction. But a similar narrative about purpose is...outright creepy.
To unpack, for a decent part of my career, purpose was very straightforward - a paycheck. One might categorize it as extrinsic motivation, but I just view it as logistics. When I was in the Senate, the purpose was making a difference, however small, and came with less $$$.
At some point, I decided it was fun to solve certain sort of problems and that gave a purpose. At other points, I determined that I'm uncomfortable letting problems lie and need to tackle them, and that was also purpose.
That last - see a problem and want to fix it - has been a very beneficial motivator for me in my current context because it translates into initiative (which pairs with capability into autonomy, thank you Daniel Pink) and that's great, but it's not a *progression*.
From a certain perspective, my purpose has become more "professional" over time, but that's looking at it backwards. My contexts have changed, and my purpose changes with it. If my situation changed, my purpose could ABSOLUTELY go back to "paycheck".
Which is 100% reasonable, but difficult to frame because progression narratives are so powerful that there's an instinct to frame that sort of context change as falling back to a lower "level". Hard instinct to fight, but naming it helps.
Worse, there is a toxic, reductionist flipside to this which is SUPER tied to the power dynamics of work. Yes, people need to get paid, and yes, people are expected to do their jobs, but if that dynamic is reduced to just the paycheck, then that's all it will be.
And that's a problem when, as in this case, the criteria for *success* rely on more than just compliance.
When I say I was lucky, this is exactly what I mean. My inclination (ooh, problem! Shiny! Let's fix it!) set me up for success because it produced the desired outcome (examples of initiative, problem solving, and helping others).
And the bit I need to wrestle with a bit is how to help my people reach similar outcomes WITHOUT assuming that the correct answer is "to have the same purpose/motivation I have."
That would probably work, in a classic managerial sense. I could push that motivation narrative, and it would work for some, and others would underperform and get pushed out, allowing me to bring in people aligned with my vision, and I could selection-bias my way to the top!
I say all this to make it clear how narrow-visioned and monocultured such an approach would be, it's still hard to resist. The self-narrative of "my experience, inclination and earned wisdom have created a template for success for others" is *super* compelling.
Which is why I'm going to need to do the much harder and, more critically, much more uncomfortable thing of figuring out how to help them find my kind of luck based on what works for *them*.
(And if you don't understand why 'uncomfortable' is more of a barrier than 'hard', that may be more than I can unpack in a tweet, so just accept that many brains are happy to do the *work*, but find the work the easy part)
Of course, part of the challenge is figuring out what makes that connection for them (one more reason it's SO MUCH EASIER to just use MY model), and to do *that* (with a nod to @kleenestar) I'm going to need to carve a space where that can be safely spoken to.
Seems like a small thing, and in the grand scheme it maybe it, but it's going to be a trick in and of itself.

But I have about one year before these people get to go through the grinder, and if they're not set up for success, that's on me.

So there's work to do.
(Coincidentally, this is also the year I've given myself to see if this management thing is something I genuinely want.)

• • •

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

Keep Current with Rob Donoghue

Rob Donoghue 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 @rdonoghue

18 Nov
I've been getting involved more in how we form scrum teams (in the logistics and hiring sense, not the "forming, storming etc) and it's struck me that it is ass backwards that we seek out Scrum Masters & Product Owners the same way.
Getting a Scrum master for a team is like hiring any other specialist. Some overlap of domain knowledge is valuable, but you are bringing them in to do specific work with specific tools and learning what they know is part of the expertise.
Like a facilitator, much of what a good scrum master can contribute is agnostic to what the product is. Expertise and learning add value, but the baseline requires very little. Which is great, because it means you can air drop a scrum master into most situations and see results
Read 32 tweets
18 Nov
Just seeing the snippets from #agiletesting is making me miss live events. Not because of seeing people (though I miss the too) but because actual presentations are so much better than Zoom presos.
Not that Zoom presos are bad - they enable lots of things that would otherwise be impossible - but they impose different constraints on the speaker, and because we’re still immature at this, they are not all terribly fruitful.
Zoom (as a stand in for the category of software) makes the habit of presenting to the slide deck so much worse due to the default nature of screen sharing. It removes the speakers ability to read and respond to the room.
Read 4 tweets
17 Nov
Got to spend time today talking with folks whose team has been through some stuff, and got to give what I think (hope) was pretty practical advice without ever actually saying out loud "What you need to realize is that story points are bullshit. USEFUL bullshit, but bullshit"
Found all kinds of nice, positive ways to convey the sentiment, but MAN, I am all for less profanity in my professional communications, but the loss of the word "bullshit" just feels like a palpable drop in communications bandwidth.
Also, I realized my answer to "what metrics do you track?" is "how much time do you have?".

But what they're *really* asking is "what metrics do you report out?" And that is, thankfully, a shorter list. Because it's hard to explain that I track ALL THE METRICS
Read 7 tweets
17 Nov
Gonna be honest: Dual Track Agile gets a lot of flak, partly because it seems to pull critical engagement AWAY from the team, and I'm not really sold on it as a product research replacement.

But the actual model? Turns out, it works pretty well for engaging architects.
(Yes, this presupposes a situation where architects exist outside the team rather than the team having ALL the skills you need in one place, but that is just the hand some of us are dealt)
There's other stuff in it, but from a purely logistical perspective, "Dual Track Agile" gives an ok toolset for engaging outside dependencies (like architects) whose time is constrained and who need to do more than trivial work to Lay down runway for your team.
Read 4 tweets
16 Nov
I have no opinion on this event, but I am *FASCINATED* by the format! Creat a limited-time, event driven Slack as an event, and use it to drive conversations, maybe presentations and all sort of other convention-like things. Could probably self org a lot of cool stuff. NEAT!
Could do the same thing with a Discord or equivalent, no doubt. This seems like such a solid idea that I assume it's already happening. Are people spinning up short lived, purpose driven Slacks or Discords already and I just missed the trend? I hope so! It's too cool not to!
And, yes, I know that these things are often created as supplements/supports for online conventions. I'm just intrigued by the possibility of them as their OWN THING.
Read 4 tweets
14 Nov
Ok, trying to watch the next arc of Arcane.

Warp Gates + Airships == Fantastic bit of worldbuilding.

Steampunk hoverboards, not quite so much.
This is a really the 1990s WoD school of trauma stuff, isn't it?

But the visuals have, if anything, gotten better. The parkour is amazing. And there's a scene in an opera house where a background element is the mechanics of stagecraft, and I love everything about it.
Got some good punching in for the second episode of the arc, but I was wondering how they were going to wrap it up in another tight arc, because the pacing was a bit meandering. Turns out the answer is, they weren't - seems like they're going into a more traditional arc now.
Read 11 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

Thank you for your support!

Follow Us on Twitter!

:(