tells my advisor
the story under the squares
Orders just came through.
Mapped the way I'd map it with a team: chalked on the ground, plotted on the grid, worked out in sticky notes.
an illustrative story.A composite student, not any one university or office. The pattern repeats wherever support is split across offices.
Learnerwhat they do
tells financial aid
tells the registrar
tells the help desk
says it once
line of interaction
Peoplefrontstage
advisor writes a new note
aid office asks for the orders again
"start a withdrawal form"
"have you asked your advisor?"
a guide who already knows, by name
line of visibility
Product + processbackstage
note lives in one inbox
a PDF upload, no shared record
another form, another login
back to square one
one record that travels
checklist done behind the scenes
under the dust: the People and Product + process lanes of the blueprint
Four doors, one story
Orders in one hand, an unfinished course in the other. They tell their advisor. Then financial aid. Then the registrar. Then the help desk. Four offices, four forms, four times saying the hardest sentence of their week.
What each retelling costs
Time they don't have. A little more of the belief that they'll come back and finish. That's the dropped ball: not a bad person or a bad tool, but a handoff nobody owned. The student became the middleware, carrying context between systems that should carry it for them.
One conversation, carried
Now they say it once, to someone who already knows them. The offices move behind the scenes, and the checklist is done before they ask. What comes back sounds human: thank you for serving. You're not doing this alone.
4 offices × 1 story = 4 retellings1 guide + 1 record = 1 tellingshow your work: the difference is everything that happens behind the line of visibility.
how might we… (dot-voted)
- how might welet a student say it once, and only once?
- how might wemake the handoff the system's job, not the student's?
- how might wesound human at the hardest moment of their week?
The learner carries the goal. We carry the context.
so here's the question I bring to every team ↓