Practical guide · 4 min read
Digital etiquette for meetings, messages, phones and websites
Digital etiquette is often described as a list of manners, but many online disagreements are really design and power problems. A camera request from a friend is not the same as a camera rule from an employer. A notification from a colleague is not the same as an expectation of an immediate reply.
Useful norms make expectations explicit while preserving access, privacy and the ability to disconnect. They also place responsibility on the person designing the meeting, website or workflow, not only on the individual trying to cope with it.
Choose the lightest channel that can do the job
Before scheduling a meeting, ask whether a short document, message or recorded update would let people respond in their own time. Before sending a long message, ask whether a conversation would prevent confusion. The goal is not to make one channel “correct”, but to match its cost and immediacy to the task.
A recurring meeting earns its place when it creates shared understanding, a decision or a relationship that asynchronous work cannot. It should have a purpose, a finish point and enough context for people to prepare. Protected focus blocks can then become a team agreement rather than something each person must defend alone.
Presence is not the same as participation
Cameras can provide social cues and help some groups feel connected. They can also expose a home, reveal other people, consume limited bandwidth or make concentration harder. In an ordinary meeting, optional video plus clear verbal and written participation routes is a strong default.
If video is genuinely needed for a demonstration, identity check or access reason, explain why and for how long. Alternatives such as a profile image, chat, captions, dial-in audio or a blurred background should remain available wherever the task permits them.
Separate sending from expecting
People work across time zones and different schedules, so banning every after-hours message can be impractical. The more important boundary is whether the recipient is expected to read or answer it. Teams can use scheduled send, status indicators and a written definition of what counts as urgent.
Managers and group leaders have extra influence: a late message from them may feel compulsory even when labelled “no rush”. Model the norm consistently, put emergency routes somewhere else, and review whether workloads make the stated boundary impossible in practice.
Give attention a negotiated place
A phone on a shared table can mean distraction, but it can also be a translation tool, medical aid, payment device or route to a person needing care. For planned conversations and meals, agree on the aim: perhaps phones stay away except for a stated need, or everyone accepts that the occasion is informal.
Explicit agreements are kinder than silent tests. If someone must check a message, a brief explanation can prevent the action being interpreted as disinterest. The same courtesy works online: say when you are stepping away, and do not infer someone’s commitment from a single indicator such as a camera light or response time.
Build respectful defaults into the interface
Autoplaying sound takes control of a person’s environment and can conflict with access needs. Long forms that cannot be saved assume uninterrupted time, a stable connection and easy access to every document. These are not failures of user etiquette; they are choices made by a service.
A considerate default keeps unexpected audio off, gives clear controls, preserves entered information safely and lets someone return later. Test with keyboards, assistive technology, slow connections and small screens. The fairest reminder is often the one a system no longer needs to send because the task became easier to complete.