If you're afraid of being a micromanager

I can guarantee you are one.

It's the Micromanagement Spiral. 🌀

Let me explain:
You delegate a project to your team.

You don't want to micromanage.

So you share just the big details in order to leave room for:

🔹 interpretation
🔹 creativity
🔹 alternatives
🔹 opposition
The team heads off to work on the project.

It wraps, but the team didn't execute as you hoped.

😐 The objective was missed
😕 A key stakeholder is unhappy
🙁 Deadlines passed
😣 Strategic alignment is missing
Now you have to go back to the team.

"The UI needs to be redone."
"We need to change course."
"Can I have a detailed timeline for this project?"
"You need to start holding a standup that these VPs attend."

Suddenly, you've morphed into the micromanager you dreaded.
And this is the Micromanagement Spiral:

🌀 Delegate a task
🌀 Give minimal direction
🌀 Be disappointed by results
🌀 Micromanage the details to course correct

This cycle will continue on and on and on

Until you can break it.
📢 Giving your team direction and context is not micromanagement.

📢 It's also not micromangement to expect proactive updates about the status of a project.

When those two elements are missing, you'll find yourself needing to micromanage details to correct the course.
So, you can avoid micromanagement by giving:

🔹 Enough direction
🔹 Clear expectations
🔹 What's been tried before, and why it didn't work
🔹 Details about stakeholder expectations or company politics
🔹 Assumptions and opinions
🔹 Timeline details
And avoid micromanagement by getting:

🔹 Project updates that are useful and frequent enough
In practice, it might look like this:

"I need to stay updated on this project in order to give updates to the executive team at our meetings on Wednesdays. How would you like to provide those updates for me?"

"We've already tried X. How will this impact your approach?"
Or this:

"I'd like you to research solutions and make a recommendation. When would you like to share your findings?"

"The CEO is expecting that we deliver before Sept 1. It must include UI changes, or the update won't be tangible enough. Who has an idea?"
The road to micromanagement is paved with good intentions.

Most of the time, trying to avoid micromanagement will lead you right down the path to being a micromanager.

The antidotes?
🔹 Direction
🔹 Transparency
Are you caught in a micromanagement spiral?

Use this thread to spot the signs.

🌀

RT to share with someone who's afraid being a micromanager, so they don't get caught in the spiral, too.

• • •

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

Keep Current with Laura Tacho 🌮

Laura Tacho 🌮 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 @rhein_wein

Jun 30
"How do you measure burnout on your team?"

Someone asked this question in my course today.

Required reading for any leader:
Burnout can be hard to measure, because it's multi-faceted.

It's not necessarily about the amount of time someone is working.

Burnout happens when people are
🔷 overworked
🔷 chronically under stress
🔷 disconnected from results
🔷 lacking control over how they spend their time
You won't find a neat and tidy metric to measure all of those things.

Burnout is often a lagging indicator.

Here are two strategies to measure it:

1️⃣ Look for leading indicators
2️⃣ Use the "clone" method
Read 11 tweets
Jun 28
I interview a lot of people, from C-suite to interns.

Want to nail your next interview and get a high offer?

Avoid these 5 mistakes.
🚫 Repeat your entire CV

Assume that everyone has read your CV.

You don't need to recap your whole career when asked to introduce yourself.

The interview questions themselves will give you an opportunity to highlight your accomplishments.
Instead, introduce yourself with:

🔷 Your name, location, and most recent job title
🔷 What you're great at
🔷 One goal you have for the conversation
Read 11 tweets
Jun 13
We've all heard about (and rolled our eyes at) the out-of-touch software engineering manager:

"Can we deliver faster by adding more people?"
"I want to see more PR activity."

But here's an interesting study on the definitions of productivity from managers and developers:
165 managers & developers responded to these questions.

➡️ How do you define productivity?
➡️ (for devs) How do you think your manager defines productivity?
➡️ (for managers) How do you think your team defines productivity?

The results?

Unexpected.
Developers define productivity largely based on output and efficiency:

📊 Activity (tickets closed, PRs, deployments) (50%)
🏄🏾 Efficiency and flow (38%)
🛠 Performance and quality of projects delivered (35%)
🎙 Communication (24%)
🌿 Satisfaction and well-being (8%)
Read 14 tweets
May 16
Scheduling your team at 100% capacity is a great way to ensure that nothing will be delivered on time.
There is some cool math behind why this happens.

Let's take this example: each customer at a bank takes an average of 10 minutes to be served.

One new customer comes every ~10 minutes.

With one teller window open, the wait time is FIVE HOURS.
Not minutes. Hours.
On paper, the example above sounds ideal. The teller can keep up with the flow of customers at a steady pace. But these are average rates, and "average" isn't reality.

Some customers will need 20 minutes to be served. And sometimes, three customers might come at once.
Read 8 tweets
May 13
I've spent 750+ hours coaching managers and executives to become more impactful leaders.

Here are 7 quick lessons to level up your leadership skills:
1/ Say no often

Focus is expensive. It's the most precious commodity in your business. Great leaders let their teams focus.

Great companies aren't made by saying yes.

They're made by saying no.
2/ Focus on outcomes, not outputs

Exceptional leaders care deeply about results. They care less about the how, or the where.

They create environments where people can do their best work.

That also means respecting boundaries.
Read 9 tweets
May 7
Anonymous coding challenges don't eliminate bias from engineering interviews.

Here's what the research shows (and what to do instead):
Assessing coding exercises is just one of the many places where bias shows up in an interview process.

Your sourcing strategies, screening criteria, and interview panelists introduce bias as well.
In 2018, The IZA Institute of Labor and Economics published a study reporting on the impact of anonymous hiring practices on diversity.

While anonymous screening & evaluation can reduce bias in orgs where discrimination is already high, it also has many downsides:
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

Don't want to be a Premium member but still want to support us?

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

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us on Twitter!

:(