liveBook · Manning

Emic perspective

As explained in Collaborative Software Design: How to facilitate domain modeling decisions

An emic perspective is an insider's account of a culture based on the lived experience of its members.

An emic perspective is the lived experience of someone within a culture. It is gathered through participatory observation: spending time inside everyday practices, noticing shared symbols, and listening to how people experience group interactions. This view matters because formal authority alone does not reveal who influences a collaborative session. section 6.3.1

Use the emic perspective before judging a group from outside. Collect anecdotes and reactions, then contrast them with an etic perspective: an outsider’s conclusion about why those experiences occur. Together, these views make implicit ranking and power dynamics easier to examine without treating first impressions as facts. section 6.3.1

Hesitation in an EventStorming session

During Big Picture EventStorming, someone may fear writing the wrong domain event and wait for another participant to add an example first. That hesitation is an emic account of the session. Recording such stories can reveal how safety, influence, or rank shape participation. section 6.3.1

Figure 6.3 An example map of how to model the organization and capture symbols, anecdotes, and our own thoughts. In reality, this would be a lot bigger, so we like to use online tools where we can easily enlarge the area and collaborate on capturing our observations.

Use an observation map to capture organizational symbols, anecdotes, and reflections collaboratively, creating material for examining lived experience and implicit influence. section 6.3.1

How Collaborative Software Design: How to facilitate domain modeling decisions covers it

How deep it goes
Defines the insider view and links it to participatory observation, symbols, stories, and outsider judgment.
Examples
Uses a participant waiting to post an event and observations of routines, meals, and informal activities.
What it assumes
Assumes a collaborative organizational setting while introducing participatory observation from zero.
What you can do after
Evaluate/understand implicit ranking by collecting lived-experience stories before forming judgments about group influence.
How it connects
Connects participatory observation with etic perspective, organizational culture, power dynamics, and Big Picture EventStorming.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Collaborative Software Design: How to facilitate domain modeling decisions. The section links point to the parts of the book it draws on.