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.

Stephen R. Barley reflects on over three decades of research to explore both the history of technological change and the approaches used to investigate how technologies, including intelligent technologies such as machine learning and robotics, are shaping our work and organizations.

This book examines how new workplace technology can improve performance - and how it can have the opposite effect when it is not properly planned and introduced with the participation of key stakeholders. It provides an overview and explanation of the steps involved in technology planning, acquisition, development, implementation, and assessment.

First published in 1995, Organizations and Technical Change examines the key changes that have taken place in the external and internal contexts of organizations which have experienced technical change. It reviews and assesses major elements of new technology, including: the development of strategy; the setting of objectives; employee involvement; and the management of the adoption process. Through four case studies, the book considers in detail a variety of approaches and shows how the adoption of technology and the issues involved have changed since the 1980s.

This book examines the management of technical change in manufacturing and services through an explicit political-economic framework. It examines the management of automation in Britain and America since 1950, and it applies the same useful framework to explore the impact of Japanization on both Britain and the US in the 1980s and 1990s.

The overwhelming majority of a software system’s lifespan is spent in use, not in design or implementation. So, why does conventional wisdom insist that software engineers focus primarily on the design and development of large-scale computing systems? In this collection of essays and articles, key members of Google’s Site Reliability Team explain how and why their commitment to the entire lifecycle has enabled the company to successfully build, deploy, monitor, and maintain some of the largest software systems in the world. You’ll learn the principles and practices that enable Google engineers to make systems more scalable, reliable, and efficient—lessons directly applicable to your organization. This book is divided into four sections: Introduction—Learn what site reliability engineering is and why it differs from conventional IT industry practices Principles—Examine the patterns, behaviors, and areas of concern that influence the work of a site reliability engineer (SRE) Practices—Understand the theory and practice of an SRE’s day-to-day work: building and operating large distributed computing systems Management—Explore Google's best practices for training, communication, and meetings that your organization can use

In his first complete text on the ADKAR model, Jeff Hiatt explains the origin of the model and explores what drives each building block of ADKAR. Learn how to build awareness, create desire, develop knowledge, foster ability and reinforce changes in your organization. The ADKAR Model is changing how we think about managing the people side of change, and provides a powerful foundation to help you succeed at change.