The point is to impose a pattern on the way a manager copes with problems. To make something regular that was once irregular is a fundamental production principle, and that's how you should try to handle […] interruptions […] Sounds like an echo of ‘work to code’ from Tom Sachs’ Ten Bullets
High Output Management
from Andrew S. Grove 📕
Filed under:
Same Source
- Today's gap represents a failure of planning sometime in the pa...
- What decision needs to be made? When? Who will decide? Who will nee...
- any decision [should] be worked out and reached at the lowest compo...
- Task-relevant maturity: How senior someone is for the task at hand....
- the real sign of malorganization is when people spend more than 25%...
- managers do not talk to their subordinates about their problems but...
- two basic kinds of meetings: - process-oriented meeting, knowledge ...
- View all
Related Notes
- It is far easier to collaborate on a first principle model. At this...from sirupsen.com
- If you are designing for 8 demands it’s likely that 6 are easy, 7 r...from sirupsen.com
- Good architecture is built incrementally, but **not** designed incr...from sirupsen.com
- Organizing into services taught teams not to trust each other in mo...from gist.github.com
- I was taken with this cybernetic description of an aircraft factory...from interconnected.org
- These are qualities of a good system that we should strive to fulfi...from Josh Beckman
- BIG SYSTEMS EITHER WORK ON THEIR OWN OR THEY DON’T. [[Big systems s...from John Gall and D.H. Gall
- "Jobs to be done" is an attempt to identify demand withou...from Josh Beckman