Agile CoE vs. Agile CoP - Building Your Internal Coaching Platform
Stacey Louie
3x-CIO | Silicon Valley Entrepreneur | Management Thought Leader | Author | Product & Innovation Expert
Achieving “business agility” and maintaining Agile teams takes persistence, time, and dedication. Maintaining that positive momentum and engagement throughout an organization takes care, coordination, and encouragement. How do you cultivate collective thinking and exchanging of ideas within your team, and then eventually, the entire organization? No matter how you choose to approach Agile, it’s essential that your organization has a community platform to learn, grow and share this expert knowledge.
Building internal Agile coaching capabilities in an organization is a strategic investment that can help create a powerful agile culture for all leadership levels. Not only can it be cost-effective, but it also provides consistency, better context and value to your teams. Across the industry there are companies like Salesforce, Target, ExxonMobil, and many more who have developed robust approaches to supporting internal Agile Coaches as well as supporting a community of Agilists.
Community of Practice (CoP) vs. Center of Excellence (CoE)
The development of community encourages the deeper exploration of ideas. Communities of Practice (CoP) and Centers of Excellence (CoE) are two platforms that provide people with ways to organize and build on their ideas and expert knowledge. Implementation of these systems can have direct financial results, but just as importantly, can translate to higher customer satisfaction, sustained resources, and improvements in capacity and capability of teams.
While similar, there are some major differences between CoP’s and CoE’s that you may find work with or against your organizational goals.
Communities of Practice (CoP)
Communities of Practice are groups of people with similar interests who share experiences with a common goal. They come together to talk to one another and learn from each other. In this platform, all levels of expertise are welcomed, and all experiences can provide their perspectives and learnings. There is no one person in charge or set standards. Instead, the community works together to solve a problem and adopt a common solution together. Consider it as organized yet informal with opportunities for a wide range of people to participate irrespective of where they are in an organizational structure. If we consider the “Spotify” model, a CoP can be organized as a guild.
Centers of Excellence (CoE)
On the other hand, a Center of Excellence establishes a set of organized practices or standards that support and align teams. Generally, a smaller group of leaders are the ones who establish and enforce these parameters. This form of organizational learning stems from a belief that excellence can be achieved by applying the same behaviors and practices across teams – think a best practices resource. A CoE will have more distinct authority over a method of how things will operate and has influence on operations. These are also more often aligned to domains where practices require more stringent alignment and controls across an organization (e.g. in tech this can be “coding standards” or in manufacturing this can be “safety standards”).
So, which system works best? My answer: It depends.
I know this may not be the response you were searching for, but I do believe there are pros and cons to both CoP’s and CoE’s. When it comes down to it, I believe the decision relies on two factors: culture and need for consistent control.
If your interest area is willing to be inspired by many points of view, then a community of practice is best. Like a guild, it’s an organization designed to enhance our craftsmanship in the work that we do. However, if the interest area is needed to establish parameters on how things are done across the organization or your organization is traditionally more regimented in mindset, has the organizational support and operational budget, then a center of excellence may be a better fit.
Can both coexist? Absolutely.
Imagine that an Agile CoE can help establish broad standards on how we establish Agile practices at different altitudes (team, program, enterprise levels) for the purpose of alignment and coordination. At the same time, an Agile CoP can be used to bring people together across domains so that they can discover, discuss, debate, and learn from practices from across the enterprise. Keeping the CoP can help bring in others who may be interested in Agile irrespective of where they generally work in the organization.
If there is a debate on whether your organization needs one over the other, I recommend to explore both for the sake of balancing the needs of operational coordination along with the needs of operational inspiration.
If you have any questions or need guidance on how to further develop your organization’s Agile practice, our team is ready to help! Hyperdrive Agile offers comprehensive Agile training and consulting services for organizations of every scale.
APAC Initiatives Lead Agency Trading Technology, ????????????????????????????????????????????????
3 年Thanks for this great summary of the differences between CoP and CoE! In my mind, they are really complementary with CoEs acting as workgroups with a focus on alignment beyond best practice, for instance, use of a preferred tool. CoP have a more fundamental role in gathering energy and passion in a more open and grassroots fashion. Reproducing here extracts from an article. Becoming agile takes many forms, particularly in large organisations; one size does not fit all. The need to nurture the agile mindset cuts across all initiatives and joining a Community of Practice is an excellent way to address that need across the organisation. Many directions are open such as building an online community, publishing articles or sharing the experience of successful teams and leaders.? Organizing events will help along the way. Extending the community beyond the organization is critical for learning. a CoP is a unique way to gather energy and engagement, identify and support your agility champions and innovators, providing a space for learning and experimenting at the grassroots. Full text at https://lnkd.in/gpBAmhE
Product Transformation | Product Coaching, Product Management, Brokerage Modernization, Platform Re-Engineering, Scaled Agile Program Management
4 年Love this
Agile Enthusiast! Trainer & Coach for All - Enterprise, Executive, Management, Teams | CEO of Wright Path Corp.
4 年Stacy, thanks for the thoughtful illumination. I'm "striving" for CoP in the near-term with my clients, yet hoping for CoE in their future. Always optimistic!
Immediate Joiner/ Digital Transformation Specialist @ KPMG India | Lean Six Sigma Black Belt
4 年Wow !!!
Partnering with executives and organizations to build, motivate, and scale happy teams | Founder of Agile by Design Consulting Firm
4 年Good post, I make a similar distinction in my book on Agile Organizational Design, but use the term Enabler as opposed to COE, along with some subtle distinctions so that the Enabler/COE doesn't devolve into command and control... https://www.dhirubhai.net/pulse/team-collaboration-patterns-part-5-communities-jeff-anderson/?lipi=urn%3Ali%3Apage%3Ad_flagship3_profile_view_base_post_details%3BSgZOie5%2FRE6FvEZKEN7w4g%3D%3D https://www.dhirubhai.net/pulse/team-collaboration-patterns-part-1-enabler-jeff-anderson/?lipi=urn%3Ali%3Apage%3Ad_flagship3_profile_view_base_post_details%3BSgZOie5%2FRE6FvEZKEN7w4g%3D%3D