Example
How a nursing student can organize a clinical rotation week
Jordan's problem is not a lack of effort. It is that Arrive at the first clinical week with onboarding, skills evidence, and transport settled, without hiding the exam that still has to happen has outgrown scattered reminders, tabs, and memory. This fictional playbook shows a concrete Board, the Cards inside it, one consequential Room, and the line Ava does not cross.
This fictional example was created with AI assistance from a structured editorial brief and reviewed by the You.one Editorial Team for usefulness, distinctness, and product truth.
Jordan is an explicitly fictional portrait, not a customer or testimonial.
The Clinical week one Board gives one mission a visible field; the Choose the exam versus Wednesday swap Room keeps its evidence, conversation, state, and decision together.
Current Superboard provides the durable structure and explicit, bounded Ava paths described here; broader proactive or external work is not a current promise.
Jordan's pressure is ordinary—and still heavy
Jordan is a fictional 24-year-old nursing student entering a medical-surgical clinical rotation in Portland, Oregon. Jordan’s rotation starts Monday. Skills checklists, hospital onboarding modules, a parking permit, and a preceptor’s shift pattern arrived in four different emails. The first week also includes an exam they have not scheduled study time around.
Jordan is prepared in the sense that the skills lab went well. They are not prepared in the sense that badge pickup, a 6:30 a.m. start, and a medication-calculation quiz all still live in separate inboxes.
The hospital portal, the school learning system, and a printed skills booklet each think they are the plan.
A preceptor note says “ask if you need a different day.” That sentence is not a schedule, and treating it as flexibility has already cost one unanswered email.
The rotation is a week of proof, not a vibe of being ready
The mission is specific: Arrive at the first clinical week with onboarding, skills evidence, and transport settled, without hiding the exam that still has to happen
The consequential choice is not something a board or an AI should quietly make: Whether to ask the preceptor to swap Wednesday, take the exam Tuesday night after clinical, or use the published makeup date
That distinction matters. Superboard can make the work, evidence, waiting, and decision visible. Jordan still owns the purpose, tradeoff, and final call.
Available today
Clinical week one: one Board shape to adapt
A useful Board gives this mission one durable operating picture. Jordan does not have to convert life into project-management jargon or decide the perfect taxonomy first. Lists separate kinds of attention; Cards keep each meaningful item visible and movable.
The Cards are deliberately mixed. Some are tasks, some are decisions, some hold a person or promise, and some are reference points. Current Superboard supports that flexibility without flattening the mission into one long to-do list.
| List | What belongs here |
|---|---|
| Mission | What “ready for Monday” actually includes |
| Onboarding | Badges, modules, forms, and site rules |
| Skills and study | Checklists, quizzes, and the school exam |
| People and shifts | Preceptor, instructor, and start times |
| Waiting | Replies, badge desk hours, and parking confirmation |
Available today
The Cards make the operating picture concrete
A Board becomes useful when the Card titles sound like the actual situation. These are not generic placeholders; they show what Jordan would need to see to run this mission without carrying every open loop in memory.
| Card | List | Job |
|---|---|---|
| Be ready for Monday without dropping the exam | Mission | Keep clinical start and the school exam on the same operating picture |
| Choose the exam versus Wednesday swap | Skills and study | Compare swap, Tuesday-night study, and makeup-date options against shift start times |
| Badge and parking pickup | Onboarding | Hold desk hours and required ID so Monday morning is not an errand surprise |
| Hospital modules remaining | Onboarding | List unfinished required modules as work, not as a portal tab |
| Preceptor Wednesday question | Waiting | Keep the unsent or unanswered swap request from pretending to be a plan |
| Medication-calculation practice set | Skills and study | Attach the practice set and the quiz date to the rotation week |
Available today
Available today: Choose the exam versus Wednesday swap becomes a Room
Opening the Card gives the visible item durable depth. Stage can hold Week-one schedule brief: Place clinical start times, exam window, makeup policy, and the swap question on one page. Chat keeps the request and response beside that artifact instead of in a detached thread. Pulse can show Waiting for Jordan to choose how the exam fits the first clinical week. Activity preserves the attributable Card record supported by the current product.
A useful Card Chat request would be: “Using only this Board, compare swapping Wednesday, studying Tuesday night, and using the makeup date. Do not contact the preceptor or choose for me.” When live AI is configured, current Ava can respond to an explicit Card mention using supported context and can make limited reversible product changes. She does not deeply reason over the whole Board by default, and she does not gain authority over the decision merely because the context is organized.
Jordan's call remains explicit: Jordan chooses the schedule, writes any message to the preceptor or instructor, and owns their own clinical and exam work
| Surface | Job in this example |
|---|---|
| Stage | Week-one schedule brief: Place clinical start times, exam window, makeup policy, and the swap question on one page |
| Chat | Keep Jordan's request and Ava's attributed response with the work |
| Pulse | Waiting for Jordan to choose how the exam fits the first clinical week |
| Activity | Preserve attributed Card changes and the supported record around the request |
What to ask Ava—and what not to assume
These are useful requests to adapt, not claims that current Ava automatically surveys the whole Board, prepares every comparison, or follows up on her own. The relevant facts must be present in supported Board/Card context, and the human still checks the result.
Jordan owns clinical judgment, patient safety, schoolwork, and every message to preceptor or instructor. Ava does not give clinical advice, complete modules, or speak to the site.
The modest outcome is not that Ava lives Jordan's life. The modest outcome is a first week Jordan can scan: onboarding is listed, the exam has a chosen place, and a maybe-swap is no longer the hidden plan.
- Request idea: summarize remaining onboarding, skills, and waiting items already on the Board
- Request idea: compare the three exam-week options using only stated times and policies Jordan has captured
- Request idea: help separate Waiting replies from work Jordan can actually do tonight
School email plus a printed skills booklet may still be enough
School email plus a printed skills booklet is enough when onboarding is already done and the week is simple
It starts to break when hospital modules, badge pickup, a preceptor, and an exam all claim to be Monday
Superboard earns a place only when the responsibility needs a durable picture around the list: the reason, artifact, conversation, current state, decision, and history.
A starter recipe to adapt, not obey
Use the names that already make sense in Jordan's world. The recipe is successful when the Board reduces remembering and exposes the real decision—not when every Card is perfectly categorized.
| Step | Action |
|---|---|
| 1. Define ready | Write what Monday actually requires: badge, modules, transport, skills |
| 2. Capture onboarding | One Card per unfinished form, module, or pickup |
| 3. Place people and hours | Add preceptor, start times, and instructor contacts as Cards |
| 4. Park unanswered asks | Move the Wednesday question to Waiting until it is sent and answered |
| 5. Decide the exam collision | Open a Room and record how the quiz fits the week |
Direction
Direction, not a current promise
Later, Ava may help this Board notice when an exam Card has no attached study block beside a clinical start time, still leaving every request with Jordan.
The unified You.one and Superboard runtime, cross-product personalized Memory Spine, broad proactive coordination, realtime shared editing, and general external execution are not available today. Future actions would still require the applicable capability, connection, grant, and human authority.
What this realistic example does not claim
- Jordan is fictional and is not a customer, testimonial, research participant, or disguised real person.
- This is not clinical, medical, or licensing advice, and it is not a hospital onboarding system.
- It does not show Ava contacting a preceptor, completing modules, or making a patient-care judgment.
- It is not a claim about any school’s rotation policy or a measured student result.