As an operator, one thing I've found massively helpful in my output is having a bias towards action.
But what exactly is BTA? And how do you cultivate it? π€
I've written an article on exactly this. π
Bias towards action contains four steps:
2/9
STEP ONE
Are *you* the one that needs to do the action?
For every request you say yes to, you're saying no to something else. Is that trade-off worth it?
Below are two questions you can ask yourself if you're a manager or IC:
3/9
STEP TWO
π Is this the best thing you can do with your time *right now?*
Look at your company's goals, areas of responsibility, or action tracker for helpful hints when evaluating.
Here's a breakdown of what your role might be if you're a manager or IC:
4/9
STEP THREE
π How can I make this action happen in the *next 30 minutes?*
IMO, this is where the real magic happens.
30 min might seem like a jarringly small amt of time, but all of a sudden one day now seems like a luxury.
This post-it is how I remember to ask myself:
5/9
With that question, I can now encourage my team to:
-declare what they're going to do instead of asking for permission
-actively solicit feedback
-act on their declaration
...rather than waiting for me to say yes or no. With 30 mins, there is no time to wait.
6/9
STEP FOUR
π What can I accomplish before someone *assigns* me an action?
With this, you & your team will not wait for someone to *tell* you what to do.
You will evaluate company goals, declare what needs to be done, and go do it.
That is a true bias towards action.
7/9
In summary:
1. Are *you* the one that needs to do the action? 2. Is it worthy to do *right this second*? 3. If yes, how can you do the action in the next 30 mins? 4. What can you do *before* anyone asks you to do it?