{ "schema_version": 1, "updated_at": "2026-09-15", "canonical_id": "brali:problem:plan-realistic-week", "slug": "plan-realistic-week", "acquisition_cluster_id": "weekly-prioritization", "title": "Plan a realistic week when everything looks important", "question": "How do I choose priorities for the week without overloading the plan?", "aliases": [ "prioritize work for the week", "plan a week without overloading it", "decide what not to do this week" ], "summary": "Protect fixed constraints, make a small number of outcomes visible, and separate controllable actions from uncertain results.", "canonical_url": "https://brali-lifeos.github.io/problems/plan-realistic-week/", "json_url": "https://brali-lifeos.github.io/problems/plan-realistic-week/index.json", "query_url": "/for-ai/query/?q=How%20do%20I%20prioritize%20my%20work%20for%20this%20week%20without%20overloading%20the%20plan%3F", "related_url": "/life-os/areas/work-money-strategy/", "topics": [ { "id": "planning-prioritization", "title": "Planning & Prioritization", "canonical_id": "brali:topic:planning-prioritization" }, { "id": "goals", "title": "Goals", "canonical_id": "brali:topic:goals" }, { "id": "work-systems", "title": "Work Systems", "canonical_id": "brali:topic:work-systems" } ], "related_topics": [ { "id": "decision-making", "title": "Decision Making", "canonical_id": "brali:topic:decision-making" } ], "decision_path": [ { "if": "The calendar already contains fixed constraints", "try": "Make them visible before assigning discretionary work. Capacity is what remains, not what you wish remained." }, { "if": "Too many outcomes look important", "try": "Choose a small set that can actually move this week and explicitly defer the rest." }, { "if": "A priority depends on another person or external event", "try": "Separate the action you control from the outcome you can only influence or monitor." } ], "stop_rule": "Re-plan when a material constraint changes. A weekly plan is a decision aid, not a promise that reality must preserve Monday's assumptions.", "protocols": [ { "canonical_id": "brali:protocol:3-3-3-workday-planner", "slug": "3-3-3-workday-planner", "url": "https://brali-lifeos.github.io/life-os/3-3-3-workday-planner/", "title": "Plan Your Workday in Three Simple Blocks", "description": "Split the day into a few broad work blocks and choose a small set of clear outcomes for each. Use three blocks and up to three tasks per block as a template, not a rule.", "action": "Divide the workday into up to three broad blocks. Give each block one to three clear outcomes that fit the time you actually have. Replan when meetings, urgent work, or delays change the day.", "check_in": "Did the blocks help me choose what mattered, and was any block overloaded, too vague, or too rigid?", "evidence": { "status": "practical", "source_recorded": false, "source_url": null, "reviewed_at": "2026-08-18" }, "topic_ids": [ "work-systems" ], "is_flagship_100": true, "fit": "best-fit", "when": "You need a lightweight structure that keeps fixed constraints visible and reduces a large task inventory to a few observable outcomes.", "why": "Its block logic is useful as a capacity-and-priority template even when the exact number of blocks is adjusted to the real schedule.", "caveat": "The number three is not an evidence-backed optimum; use fewer or different blocks when the work is interrupt-driven or tightly constrained.", "gold_review": { "reviewed_at": "2026-09-09", "review_status": "gold-ready", "first_action": "Look at today's fixed constraints, then write up to three broad work blocks and give each block one to three observable outcomes that fit the time you actually control.", "observable_signal": "Whether the user could identify the current important outcome, whether fixed constraints remained visible, and whether the remaining plan could be updated without carrying obsolete blocks forward as guilt or hidden backlog.", "eligibility": [ "The user is planning an ordinary low-risk workday and can choose or renegotiate at least some priorities.", "Grouping work into a few broad blocks would reduce decision friction without hiding fixed meetings, dependencies, service levels, or deadlines.", "The user is willing to replan when reality changes instead of treating the initial blocks as commitments that must be completed exactly." ], "when_not_to_use": [ "Do not use the template as the controlling workflow for emergency response, incident management, clinical care, driving, safety-critical operations, or another setting where priorities must update continuously from external events.", "Do not compress mandatory sequences, deadlines, handoffs, or dependencies into three blocks when doing so would hide operational constraints.", "Do not interpret three blocks or three outcomes as an evidence-backed optimal dose for productivity." ], "evidence_boundary": { "status": "practical", "statement": "The 3-3-3 structure is a low-risk editorial planning template. Brali has no reviewed source establishing three blocks, three outcomes, or any exact 3×3 schedule as a scientifically optimal productivity method; the value claim is limited to whether the user finds the structure useful in the current workday.", "source_decision_ids": [] } } }, { "canonical_id": "brali:protocol:circles-of-control-planner", "slug": "circles-of-control-planner", "url": "https://brali-lifeos.github.io/life-os/circles-of-control-planner/", "title": "Separate Outcomes From Actions You Can Control", "description": "Draw two circles; one for factors you can control and another for those you cannot. Set clear, achievable goals based on what’s within your control.", "action": "Write down one concern, separate the outcome from the actions you can take, convert anything you can influence into one concrete behavior, and choose the next useful action without pretending you control the final result.", "check_in": "What part of this situation was actually mine to act on, what remained outside my control, and did the sorting help me choose a clearer next step?", "evidence": { "status": "practical", "source_recorded": false, "source_url": null, "reviewed_at": "2026-08-18" }, "topic_ids": [ "decision-making", "stress-regulation" ], "is_flagship_100": true, "fit": "alternative", "when": "A large part of the week's uncertainty depends on other people, approvals, timing, or external events.", "why": "It separates controllable behavior from outcomes that should be influenced, monitored, escalated, or accepted rather than scheduled as if guaranteed.", "caveat": "Do not use control language to erase structural constraints, safety concerns, or legitimate escalation needs.", "gold_review": { "reviewed_at": "2026-09-15", "review_status": "gold-ready", "first_action": "Write one concern, separate the uncertain outcome from your own observable actions, and choose the smallest useful behavior you can take without pretending it guarantees the result.", "observable_signal": "Whether the user can distinguish an outcome from a behavior, name one real controllable action, and decide what to do with remaining uncertainty without claiming control over the final result.", "eligibility": [ "The user can name one ordinary concern and identify at least one observable action that is genuinely under their control.", "Separating outcome from behavior would help allocate effort without denying that external factors still matter.", "The situation is low-risk enough for a self-guided planning exercise and does not require immediate crisis, legal, medical, safety, or other professional intervention." ], "when_not_to_use": [ "Do not use the framework to blame a person for structural constraints, discrimination, coercion, unsafe conditions, missing resources, or another external barrier.", "Do not relabel an outcome as controllable simply because the user can influence its probability.", "Do not use acceptance language to discourage monitoring, support-seeking, escalation, advocacy, contingency planning, or other appropriate responses to external risk." ], "evidence_boundary": { "status": "practical", "statement": "This is a practical action-allocation reflection. Brali does not attach reviewed evidence that drawing control circles, using this wording, or this exact sequence reliably reduces stress or improves decision quality.", "source_decision_ids": [] } } }, { "canonical_id": "brali:protocol:woop-goal-planner", "slug": "woop-goal-planner", "url": "https://brali-lifeos.github.io/life-os/woop-goal-planner/", "title": "Use WOOP to Turn a Wish Into an If-Then Plan", "description": "Use a Wish, desired Outcome, likely internal Obstacle, and a concrete if-then Plan to make one meaningful goal easier to act on. Treat the method as a self-regulation tool, not a guarantee of goal achievement.", "action": "Choose one meaningful and reasonably feasible wish. Describe the outcome you want, identify an internal obstacle that could derail you, then write: If I notice this obstacle, then I will take this specific action. Try the plan in real life and revise it if the cue or response is not useful.", "check_in": "Did the obstacle actually appear, did my if-then response help me act, and what should I keep or change next time?", "evidence": { "status": "reviewed", "source_recorded": true, "source_url": "https://doi.org/10.3389/fpsyg.2021.565202", "reviewed_at": "2026-08-18" }, "topic_ids": [ "goals" ], "is_flagship_100": true, "fit": "alternative", "when": "One meaningful weekly priority is feasible but a recurring internal obstacle keeps derailing execution.", "why": "It turns the obstacle into an explicit if-then response that can be tested during the week.", "caveat": "Keep external blockers separate; WOOP is not a guarantee that the weekly outcome will be achieved.", "gold_review": { "reviewed_at": "2026-09-09", "review_status": "gold-ready", "first_action": "Write one meaningful and reasonably feasible wish, one concrete outcome, one internal obstacle that could derail you, and one sentence in the form: If I notice this obstacle, then I will take this specific action.", "observable_signal": "Whether the chosen obstacle actually appeared, whether the user noticed it, whether the if-then response was executed, and what changed in the next action. Goal completion itself is a separate longer-horizon outcome and is not guaranteed by the protocol.", "eligibility": [ "The wish is meaningful, reasonably feasible, and low-risk enough to test through ordinary self-directed action.", "The user can identify at least one internal obstacle, such as a thought, feeling, habit, or impulse, that is relevant to the goal and partly within their influence.", "The user can define a specific action to try when that obstacle or cue appears and can later inspect what happened." ], "when_not_to_use": [ "Do not use WOOP to reframe an external constraint such as missing permission, money, staffing, safety, discrimination, or another structural blocker as a personal self-regulation failure.", "Do not use the protocol as a guarantee that a goal will be achieved or as a substitute for professional assessment in medical, legal, safety-critical, or other consequential decisions.", "Do not force a wish that is not reasonably feasible or personally meaningful merely to complete the template." ], "evidence_boundary": { "status": "reviewed", "statement": "A 2021 meta-analysis of mental contrasting with implementation intentions reported a small-to-medium average effect on goal attainment across heterogeneous field interventions, with mixed publication-bias diagnostics and a smaller trim-and-fill estimate. A 2026 randomized undergraduate procrastination study provides narrow corroboration for task aversiveness and willingness to act. Brali therefore treats WOOP as a bounded self-regulation option for feasible goals, not as a universal or guaranteed goal-achievement method.", "source_decision_ids": [ "woop-mcii-goal-attainment-meta-analysis-2021", "woop-mcii-academic-procrastination-rct-2026" ] } } } ], "answer_packet": { "schema_version": 1, "canonical_id": "brali:problem:plan-realistic-week", "problem": "How do I choose priorities for the week without overloading the plan?", "canonical_url": "https://brali-lifeos.github.io/problems/plan-realistic-week/", "best_fit": { "canonical_id": "brali:protocol:3-3-3-workday-planner", "slug": "3-3-3-workday-planner", "title": "Plan Your Workday in Three Simple Blocks", "when": "You need a lightweight structure that keeps fixed constraints visible and reduces a large task inventory to a few observable outcomes.", "why": "Its block logic is useful as a capacity-and-priority template even when the exact number of blocks is adjusted to the real schedule.", "caveat": "The number three is not an evidence-backed optimum; use fewer or different blocks when the work is interrupt-driven or tightly constrained.", "first_action": "Look at today's fixed constraints, then write up to three broad work blocks and give each block one to three observable outcomes that fit the time you actually control.", "evidence_state": "practical" }, "alternatives": [ { "canonical_id": "brali:protocol:circles-of-control-planner", "slug": "circles-of-control-planner", "title": "Separate Outcomes From Actions You Can Control", "when": "A large part of the week's uncertainty depends on other people, approvals, timing, or external events.", "why": "It separates controllable behavior from outcomes that should be influenced, monitored, escalated, or accepted rather than scheduled as if guaranteed.", "caveat": "Do not use control language to erase structural constraints, safety concerns, or legitimate escalation needs.", "first_action": "Write one concern, separate the uncertain outcome from your own observable actions, and choose the smallest useful behavior you can take without pretending it guarantees the result.", "evidence_state": "practical" }, { "canonical_id": "brali:protocol:woop-goal-planner", "slug": "woop-goal-planner", "title": "Use WOOP to Turn a Wish Into an If-Then Plan", "when": "One meaningful weekly priority is feasible but a recurring internal obstacle keeps derailing execution.", "why": "It turns the obstacle into an explicit if-then response that can be tested during the week.", "caveat": "Keep external blockers separate; WOOP is not a guarantee that the weekly outcome will be achieved.", "first_action": "Write one meaningful and reasonably feasible wish, one concrete outcome, one internal obstacle that could derail you, and one sentence in the form: If I notice this obstacle, then I will take this specific action.", "evidence_state": "reviewed" } ], "stop_rule": "Re-plan when a material constraint changes. A weekly plan is a decision aid, not a promise that reality must preserve Monday's assumptions." }, "evidence_decisions": [ { "id": "ai-review-correction-friction-boundary-2026", "decision": "propose-protocol", "reviewed_at": "2026-08-29", "source_title": "Bias in the Loop: How Humans Evaluate AI-Generated Suggestions", "source_url": "https://hdsr.mitpress.mit.edu/pub/nrcn4h7d/release/2", "supported_claim": "When humans review AI-generated suggestions, the review interface itself can bias behavior. In this experiment, adding repair work to the act of rejecting an AI suggestion reduced correction activity and increased undercorrection. Brali can therefore justify a bounded workflow rule: make it cheap to flag or reject an AI output, and separate validation from repair when the repair burden would otherwise make acceptance the path of least resistance.", "unsupported_or_overstated_claims": [ "Making correction easier will always increase overall accuracy.", "People who distrust AI are universally better reviewers.", "Performance bonuses cannot improve AI review in other settings.", "The same effect size applies to expert, medical, legal, financial, or safety-critical review.", "A human-in-the-loop label by itself guarantees reliable oversight.", "AI suggestions should be hidden from reviewers." ], "limitations": [ "The experiment used crowdworkers rather than domain experts.", "The task was limited to ten greenhouse-gas reporting tables and one pre-annotation workflow.", "Several difficult items required domain knowledge that many annotators lacked.", "The randomized correction-burden manipulation changed correction behavior, but the regression analysis did not show a clear overall accuracy loss because overcorrections also decreased.", "AI attitudes predicted behavior observationally rather than through randomized manipulation.", "The study did not include a no-AI baseline and could not analyze item-order effects." ] }, { "id": "ai-structured-intake-human-judgment-boundary-2026", "decision": "propose-protocol", "reviewed_at": "2026-08-29", "source_title": "Voice AI in Firms: A Natural Field Experiment on Automated Job Interviews", "source_url": "https://arxiv.org/html/2607.28222", "supported_claim": "A defensible way to divide some repetitive high-volume workflows is to automate structured information collection while keeping consequential evaluation with a human. In this field experiment, that division improved several downstream hiring outcomes without a measured decline in worker productivity. Transcript evidence is consistent with greater standardization and comparability as a mechanism, but does not prove that mechanism independently. Brali should treat this as a task-allocation pattern to test, not as evidence that AI should make final hiring or other high-stakes decisions.", "unsupported_or_overstated_claims": [ "AI interviewers are generally better than human interviewers.", "AI should make final hiring decisions.", "The result generalizes to specialized, relationship-heavy, tacit-knowledge, executive, clinical, legal, or other high-stakes work.", "Automating information collection removes discrimination or guarantees fairness.", "The same voice-AI system will produce the same results in other firms, languages, cultures, or labor markets.", "Human oversight automatically prevents automation bias.", "The controlled-variance mechanism is causally proven by the experiment." ], "limitations": [ "The source is a working paper rather than a peer-reviewed journal article.", "The experiment was conducted with one recruitment-process outsourcing firm and entry-level customer-service hiring in the Philippines.", "Five percent of AI interviews ended because applicants were unwilling to continue with AI and seven percent experienced technical failure.", "The transcript-based mechanism analysis is associative even though interviewer assignment was randomized.", "The candidate-experience survey had a low response rate and may not represent all applicants.", "Applicants who were allowed to choose showed negative sorting into AI, limiting interpretation of the choice condition.", "Employment selection has legal, fairness, accessibility, and accountability requirements that this study does not resolve." ] }, { "id": "consider-opposite-social-judgment-boundary-1984", "decision": "propose-protocol", "reviewed_at": "2026-09-11", "source_title": "Considering the opposite: A corrective strategy for social judgment", "source_url": "https://doi.org/10.1037/0022-3514.47.6.1231", "supported_claim": "When a judgment is vulnerable to one-sided evidence processing, deliberately generating an opposed possibility can reduce bias on some tasks more effectively than simply telling oneself to be fair or unbiased. Brali can use this as a concrete pre-decision check while preserving the possibility that the original conclusion remains correct.", "unsupported_or_overstated_claims": [ "Consider-the-opposite eliminates confirmation bias.", "The technique transfers automatically to every real-world decision.", "The opposite conclusion should be preferred once generated.", "More counterarguments are always better.", "The strategy should be used for every trivial or reversible choice." ], "limitations": [ "Classic laboratory/social-judgment evidence from undergraduate samples.", "Only two focal task domains were tested in the original article.", "Long-term persistence and broad transfer were not established.", "The authors note that considering the opposite can in some circumstances overweight disconfirming evidence and create a different form of partiality.", "Demand characteristics and task-specific effects remain possible." ] } ], "trust_note": "Recommendations come only from protocols that are both trusted in the Brali Protocol Feed and manually Gold-ready. The problem-to-protocol fit is editorial decision logic; it is not a claim that one sequence is universally best." }