Notion Office Hours: Weekly Planning 🏁

Weekly planning and retrospectives work best when they’re treated as a repeatable end-of-week “wrap” that protects predictability, reduces anxiety, and preserves personal time—not just as a work-management chore. DeeDee Medina frames the core problem as simple: when weekly review and planning slip, work becomes domino-like, fires multiply, and the week’s outcomes get less predictable. The payoff is measurable in time and energy—she describes spending about two hours on weekly planning/retros and then gaining roughly seven to twelve hours back across the week, with better sleep and fewer reactive detours.

A key argument is that the cadence matters. Planning bi-weekly creates diminishing returns because the “next-next week” becomes too speculative; planning daily breaks down for complex objectives that need incubation time (especially in design work). Her practical model is to plan weekly, then use the week’s structure to sequence tasks that require gaps—brainstorming, letting ideas sit, then returning for focused execution. She also emphasizes that planning isn’t only about work deliverables. Client issues and overtime are real, but the bigger cost of poor planning is crowding out friendships, relationships, and rest. Weekly planning becomes a lifestyle negotiation: work and personal priorities share the same calendar, so the week ends with clarity rather than lingering open loops.

The session also pushes back on the idea that plans must be bulletproof. Unexpected variables will always appear—“no war has ever gone unplanned”—so the purpose of planning is not certainty but a sweet spot of preparation. Medina recommends leaving margin in the schedule via buffer blocks and non-negotiable time, and using a cost/benefit mindset: if extra planning yields more results than skipping it, keep it; if not, cut it. She repeatedly returns to accountability as the mechanism: retros should include meta-reflection on what’s working, what isn’t, and what patterns are being avoided.

To make weekly review actionable, she shares a concrete Notion-based retro structure built around writing and context rather than vague bullet lists. The process starts with a kickoff checklist: skim yearly objectives, review the previous week’s goals, and read calendar time allocation as a “story” of what happened. Next comes a situation summary written as a narrative of the week; then takeaways are extracted as lessons learned, with a rule to avoid clutter—no takeaways usually means a “vanilla” week. For self-employed work, she adds a pipeline-style stats section (contacts → relationships → opportunities → screening → discovering → deciding → working → closing/invoicing) to spot where zeros appear and force follow-through.

Finally, she operationalizes the plan through objectives and time blocks placed directly onto the calendar. Time blocks should represent deep work with tangible, checkable tasks (not vague goals), and deep work is reserved for multi-hour focus requiring attention. Shallow tasks are handled by default; the system’s job is to ensure deep work gets protected. The retro ends with a wrap-up: transfer relevant context to the calendar, negotiate overbooking, and complete a weekly behavior audit (sleep, deep work count, nutrition, exercise, emotional conversations) to reduce anxiety by closing loops before the weekend.

Throughout, the message is pragmatic: start simple, iterate, and don’t over-engineer Notion setups. The best system is the one that prevents self-deception, is maintainable, and leaves enough mental bandwidth for creativity and life outside work.