Ask why, not what
When you get assigned a task, there's one way to approach that, which is: just do what I got to do. They've told me to call 10 people, or they've told me to produce X amount of posts; let me just make sure I check that box.
But in reality, if you ended up doing that and we didn't see any results: sure, you did what you were meant to do, but you're not necessarily someone we're going to trust with a lot more.
So the mentality to have is: as long as you understand what the main vision of the company is, you have to cascade that down into what has been assigned to you. So that when you get assigned something, the first question you ask is not the what, is the why. Why have they assigned this to me? What exactly is this going to represent in terms of trying to move this goal forward?
And by the time you start taking action, if you realize that yes, they told me to do 20 calls, but I've done five or six calls so far and I'm not really learning anything new: that's not the point to then say, let me go all the way to 20 the same exact way. I think that's the point to recalibrate. What else do I think I can do differently on maybe the next couple of calls, to get me towards this outcome that I'm looking for?
Said out loud in a team meeting, 6 November 2026. Trimmed for filler; not rewritten.