Why high performers make assertions: The difference between insights, suggestions, and assertions — from newsletter.weskao.com by Wes Kao; w/ thanks to Roberto Ferraro for this posting
An insight is just a starting point. The rare, courageous thing to do is to develop an assertion, i.e. a hypothesis and point of view that answers “so what?”
But the next step is what actually moves the needle. The rare, courageous thing to do is to develop an assertion.
What’s the difference between insights, suggestions, and assertions?
When you point out an insight, you’re calling attention to an observation, something you noticed and wanted to remark on. In response, your colleague could say, “Hmm interesting. That’s nice to know.” They carry on with their day. You carry on with yours. Nothing changes.
When you make a suggestion, you’re putting forth a recommendation. You’re proposing a few different options to choose from. But you’re still not on the hook because your boss ultimately decides what to do. And the person who decides holds the emotional burden of that decision.
When you make an assertion, all of a sudden, things get real. You’re on the hook because there’s more of you in what you’re positing. You’re now advocating for your point of view and trying to convince others to support you.
From DSC:
Perhaps there’s something in here for academics when they write for the journals within their discipline. When I was getting my Masters Degree, I hated readying the same ol’ same ol’ –> “…this needs further research, blah, blah, blah.”
I wanted to know what the researcher/author had to actually say about the topic. Too often, they seemed to hold back any kind of thesis or what they believed to be true about a topic. They were far too reserved in my opinion.