Context is critical–to pretty much everything. But too often, context is either assumed or not established. Examples of this can be seen daily:
- Blog posts touting essential customer experience strategies –without establishing clarity of whether this is for consumers or B2B situations (and if you are going to tell me “its all the same now,” please listen to this podcast I did with Jon Reed of diginomica. There are clear differences).
- Name dropping – Have you ever been in a conversation where someone mentions a name, acting like you’d be an idiot if you don’t know who they are. Well, for me, I often have no idea who they are, so I just act like I know and then realize I really have no idea what they are talking about.
- Joining the middle of “conversations” – This happens at work all the time. You get involved after several other meetings or discussions (we know this happens with occasional participants on buying teams). Trying to catch up is hard. Being asked to jump in and take action is even harder–when you have no idea of expectations.
And I could go on and on.
In our distraction-driven world, we can never assume context. We need to confirm context and understanding.
I’m not saying this is easy. It’s pretty hard, particularly when you think about the fact that this is happening constantly. It’s not just with one person; it’s with 2,3, 5 or more.
But there are things that can be done.
- Create short-form “catch-up” communications – These can be written or verbal, but quick recaps of “this is how we got here” will help everyone. Short form is critical. It is a form of progressive engagement. It might provide the context to dig deeper. But I’ve seen some say “here’s the project folder, that will have the information that you want.” Really, wading through file after file isn’t exactly helping people get up to speed quickly.
- Look for signs of confusion – Maybe this could be called “active talking,” but look for signals of tacit confusion vs. strong agreement and understanding. If that is happening, be willing to take a step back and clarify.
- Start stories with the intended audience – This is built into our recommended storytelling approach. Rather than start with the answer, start with the situation and the group that is impacted. This allows them to put themselves in the story.
The absence of context may be just a nuisance, but in some situations in can make the difference between success and failure. Clients ask for details on something that had been suggested, but no one is really sure what that is–or what was committed to them. The delivery team gets frustrated. A subscription is established for software, but users aren’t trained or given clear guidance on what the usage expectations are.
Want to make a difference in decision-making, team effectiveness, and customer relations? Don’t assume or ignore the importance of context.
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.