Running your day · Lesson 3 of 3
How does YAGNI prepare your Calendar and track Work?
Published June 9, 2026
The Calendar is the agenda @yagni reads and prepares against: before each meeting, the picture on your Brief is current and the context is ready. Work is the cross-Team surface for work-items that span Teams, tracked from proposal to done while the source records stay in your tools.
What does @yagni do with your Calendar?
It reads the agenda and prepares against it. The events themselves stay in Google Calendar; YAGNI does not host a second calendar or ask you to move. What changes is what happens before each event: the relevant Team has the picture current by the time you walk in.
A sales call means the account’s thread history, the deal’s state, and the open questions are ready. An engineering planning session means what shipped, what is blocked, and what the Front already flagged. The preparation you used to do by opening six tabs in the ten minutes before the meeting is already done, cited, and waiting.
What is the Work surface for?
Work is the cross-Team surface for work-items: the things that need doing which span more than one part of the business. A customer-promised fix touches the Support Team, the Engineering Team, and a Gmail thread. A work-item holds that whole shape in one place, from proposal to done.
Within one tool, the tool’s own object is the record, and it stays that way. Work exists for the things that never had a home because they belonged to three tools at once.
How do work-items relate to the records in your tools?
They reference them, never replace them.
| Lives in your tools (connector objects) | Lives in Work |
|---|---|
| Linear issues, GitHub pull requests | Work-items that reference them |
| Gmail threads, Slack conversations | The cross-Team shape they add up to |
| HubSpot deals, Stripe invoices | The follow-through that spans them |
This is the additive rule applied to work tracking: your engineers keep working Linear, your sales team keeps working HubSpot, and nobody migrates anything. Work is where the connective tissue becomes visible, with every reference clickable back to its source.
How does work move without you pushing it?
Teams watch their pieces. When the Linear issue a work-item references gets closed, the item advances and the receipt lands teal in the Inbox. When something stalls, the responsible Team weighs it and either acts within its Playbook or raises it amber. Approvals, as everywhere in YAGNI, come to you: a proposed work-item or a consequential step waits for your nod in the Feed.
The effect, after a few weeks, is that “did anyone follow up on that” stops being a question you ask people in meetings. The follow-through is on the page, and the Teams that own it are the next thing worth understanding.
Common questions
Does YAGNI replace my calendar app?
No. Your events stay in Google Calendar. YAGNI reads the agenda and prepares against it, so what you see in the workspace is your real calendar with the preparation already done.
What does preparation actually look like?
Before a meeting, @yagni has the relevant picture current: the account's history for a sales call, the open work for a planning session, the thread that prompted the invite. You walk in having read it, not hunting for it.
How is a work-item different from a Linear issue?
A Linear issue is a connector object that lives in Linear and stays there. A work-item lives in Work and can span Teams: one item can reference the Linear issues, the Gmail thread, and the HubSpot deal it touches.
Who creates work-items?
Both of you. You can file one directly, and Teams propose them when something cross-cutting needs tracking. Proposed items land amber in your Feed for a yes, a no, or an edit.