Work Etiquette
General guidelines
Please behave professionally and reduce visual noise on camera (items in background), auditory noise (background) and contextual noise (unnecessary words or comments) to a minimum.
Always listen to the client and pay attention to their needs.
Always-Be-Capturing. When someone speaks and the content of the conversation is important, write notes on a Miro board or in your personal notebook to make sure that you can refer back to them later.
Always have Discord open with the internal project channel for conversations with the team outside of Zoom.
Mute your phone and desktop's notifications.
Don't eat, smoke or do any other activities during workshops. If you are not the main facilitator, turn off your camera in case you need to step away from the screen.
By default, your objective is to overdeliver and make sure everyone you work with is happy with your work. There are many internal feedback rounds that are there to improve each other.
Please make sure your internet connection is 100% reliable throughout the entire workshop and you have access to all tools.
Always be on time or a minute earlier. If you need to come late, discuss the best way to join with another expert of the sprint.
Please make sure your background has as little visual noise as possible.
Please have good audio and no background noise. We recommend a setup with a professional microphone but good headphones do the trick!
When you work with the team, put 100% of your attention to the client and their requirements.
Don't schedule other meetings or phone calls in the breaks. Ideally take the time to get fresh air, look at a panoramic view or rest/meditate.
Drink enough water and avoid sugary snacks, it will impact your attention span and focus.
Representing Deep Work as a Collaborator
Once you filled out the collaborator application, you can contribute and learn but not vote or give advice, commonly known as shadowing (more on that below).
Once you receive the Collaborator status, you can apply to shadow (unpaid) on projects by observing and learning.
In order to become an Expert, you first collaborate with an Expert on a project, contribute with work, get reviewed, and can then apply to become an Expert on a specific domain. Reviews and feedback happen through existing Experts, who know the quality of the work.
Who are you not as a part of Deep Work?
We make it clear you're part of Deep Work. To a client we don't want to give the impression that you are:
An unrelated external contractor
Not taking responsibility for your work
Splitting time between other projects
Disorganized, unfocused, and not paying attention
Representing Deep Work as an Expert
Everyone on our team (e.g. facilitators, product designers, user researchers, etc.) who provides critical advice to the client is seen as an Expert on the project. Due to their past experience working in the product design space and familiarity with building a product, their role is similar to that of a traditional consultant. They are confident with their expertise and knowledge and their advice is appreciated.
As an Expert, you:
Participate in governance decisions
Put your health and wellbeing before everything else
Are knowledgeable within your domains of expertise (Facilitation, Communication Strategy, Product Design, Research, etc.)
Can confidently say you're experienced
Use friendly and professional language
Can express your thoughts succinctly, honestly, and clearly
Are interested in the success of our customers more than money or status
Last updated
Was this helpful?