liveBook · Manning

Persona

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

A persona is a representative characterization of a user or participant whose goals, context, and behavior are used to explore an experience.

A persona is a representative characterization of a participant in a domain. Mapping personas surfaces their purpose, jobs to be done, responsibilities, and relationships before exploring the broader experience. section 7.2.3

Use personas to:

  • Warm up a group before EventStorming and build confidence through early domain conversations. section 7.2.3
  • List people, describe their responsibilities, and reveal terminology and demand-side or supply-side groupings. section 7.2.3
  • Represent participants with small yellow stickies, while keeping notation sparse enough to preserve engagement and clarity. section 7.1.1
  • Tell specific stories for different personas instead of hiding meaningful variation inside an overly abstract model. section 7.4.1

Real-estate domain mapping

A workshop maps the people in a real-estate domain and describes their roles and responsibilities. The group distinguishes demand-side and supply-side participants and notices that one person may be both buyer and seller. section 7.2.3

Figure 7.9 Mapping out roles and personas before kicking off an EventStorming session

Use the role-and-persona map as a visual starting point for domain conversations and EventStorming preparation. section 7.2.3

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

How deep it goes
Explains purposes, responsibilities, notation, and storytelling, but stops short of prescribing a rigid persona-development process.
Examples
Uses real-estate buyers and sellers, plus advertisers from startups and enterprises, to show overlapping roles and divergent experiences.
What it assumes
Assumes a domain workshop context and teaches participants to begin persona mapping from a blank canvas before comparing existing personas.
What you can do after
Practice mapping domain participants and telling differentiated experience stories during collaborative EventStorming.
How it connects
Connects personas with roles, jobs to be done, EventStorming, domain events, systems, hot spots, and customer segments.

Also explained in

Compare how 6 books explain persona →

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.