Chapter-11-Phones,-Phones,-and-Phones.md

+- [[Japanese]]
+   * Part II Office Environment and Productivity
+     * [[Chapter 7 Equipment Police]]
+     * [[Chapter 8 The program can be done at night]]
+     * [[Chapter 9 Saving Office Investments]]
+     * [[Break a minute... Intermezzo]]
+     * [[Chapter 10: Mental Labor Hours vs. Physical Labor Hours]]
+     * [[Chapter 11 Phones, Phones, and Phones]]
+     * [[Chapter 12 Restoration of the Door]]
+     * [[Chapter 13 Office Environment Evolution Theory]]
+
+## Chapter 11 Telephone, Telephone, and Telephone (pp.78-84)
+
+- If you think about the phone, it's dangerous, and the analogy continues...
+
+> Of course the phone has changed the way we work, but it's bad that people have become desensitized to how badly an interrupted call can be. At the very least, managers should be aware of how their employees' productivity suffers when a phone call comes in.
+
+- We must think of a tolerant and efficient way for programmers to ignore phone calls so they can focus on their work.
+- "tolerance": there is a corporate culture that allows programmers to sometimes want to work without answering the phone
+- Efficient: you don't have to wait for the bell to stop ringing to get back to work
+
+- email
+- Phone interrupts your work, but email does not interrupt your work
+- However, there are reliability issues (mail lifetime, read status, sent status, etc.)
+
+>What's more important than playing tricks is changing your attitude. Staff must remember that sometimes they can be forgiven for not answering the phone. And managers need to understand that too.
+
+- The question of whether a phone call is bad or an e-mail is better is more complicated.
+- Expanded in Part V, Chapter 33.
\ No newline at end of file