Workplace Communication and Professionalism

The communication skills that get you hired keep mattering once you start the job — arguably more, since workplace communication happens constantly and in writing as much as in speech.

Status updates are one of the most common professional documents you'll write, and a useful one has three parts: progress (what's actually been done), blockers (what's stopping further progress, if anything), and next steps (what happens next, and roughly when). A status update that only lists completed tasks and omits blockers can be actively misleading — it lets a stuck project look fine right up until a deadline is missed, because no one flagged the problem while there was still time to address it.

Feedback, both giving and receiving it, follows a similar principle: it should be specific and about behavior, not about the person. "You're not detail-oriented" is a judgment about someone's character that they can't directly act on. "The last two reports had numbers that didn't match the source spreadsheet — can we add a quick double-check step before sending?" describes a specific, observable behavior and pairs it with something concrete to change. The second version is far more likely to actually change what happens next, which is the entire point of giving feedback in the first place.

Escalating a blocker — telling someone, usually a manager, that you're stuck and need help — is a skill many new professionals are hesitant to use, out of a (usually mistaken) worry that asking for help looks incompetent. In practice, sitting silently on a blocker for days, especially one that affects other people's work, is the version that actually damages trust. A reasonable norm is to attempt to resolve something yourself first, but to escalate once you've spent a meaningful amount of time stuck, or immediately if the blocker is stopping someone else's work too — waiting on someone else is a very different situation from quietly struggling alone.

Finally, workplace norms take real observation to learn, especially as a new hire. Every team has unwritten conventions — how quickly people are expected to respond to messages, how meetings are run, how decisions actually get made versus how the org chart suggests they get made. A new hire who immediately tries to change established processes before understanding why they exist tends to create friction, even when the suggested change is genuinely reasonable. Asking clarifying questions early, and observing before proposing changes, is not passivity — it's how you learn enough about the actual system to make a change that will actually stick, rather than one that ignores a constraint you didn't know existed yet.