liveBook · Manning

Community of practice

As explained in Architecture Modernization: Socio-technical alignment of software, strategy, and structure

A community of practice is a group of people with shared skills, interests, or concerns who meet regularly to improve their knowledge and practice in a focused area.

A community of practice is a group with shared skills, interests, or concerns that meets regularly to improve knowledge and practice in a focused area. It supports continuous learning and upskilling when learning is treated as part of normal working time rather than a one-off intervention. section 17.3.1 section 17.0

Create the conditions that help a community of practice remain useful:

  • Meet regularly so members can sustain participation and improve over time. section 17.3.1
  • Provide community leadership that gives the group direction and support. section 17.3.1
  • Create a safe-to-learn environment where members can raise concerns and seek advice. section 17.3.1
  • Secure organizational support, including sufficient time to organize and attend. section 17.3.1

Supporting a product-centric transition

An organization formed a community of practice for heads of product and platform during its move from project-centric to product-centric work. The group met for an hour every two weeks, allowing leaders to raise transition problems and receive advice from peers and external experts. Early discussions exposed how leaders still applied project habits, including managing team capacity through a day-by-day spreadsheet. section 15.1.4

Use the group to connect new practices with real work, surface recurring organizational problems, and reinforce change after a modernization effort ends. Treat participation as supported work, because overloaded teams may otherwise return to older habits. section 15.1.4 section 17.5

How Architecture Modernization: Socio-technical alignment of software, strategy, and structure covers it

How deep it goes
Defines the practice, identifies four success conditions, and demonstrates an organizational transition, but does not prescribe a detailed operating model.
Examples
Uses a product-and-platform leadership group, fortnightly advice sessions, external experts, and a team-capacity spreadsheet as teaching examples.
What it assumes
Starts from a plain definition and assumes organizational willingness to provide time, leadership, psychological safety, and support.
What you can do after
Apply it to create a recurring peer-learning forum that supports new practices and exposes persistent transition problems.
How it connects
Connects continuous learning, upskilling, architecture modernization, organizational change, and product-centric approaches.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Architecture Modernization: Socio-technical alignment of software, strategy, and structure. The section links point to the parts of the book it draws on.