One of the most difficult things for me to manage when I became a leader is the timing of decisions. You must spend some of your time looking at the strategic landscape, orienteering, essentially. This work is almost always many steps ahead of your actual problem.
In my life, when I'm spending a lot of time thinking about what I want to happen many steps down the line - that's when anxiety starts. What if X happens, or Y? The further out I am from my span of control (decisions I can actually make, things I can impact), the worse it gets.
One of the most important things I learned at having a very long run at Chef is: the next obstacle is always critical. If you don't solve it, bad things will happen. Solving it is about making a choice and then working hard to make it the right one.
When you smooth out the day to day ride, it turns out that the number of strategic decisions that truly matter are very small. Most of them happen really early on. After that it tends to be refinement, because your velocity carries you forward inexorably.
So back to when to make decisions. As a person, I tend to want to make them quickly, and change my mind if I'm wrong. It turns out making decisions about things that don't matter is a way for me to feel like I have some control over the uncontrollable.
If the critical problem in front of me is shipping software, the temptation to make a bunch of decisions about what happens *after* I ship software (I'm not talking planning - I'm talking decisions!) is very high. It feels good! Decisive!
But it turns out it isn't. It's wasted energy. It's the equivalent windmilling your arms around when you are running a marathon. It might feel good or whatever, but it's not conserving your energy for later. And there is always a later.
Learning to let go of those decisions until they are ripe has been a very difficult skill for me to learn. But it's the one that has probably had the most positive impact on my career and absolutely my life outside my job. I carry less stress. I can focus more.
If you find yourself worrying about the future, and feeling like you need to start taking action - ask yourself if the action your taking results in moving that immediate constraint. That's where your decisions need to be. The rest will come in its own due time.
Because I'm a person who loves a pithy platitude, I usually talk about this as finding "safety in the work", rather than "safety in the plan". I don't know if my plans will work. I don't know if my decision was right or wrong - won't know, usually, till much later.
What I know is that I can do the work. Day in day out. Making the best decisions I can with the information I have. Let go of trying to control the future. I have to get my control fix from the work itself. Because in the end, that's what it will all boil down to.
People also talk about this as "execution eats strategy for breakfast", etc etc. But to be more tactical: practice making fewer decisions, and delaying decisions longer. You'll thank me for it.

• • •

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

Keep Current with Adam Jacob

Adam Jacob 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 @adamhjk

8 Sep
Huh. One the one hand: it’s automatic deployment and management of a complex database across multiple clusters. One the other hand, holy guacamole that’s a lot of management tech. I really like the post - details, details.
I don’t think it’s possible to do inherently complicated management tasks “simply” - too many edge cases stack up on you.
I’m reminded of what happened in the Chef community over time - we all headed to patterns like Helm, then patterns like Operators, and eventually unwound it all and said it’s better to ignore the edge cases you don’t care about.
Read 18 tweets
7 Sep
Kelsey drops true wisdom here.

People->Teams->Technology->Products->Companies

You have to find a path to being great at every layer. Focus on how to be great at each layer, and you’ve got a shot at success. And those are only the variables you can pretend to control!
Perhaps even more deep in his wisdom - it’s good to think about what went wrong, and to try and not repeat the mistakes of your (or others) past. But in the end, you won’t succeed because of that - you won’t strategize your way out of future problems.
You find the ways it’s right, and replicate those. Transformative user experience. Massive adoption. Strong sense of community. Advancing people’s careers. Incredible conferences.
Read 5 tweets
11 Aug
What a weird self own. This is the kind of shit that happens when you have “rational people” write “policies” bbc.com/news/business-…
Human A at Google said: should we pay people the same for the same job if they don’t live in the same place?

B: we already do! We don’t pay the same in Ireland, or Poland, or India!
A: holy shit, you’re right!

B: it wouldn’t be fair to not apply that across the company!

A: Absolutely. Also, it’ll be good for the bottom line!

B: We won’t be evil, and we will save money!
Read 11 tweets
7 Aug
Here is the open source business model (yes, open source isn’t a business model. But we say that all the time, so.. whatever). Make something great. Turn it into a product that only you can sell (by packaging it up, branding it, selling it).
Collaborate with anyone who get value from the software on the software. Allow others to make money by *also* creating products if they so choose.
Under no circumstances should you give up the upstream control. Either by giving it away, or by refusing to play well with others.
Read 10 tweets
21 Jul
When you create a category, it’s because *you want competition* to help push the narrative forward in the market. You want other people to be winning *in your category*. Because that’s what makes your category grow.
If you have a paradigm shifting technology product, and your plan is that nobody but you will have anything like it forever, and you’ll eat the value of the whole market
That’s a bad plan. Because who wants to join a category that’s being promoted by a single giant shark that’s going to eat you?
Read 6 tweets
20 Jul
Every venture capitalist on the planet should become Rick Rubin devotees. That is the shit entrepreneurs need you to do for them. Especially early stage. It’s not just belief - it’s seeing the art. Maybe it lands, maybe it doesn’t - but you gotta be on the journey.
Don’t get me wrong - you bring the money, we bring the work. But there is a thing to production - and it’s not that different. That delicious feedback, that external perspective, someone who feels that vibe.
Artists are going to go on tour, they’re going to write more songs. But who else is in the position to not only witness, but to see it. To participate. Not by being right or wrong - just by going on the trip.
Read 9 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!

:(