Driving Technical Change

Driving Technical Change

Terrence Ryan

Language: English

Pages: 200

ISBN: 1934356603

Format: PDF / Kindle (mobi) / ePub

Driving Technical Change

Terrence Ryan

Language: English

Pages: 200

ISBN: 1934356603

Format: PDF / Kindle (mobi) / ePub


Your co-workers' resistance to new technologies can be baffling. Logical arguments can fail. If you don't do politics, you will fail. With Driving Technical Change, by Terrence Ryan, you'll learn to read users' "patterns of resistance"-and then dismantle their objections. Every developer must master the art of evangelizing. With these techniques and strategies, you'll help your organization adopt your solutions-without selling your soul to organizational politics.

Finding cool languages, tools, or development techniques is easy-new ones are popping up every day. Convincing co-workers to adopt them is the hard part. The problem is political, and in political fights, logic doesn't win for logic's sake. Hard evidence of a superior solution is not enough. But that reality can be tough for programmers to overcome.

In Driving Technical Change: Why People On Your Team Don't Act on Good Ideas, and How to Convince Them They Should, Adobe software evangelist Terrence Ryan breaks down the patterns and types of resistance technologists face in many organizations.

You'll get a rich understanding of what blocks users from accepting your solutions. From that, you'll get techniques for dismantling their objections-without becoming some kind of technocratic Machiavelli.

In Part I, Ryan clearly defines the problem. Then in Part II, he presents "resistance patterns"-there's a pattern for each type of person resisting your technology, from The Uninformed to The Herd, The Cynic, The Burned, The Time Crunched, The Boss, and The Irrational. In Part III, Ryan shares his battle-tested techniques for overcoming users' objections. These build on expertise, communication, compromise, trust, publicity, and similar factors. In Part IV, Ryan reveals strategies that put it all together-the patterns of resistance and the techniques for winning buy-in. This is the art of organizational politics.

In the end, change is a two-way street: In order to get your co-workers to stretch their technical skills, you'll have to stretch your soft skills. This book will help you make that stretch without compromising your resistance to playing politics. You can overcome resistance-however illogical-in a logical way.

Large-Eddy Simulation in Hydraulics

Stuff [UK] (December 2011)

Thinking About America's Defense: An Analytical Memoir

The Book of Qt 4: The Art of Building Qt Applications

Cells and Robots: Modeling and Control of Large-Size Agent Populations (Springer Tracts in Advanced Robotics)

Marconi's Wireless and the Rhetoric of a New Technology (SpringerBriefs in Sociology)

 

 

 

 

 

 

 

 

 

 

 

 

. . . . . . . . . . . . . . . 34 35 37 37 8 The Burned 8.1 Underlying Causes . . . . . . . . . . . . . . . . . . . . . 8.2 Effective Countering Techniques . . . . . . . . . . . . . 8.3 Prognosis . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 39 39 40 9 The Time Crunched 9.1 Underlying Causes . . . . . . . . . . . . . . . . . . . . . 9.2 Effective Countering Techniques . . . . . . . . . . . . . 9.3 Prognosis . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 41 42 43 10 The

opportunity to tell her about your special baby. You’ve been working on an automation engine that can introspect a database, build a CRUD application, and style it with a companybranded look and feel. After it is built, you can spend a little time tweaking the model and tweaking the UI to perfect your application. It’s simple scaffolding, but it’s awesome. You tell your boss about it. She doesn’t seem to get it. She just asks how much time you’ve been spending on it. You tell her, and she goes

You can build an internal solution requiring your tool or technique. If that internal solution is compelling enough, people will be forced to use the required bits. Creating something compelling shares a lot with some of the other tools and techniques and in a way is composed of several of them. By creating something very useful, you Demonstrate the Technique. You’ll probably have to Gain Expertise to accomplish it. You also Focus on Synergy, using your tool or technique to solve a company

creating something compelling for, 103 demonstrating to, 71 expertise countering, 58 getting publicity to, 89 next attempt behavior, 125 unit tests, 18, 60, 97 universal techniques, 51 T V Target the Willing, 111–114 teaching to gain expertise, 57, 58 techniques countering, 51–52 demonstrating, 30, 68–73 ignorance of, 30 researching, 55 using, 56–57 technology matching rules to, 76 not using, 29–30 test-driven development (TTD), 97 testing framework, 77 validation, 85 vulnerability, 18 W web

wasting time using slow methods and tools. That cost can be a little more subtle sometimes. Programmers tend to define themselves by their language: “I’m a Java developer.” or “I’m a .NET developer.” Getting a Java developer to try Ruby is more than getting them to spend the time; it’s about getting them to rethink their identity, even for a bit. Don’t even get me started on trying to get people to try other OS platforms. It can get even more ephemeral than that. There comes a point when some

Download sample

Download