Wardley's Pioneers, Settlers & Town Planners

Wardley's Pioneers, Settlers & Town Planners

Pioneers explore new ideas, Settlers turn them into working products, and Town Planners make them efficient and stable. Great organizations need all three, at the right moments.

Every frontier needs explorers, builders and planners. "Pioneers, Settlers, and Town Planners", from Simon Wardley (of Wardley Map fame), applies that idea to the roles in a company or project:

  1. PioneersInnovators and risk-takers who explore new ideas and technologies. They thrive on uncertainty and go looking for what's next.

  2. SettlersThe people who take what pioneers find and make it work. They refine promising concepts and scale them up.

  3. Town PlannersStrategic thinkers who bring long-term stability and efficiency. They organize and optimize processes and line them up with the overall business strategy.

Pioneers, Settlers & Town PlannersOrg Hacking - Pioneers, Settlers, Town Planners [Wardley]

Organizations need all three to balance exploration, scaling and efficiency over an innovation's life.

Pioneers, Settlers and Town Planners is a memorable metaphor from Simon Wardley, building on labels from Robert X. Cringely's 1993 book Accidental Empires. It is a practitioner's model drawn from experience, not a research finding, and it comes with some real cautions. The main objections:

  1. It's easy to misuse as a personality testWardley describes the three as attitudes and cultures, not fixed types of people. In practice, the labels get pinned on individuals ("she's a pioneer, he's a town planner"), which can box people in and ignore how they change with context. It's the same risk that hangs over other team-typing schemes like Belbin's team roles.

  2. Splitting the organisation can backfireMatt Edgar, who calls himself a settler, warns against structuring a large organisation into pioneer, settler and town planner groups. He describes groups at Orange fighting over who owned app-store components, losing months that could have gone into learning what users needed. He likens the idea to the "bimodal IT" approach and suggests mixing the attitudes within teams instead.

  3. Hand-offs are glossed overWardley's model moves work along by a kind of "theft", with settlers taking from pioneers and town planners from settlers. That framing says little about the real coordination costs and friction of handing work between groups.

  4. The evidence is anecdotalSupport comes from historical examples, comparisons with companies like Amazon and Haier, and Wardley's own experience running a company. Wardley himself describes such structures as uncommon. There are no controlled studies showing they outperform other ways of organising.

  5. It inherits the weak spots of the mapThe model rests on the evolution axis of Wardley Maps, which critics argue is less predictable and more a matter of opinion than the word "evolution" suggests. If components don't evolve in a tidy line, the neat hand-off from one group to the next is tidier on paper than in life.

Used lightly, the model is a helpful reminder that exploring, scaling and industrialising need different mindsets, and that all three deserve respect. Used rigidly, as an org chart or a label for people, it can create the very turf wars it was meant to avoid.

Resources

Simon Wardley's "Pioneers, Settlers, and Town Planners" framework grew out of the evolution axis of his Wardley Maps, and it echoes several established ideas in innovation and organizational theory:

  1. Innovation AmbidexterityIt mirrors the classic tension between exploration and exploitation in organizations (March, 1991). Pioneers explore new territory, settlers exploit the opportunities they uncover, and town planners optimize and stabilize what works.

  2. Diffusion of InnovationsIt tracks the stages of innovation adoption described in diffusion theory (Rogers, 1962), with pioneers as the early adopters, settlers as the majority who follow, and town planners securing lasting adoption and integration.

  3. Agile and Lean PrinciplesIt fits agile and lean thinking, which stress innovation, efficient scaling and continuous improvement (Beck et al., 2001; Poppendieck & Poppendieck, 2003).

References

  • March, J. G. (1991). Exploration and Exploitation in Organizational Learning. Organization Science, 2(1), 71–87.
  • Rogers, E. M. (1962). Diffusion of Innovations. Free Press.
  • Beck, K., et al. (2001). Manifesto for Agile Software Development. Agile Alliance.
  • Poppendieck, M., & Poppendieck, T. (2003). Lean Software Development: An Agile Toolkit. Addison-Wesley.

More Resources