recommended_reading
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
recommended_reading [2020/12/01 08:14] – [Table] Added Accelerate hans | recommended_reading [2020/12/01 08:41] (current) – hans | ||
---|---|---|---|
Line 2: | Line 2: | ||
List of books that I have found useful as I work with people and try to understand how to improve both my effectiveness and those I work with: | List of books that I have found useful as I work with people and try to understand how to improve both my effectiveness and those I work with: | ||
- | |||
- | |||
- | ====== Organizational Change ====== | ||
- | |||
- | |||
- | |||
- | [[team_of_teams_-_new_rules_of_engagement_for_a_complex_world_-_general_stanley_mcchrystal|" | ||
- | |||
- | Really good book on the change in management approach that we need to put in place to become a more resilient and agile organization - beyond team agility to organization agility. Or to quote General McChrystal “Teams can bring a measure of adaptability to previously rigid organizations. But these performance improvements have a ceiling as long as adaptable traits are limited to the team level.” | ||
- | |||
- | I recommend this to executives especially who are trying to understand how they and the overall organization will need to change in order to become the organization they want it to be. This book covers the move in approach from the “scientific management” / “reductionist” and “command and control” view of managing an organization to one based on “common purpose” / “extreme transparency” and “de-centralized decision making”. “The role of the senior leader was no longer that of controlling puppet master, but rather that of an empathetic crafter of culture.” | ||
- | |||
- | If you are familiar with the agile approach to management the book will cover a lot of ideas that will seem very familiar to you. The benefit of this work is that presents these concepts from an organizational / enterprise level. | ||
- | |||
- | [[http:// | ||
- | |||
- | There are a lot of books about organizational change. This book helps you craft the message (in story form) so that you can engage people' | ||
- | |||
- | ====== Systems Thinking ====== | ||
- | |||
- | [[the_principles_of_product_development_flow_second_generation_lean_product_development_-_don_reinertsen|" | ||
- | |||
- | Probably the greatest book ever written on how to improve the creation of products. Also probably the most information packed so the recommended approach to this one is to skim read it the first time for basic content, and then re-read sections as you need it. If you want to understand how to manage risk, how to make decisions of what work to schedule first, on [[what_is_wrong_with_100_utilization_thinking|why you should not focus on 100% utilization of your people]] and so on ... you get the picture. This is the book. | ||
- | |||
- | [[http:// | ||
- | |||
- | Another book that really is excellent but a non-trivial read. Helps you understand the application of a lean thinking approach to the problem of new product development (i.e. invention). If you are interested in: | ||
- | |||
- | * Reducing your development time and resources use as much as four times. | ||
- | * Reducing the risk of quality problems, schedule and cost overruns, and failed products as much as 10 times. | ||
- | * Increasing innovation as much as 10 times. | ||
- | * Reusing production systems and parts, slashing capital costs and improving quality. | ||
- | |||
- | The book shows how to leverage learning and how working multiple design approaches (and deciding as late as possible) will improve solutions. This book combats the notion that phase gate approach to development does not result in improved results and that an approach based on pulling together a total system as an objective milestone makes sense. | ||
- | |||
- | The last 1/4 of the book is a series of case studies at the end of the book are really interesting although if you have already read [[http:// | ||
- | |||
- | As said, an excellent book. It is clear how this booked influenced the thinking at Harley Davidson - see below. | ||
- | |||
- | [[http:// | ||
- | |||
- | Business novel aimed at helping you understand the " | ||
- | |||
- | If you want this thinking applied to project management you might want to try [[http:// | ||
- | |||
- | [[http:// | ||
- | |||
- | Brilliant book, just brilliant, if you are trying to understand how to implement " | ||
- | |||
- | [[https:// | ||
- | |||
- | There are two uses of this book: | ||
- | |||
- | - To understand a small set of metrics which, if tracked correctly, will help you improve your process and | ||
- | - To understand how to interpret scatterplots, | ||
- | |||
- | This book is a little " | ||
- | |||
- | [[https:// | ||
- | |||
- | Great book! Applies agile / lean approach to the idea of working (and importantly) measuring progress on a true innovation by measuring true learning. While written from the perspective of a startup, the approach can be applied to any innovative endeavor. | ||
- | |||
- | [[this_is_lean_-_resolving_the_efficiency_paradox_-_niklas_modig|" | ||
- | |||
- | I thought this was a great book, a fabulous introduction to help you understand what lean is all about and, just as importantly, | ||
- | |||
- | The base premise is that lean is about “flow efficiency” as opposed to resources efficiency in how work gets done. Flow efficiency focuses on the amount of time it takes from identifying a need to satisfying that need, whereas resource efficiency focuses on efficiently using the resources that add value within an organization. | ||
- | |||
- | Why is this important? For more than two hundred years, industrial development has been built around increasing the utilization of resources. Efficient use of resources has long been the most common way of looking at efficiency. It continues to dominate the way in which organizations in different industries and sectors are organized, controlled, and managed. From an economic perspective, | ||
- | |||
- | ====== Sustaining Change ====== | ||
- | |||
- | [[http:// | ||
- | |||
- | Once you have an Agile implementation at scale, you often have a new problem. Whereas before you had silos associated with the disciplines, | ||
- | |||
- | ====== People and Motivation ====== | ||
- | |||
- | [[http:// | ||
- | |||
- | Your first step on a journey on how to really motivate people. Mastery, autonomy and purpose, not money (or at least not directly). For the " | ||
- | |||
- | |||
- | |||
- | [[http:// | ||
- | |||
- | An absolute classic book. This book is a discussion about the counterintuitive principle that explains why efficiency efforts can slow a company down. Fights against the concept that, for example, 100% utilization of people is the most efficient way to get something done and helps you understand why, and what to do about it. | ||
- | |||
- | ====== Organizational Change ====== | ||
- | |||
- | [[implementing_beyond_budgeting-_unlocking_the_performance_potential_by_bjarte_bogsnes_-_bjarne_bogsnes|Implementing Beyond Budgeting: Unlocking the Performance Potential - Bjarte Bogsnes]] | ||
- | |||
- | Just a great book if you want to understand how to work better with finance and HR. There is a lot here, and some of it may not be immediately something to work, but the ideas can be applied to a wide variety of situations. | ||
< | < | ||
Line 126: | Line 33: | ||
| [[http:// | | [[http:// | ||
| [[http:// | | [[http:// | ||
- | | [[https:// | + | | [[https:// |
+ | |[[https:// | ||
+ | |[[http:// | ||
+ | |[[http:// | ||
+ | |[[http:// | ||
+ | |[[https:// | ||
+ | |[[https:// | ||
+ | |[[http:// | ||
+ | |[[http:// | ||
+ | |[[https:// | ||
</ | </ | ||
</ | </ | ||
- | |||
/home/hpsamios/hanssamios.com/dokuwiki/data/attic/recommended_reading.1606839291.txt.gz · Last modified: 2020/12/01 08:14 by hans