• Workflow (Work in process based on Adler - How To Read A Book)
  • Inspectional
  • Analytical & Syntopical
• Purpose
• Expectations
• Table of Contents
• Topics
• Initial Summary
• Structure
• Notes
• Works Cited

Workflow (Work in process based on Adler - How To Read A Book)

Keeping this handy for the moment- will move to probably the sources page.

Inspectional

1. Write purpose and expectations
2. Review ToC
3. Scan Index and note interesting terms.
4. Read book quickly to try and understand it as a whole.
5. Write brief summary.
6. Define the structure.

Analytical & Syntopical

5. Read Works Cited (Notes section).
6. Go back and review particularly interesting sections where detailed notes may be useful if warranted. Suport of Syntopical reading.
7. Start at the beginning and read more thoroughly and take detailed notes if warranted. Support of Analytical reading.

Purpose

I've followed Cal for a while and like what he has to say. I have some issues with email, but generally my work has been such that I don't feel like I get overwhelmed compared to most. That being said, I'm interested to read about some of his strategies.

Expectations

This is largely a practical book, so I'm expecting a set of strategies to reduce the overall amount of mail that comes into my inbox. I'm also hoping for some philosophy that can extend beyond the practical tips and hopefully be applicable in other areas.

My measure of disappointment will be if this is a budget version of Getting Things Done.

Table of Contents

1. Introduction: The Hyperactive Hive Mind
2. Part 1: The Case Against Email
   1. Email Reduces Productivity
   2. Email Makes Us Miserable
   3. Email Has a Mind of its Own
3. Part 2: Principles for a World Without Email
   1. The Attention Capital Principle
   2. THe Process Principle
   3. The Protocol Principle
   4. The Specialization Principle
4. Concolusion: The Twenty-First-Century Moonshot

Topics

• Admin work,lack of specialization
• Agile Methodologies
• Algorithms
• David Allen - Getting Things Done
• Assembly Lines
• Attention Capital Principle
• Autonomy
• Bell Labs
• Tragedy of the Commons
• Peter Drucker
• Henry Ford
• Thomas Hobbes - Leviathan
• Information Theory
• Kanban
• Justin Kruger
• Scientific Management
• Process Principle
• Productivity
• Protocol Principle
• Specialization Principle
• Task Boards
• Frederick Taylor Winslow
• Extreme Programming (XP)
• Workflows

Initial Summary

Digital distraction. Paul Graham - Maker's Schedule, Manager's Schedule. Counter- George C. Marshall - cut beaucracy, admonished time wasting, left at 5:30 always. Key decisions, delegate the rest. Ticketing systems? If you didn't respond quickly to slack, you were considered slacking off. Higher friction systems forces more thought about process Tragedy of the Commons - solutions? Ownership vs Stewardship Locus of Control Can Production Processes apply to Knowledge work? Is there a belief that a lack of process allows for nibleness?

Structure

Notes

Works Cited