Concept — Empathy, Personas & the Emotional Story

← tree index · overview

Visual companion: the interactive Empathy maps & personas page (personas, empathy-map quadrants, and the cross-section event diagram). This doc is the textual source of truth behind it.

The platform’s job is behavioral change, and behavior rides on emotion. A teacher applies a strategy on Tuesday not because a dashboard told them to, but because the moment felt safe, respected, and worth it. So empathy is the spec, not the garnish: every nudge, screen, and aggregate either honors what a person feels — or quietly erodes it.

This concept names who we serve, what they feel across the Applied Learning Cycle, where those feelings cross over between people, and how each one is honored by the intervention layer.

The five lenses

Three sit inside the product (they have screens); two are the relationship around it. Full scenes, inner monologues, emotion arcs, and trust-makers/breakers live on the visual page — this is the index.

Persona	Role	Core fear	Core hope	Defining line
Maya Okonkwo	Participant · 4th-grade teacher	Being judged; no time; one more dead-end PD	One strategy that works Monday; being respected	“I don’t need to be fixed — I need ten minutes and one idea I can use on Monday.”
Darnell Price	Learning Administrator · school coach	Being cast as the compliance cop	Champion his teachers with morale-safe evidence	“I’m not checking up on you. I’m checking in. I don’t know how to make the app say that.”
Sofia Reyes	Instructional Strategist · Inspired	The work evaporating after she leaves the room	See who’s stuck (as patterns) and reach back with care	“I can read a room in ten minutes — but I’ve no idea who’s quietly drowning by Wednesday.”
Karen Whitfield	School leader · principal	Initiative overload; wrecking morale	Evidence she can hold up; staff who aren’t drowning	“I’ll fight for anything that helps my teachers — and I’ll kill anything that just watches them.”
Dr. James Holloway	District · curriculum director	Unjustifiable spend; equity gaps across schools	One true number; cross-school proof of change	“I can count who showed up. I can’t count who changed.”

A moment with each (the scenes in one line)

Maya caps her cold coffee at 7:52 a.m. — twenty-seven kids on the rug, six hours ahead — and just wants to be worth it.
Darnell carries warm laminated cards past Room 114 and takes his hand off the doorframe, so the strategy doesn’t die of being watched.
Sofia drafts “Just wanted to say” to a tired teacher from I-35, then deletes it — she won’t be one more thing buzzing in a tired pocket.
Karen counts the eleven minutes Denise sits in her Corolla in the dark lot, and steps back from the window so she won’t be seen watching.
Dr. Holloway hears himself tell the board they’re seeing “encouraging signs” — and feels the word signs land hollow.

Empathy maps (the three in-product users)

Full Says / Thinks / Does / Feels / Pains / Gains live on the visual page. The load-bearing summary:

Maya (Teacher): feels time-pressured and a little exposed; pain = fear of evaluation + initiative fatigue + discouragement after a flop; gain = one strategy that works, quiet momentum she can see, feeling respected not surveilled.
Darnell (LA): feels caught between staff and leadership; pain = being the enforcer, no visibility, proving ROI without numbers; gain = patterns not a watchlist, a way to champion.
Sofia (IS): feels invested but helpless post-workshop; pain = the work evaporating, nagging tired teachers, flying blind; gain = cohort weather she can act on, care at scale.

The empathy cross-section (feeling × cycle × user)

The most useful artifact: read the cross-role view, but for emotion. Columns are the six phases; rows are the user sets; each cell is the feeling + the message that honors it. The Apply phase (the 48-hour gate) is the emotional crux — where care either lands or curdles into surveillance. See the full grid on the visual page. The crux cells:

Teacher @ Apply: busy + guilty → “When you get a quiet minute this week, try it once. Not this week? That’s okay.” (care language + self-snooze, never a countdown).
LA @ Apply: doesn’t want to nag → a gentle whole-group reinforcement, no names.
IS @ Apply: “did it land?” → cohort weather + one suggested support action, never a watchlist.
School/District @ Apply: “is it changing classrooms?” → aggregate time-to-apply, never individual scores.

Crossover threads (where empathy overlaps)

The columns of shared feeling matter more than any single cell. Four threads run across multiple users at once — and each has one message that honors everyone on it:

“Will this stick?” — Strategist + LA + Principal + District. → Narrated progress + time-to-apply momentum shows the cycle moving without grading any teacher.
“Don’t make us feel judged.” — Teacher + LA + Principal. → “This is support, not a scorecard.” Patterns-not-individuals; reveal only behind a logged, reasoned action.
“Respect my time.” — Teacher + LA + Strategist. → Every ask is time-boxed and says so (“usually about 2 minutes,” “under 5 minutes”).
“Prove it mattered.” — LA + Principal + District (vs. the teacher who just wants help). → The same application data that gives the teacher private momentum becomes the aggregate evidence leadership needs. One signal, two audiences, zero extra teacher burden.

Thread 4 is the key product insight: the teacher-facing and leadership-facing needs share one source (the ApplicationEvent), so honoring the teacher and satisfying the district are the same build, not competing ones.

Empathy → mechanism (how it shows up in the product)

The emotion decides the tone; the intervention layer decides the trigger. See the empathy section there and the mapping table on the visual page. Examples: fear of judgment → no scores + cohort weather; guilt → care nudge + self-snooze; discouragement → the attempted-but-failed branch routes to support, not a failing grade.

Intervention layer (now carries an Empathy-in-the-loop section)
Applied Learning Cycle · Roles and goals
Dashboard designs · Business loop (the LA-first renewal honors Thread 4)
Visual: design/empathy/empathy-maps.html