Example
How to keep a year of language learning visible without a streak app
Naomi does not need another daily reminder. She needs to see which skills she is actually practicing, which situations are coming, and which months are already full of work travel.
Build a year of French practice aimed at work meetings and a July family visit, without pretending an app streak is the plan
The July visit and the work-meeting situations that define enough
Keep the July family visit and standup phrases as the definition of progress
Keep the months with reduced practice capacity beside the spring decision
Weekly habits that are specific, not streak theater
Treat the group as a standing practice Card with what she wants to try each week
Keep one current listening piece attached to the week instead of an infinite saved folder
Real conversations, meetings, and visits to prepare for
Collect the actual phrases from her team’s standup rather than generic textbook dialogues
Keep the July conversations as a dated situation, not a streak
Classes, tutors, shows, and clippings actually in use
Compare twice-weekly class, Saturday-plus-June-tutor, and July-visit-as-deadline options
Ground the three spring options in the prices, Tuesday-and-Thursday class hours, and tutor availability Naomi actually captured
Class seats, tutor replies, and calendar holds
Hold the unconfirmed seat so it is not already in the plan
Naomi is an explicitly fictional portrait, not a customer or testimonial.
The French year Board gives one mission a visible field; the Choose the spring class load Room keeps its evidence, conversation, state, and decision together.
Current You.one provides the Superboard structure and explicit, bounded Ava paths described here; broader proactive or external work is not a current promise.
Why French year needs an operating picture
Naomi is a fictional 33-year-old product operations specialist returning to French after years of English-only work in Montreal, Quebec. Naomi moved back to Montreal and can handle shops, but work meetings and a summer visit with relatives still feel out of reach. She has an app streak, a Saturday conversation group, and a stack of news clippings. None of them is a year plan.
The app counts minutes. The Saturday group chats in a thread that disappears. Work meetings where she wants to contribute are not on any study list.
Relatives visit in July. If she treats every week as identical, June will arrive with the same beginner exercises and conversations she still cannot join comfortably.
In You.one's Superboard view, Naomi can give “Build a year of French practice aimed at work meetings and a July family visit, without pretending an app streak is the plan” a Board of its own. That Board connects requirements, practice or work evidence, deadlines, and accountable human judgment; opening “Choose the spring class load” creates a Room for its evidence, discussion, state, and decision.
A streak is not the same as a speaking situation
The mission is specific: Build a year of French practice aimed at work meetings and a July family visit, without pretending an app streak is the plan.
The consequential choice is not something a board or an AI should quietly make: Whether to take the twice-weekly evening class if the waitlist seat is confirmed, keep Saturdays only and add tutoring in June, or delay the class and use the July family visit as the deadline.
You.one can keep the work, evidence, live dependency, and “Choose the spring class load” decision visible through its Superboard view. The Owner boundary stays explicit: Naomi chooses the class load, spends any tuition, and shows up for her own practice.
Available today
French year: one Board shape to adapt
The French year Board gives this mission one durable operating picture. Naomi can use familiar language instead of translating the situation into project-management jargon. Its five Lists separate the kinds of attention this situation actually requires.
Its Cards deliberately distinguish actions, evidence, a live dependency, and decisions. A Waiting List is useful here only because a named request or outside condition is already in motion. That separation makes the current choice, evidence, and next move easier to scan.
| List | What belongs here |
|---|---|
| Mission | The July visit and the work-meeting situations that define enough |
| Practice | Weekly habits that are specific, not streak theater |
| Situations | Real conversations, meetings, and visits to prepare for |
| Resources | Classes, tutors, shows, and clippings actually in use |
| Waiting | Class seats, tutor replies, and calendar holds |
Available today
The Cards make the operating picture concrete
These Card titles come directly from Naomi's situation: “Choose the spring class load” is the live choice, “Saturday conversation group” holds evidence, and “Twice-weekly evening class waitlist” names something genuinely in motion outside Naomi's control. The point is recognition, not a perfect taxonomy.
| Card | List | Job |
|---|---|---|
| Be ready for July conversations | Mission | Keep the July family visit and standup phrases as the definition of progress |
| Choose the spring class load | Resources | Compare twice-weekly class, Saturday-plus-June-tutor, and July-visit-as-deadline options |
| Saturday conversation group | Practice | Treat the group as a standing practice Card with what she wants to try each week |
| Standup meeting phrases | Situations | Collect the actual phrases from her team’s standup rather than generic textbook dialogues |
| Twice-weekly evening class waitlist | Waiting | Hold the unconfirmed seat so it is not already in the plan |
| Radio-Canada clip this week | Practice | Keep one current listening piece attached to the week instead of an infinite saved folder |
| March and April work travel | Mission | Keep the months with reduced practice capacity beside the spring decision |
| July family visit | Situations | Keep the July conversations as a dated situation, not a streak |
| Class and tutor cost notes | Resources | Ground the three spring options in the prices, Tuesday-and-Thursday class hours, and tutor availability Naomi actually captured |
Available today
Available today: Choose the spring class load becomes a Room
Opening the Card gives the visible item durable depth. Stage can hold Spring practice brief: Place “March and April work travel,” “July family visit,” “Saturday conversation group,” “Class and tutor cost notes,” and “Twice-weekly evening class waitlist” beside the three options. Chat keeps the request and response beside that artifact instead of in a detached thread. Pulse can show “Open decision: Naomi will choose the spring practice load.” Activity can preserve this attributed receipt: “Ava compared the options in Card Chat using the Spring practice brief and this Card Room's visible notes and left “Choose the spring class load” with Naomi.”
A useful Card Chat request would be: “Using only the context visible in this Card Room, compare taking the twice-weekly evening class if its waitlist seat is confirmed, Saturday-plus-June-tutor, and delaying the class while using the July family visit as the deadline. Treat the class seat as waitlisted, not enrolled. Do not enroll me or choose for me.” When live AI is configured, current Ava can respond to an explicit Card mention using supported Room context and can make limited reversible changes inside this Card Room after an explicit request. She uses only supported Room context; she cannot summarize the Board, watch other Lists, or act outside this Card Room. She does not gain authority over the decision merely because the context is organized.
Naomi's call remains explicit: Naomi chooses the class load, spends any tuition, and shows up for her own practice.
| Surface | Job in this example |
|---|---|
| Stage | Spring practice brief: Place “March and April work travel,” “July family visit,” “Saturday conversation group,” “Class and tutor cost notes,” and “Twice-weekly evening class waitlist” beside the three options |
| Chat | Keep Naomi's request and Ava's attributed response with the work |
| Pulse | Open decision: Naomi will choose the spring practice load |
| Activity | Ava compared the options in Card Chat using the Spring practice brief and this Card Room's visible notes and left “Choose the spring class load” with Naomi |
What to ask Ava—and what not to assume
These requests use the visible supported context inside the “Choose the spring class load” Card Room. They do not imply that current Ava automatically surveys the whole Board or follows up on her own; Naomi must provide the relevant facts and check the result.
Current Ava can reply in this Room to an explicit Card mention using supported Room context. She cannot summarize the Board, make the choice, represent Naomi, watch other Lists, or act outside this Card Room.
Naomi owns enrollment, spending, practice, and every real conversation. Ava does not teach French, book a class, or speak for her at work.
A year with a chosen spring load: July is the mission, standup phrases have a Card, and a streak is no longer pretending to be a plan.
- Request idea: using only the context visible in this Card Room, compare taking the twice-weekly evening class if its waitlist seat is confirmed, Saturday-plus-June-tutor, and delaying the class while using the July family visit as the deadline. Treat the class seat as waitlisted, not enrolled. Do not enroll me or choose for me.
- Request idea: use only the Spring practice brief and notes the Owner has placed in this Card Room to separate facts, assumptions, and unanswered questions
- Request idea: name which visible Room note could most change the comparison; do not watch other Lists or follow up autonomously
A language-learning app streak may still be enough
A language-learning app streak is enough when the only goal is not to break a number.
It starts to break when a family visit and real meetings need situations, not minutes.
The French year Board earns its place only when the familiar tool—a language-learning app streak—can no longer keep the reason, Spring practice brief, conversation, current state, decision, and history connected.
A starter recipe to adapt, not obey
Naomi should rename every List or Card that feels artificial. This recipe succeeds when “Choose the spring class load” becomes easier to decide and fewer open loops depend on memory—not when the Board looks tidy.
| Step | Action |
|---|---|
| 1. Name the situations | Write the July visit and the work meetings that define enough |
| 2. Make practice specific | Replace streak minutes with Cards for group, listening, and phrases |
| 3. Capture resources | Add only the class, tutor, or show actually in play |
| 4. Add spring constraints | Put work-travel months and the current class or tutor costs on the Board |
| 5. Park waitlists | Keep unconfirmed seats out of the plan |
| 6. Choose the spring class load | Open a Room before paying for a class that collides with travel |
Direction
Direction, not a current promise
Later, Ava may help this Board notice when a situation Card has had no attached practice for a while, still leaving every enrollment and conversation with Naomi.
A future unified You.one experience could carry relevant context from “Choose the spring class load” across guidance and the Superboard view. Broad proactive coordination, cross-surface personalized memory, realtime shared editing, and general external execution are not available today. Any future action would still require the applicable capability, connection, grant, and human authority.
What this realistic example does not claim
- Naomi is fictional and is not a customer, testimonial, research participant, or disguised real person.
- This is not a language-learning method, fluency claim, or measured progress score.
- It does not show Ava tutoring, enrolling Naomi, or joining a work meeting.
- It is not a testimonial for any app, school, or tutor.