In the flow of work

The Wings

Development stalls when it lives somewhere you have to remember to visit. The fix is to reach people at the moment they already feel the need. Greenroom waits in the wings and steps out on a cue: a 1:1 on the calendar, a return from leave, a hard conversation booked. Same engine as The Show, surfaced where you already are.

Greenroom
Direct message · Slack
GreenroomApp9:02 AM
You have a 1:1 with Priya tomorrow at 10:00. She is three weeks into her first manager role. Want a two-minute prep from the library?

The Slack chrome is illustrative. The prep is a real Greenroom call, the same engine as The Show, reached through a door you already have open.

Calendar · tomorrow
10:00 – 10:30
1:1 with Priya Anand
Recurring · weekly

The trigger is the moment, not the menu. A calendar event Greenroom already understands becomes the reason to reach out, so the prep arrives before you need it instead of waiting in a catalog you never open.

Cues that bring Greenroom out

New manager

First 1:1 with a report lands on the calendar

Nudges a 30-minute prep before the meeting.

Return from leave

A return date arrives after extended leave

Offers a gentle re-onboarding running order, week one.

Hard conversation

A meeting titled like a tough talk is booked

Surfaces the prep worksheet the day before.

Skill gap

A check-in flags a development need

Drops one small first step into Slack, not a course list.

One engine, several doors

The web app, the Slack nudge, and the calendar prep are surfaces over the same retrieval and grounding core. Build the engine once, meet people through whatever door they already have open. It is the same two-surface pattern I shipped at Airbnb: one core, a web skin and a Slack skin.

See the engine on The Show

The Slack and calendar cards above are illustrative. In production this is a Slack app plus a calendar integration over the existing engine; wiring those live is out of scope for the prototype, but the data contract and triggers are the same ones used here.