Closed
Sigrid’s onboarding doc is ready
Marte finished it this morning. I’ve told Sigrid, since she asked on Monday.
One request, start to finish
Asked
Helga asks Henrik for the pricing copy in #launch, due Friday.
Noted
Otmar notes who owes what to whom, and by when. Nobody has to tag him.
Nudged
No reply, and the date is close. He checks in with Henrik once, with a link to the message.
Done
Henrik ships it. Otmar closes the request and lets Helga know.
And a whole week of them.
An example week for Henrik’s team of six. Every dot is something one person asked another for, in Slack or Telegram. Watch which ones need him.
In an example week, Otmar noticed 38 requests. 33 closed on their own, 5 needed one nudge and then closed, and none slipped.
A colleague who remembers what everyone asked for.
You have seven requests from teammates, and three are due tomorrow. I can draft the two that only need a yes, and ask Marte whether hers can wait until Monday.
Reading seven requests
Anders: Can I take Friday off?
DraftYes, enjoy it. I’ll let the team know.
Solveig: Does Thursday at 14:00 work for the demo?
DraftYes, Thursday at 14:00 works.
Marte: Feedback on the brief by tomorrow?
NextI’ll ask Marte whether Monday works.
The Berlin partner raised their Team plan to €49 and dropped the setup fee, so we’re now €6 cheaper a month. I’ve put a comparison in Helga’s notes for this afternoon’s call. Want me to draft the talking points?
Used 0 tools
| What | Berlin partner | Us |
|---|---|---|
| Team plan | €49 a month | €43 a month |
| Setup fee | None | €200, waived on annual |
| Annual plans | Two months free | Two months free |
Anders spotted a typo on the billing page, so I opened merge request !214 with the fix. Shall I merge it, or would you like someone to review it first?
Used 0 tools
Solveig sent the October invoices to the accountant, so I’ve marked it done and let you know, since you asked for them.
Here’s your week: six open requests, one at risk. I’ve put that one first.
Henrik’s week
Your part takes one tap.
When something gets done
Swipe it away. Whoever asked has already heard.
When it’s your call
One tap, and he does the rest. Anything that leaves your workspace waits for you first.
Merge !214, the billing page typo Anders found?
One line, and the checks pass. A merge to main waits for a person.
Tell Helga the pricing copy will be Monday?
It’s due Friday, and #launch has been quiet since Tuesday.
Send the reply to the Berlin partner?
I drafted it from Helga’s notes. It leaves your workspace, so it waits for you.
Nothing waiting on you – new decisions show up here.
Ask him anything.
About your team or the world outside it. He searches your channels, docs and repositories, reads the web, and answers with a link to every source.
He works where your team already talks.
- Slack
- Reads the channels you invite him to, and talks to each person in direct messages.
- Telegram
- Joins your team groups, and keeps a private chat with anyone who starts one.
- Git
- Follows issues and pull requests in GitHub or GitLab, so a request closes itself when the work ships. Opens a pull request himself when a fix is small.
Careful by default.
He reads only the channels you invite him to.
Private conversations between teammates stay private. He can’t see them, and doesn’t ask to.
He asks before anything leaves your workspace.
A message to a client, a merge to main, an invoice: each one waits for a person to approve it.
He remembers like a teammate, and shows his sources.
Who asked for what, what was decided, and where it was said. When he needs the details, he reads the thread again instead of keeping copies of your messages. You can correct anything he knows.
Start with your busiest channel.
Connect Slack or Telegram and invite Otmar where requests get lost. From the first message, he keeps track of who promised what.
Open Otmar