Example
How to finish a graduate thesis without losing the last month to scattered notes
Elise does not need more research ideas. She needs to see which chapters are blocked on advisor notes, which figures still need sources, and which cuts she is postponing because they feel like losing the thesis.
Submit a complete, formatted thesis by the portal date without hiding unfinished figures inside chapters marked done
Submission date, degree requirement, and the quality line Elise will not fake
Keep the portal date and the rule that almost-done chapters are not done
Keep the remaining days visible beside every scope option
Keep the committee date from disappearing inside the final portal countdown
Each chapter or major section as its own Card
Compare cut, appendix, and keep-and-narrow options against remaining days
Show the actual state of the section being cut, moved, or kept
Keep an ordinary completed chapter beside the still-open case-study scope
Keep the other live chapter visible so scope is compared against the whole remaining month
Figures, tables, citations, and files that still have to be true
Keep the missing caption and citation visible instead of buried in a chapter file
Advisor and committee notes to apply, plus questions Elise still owns
Hold the advisor’s shortening request with the current paragraph, not as a vague memory
Preserve margin, heading, and citation-style comments as work, not as rereading
Hold the unsent request Elise would need to make if she keeps the case study in the body
Formatting, permissions, and portal steps
Separate PDF export, naming, and confirmation from the writing itself
Elise is an explicitly fictional portrait, not a customer or testimonial.
The Thesis finish line Board gives one mission a visible field; the Decide the third case study 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 Thesis finish line needs an operating picture
Elise is a fictional 27-year-old master’s student in environmental policy in Edmonton, Alberta. Elise has a complete draft and a committee date. Feedback lives in three email threads, comments in a shared document, and a notebook of cuts she is afraid to make. The submission portal date is real; the current chapter order is not.
Advisor comments arrived as a long email. Committee notes are in the document. Formatting rules are a PDF she has not opened since last term.
A chapter that is “almost done” still contains two figures without captions and a methods paragraph the advisor asked her to shorten. Almost is occupying the same rank as actually ready.
In You.one's Superboard view, Elise can give “Submit a complete, formatted thesis by the portal date without hiding unfinished figures inside chapters marked done” a Board of its own. That Board connects requirements, practice or work evidence, deadlines, and accountable human judgment; opening “Decide the third case study” creates a Room for its evidence, discussion, state, and decision.
The last month is a sequence, not a feeling of almost done
The mission is specific: Submit a complete, formatted thesis by the portal date without hiding unfinished figures inside chapters marked done.
The consequential choice is not something a board or an AI should quietly make: Whether to cut the third case study, keep it as an appendix, or keep it in the body and ask the advisor for a narrower revision window.
You.one can keep the work, several kinds of evidence, and “Decide the third case study” decision visible through its Superboard view. The Owner boundary stays explicit: Elise chooses the case-study scope, writes the revision, and owns every conversation with her advisor and committee.
Available today
Thesis finish line: one Board shape to adapt
The Thesis finish line Board gives this mission one durable operating picture. Elise 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, multiple kinds of evidence, and decisions. A Waiting List would be premature until a named request or outside condition is actually in motion. That separation makes the current choice, evidence, and next move easier to scan.
| List | What belongs here |
|---|---|
| Mission | Submission date, degree requirement, and the quality line Elise will not fake |
| Chapters | Each chapter or major section as its own Card |
| Evidence | Figures, tables, citations, and files that still have to be true |
| Feedback and asks | Advisor and committee notes to apply, plus questions Elise still owns |
| Production | Formatting, permissions, and portal steps |
Available today
The Cards make the operating picture concrete
These Card titles come directly from Elise's situation: “Decide the third case study” is the live choice, while “Methods chapter cuts” and “Committee formatting notes” hold different facts that can change it. The point is recognition, not a perfect taxonomy.
| Card | List | Job |
|---|---|---|
| Submit a thesis that is actually finished | Mission | Keep the portal date and the rule that almost-done chapters are not done |
| Decide the third case study | Chapters | Compare cut, appendix, and keep-and-narrow options against remaining days |
| Methods chapter cuts | Feedback and asks | Hold the advisor’s shortening request with the current paragraph, not as a vague memory |
| Figure 4 caption and source | Evidence | Keep the missing caption and citation visible instead of buried in a chapter file |
| Committee formatting notes | Feedback and asks | Preserve margin, heading, and citation-style comments as work, not as rereading |
| Portal upload checklist | Production | Separate PDF export, naming, and confirmation from the writing itself |
| Advisor request: narrower revision window | Feedback and asks | Hold the unsent request Elise would need to make if she keeps the case study in the body |
| Portal deadline: 24 days left | Mission | Keep the remaining days visible beside every scope option |
| Committee review: 18 days left | Mission | Keep the committee date from disappearing inside the final portal countdown |
| Third case study: full draft, two figures unfinished | Chapters | Show the actual state of the section being cut, moved, or kept |
| Literature review: revised | Chapters | Keep an ordinary completed chapter beside the still-open case-study scope |
| Discussion chapter: advisor comments open | Chapters | Keep the other live chapter visible so scope is compared against the whole remaining month |
Available today
Available today: Decide the third case study becomes a Room
Opening the Card gives the visible item durable depth. Stage can hold Case-study options brief: Place “Portal deadline: 24 days left,” “Committee review: 18 days left,” “Third case study: full draft, two figures unfinished,” “Discussion chapter: advisor comments open,” the unsent “Advisor request: narrower revision window,” and the cut / appendix / keep-in-body options on one page. Chat keeps the request and response beside that artifact instead of in a detached thread. Pulse can show “Open decision: Elise will choose the case-study scope.” Activity can preserve this attributed receipt: “Ava compared the options in Card Chat using the Case-study options brief and this Card Room's visible notes and left “Decide the third case study” with Elise.”
A useful Card Chat request would be: “Using only “Portal deadline: 24 days left,” “Committee review: 18 days left,” “Third case study: full draft, two figures unfinished,” “Discussion chapter: advisor comments open,” and the unsent “Advisor request: narrower revision window,” compare cutting the third case study, moving it to an appendix, and keeping it in the body while sending the narrower-window request. Do not rewrite the chapter 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.
Elise's call remains explicit: Elise chooses the case-study scope, writes the revision, and owns every conversation with her advisor and committee.
| Surface | Job in this example |
|---|---|
| Stage | Case-study options brief: Place “Portal deadline: 24 days left,” “Committee review: 18 days left,” “Third case study: full draft, two figures unfinished,” “Discussion chapter: advisor comments open,” the unsent “Advisor request: narrower revision window,” and the cut / appendix / keep-in-body options on one page |
| Chat | Keep Elise's request and Ava's attributed response with the work |
| Pulse | Open decision: Elise will choose the case-study scope |
| Activity | Ava compared the options in Card Chat using the Case-study options brief and this Card Room's visible notes and left “Decide the third case study” with Elise |
What to ask Ava—and what not to assume
These requests use the visible supported context inside the “Decide the third case study” Card Room. They do not imply that current Ava automatically surveys the whole Board or follows up on her own; Elise 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 Elise, watch other Lists, or act outside this Card Room.
Elise owns the scholarly argument, cuts, citations, and committee conversations. Ava does not write the thesis, invent sources, or submit the portal package.
A finish-line picture: the third case study has a chosen fate, unfinished figures are not hiding inside “done,” and the portal steps are their own work.
- Request idea: using only “Portal deadline: 24 days left,” “Committee review: 18 days left,” “Third case study: full draft, two figures unfinished,” “Discussion chapter: advisor comments open,” and the unsent “Advisor request: narrower revision window,” compare cutting the third case study, moving it to an appendix, and keeping it in the body while sending the narrower-window request. Do not rewrite the chapter or choose for me.
- Request idea: use only the Case-study options 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 long shared document plus email may still be enough
A long shared document plus email is enough when there is one reader, one draft, and one round of comments.
It starts to break when chapters, figures, formatting, and committee notes all claim to be the next hour.
The Thesis finish line Board earns its place only when the familiar tool—a long shared document plus email—can no longer keep the reason, Case-study options brief, conversation, current state, decision, and history connected.
A starter recipe to adapt, not obey
Elise should rename every List or Card that feels artificial. This recipe succeeds when “Decide the third case study” becomes easier to decide and fewer open loops depend on memory—not when the Board looks tidy.
| Step | Action |
|---|---|
| 1. Put both dates on Mission | Record the submission-portal date and committee date before sequencing the month |
| 2. Split the document | Make one Card per chapter or major remaining section |
| 3. Surface evidence gaps | Create Cards for missing figures, captions, and citations |
| 4. Capture feedback as work | Turn advisor and committee notes into Cards, not rereading loops |
| 5. Isolate production | Keep formatting and portal steps off the writing lists |
| 6. Decide the third case study | Open a Room for the scope choice that unblocks the last month |
Direction
Direction, not a current promise
Later, Ava may help this Board notice when a chapter marked ready still has open evidence Cards, still leaving every scholarly call with Elise.
A future unified You.one experience could carry relevant context from “Decide the third case study” 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
- Elise is fictional and is not a customer, testimonial, research participant, or disguised real person.
- This is not academic editing, originality checking, or a claim Superboard accessed a thesis portal.
- It does not show Ava writing chapters, contacting a committee, or guaranteeing a defense result.
- It is not a measured completion rate or a recommended thesis structure.