Skip to content
Snippets Groups Projects
Commit 54a1df59 authored by Dave Jagoda's avatar Dave Jagoda
Browse files

Fix spelling error 'syncronous'

parent 4b7fdcab
No related branches found
No related tags found
1 merge request!751Migrated culture from www-gitlab-com to here
......@@ -371,7 +371,7 @@ Following pivots to synchronous calls, there should be a written summary created
</figure>
<!-- blank line -->
*In this GitLab Unfiltered [video](https://youtu.be/amiDcpIXIQ8), two GitLab colleagues discuss lessons learned from managing a team asyncronously, across many time zones, while traveling.*
*In this GitLab Unfiltered [video](https://youtu.be/amiDcpIXIQ8), two GitLab colleagues discuss lessons learned from managing a team asynchronously, across many time zones, while traveling.*
### Focus on the positives
......@@ -389,7 +389,7 @@ The organizer is responsible for informing the entire company, via post-meeting
Team needs are as unique as their objectives and will experience asynchronous communication differently. However, team leaders and managers can set KPI targets based on one or all of the following:
1. Percent reduction of minutes spent in syncronous meetings
1. Percent reduction of minutes spent in synchronous meetings
2. Percent increase in GitLab issue/epic/merge request usage
3. Improved ratio of meeting minutes-to-[GitLab contributions](https://docs.gitlab.com/ee/user/group/contribution_analytics/)
4. Increase in [360 feedback](/handbook/people-group/360-feedback/) citing '[bias towards asynchronous communication](/handbook/values/#bias-towards-asynchronous-communication)' in the Diversity, Inclusion & Belonging field
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment