Office hours → team briefing

2 months ago

This presentation was not written. It was asked for. A few hours ago a working session ended, and one sentence turned that session into what you are watching. I will show you the outcomes first. Then the sentence.

Ask

Ask about this presentation

Answers are generated from this presentation.

Chapters

  1. 0:00The session ended.This is the report.
  2. 0:13Office hours,on a real question.
  3. 0:29A series ofworkflow guides.
  4. 0:50The workflow isthe thing shared.
  5. 1:07Slide 5
  6. 1:29Four minutes,not forty linesof scrollback.
  7. 1:50End your next sessionwith a link.
Show transcript

The session ended.This is the report.

Workflow guides · 01

Office hours, then a team briefing. Made by the workflow it teaches.

01

This presentation was not written. It was asked for. A few hours ago a working session ended, and one sentence turned that session into what you are watching. I will show you the outcomes first. Then the sentence.

Office hours,on a real question.

The session

A launch is three days out. The watch site needs its opening content.

THE QUESTION

What does the front page teach on day one?

THE ONE CONSTRAINT

Every piece has to teach something real. No sample reports. No filler.

02

The session was office hours, on a real question. A launch is three days out, and the watch site needs its opening content. We held one constraint the whole hour. Everything published has to teach something real. No sample business reports, no filler.

A series ofworkflow guides.

The decision

Each one takes a session you already run with your agent, and shows it ending in a presentation.

01

Office hours, then a team briefing

02

A pull request, walked through out loud

03

A research session, turned into a briefing

04

A week in review, read from git

03

Here is what came out. A series of workflow guides. Each one takes a session you already run with your agent. Office hours. A pull request. A research question. A week of commits. And each shows that session ending in a presentation. Every guide is made by the workflow it teaches, and you are inside the first one right now.

The workflow isthe thing shared.

Why this shape

Not the slides. The habit that produced them.

A FEATURE TOUR

Explains a product. Watched once, politely.

A WORKFLOW GUIDE

Hands you a habit you can copy tomorrow, in a session you already run.

04

We grilled the obvious alternative, a feature tour. A tour explains a product, and gets watched once, politely. A workflow guide hands you a habit you can copy tomorrow, inside a session you already run. The thing worth sharing was never the slides. It is the workflow.

Slide 5

The recipe
1

Run the session the way you always do.

2

When it ends, do not summarize it yourself. Your agent was in the room.

3

Ask for the briefing. It narrates on your machine, free, and hands back a link.

THE SENTENCE THAT MADE THIS
Present the outcomes of this session and share it with the team.
05

The whole recipe. Run the session the way you always do. When it ends, do not summarize it yourself. The context is already loaded, your agent was in the room the entire time. So ask it. Present the outcomes of this session and share it with the team. That is the sentence. It writes the slides from what it heard, narrates them on your machine for free, and hands back a link.

Four minutes,not forty linesof scrollback.

The handoff

The team opens a link and the decisions are spoken, in order, with the reasoning attached.

WHEN A DECISION CHANGES

Edit that one slide and republish. Only the changed slide is narrated again.

06

What the team gets is this. Four minutes, instead of forty lines of scrollback. They open a link and the decisions are spoken, in order, with the reasoning attached. And when a decision changes tomorrow, you edit that one slide and republish. Only the changed slide is narrated again, so keeping the briefing current costs almost nothing.

End your next sessionwith a link.

Workflow guides · 01

The agent that did the work gives the briefing.

bisque.cloud

07

That is the first guide. Your next working session does not have to end in a wall of text. The agent that did the work gives the briefing. End the session with a link.