DOCSLIB.ORG

Fear Less and Other Patterns for Introducing New Ideas Into Organizations

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Fear Less and Other Patterns for Introducing New Ideas Into Organizations Fear Less And Other Patterns for Introducing New Ideas into Organizations PRELIMINARY VERSION OF PATTERNS Last Update: February 25, 2003 This document is a preliminary version of the final patterns that will appear in a book on introducing new ideas into organizations. It is only a draft – you can expect to see typos and incomplete material. The book will be published in 2004. It will include an updated version of the patterns, case studies and background material on the research and patterns development. Copyright © 2003, Addison-Wesley Publishing Company Dr. Mary Lynn Manns Dr. Linda Rising University of North Carolina at Asheville 1109 E. Tapatio Drive Department of Management & Accountancy Phoenix, AZ 85020-1185 USA Asheville, NC 28804 USA [email protected] [email protected] The work in using and writing patterns began with Christopher Alexander who wrote A Timeless Way of Building [Alexander79] and A Pattern Language [Alexander+77] in the 1970s. When the software community began studying his ideas, interest in patterns began to spread throughout the software development industry in the 1990s. However, efforts to introduce patterns into organizations have had mixed success. The patterns presented here are the beginning of a pattern language whose focus is the introduction of a new idea into an organization. When the language was begun, the focus was on introducing patterns into an organization but over the years, we have come to realize that most of the patterns can be used for introducing most any new idea. The contributors are from organizations all over the world. We have found a close connection between our experiences, which is reflected in the patterns we have written. The creation of a pattern language should be the work of a community. Many people have contributed, and continue to contribute, to the development of this language. These include the pattern authors, those who have attended the Introducing Patterns into an Organization workshops, and the countless others who are providing feedback and ideas for improving the patterns. Especially valuable was the effort of all the shepherds who have worked with us along the way: Ken Auer, PLoP ’97, David DeLano, PLoP'99, Jim Coplien, EuroPLoP'00, Brian Marick, PLoP’01, David Kane, EuroPLoP’02. Special thanks also goes out to Alan O’Callaghan for his unwavering support and his invaluable help with some of our conference sessions. As Christopher Alexander states, we hope that “many of the people who read, and use this language, will try to improve these patterns—will put their energy to work, in this task of finding more true, more profound invariants—and we hope that gradually these more true patterns, which are slowly discovered, as times goes on, will enter a common language, which all of us can share.” [Alexander+77] The Patterns The patterns in this collection can be used to introduce a new idea into an organization. The objective is to build a grass roots group that becomes interested in the idea and can be part of spreading the word throughout the organization. There are relationships between these patterns, thus forming a pattern language. All useful pattern languages are living things that continue to grow. We describe several sequences in the pattern language in the case studies and we also include the following categories. Roles Champion Skeptic Connector Corporate Angel Early Adopter Early Majority Dedicated Champion Evangelist Innovator Local Sponsor Mentor Respected Techie Events Big Jolt Brown Bag Do Food Hometown Story Location, Location, Location Piggyback Royal Audience Keeping the Idea Visible e-Forum Group Identity In Your Space Plant the Seeds Stay in Touch Treasure Token Dealing with Skeptics Adopt a Skeptic Champion Skeptic Fear Less Early Activities Ask for Help Brown Bag Just Do It Test the Waters Reaching Out Ask for Help Just Say Thanks Shoulder to Cry On Convincing Others Corridor Politics External Validation Guru Review Personal Touch The Right Time Smell of Success Tailor Made Whisper in the General’s Ear Teaching and Learning the Idea Just Enough Study Group Long-term Activities Involve Everyone Next Steps Small Successes Step by Step Sustained Momentum Time For Reflection The Pattern Summaries Adopt a Skeptic Pair those who have accepted your new idea with those who have not. Ask for Help Since the task of introducing a new idea into an organization is a big job, look for people and resources to help your efforts. Big Jolt To provide more visibility for the change effort, invite a well-known person to do a presentation about the new idea. Brown Bag Use the time when people normally eat lunch to provide a relaxed setting for hearing about the new idea. Champion Skeptic Ask for Help from strong opinion leaders, who are skeptical of your new idea, to play the role of ‘official skeptic.’ Use their comments to improve your effort, even if you don’t change their minds. Connector To help you spread the word about your new idea, Ask for Help from the people who have connections with many others in the organization. Corporate Angel To help align the innovation with the goals of the organization, get support from a high-level manager. Corridor Politics Informally work on decision makers and key influencers before an important vote, to make sure they fully understand the consequences of the decision. Dedicated Champion To increase your effectiveness in introducing your new idea, make the work part of your job description. Do Food Make an ordinary gathering a special event by including food. e-Forum Set up an electronic bulletin board, distribution list, WIKI, or listserver for those who want to hear more. Early Adopter Ask For Help from the opinion leaders in your organization. Early Majority To create commitment to your new idea in the organization, you must convince the majority. Evangelist To begin to introduce the new idea into your organization, do everything you can to share your passion for it. External Validation To gain credibility for the new idea inside your organization, market your ideas externally so that people inside your organization become aware of them. Fear Less Turn resistance to your new idea to your advantage. Group Identity Give the change effort an identity to help people recognize that it exists. Guru Review Gather Respected Techies and other interested colleagues to evaluate your new idea for managers and other developers. Hometown Story To help people see the usefulness of your new idea, encourage those who have had success with it to share their stories. In Your Space Keep the new idea visible by placing reminders throughout your organization. Innovator When you begin the change initiative, Ask for Help from colleagues who like new ideas. Involve Everyone For a new idea to be successful across an organization, everyone should have an opportunity to support the innovation and make a unique contribution. Just Do It To prepare to spread the word about your new idea, find out for yourself what the benefits and limitations are. Just Enough To ease learners into the more difficult concepts in a new idea, give a brief introduction and then make more information available when they are ready. Just Say Thanks To make people feel appreciated, say “thanks” in the most sincere way you can to everyone who helps you. Local Sponsor Ask for Help from first-line management. When your boss supports the tasks you are doing to introduce the new idea, you can be even more effective. Location, Location, Location To avoid interruptions that disrupt the flow of an event, try to hold significant events off site. Mentor When a project wants to get started with the new idea, have someone around who understands it. Next Steps Take time near the end of a presentation about your new idea to identify what participants can do next. Personal Touch To convince people of the value of your new idea, show how it can bepersonally useful and valuable to them. Piggyback To increase attendance and help people see that your new idea isn’t anything unusual, hold a presentation about your new idea during a regularly scheduled event in the organization. Plant the Seeds To spark interest, carry materials (“seeds”) and display (“plant”) them around whenever the opportunity arises. Respected Techie Enlist the support of senior-level people who are esteemed by members of the organization. The Right Time Consider the timing when you schedule events or when you ask people for help. Royal Audience Arrange for management and members of the organization to spend time with speciala Big Jolt visitor. Shoulder to Cry On To avoid becoming too discouraged when the going gets tough, find opportunities to talk with others who are also struggling. Small Successes To avoid becoming discouraged by the challenges and all the things you have to do when you’re involved in an organizational change effort, celebrate each small success. Smell of Success When your efforts result in some visible positive result, people will "come out of the woodwork" to talk to you. Treat this opportunity as a “teaching moment.” Stay in Touch Once you’ve enlisted the support of key persons, don’t forget about them and make sure they don’t forget about you. Step by Step Relieve your frustration at the enormous task of changing an organization by taking one small step at a time to meet your goal. Study Group Form a small group of colleagues who are interested in exploring or continuing to learn about a specific topic. Sustained Momentum Take a pro-active approach to the on-going work of sustaining the interest in the new idea in your organization. Tailor Made To convince the organization of the value it can gain from the new idea, tailor your message to the needs of the organization.
Load more

