Case Study: Designing a Two-Shift Writing Workflow with Calendar Blocks
We applied a two-shift writing routine to an editorial team in 2025. This case study details the calendar blocks, tooling and rituals that produced measurable output improvements.
Hook: Timeboxing can be a craft — we tested a two-shift writing routine on a live newsroom.
Over the last year our editorial team experimented with a two-shift writing routine inspired by the "Morning Pages, Evening Wins" method. This case study walks through how we scheduled blocks, measured outcomes, and scaled the practice across remote contributors using calendar tooling.
Background: Why two shifts?
The two-shift routine splits creative writing into two focused sessions: morning pages to capture ideas, and an evening wins block to finalize drafts or celebrate progress. We adapted the routine into calendar-first rituals to protect focus and encourage iterative momentum.
Practical setup
Our config included:
- Morning Pages (45 mins) — an unshared block where writers free-write and capture sparks. Inspired by the original routine: Morning Pages, Evening Wins.
- Work Sprint (90 mins) — focused writing or research time.
- Evening Wins (30 mins) — short reflection and publishing or scheduling time.
Calendar features we used
- Protected focus blocks with automatic Do Not Disturb and app timers.
- Shared project blocks for peer review windows so feedback arrives predictably.
- Templates and snippets to speed editorial drafts and ensure consistent recording of outcomes.
Tools and practical pointers
We paired calendar rituals with tools and practices to ensure adoption:
- Notebook practices — writers compared digital templates with physical options; for those wanting tactile notes, see our supplemental reading: Notebook showdown.
- Short book lists to seed morning pages — January picks and short readings helped prompt ideas: January picks.
- Power and continuity planning for remote contributors delivered via battery guides for long streams or off-grid sessions: Batteries & power solutions.
Pilot results
Over 8 weeks, our pilot produced measurable improvements:
- Output frequency increased by 28% (pieces completed on schedule).
- Quality markers (editor satisfaction ratings) improved by 12%.
- Writers reported lower planning friction and fewer context switches.
Rituals that enabled success
- Start the day with an anchor — a micro-reading prompt or a short audio piece to prime the morning pages.
- Hold the evening wins time sacred — make it the place to close loops and celebrate small victories.
- Use calendar nudges — gentle nudges remind contributors of their upcoming block without interrupting flow.
Mistakes and recoveries
Common issues included over-scheduling and misaligned expectations about collaboration windows. We solved this by:
- Introducing a weekly planning sync to align on shared blocks.
- Allowing one "flex day" where blocks are optional to prevent burnout.
Scaling beyond the newsroom
The two-shift routine scales to product, design and sales teams when adapted to domain rhythms. Key advice for scaling:
- Collect qualitative feedback monthly.
- Use template calendars for new hires.
- Provide choices — not all contributors need identical block lengths.
Further reading and inspiration
- Original two-shift note framework: Morning Pages, Evening Wins.
- Notebook comparisons to choose the right analog tools: Notebook showdown.
- Short reading lists for morning prompts: January picks.
- Power solutions for remote writing sessions: Batteries & power solutions.
Consistency beats intensity — regular rhythm creates compounding gains in writing output.
If you want to trial this with your team, start with a two-week pilot on three volunteers and iterate weekly. Our templates are available inside Calendar.live to get started.
Related Topics
Avery Cole
Senior Editor, Calendar.live
Senior editor and content strategist. Writing about technology, design, and the future of digital media. Follow along for deep dives into the industry's moving parts.
Up Next
More stories handpicked for you