Running your day · Lesson 3 of 3

How does YAGNI track Work and prepare your Calendar?

Quick answer

Work is the record of what your Teams are watching, working, and have shipped: by-Team lanes over live work-items, with a case file as the detail view. A staged Decision is answerable right on the case file. The Calendar is the agenda YAGNI reads and prepares against before each meeting.

What is Work?

The record: the cross-Team operating picture of what your Teams are watching, working, and have shipped. It is organized as by-Team lanes over live work-items, so you can read one Team’s lane like a standup that already happened, or scan across lanes for the shape of the week. The rule that keeps it distinct from the Feed: the Feed is the stream of asks, Work is the record. You clear one and consult the other.

What is a case file?

The detail view of a work-item: the history, the linked artifacts, the receipts, and anything currently waiting on a person. Because the record is live, a staged Decision is answerable in place on the case file. Nothing mints a second copy of an ask; answering it here clears it everywhere it renders.

Who sees what in Work?

Your view is your own: one picture across every record you are permitted to see, governed by each Team’s privacy setting. Shared Teams are readable by the workspace, restricted and private Teams by their people. The operating picture composes per reader, so a sensitive lane can exist without leaking into everyone’s view.

What does YAGNI do with your Calendar?

It reads the agenda and prepares against it. The events stay in Google Calendar; what changes is what happens before each one. A planning session means the open work and the case files behind it are current. An incident review means the timeline is assembled. A customer call means the account’s history is ready. You walk in having read it, not hunting for it.

How do the two surfaces work together?

The Calendar tells the Teams what is coming; Work holds what came of it. Preparation lands where you will look anyway, decisions get made in the meeting, and the record catches what was decided, with the Brief citing both. None of it requires you to maintain a tracker; the tracker you already run stays the system of record for its own objects.

Common questions

How is a work-item different from a Jira ticket or Linear issue?

A ticket is a connector object that lives in your tracker and stays there. A work-item lives in Work and can span Teams: one item can reference the Jira ticket, the GitHub PR, and the Slack thread it touches, with the case file holding the whole story.

Can Teams run work on a schedule?

Yes. A Rhythm is a recurring task a Team runs on a schedule, deploy digests, staging nudges, a Monday-morning sweep, and each firing lands on the record. Proposing a Rhythm or changing one always stages for a person's approval, whatever the Team's level.

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 is your real calendar with the preparation already done.

Who creates work-items?

Both of you. You can file one directly, and Teams propose them when something needs tracking. A proposed item is a staged Decision like any other: it waits for a yes, a no, or an edit from the person authorized to answer.

Read enough. Run it.