The Zen Workflow: From Overwhelmed to In Control
You know that feeling when you check off a task and immediately worry you’ll forget something? When you delegate work but can’t remember if it got done? When your task list feels like a graveyard of half-finished threads?
MakeTimeFlow’s Zen Workflow changes this. It’s designed for people managing multiple responsibilities—work projects, family commitments, personal goals—who need a system they can actually trust.
What Makes Zen Different
The Problem with Most Task Managers
Traditional tools assume work is simple: you have a task, you do it, it’s done.
But your reality is messier:
- You send a proposal → need to check if they responded
- You ask your team to review something → need to verify they did
- You schedule a call → need to prepare and then follow up after
Most task managers force you to either keep tasks open (cluttering your list) or complete them and hope you remember to check back (you won’t).
The Zen Solution
Zen gives you three powerful capabilities working together:
- Structure your thinking in the outliner
- Execute your day in the task list
- Never drop the ball with closing the loop
Let’s see how real people use this.
Sarah’s Story: The Product Manager
Sarah manages three product launches simultaneously. Before Zen, she’d finish a deliverable, mark it done, and then two weeks later realize she never confirmed the client received it.
Morning: Planning in the Outliner
Sarah opens her outliner and sees her projects as a hierarchy:
Q1 Product Launch
├── Finalize feature specs
├── Get design approval
├── Development handoff
└── QA review
Client Onboarding
├── Send welcome packet
├── Schedule kickoff call
└── Follow up on requirements
She breaks down “Finalize feature specs” into subtasks by pressing Tab:
Finalize feature specs
├── Draft initial specs
├── Review with engineering
└── Incorporate feedback
Each task shows its priority and deadline right in the outline—no clicking into detail views. She moves today’s work to @today with a quick /bucket:today command.
Time spent: 3 minutes. Result: Clear plan for the day.
Midday: Executing in the Task List
Sarah switches to the Zen list view. Her @today bucket shows 6 tasks.
She navigates with j and k (down and up), completes tasks with Space, and starts her timer with s when she needs focus time.
When she finishes “Draft initial specs,” she knows this isn’t really done—she needs Michael to review it. Instead of completing it normally, she presses >:
- The task is marked complete
- A new task “Get feedback from Michael on specs” is created
- It’s linked to the original, so she can see the full context later
She didn’t have to remember to create the followup. The system captured it in the same motion as completion.
Later: Waiting on Others
Sarah sent the specs to Michael two hours ago. She marks the followup task with w for “waiting for”:
- The task gets a
@waiting_fortag - It moves to @next (visible but not cluttering @today)
- She’ll review waiting items during her end-of-day shutdown
The ball is in Michael’s court. Sarah isn’t carrying it in her head anymore.
End of Day: The Shutdown Ritual
Sarah glances at her mini bucket bar:
┌─────────┐ ┌─────────┐ ┌─────────────────┐
│ @next │ │ @later │ │ 8 Done │
│ 12 tasks│ │ │ │ Followup? │
└─────────┘ └─────────┘ └─────────────────┘
Eight tasks done. She clicks to review them and creates followups for two that need checking next week.
She drags one straggler from @today to @next—it can wait until tomorrow.
Tomorrow’s @today starts clean. Nothing was forgotten.
Marcus’s Story: The Entrepreneur
Marcus runs a small agency with three employees. He’s constantly context-switching between client work, team management, and business development.
The Followup Chain That Saved a Deal
Marcus sent a proposal to a potential client on Monday. In most systems, he’d either:
- Keep “Send proposal” open (cluttering his list)
- Complete it and try to remember to check back (risky)
With Zen, he pressed > after sending:
Send proposal to Acme Corp [completed]
↓ followup
Check if Acme Corp received proposal (Thursday)
On Thursday, the followup surfaced in @next. He clicked the link icon and saw the original task with all its context—what he sent, when, the key points.
The client hadn’t responded. He sent a gentle nudge and pressed > again:
Check if Acme Corp received proposal [completed]
↓ followup
Follow up on Acme Corp proposal (next Tuesday)
On Tuesday, they responded. Deal closed.
Without the followup chain, this would have slipped. With it, Marcus had a systematic way to stay on top of the deal without keeping it in his head.
Delegating Without Worrying
Marcus assigns work to his team but used to struggle with verification. Did they actually do it?
Now when he delegates, he immediately creates a followup:
Ask Jamie to review client brief [completed]
↓ followup
Verify Jamie reviewed client brief (Friday)
On Friday, the task surfaces. If Jamie finished, Marcus completes it. If not, he follows up with Jamie and creates another followup:
Verify Jamie reviewed client brief [completed]
↓ followup
Check Jamie's progress on client brief (Monday)
Delegation became trustworthy. Marcus stopped carrying “did they do it?” anxiety.
Elena’s Story: The Parent and Professional
Elena is a marketing director and mother of two. Her days blend work deadlines, school pickups, family dinners, and personal goals.
The Outline That Keeps Everything Visible
Elena’s outliner shows her full life:
Work: Q1 Campaign
├── Finalize ad creative
├── Coordinate with sales team
└── Review analytics
Family: Spring Break Planning
├── Book flights
├── Confirm hotel
└── Plan activities for kids
Personal: Health Goals
├── Schedule annual checkup
└── Sign up for yoga class
She doesn’t separate “work” and “life” into different apps. Everything lives in one trusted system where she can see the full picture.
The Waiting Game with Kids
Elena’s son needs a permission slip signed by his teacher. She sent it Monday:
Send permission slip to school [completed]
↓ followup
Check if permission slip was signed (Wednesday)
On Wednesday, the followup appeared. She checked her son’s backpack—not signed yet. She pressed w to mark it waiting:
Check if permission slip was signed [@waiting_for]
The task moved to @next with a visible tag. During her weekly review, she saw all her @waiting_for items and followed up with the teacher.
Family tasks get the same rigor as work tasks. Nothing falls through the cracks.
The End-of-Day That Actually Ends the Day
Elena’s mini bucket bar at 5pm:
┌─────────┐ ┌─────────────────┐
│ @next │ │ 11 Done │
│ 8 tasks │ │ Followup? │
└─────────┘ └─────────────────┘
She clicks “Done” and sees her completions. Two need followups—she creates them with >. One work task didn’t get done—she drags it to @next without guilt.
Her @today is empty. The day is actually over. She can be present with her kids knowing nothing will slip.
The Keyboard That Becomes Muscle Memory
After a week with Zen, your hands learn the rhythm:
| Key | Action | When You Use It |
|---|---|---|
j/k | Move down/up | Navigate your list |
Space | Complete | Task is done-done |
> | Complete + Followup | Task is done but needs checking |
w | Waiting For | Ball is in someone else’s court |
t/n/l | Move to @today/@next/@later | Triage quickly |
s | Start timer | Need focus time |
Enter | Edit task | Add notes or details |
You stop thinking about the tool. You just flow.
The Philosophy: Don’t Over-Optimize on Dates
When you create a followup, you often don’t know exactly when you’ll need to act. Will the client reply in 2 days or 5? Will the review take a day or a week?
Zen defaults followups to @next without a specific date. This is intentional.
@next means “soon, but not today.” The task will surface when you review your @next bucket. If you do need a specific date, one click gives you “Tomorrow” or “Next week.”
Most followups are “check back soon.” Zen makes that effortless without forcing false precision.
Getting Started
Step 1: Process Your Inbox
Open the Zen list view. Everything starts in @inbox.
For each task:
- Is it something for today? Press
t - Is it something for this week? Press
n - Is it something for later? Press
l
5 minutes → Clean inbox, clear buckets
Step 2: Complete with Intention
When you finish a task, pause:
- Is this truly done? Press
Space - Do I need to check back on this? Press
> - Am I waiting for someone? Press
w
This becomes automatic within a day.
Step 3: End Each Day Clean
Before you stop working:
- Glance at mini buckets—how many done?
- Review @today—anything left?
- Drag stragglers to @next (or complete with
>if they need followup) - Check @waiting_for—anything stale?
2 minutes → Peace of mind
The Transformation
Before Zen:
- Tasks marked “done” that weren’t really done
- Mental burden of “did I follow up on X?”
- Anxiety about dropped balls
- End of day never really ends
After Zen:
- “Done” means outcome achieved, not just action taken
- Followups captured automatically
- Waiting items visible and tagged
- Days end clean, mind is free
Your Turn
Start with one change: the next time you complete something that needs checking, press > instead of Space.
That simple shift—from “done” to “done with followup”—will change how you think about completion.
Then learn j and k for navigation. Then t/n/l for triage.
Within a week, you’ll wonder how you worked without this.
The Zen Workflow is available now in MakeTimeFlow. Questions? Reach out—we’d love to hear how it’s working for you.