ThinkingThought for NsTodayClick to sendYour turn. Press send.Your turn. Press send, or say it another way:Off your mind: NKept: NStarting nowin #billing-teamBehind the scenes (N)
Intro
Zebra in four minutes
Three phrases run your week
Every morningPrepare my day
Every eveningCapture today's promises
Every FridaySummarize my week
You say the phrase. Your assistant reads your tools with its own connectors. Zebra remembers your promises and applies your rules.
Saves your profileAlex, New York, focus: ship the billing migration
Alex, New York Focus: ship the billing migration Tasks, Calendar, Chat, Docs, GitHub
Zebra is connected and knows who you are. Your Zebra, on the right, shows everything it remembers. It starts almost empty.
1. Prepare my day
Step 1 of 3 · Monday, 7:30
Prepare my day
Nine open tasks, and a pull request that merged last night. You say one phrase, and the morning routine:
checks what finished since yesterday
picks the one task that moves your focus
applies the rules you taught it
Prepare my day
What should I work on today?
Gets the morning routinea script for preparing the day
Reads the profilefocus: ship the billing migration
Lists your 9 open tasks
Checks the tasks against their sources2 tasks point to a pull request: check them
#479 merged last night
Records a finished taskkept for the weekly summary; close it in Tasks
Completes "Fix the flaky webhook retry test"
#482 still waits for your review
Plans the day7 candidates and the focus
The focus is the billing migration, so the top task has to be delivery work that moves it, never a review. Up to five next tasks, and fewer is better.
I closed "Fix the flaky webhook retry test": #479 merged last night. For today I'd pick:
Ship the billing migration to EU customers, the top task: it moves your focus.
Send the migration plan to Sam
Review Priya's PR on invoice exports
Answer Dana about the Q4 roadmap
Update the on-call runbook
Should I set the day?
Leave the runbook out. Leo owns it now.
That is a lasting correction, not a one-off. I'll save it as a rule so the runbook stays out of every plan, then plan again.
Learns a ruletasks about the runbook never enter the day
Leave out "runbook": Leo owns the on-call runbook now
Plans the day againthe runbook is out: 1 task excluded by a rule
Saves the day1 top task, 3 next, 3 moved down
Top: Ship the billing migration Next: the plan for Sam, Priya's review, Dana's roadmap
Applies the new priorities and dates
Your Monday:
Ship the billing migration to EU customers
Send the migration plan to Sam
Review Priya's PR on invoice exports
Answer Dana about the Q4 roadmap
Left out: the pricing RFC and pairing with Leo, which don't move the migration today. The runbook is Leo's now, and I'll keep it out from now on.
Step 1 of 3 · Done
What changed
One task closed by itself, because its pull request merged overnight.
Your day was picked by your focus, each task with a reason.
Your correction became a rule. You won't say it twice.
Every morning, say Prepare my day
2. Capture today's promises
Step 2 of 3 · Monday, 18:30
Capture today's promises
Two meetings and a busy channel. Watch the day, then say one phrase, and the evening routine:
reads today's meetings and chats
keeps every promise, yours and the ones made to you, with the exact quote
links each of your promises to a task
10:00 Billing sync with Sam and Priya
Billing syncAlex, can you send the migration plan before Thursday's sync?Sure, I'll send it tomorrow.I'll share the API spec for exports by tomorrow.And the cutover date?Let me check with ops.Monday 16:00
16:00 1:1 with Maya
1:1 with MayaHow is the pricing RFC going?I'll share the draft with you on Wednesday.Great. I'll introduce you to the payments team this week.Monday 17:10
17:10 A thread in #billing-team
Could you send the Q4 roadmap notes?I'll send them by Thursday.Alex, can we pair on the tax service?Yes, I'll pair with you this week.Monday 18:30
18:30 The day is over. Time to capture it.
Capture today's promises
What did I promise today?
Gets the capture routinea script for capturing the day's promises
Reads the profilemeetings in Calendar, chat in Chat, tasks in Tasks
Reads the Billing sync transcript
Keeps only your lines and the ones that mention you5 lines
Records the promises, each with its quote2 accepted, 1 task to create
Mine Send the migration plan to Sam due Tue · "I'll send it tomorrow"Priya Share the API spec for exports due Tue · "I'll share the API spec for exports by tomorrow"
Finds "Send the migration plan to Sam" already in Tasks
Links the promise to that tasklinked to "Send the migration plan to Sam"
Reads the 1:1 with Maya
Keeps only your lines and the ones that mention you3 lines
Records the promises, each with its quote2 accepted, 1 task to create
Mine Share the pricing RFC draft with Maya due Wed · "I'll share the draft with you on Wednesday"Maya Introduce Alex to the payments team this week · "I'll introduce you to the payments team this week"
Creates "Share the pricing RFC draft with Maya", due Wednesday
Share the pricing RFC draft with Maya
Links the promise to the new tasklinked to t10
Lists the open promises before reading the chat3 open
Reads today's thread in #billing-team
Keeps only your lines and the ones that mention you4 lines
Records the promises, each with its quote2 accepted, 2 tasks to create
Mine Send the Q4 roadmap notes to Dana due Thu · "I'll send them by Thursday"Mine Pair with Leo on the tax service this week · "I'll pair with you this week"
Finds tasks that already cover both
Links Dana's notes to "Answer Dana about the Q4 roadmap"linked to t7
Links the pairing to "Pair with Leo on the tax service"linked to t6
Alex said "Let me check with ops", but that promises Sam nothing to deliver and has no date. I'll leave it out and say so.
From today's meetings and #billing-team:
You promised Sam the migration plan by Tuesday, Maya the RFC draft on Wednesday, Dana the roadmap notes by Thursday, and Leo a pairing session this week.
Promised to you: Priya's API spec by Tuesday and Maya's intro to the payments team.
Each of your promises has a task now, one of them new. I left out "Let me check with ops": it doesn't promise Sam anything. Agree?
Right, that's not a promise.
Good, it stays out.
Step 2 of 3 · Done
What changed
6 promises recorded: 4 of yours and 2 made to you.
Each one keeps the exact words of whoever made it. Zebra rejects a quote that person didn't say.
Each of your promises has a task, so closing the task keeps the promise.
Every evening, say Capture today's promises
Bonus
Bonus · Tuesday, during the day
Between routines, just talk
The routines run at the edges of your day. In between, your assistant keeps Zebra up to date when you tell it what happened:
it keeps today's plan in mind while you work
it closes a promise someone kept, with the quote
it sends feedback about Zebra, only after you agree
Let's get to work
What's next?
Gets the session routinekeep today's plan in mind
Reads today's plan1 top task, 3 next
Your top task is still shipping the billing migration. Next: the plan for Sam, Priya's review and Dana's roadmap. I'll tell you if something you ask is off this plan.
Approve Priya's pull request
Approved
I finished Priya's review
#482 approved by you
Records a finished taskkept for the weekly summary
Here's the exports API spec, as promised: docs.acme.dev/exports-api
Priya sent the exports spec
Reads Priya's message
Lists the promises made to you1 open: Priya, the API spec
Closes Priya's promise with her message as the quotedone
Priya kept her promise, on the day she said. I closed it in Zebra with her message as proof.
One thing I miss: seeing my open promises grouped by person, so I can check what I owe Sam before our sync.
That is about Zebra itself, and no rule fixes it. I'll write it in a line, show it, and send it only if Alex agrees.
I can send this to the Zebra team:
In Your Zebra, I'd like to see open promises grouped by person, so I can check everything I owe Sam before our sync.
Should I send it?
Yes, send it
Sends feedback to the Zebra teamsent, with your agreement
Sent.
Bonus recap
What changed
Your assistant kept the day's plan in mind while you worked.
Priya's promise closed with her own message as proof.
Your idea reached the Zebra team, in the words you approved.
3. Summarize my week
Step 3 of 3 · Friday, 16:00
Summarize my week
First, Tuesday to Thursday in a few seconds: each task you close keeps the promise linked to it. Then you say one phrase, and the weekly routine:
shows what you kept and what others still owe you
gives you the lines for your brag document
cleans up old rules and checks your focus
Tuesday You sent Sam the plan, Priya sent the API spec, Leo took over the runbook.
Wednesday 9:00
Wednesday RFC draft to Maya, pairing with Leo. You added a rule: keep Thursday morning free for the cutover.
Guidance: keep Thursday morning free for the cutoverThursday 11:30
Thursday The migration shipped, and Dana got the roadmap notes.
The EU launch is unblocked. Thank you, Alex.Friday 16:00
Friday 4 promises kept. Nothing you owe is open.
Summarize my week
How did my week go?
Gets the weekly routinea script for the weekly summary
Reads the week4 promises kept, 1 follow-up closed, 4 days planned
Reads the rules2 rules
Reads the profilefocus: ship the billing migration
Your week:
4 promises kept: the migration plan to Sam, the RFC draft to Maya, pairing with Leo and the Q4 roadmap notes to Dana.
Kept for you: Priya shared the API spec on time.
4 days planned, with the same top task every day. The EU migration shipped on Thursday.
Still owed to you: Maya's intro to the payments team.
For your brag document: "Shipped the billing migration to EU customers, which unblocked the EU launch." I can add it whenever you want.
The script asks for rules that may be stale. "Keep Thursday morning free for the cutover" was about the cutover, and the migration shipped, so its reason is gone.
One rule looks finished: "Keep Thursday morning free for the cutover". Should I delete it? And is your focus still the billing migration?
Delete it. The migration shipped, my focus now is launching usage-based pricing.
Deletes the rule1 rule left
Changes the focusfocus: launch usage-based pricing
Alex, New York Focus: launch usage-based pricing Tasks, Calendar, Chat, Docs, GitHub
Done. From Monday I'll pick your top task by what moves usage-based pricing. Have a good weekend.
Step 3 of 3 · Done
What changed
Your week came from what Zebra recorded, so nothing depended on your memory.
Nothing you promised is still open. Maya's intro is the only thing owed to you.
An old rule is gone and next week follows your new focus.