A job description explains only part of a role. Teams also develop unwritten norms about response time, initiative, communication channels, documentation, collaboration, and when to ask for help. Missing an unwritten rule is not the same as lacking ability.
Notice three layers of expectation
Task
What result must be produced?
Process
How, when, and with whom should the work happen?
Communication
Who needs updates, in what format, and how often?
Ask what success looks like
Vague instructions such as “take ownership” or “be proactive” can mean different things. Ask for an example: “What would taking ownership of this project look like during the next two weeks?”
Create a shared record
After a verbal conversation, send a short summary: “My understanding is that the report is due Thursday, should prioritize the three largest accounts, and needs your review before distribution.” This catches differences early.
Map one work assignment
Key takeaways
- Every role includes written and unwritten expectations.
- Define success in observable terms.
- Written summaries create shared understanding.
