Outcomes

Cell based Structures for Security

View the original Working Session content
 

Outcomes/Deliverables

The session looked at how security functions can take advantage of Cell Based Structures to be more responsive to business needs. The session also focussed on the application of points of doctrine, and the division of teams into Pioneers, Settlers, and Town Planners as an efficient way to meet business needs that improves on the Squad model.

Synopsis and Takeaways

  • All maps are imperfect, but this doesn’t mean they can’t be useful.
  • Maps are a means of learning, and they are a common language
  • Different people can look at the same map and use it to challenge others’ assumptions
  • Sharing maps also allows for the discovery of duplications
    • The example was given of a spend control group that receives maps for proposals from all sectors of a business. Sharing such maps with a central point facilitates the identification of duplication of efforts
  • Maps give better guidance for planning and investment
  • Maps are a much faster way to analyse scenarios than wading through a written report
  • Maps facilitate the identification of patterns
  • Patterns that are universally useful become Doctrine

Points of Doctrine

  • Understand the user need
  • Use appropriate methods
  • Start small (use cells) and understand the details
    • Break large problems into small doable tasks
    • Use small teams
    • Build metrics so they know what to deliver
    • Design the organisation for constant evolution
  • Doctrine is associated with adaptability

Pioneers, Settlers, and Town Planners

  • The attitude and culture of different teams within a business are very different
  • Teams can be created as groups of pioneers, settlers, and town planners, according to attitude as much as aptitude
  • A critical part of this system is that to evolve, there must be a system of theft from the pioneer group by the settlers, and from the settlers by the town planners, so that the cycle of creation (pioneer), execution (settler), and industrialisation (town planner) doesn’t succumb to inertia.
  • As on a Wardley map, the team should move from left to right, from genesis to industrialisation
  • Allow your teams to self-select
  • Create your teams around the objective
  • Keep people in multiple teams but keep the multiple teams in the same area, i.e. in settler/pioneer/town planner groups
  • If the team grows too big, break it down

Hiring Pioneers/Settlers/Town Planners

  • Knowing the numbers of each type in your staff allows for better hiring decisions
  • Hiring for attitude can be as important as aptitude, and can improve attrition rates
  • Companies should hire for attitude AND aptitude

Weak Signals

  • Can be useful for anticipating next moves
  • When I want to attack a space, is there a weak signal I can exploit?

References

https://open-security-summit.org/tracks/maps-and-graphs/working-sessions/cell-based-structures-for-security/

Additional/External References

Session organiser(s)

Tony Richards Tony Richards , Simon Wardley Simon Wardley

Participants

Francois Raynaud Francois Raynaud , Fraser Scott Fraser Scott , Ian Taylor Ian Taylor , Luis Saiz Luis Saiz , Mario Platt Mario Platt , Naushad Saboor Naushad Saboor , Phil Huggins Phil Huggins , Phil Parker Phil Parker , Sven Schleier Sven Schleier , Thomas Franceschini Thomas Franceschini , Tony Richards Tony Richards , Wayne Moore Wayne Moore Barbara Schachner Barbara Schachner

Attached materials: