reading is hard, sometimes
alright, let's talk about something that I think that probably resonates with most folks navigating the bustling corridors of a modern workplace, especially in tech industries: the curious case of information asymmetry, or more simply, people not reading.
it’s a bizarre phenomenon, isn't it? we pour hours into crafting concise Slack messages, detailed emails, or meticulously structured documentation. we aim for clarity, provide context, define decisions, and outline next steps. then, almost immediately, the questions start rolling in. questions that, with a mere glance at the shared information, would be effortlessly answered.
I often wonder why this happens. is it simply a byproduct of information overload? are we so swamped by notifications and content that our brains have developed a filter that prioritises asking over reading?
this also triggers a nagging thought in my mind: "hey, am I doing something wrong here?" but ultimately I noticed that this isn't about me actually.
one thing I've developed after noticing this kind of behaviour among a few coworkers was something a former superior of mine once shared: "you're not working with yourself. Do your part but never expect that others will do the same. People are different, think differently (this isn't an Apple ad, honest!), so reduce your expectations and just do your part properly."
this piece of advice, simple as it sounds, was a genuine lightbulb moment for me. it shifted my perspective from frustration to a more pragmatic approach. it's not about accepting mediocrity, but about understanding that everyone operates with different priorities, communication styles, and indeed, information processing habits.
it doesn't mean we stop striving for clear, comprehensive communication. quite the opposite, to be honest. my role is to ensure information is as accessible and digestible as possible. knowing that I'm always trying to set this two points always clear at all meetings, discussions or threads:
Repeating crucial information: Not obsessively, but intelligently. If a decision is particularly important, it might need to be reiterated in a meeting after being shared in writing.
Setting expectations: Clearly stating in a message, "Please read this before our meeting," can sometimes help.
however, even with all these efforts, some questions will still arise that could have been answered by reading. and that's okay! my superior's advice taught me to manage my own emotional response to this. my responsibility is to provide the information effectively. their responsibility is to consume it. I can influence the latter, but I can't control it entirely.
instead of getting bogged down by the "why didn't they read?" frustration, I now focus on refining my information delivery and patiently, perhaps sometimes robotically, pointing people to the source or briefly re-explaining. it's about being effective, not just being right.
MPM