Recommended publications
  • Introducing Patterns (Or Any New Idea) Into Organizations
    Introducing Patterns (or any new idea) into Organizations ** A WORK-IN-PROGRESS ** Last Update: August 8, 2001 Copyright © 2001, Mary Lynn Manns, Linda Rising Mary Lynn Manns Linda Rising University of North Carolina at Asheville 1109 E. Tapatio Dr. Department of Management & Accountancy Phoenix, AZ 85020-1185 USA Asheville, NC 28804 USA [email protected] [email protected] Submitted to PLoP’01 August 8, 2001 Note: Since we have been working on this document for many years, there are quite a few patterns in this growing language-in-progress. However, many of the patterns have been shepherded and workshopped at previous PLoPs and other events -- this information is noted at the end of each of these patterns. In order to prevent those who shepherd and workshop these patterns for PLoP’01 from becoming too overwhelmed, we ask that they read the complete document (in order to understand the domain), provide feedback on anything, but concentrate their efforts on the patterns that have not yet been exposed to review. These are designated with asterisks in the pattern list on the next page. Thank you! The work in using and writing patterns began with Christopher Alexander who wrote A Timeless Way of Building [Alexander79] and A Pattern Language [Alexander+77] in the 1970s. When the software community began studying his ideas, interest in patterns began to spread throughout the software development industry in the 1990s. However, efforts to introduce patterns into organizations have had mixed success. The patterns presented here are the beginning of a pattern language whose focus is the introduction of patterns into an organization, with the long-term goal of developing a patterns culture.
    [Show full text]
  • Design Patterns in Communications Software Edited by Linda Rising Frontmatter More Information
    Cambridge University Press 978-0-521-79040-6 - Design Patterns in Communications Software Edited by Linda Rising Frontmatter More information Design Patterns in Communications Software © in this web service Cambridge University Press www.cambridge.org Cambridge University Press 978-0-521-79040-6 - Design Patterns in Communications Software Edited by Linda Rising Frontmatter More information SIGS Reference Library 1. Object Methodology Overview CD-ROM • Doug Rosenberg 2. Directory of Object Technology • edited by Dale J. Gaumer 3. Dictionary of Object Technology: The Definitive Desk Reference • Donald G. Firesmith and Edward M. Eykholt 4. Next Generation Computing: Distributed Objects for Business • edited by Peter Fingar, Dennis Read, and Jim Stikeleather 5. C++ Gems • edited by Stanley B. Lippman 6. OMT Insights: Perspectives on Modeling from the Journal of Object-Oriented Programming • James Rumbaugh 7. Best of Booch: Designing Strategies for Object Technology • Grady Booch, edited by Ed Eykholt 8. Wisdom of the Gurus: A Vision for Object Technology • selected and edited by Charles F. Bowman 9. Open Modeling Language (OML) Reference Manual • Donald Firesmith, Brian Henderson-Sellers, and Ian Graham 10. JavaTM Gems: Jewels from JavaTM Report • collected and introduced by Dwight Deugo, Ph.D 11. The Netscape Programmer’s Guide: Using OLE to Build ComponentwareTM Apps • Richard B. Lam 12. Advanced Object-Oriented Analysis and Design Using UML • James J. Odell 13. The Patterns Handbook: Techniques, Strategies, and Applications • edited by Linda Rising 14. Kent Beck’s Guide to Better Smalltalk: A Sorted Collection • Kent Beck 15. The Elements of Java Style • Al Vermeulen et al. 16. More Java Gems • edited by Dwight Deugo, Ph.D.
    [Show full text]
  • Session 8 – Sub-Topic 1 from Analysis and Design to Software Architectures (Part I Addendum)
    Software Engineering G22.2440-001 Session 8 – Sub-Topic 1 From Analysis and Design to Software Architectures (Part I Addendum) Dr. Jean-Claude Franchitti New York University Computer Science Department Courant Institute of Mathematical Sciences 1 Agenda • Towards Agile Enterprise Architecture Models • Building an Object Model Using UML • Architectural Analysis • Design Patterns • Architectural Patterns • Architecture Design Methodology • Achieving Optimum-Quality Results • Selecting Kits and Frameworks • Using Open Source vs. Commercial Infrastructures 2 Part I Towards Agile Enterprise Architecture Models 3 There is an Urgent Need for More Reliable, Concept-driven, Early Requirements Processes (review) • SDLC Process model frameworks have matured and converged significantly on effective practices in system development phases, however, they are still weakest on the front-end. RUP Phases: Inception Elaboration Construction Transition • Project Planning • Hi-level languages • QA Methods • ??? • Use Case Models • Frameworks • Test environments • … • Object Models • IDEs • Issue support tools • Data Models • n-Tier Architectures • Usability • UI prototypes • Design Patterns Engineering • … • … • … MSF Phases: Envisioning Planning Developing Stabilizing / Deploying Less mature methods / support More mature methods / support 4 XP Practices (review) • The Planning Game – determine the scope of the next release, based on business priorities and technical estimates. • Small Releases – every release should be as small as possible, containing the most valuable business requirements. • Metaphor – guide all development with a simple, shared story of how the whole system works. • Simple Design – design for the current functionality, not future needs, and make the design as simple as possible for that functionality (YAGNI). • Refactoring – ongoing redesign of software to improve its responsiveness to change. • Testing – developers write the unit tests before the code; unit tests are run “continuously”; customers write the functional tests.
    [Show full text]
  • Application of Patterns to Real-Time Object-Oriented Software Design
    APPLICATION OF PATTERNS TO REAL-TIME OBJECT-ORIENTED SOFTWARE DESIGN by ROSS ALBERT MCKEGNEY A thesis submitted to the Department of Computing & Information Science in conformity with the requirements for the degree of Master of Science Queen’s University, Kingston, Ontario Canada July 2000 Copyright © Ross Albert McKegney, 2000 ABSTRACT The design and development of real-time software (i.e. software that must ensure timeliness while interacting with an external environment) is more difficult than for most other software. Modeling tools help deal with this complexity, allowing developers to view the system at various levels of abstraction, animate the models in a simulation environment, and even generate the code for a variety of target hardware/RTOS configurations. A natural extension to these tools is to provide support for design patterns (a method of documenting experience in the form of problem/context/solution triples for recurring problems). Such an extension provides yet another layer of abstraction to the models, and makes explicit the application of design patterns. This thesis will extract from the patterns literature a set of patterns dealing with issues relevant to the design of real-time object-oriented software (in order to demonstrate their variety and quality) - then will propose an extension to Rational Rose-RT to support patterns as an abstraction layer. ii ACKOWLEDGMENTS I would like to acknowledge my supervisor, Dr. Terry Shepard, for his guidance and direction throughout the writing of this thesis. I also acknowledge the members of my ‘hot-topics’ group at ChiliPLoP 2000: Mary-Lynn Manns (UNCS), Linda Rising (AGCS), Don Olson (AGCS), John Letourneau (Lucent Technologies), and Carol Stimmel (MediaOne Labs) for introducing me to pattern writing workshops.
    [Show full text]
  • Plop® Pattern Writing Bootcamp 2012
    PLoP® Pattern Writing Bootcamp 2012 Panama City, Panama Joseph (Joe) Yoder [email protected] July 25th, 2012 - 1 PLoP is a registered Trademark of The Hillside Group. Objectives • At the end of this “bootcamp” you will: – Have knowledge about pattern writing – Have a better understanding of the “Quality Without A Name” – Have helped write a pattern – Be the newest members of the pattern community! Thanks Rebecca Thanks Linda & Bob July 25th, 2012 - 2 Agenda • Introductions • Why Patterns? • Discussion of What’s a pattern? • Parts of a pattern • Patterns criticism and categorization • Choosing a topic • Group Pattern Writing • Group Pattern Writing Continued • Sample Writers’ Workshop • Pattern Languages • Pattern Ethics July 25 th, 2012 - 3 Introduction to Patterns July 25th, 2012 - 4 The Reason for Patterns • Experts at work often use their knowledge of how they solved similar problems to solve the current problem. • What if they could share their knowledge with others? • Pattern descriptions record experts’ wisdom so others can reuse it. July 25th, 2012 - 5 An Example of a Pattern* Window place *Christopher Alexander et al, A Pattern Language- Towns.Buildings. Construction, 1977 July 25th, 2012 - 6 The Window Place Pattern • Everybody loves window seats, bay windows, and big windows with low sills and comfortable chairs drawn up to them…A room without a place like this seldom allows you to feel comfortable • If the room contains no window which is a “place”, a person will be drawn between: 1. Wanting to sit down and be comfortable 2. Being drawn toward the light • If comfortable places are away from the windows, there is no way of overcoming this conflict… • Therefore: In every room where you spend any length of time during the day, make at least one window into a “window place” July 25th, 2012 - 7 Part 1: Pattern Basics July 25th, 2012 - 8 Patterns • “The pattern is, in short, at the same time a thing, which happens in the world, and the rule which tells us how to create that thing, and when we must create it.
    [Show full text]
  • 97 Things Every Programmer Should Know
    97 Things Every Programmer Should Know Collective Wisdom from the Experts Edited by Kevlin Henney Beijing · Cambridge · Farnham · Köln · Sebastopol · Taipei · Tokyo 97 Things Every Programmer Should Know Edited by Kevlin Henney Copyright © 2010 Kevlin Henney. All rights reserved. Printed in the United States of America. Published by O’Reilly Media, Inc. 1005 Gravenstein Highway North, Sebastopol CA 95472 O’Reilly books may be purchased for educational, business, or sales promotional use. Online editions are also available for most titles (http://my.safaribooksonline.com). For more information, contact our corporate/institutional sales department: (800) 998-9938 or [email protected]. Editor: Mike Loukides Compositor: Ron Bilodeau Series Editor: Richard Monson-Haefel Indexer: Julie Hawks Production Editor: Rachel Monaghan Interior Designer: Ron Bilodeau Proofreader: Rachel Monaghan Cover Designers: Mark Paglietti and Susan Thompson Print History: February 2010: First Edition. The O’Reilly logo is a registered trademark of O’Reilly Media, Inc. 97 Things Every Programmer Should Know and related trade dress are trademarks of O’Reilly Media, Inc. Many of the designations used by manufacturers and sellers to distinguish their products are clarified as trademarks. Where those designations appear in this book, and O’Reilly Media, Inc. was aware of a trademark claim, the designations have been printed in caps or initial caps. While every precaution has been taken in the preparation of this book, the publisher and au- thors assume no responsibility for errors and omissions, or for damages resulting from the use of the information contained herein. This book uses Repkover,™ a durable and flexible lay-flat binding.
    [Show full text]
  • Healthy Code February - 2015 1 Healthy Code 2 February - 2015 Healthy Code February 2015 Contents 22
    Healthy Code February - 2015 1 Healthy Code 2 February - 2015 Healthy Code February 2015 Contents 22 GrailsConf 4 2015 Microservices What are they and 26 why should you care? Interview with Linda Rising 12 34 Code Jugalbandi Effective Java with Groovy 16 38 Working with Let’s go with GO Spring Data Neo4J (SDN) Healthy Code February - 2015 1 Healthy Code 2 February - 2015 From the Editor Hello readers!!! It’s hard to believe, we are already into the second month of 2015. We are back with another very interesting set of articles this month. The languages. February issue is filled with loads of information about programming Rocky Jaiswal introduces us to the Go language throwing light on its about writing better Java code using Groovy. The Code Jugalbandi team is capabilities and potential. We have our Naresha continuing to impress us back with another melody and implementing it in a variety of languages. Linda Rising a renowned speaker and author talks to us about the Agile Mindset. Linda, being such a fascinating person, the interview is sure to have an impact on you forever. Microservices Architecture. This article talks Rajesh Muppalla has written a fantastic article on one of the most happening architectures, the about several issues with practical examples that will make you rethink the strategy of your projects. Arun is back with Ravikant and his favorite Neo4j. They talk about using Neo4j with Spring framework. EnjoyAnd yes! reading Do not and forget coding. to try out the quiz on Java 8. Prabhu Healthy Code February - 2015 3 Article|-------------|Rajesh Muppalla Microservices What are they and why should you care? Healthy Code 4 February - 2015 ver the last year, Microservices has emerged as a “new” approach to building large scale distributed systems.
    [Show full text]