this repo has no description
📚 Update Processes, Teamwork, Traveling, and Metrics documents with additional insights and practical tips
+5
-2
+1
-1
Data/Metrics.md
+1
-1
Data/Metrics.md
···
19
19
- Push a culture of metrics and goals as a source of learning, not promotions or success delegation.
20
20
- Vanity metrics are surface-level metrics. They're often large measures, like number of downloads, that impress others. **Clarity metrics** are operational metrics, like the number of minutes a day your product actually gets used or how long it took for a user to get service. These are the hidden gears that drive growth.
21
21
- [Factors that are easiest to measure or most visible are the ones that get the most attention and might not be the most important ones](https://wiki.c2.com/?SovietShoeFactoryPrinciple).
22
-
- When people are pressured to meet a target value there are three ways they can proceed:
22
+
- [When people are pressured to meet a target value there are three ways they can proceed](https://www.goodreads.com/book/show/63859):
23
23
1. They can work to improve the system.
24
24
2. They can distort the system.
25
25
3. Or they can distort the data.
+1
-1
Processes.md
+1
-1
Processes.md
···
27
27
28
28
*The only purpose of good process is to produce good outcomes.* A process is not good unless it produces good outcomes.
29
29
30
-
You cannot judge the process by a single outcome. [Only a long run of outcomes tell you anything about the process](https://two-wrongs.com/statistical-process-control-a-practitioners-guide.html). Consequently, once you know what the process is like, any single outcome from that process adds nothing to your knowledge about the process.
30
+
You cannot judge the process by a single outcome. [Only a long run of outcomes tell you anything about the process](https://two-wrongs.com/statistical-process-control-a-practitioners-guide.html). Consequently, once you know what the process is like, any single outcome from that process adds nothing to your knowledge about the process. If you want to improve a process, you have to ignore the process goal first, in favour of examining the process itself and understanding it.
+1
Teamwork.md
+1
Teamwork.md
···
80
80
- Encourage to fail. Failing is good if the team [[Learning|learns]] from it!
81
81
- Encourage effectiveness. Find ways to free up your time.
82
82
- Communication is a central part of working in teams. Prefer [[Asynchronous Communications]], use common [[Communication|communications]] techniques and be friendly. Trust and efficient communication has a big impact on team effectiveness.
83
+
- Make [sure people talk to each other every day and have a way to teach each other](https://1517.substack.com/p/why-bell-labs-worked).
83
84
- Have a primary [[Communication]] channel.
84
85
- Use long-form [[Writing]], rather than [[Meetings]], speaking, and chatting. Speaking only helps who's in the room, [[Writing]] helps everyone.
85
86
- Finish projects before starting more.