One of the difficulties I have with the concept of ‘grit’ is that it is often reduced to “perseverance through failure” or “commitment despite failure” rather than the more accurate and helpful observation that “failure is information.”
“Failure is the path to success,” is a common narrative in TED circles, so we assume that failure implies progress, that we hop from failure to failure like stones to cross a river. Instead, we’re more like a blindfolded person trying to cross a field; when we find an obstacle that doesn’t yield to a shove, then we should stop and change our path, search for a gap in the fence.
The obstacle is information: not here, not this way. Try it differently.
Grit isn’t pushing against a brick wall for a few years and then congratulating yourself for a job well done. Grit is noticing, “Hey, there’s a wall here. Shit. Lets look for a way around.”
Grit requires knowing why, not how.
Grit is sometimes mistaken for commitment, but at a tactical level, grit is a complete lack of commitment. Grit is aggressively quitting what isn’t working, what is stressing you out, what you’re procrastinating on.
In a programming context, grit is not hacking on shitty code, but a complete refactor.
In an office context, grit isn’t catching up on an email backlog, but deleting the backlog and setting up an autoresponder.
In a nutritional context, grit isn’t suffering a half-dozen arbitrary restrictions (no white carbs after 7PM!), but learning the foundations of nutrition to plan your own meals.
In a jujitsu context, grit is not muscling into positions when you meet resistance, but mastering angles and leverage.
Grit is “embracing failure” in the same way that taking the wrong bus is “embracing transportation.”
Wherever you’re trying to get, you can still make it there. But please, get off the damn bus and figure out a new route.