Designing for Resilience

Laura Maguire elicits the expertise of five software leaders and in so doing operationalizes common grounding in a tangled layered network! "Designing & Managing for Resilience" infoq

Proposition #1: For resilient organizations, think in terms of networks, not just teams.

Proposition #2: Resilient networks depend on active and ongoing grounding across different levels of the organization.

Proposition #3: Resilience depends on learning.

The engineering leader's contributions to resilience in the face of surprising events is to create the conditions for learning and adaptations to occur.

Share knowledge. Surface relevant insights. Thereby, aid real time adaptation to changing conditions.

Create opportunities for teams to work cross functionally and organically using a network-based approach that includes perspectives across multiple levels and roles.

Encourage interactions that support continuous grounding including using their position to broaden the perspectives being considered in decision-making.

Strongly emphasize learning - including blameless post mortems, experimentation and short cycle feedback loops.

Like subscription fees for vital tools, investments in resilient performance are 1) ongoing, and 2) need to be made before you need them.

There's an influential paper about common ground. Despite its name, common ground is not a geographic location you can visit. It is a state of being, a relationship between people, the essential context in all human communication, continually changing.