Name: Driving Technical Change
ISBN: 9781934356609

Terrence Ryan

New technologies are popping up every day. Convincing co-workers to adopt them is the hard part. Adobe software evangelist Ryan breaks down the patterns and types of resistance technologists face in many organizations.

Why People on Your Team Don't Act on Good Ideas, and how to Convince Them They Should

Driving Technical Change

Nikolay Bachiyski

A quick book.

Two bad things, and one good:

 * Bad: the book was about how to drive small or medium technical change. Like how to convince others to use the new toys, not how to truly change perceptions.
 * Good: defining the different skeptic patterns (the uninformed, the herd, the cynic, the burned, the time crunched, the boss, the irrational). This is what I kept from the book, and it helped me understand how people think I bit more.
 * Bad: the solutions were too general and shallow. It sounded like and objective algorithm, but in my experience it can't be followed without truly knowing how the specific people think. The skeptic patterns gives us some idea, but if our end goal is something more than making our colleagues try git, we need deeper understanding.

If you're complete novice in technical office politics the book is an OK introduction, if you're not, you probably won't learn much.

Driving Technical Change Why People on Your Team Don't Act on Good Ideas, and how to Convince Them They Should

Reviews

Highlights