MyYOU

Care lives in fragments. MyYOU makes it one journey visible to staff and youth.

A coordination layer inside the Microsoft 365 they already run, visible to staff and, for the first time, to the youth themselves.

Reframed
Comms problem → Youth invisibility
0 AI
In Youth experience
1/10th $
Not a CRM
1Problem

What we heard

No standardized communication

“I told you Bobby was moving in,” said in a hallway. It never became a task, and three days later he still had no key card.

“I told you Bobbywas moving in.”No task3 days later, still no key card

What we heard

Funder-locked systems

“Funders give us money, they tell us what to do.” Care is split across HIFIS, Elrez and YWHO, and none of them talk.

HIFISElrezYWHO+ MORE · ALL FUNDER-LOCKED

What we saw

Youth can't see their own journey

Housing, goals, progress, people. Every worker sees their slice. The youth see none of it.

HousingGoalsProgressPeopleTheir journey. They can't see it.
2Solution

A coordination layer, built where they already work.

What MyYOU is, and why we built it instead of buying a CRM.

The solution

Meet MyYOU, one journey everyone can see

A thin coordination layer inside the Microsoft 365 Y.O.U. already runs. It captures care where staff already talk, and lets the youth read their own journey for the first time.

Capture care where staff talk. Show the youth one journey.

Build vs buy

A coordination layer, not another database

A CRM costs $80–200K a year and makes staff type everything twice. Building inside Y.O.U.'s own tenant lands it near $20K.

Type twice$200K / yrDouble entryMyYOU~$20K / yrCRM$80–200K / yr

A tenth of the cost. No second system to feed.

3How it works

Two surfaces, one record, and a line AI never crosses.

Staff capture care where they already work. The youth read their own journey. And the AI stays on the staff side, on purpose.

The surfaces

A phone-first portal, React on Azure with text updates over SMS. Where the youth finally read their own journey.

The AI line

AI on the staff side. Never on the youth's.

STAFF SIDEYOUTH SIDEAI runs hereon the note staff wrotethe youthAI never reachesNEVER CROSSES

These are kids who've spent their lives inside other people's systems. AI takes the paperwork off staff, but the journey the youth see stays fully human.

4AI-enabled redesign

The same care: lost by hand, captured with MyYOU.

AI turns a hallway sentence into structured tasks, a worker signs off, and a kid like Bobby stops falling through the cracks.

By handWith MyYOU
Capture
in passing
Care gets mentioned in a hallway
in flow
Worker types the note in Teams
Structure
no record
It never becomes a task
✦ AI does thisseconds
AI structures it into tasks
Approve
3 days
Three days pass, no one owns it
Human signs offhuman
Worker approves before anything moves
Cascade
✕ Where it broketoo late
Bobby still has no key card
same day
The cascade runs, the youth sees it
5Success metrics

The numbers I'd track in production to know it's working.

Care actions captured

Mentions that become tasks, not hallway air.

The key-card metric

Median time from mention to task to done.

Youth portal weekly actives

Are youth reading their own journey?

Staff approval rate

How often the AI's extraction stands as-is.

6Learnings

What I'm taking with me.

01

The reframe was the whole job

We were handed a communication problem. The work was realizing the youth couldn't see their own care. Naming the right gap mattered more than any feature.

02

The hardest AI call was where to keep it out

The youth portal has zero AI on purpose. Deciding where AI shouldn't go was a more serious product call than deciding where it should.

03

Design for the person who isn't in the room

The youth never sat in our interviews. Designing for someone absent changed every call, from the consent model to who the record is written for.