Expectations

Spoken & unspoken expectations you need to meet

Expectations shape behavior as much as any formal rule, and the unspoken ones carry more weight precisely because no one ever explains them.

Every workplace runs on a dense web of expectations: how quickly to reply to messages, how to behave in a meeting with senior people present, whether it is safe to say you do not know something, how much of your personal life it is appropriate to share. Most of these are never written down and are rarely discussed directly.

New people learn unspoken expectations by observation, by making small mistakes, or by being told informally after the fact. This process works, but it is slow, stressful, and uneven. People with networks or cultural familiarity pick things up faster; those without them are quietly disadvantaged.

Even established teams benefit from occasionally surfacing expectations that everyone assumes but no one has checked. What seemed obvious to the founder may be invisible to someone who joined two years ago. What once made sense may have quietly stopped being appropriate.

How it shows up

How this facet of culture actually appears in everyday working life, and what a healthy version tends to look like compared to one that is strained or ignored.

Explicit expectations

Clearly stated: the things in job descriptions, handbooks, onboarding documents, or direct manager conversations that set out what is required.

Implicit expectations

Learned through observation or experience: the unwritten norms about tone, availability, initiative, and social behavior that no formal document captures.

Healthy

Expectations are broadly shared and understood, new people can surface the ones they are unsure about without embarrassment, and the norms are revisited as the organization changes.

Strained

People feel like they are constantly navigating invisible rules, and mistakes that come from not knowing unspoken expectations are treated as character failures rather than onboarding gaps.

Questions to explore

Use these on your own or in a group. There are no right answers, only better conversations.

What expectations does someone need to meet here that are not written down anywhere?
How do new people typically find out what is actually expected of them, beyond the formal job description?
Are there expectations that feel outdated or that only some people actually follow?
Who tends to navigate implicit expectations most easily, and why might that be?
When expectations shift, how does the organization communicate that shift to people who operate on the old version?

Things to notice

Treating unspoken expectations as self-evident is a form of cultural gatekeeping: it advantages people who already share the founding group's background, habits, and frame of reference.
Making expectations explicit does not mean eliminating them. Some norms are worth keeping; the goal is shared understanding, not a rulebook for every situation.
Expectations can diverge between teams, levels, and locations. What counts as normal in one part of the organization may be seen as out of line in another.