Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Replace Kickoff with async updates in #internal-announcements #303

Open
DouweM opened this issue Jul 25, 2022 · 5 comments
Open

Replace Kickoff with async updates in #internal-announcements #303

DouweM opened this issue Jul 25, 2022 · 5 comments
Assignees

Comments

@DouweM
Copy link
Contributor

DouweM commented Jul 25, 2022

The Kickoff is currently a recurring meeting for the whole team, but as it is mostly one-directional communication without much interactive component, there's no need for it to be synchronous:

  • FYIs, Discussions, and department priority updates can all go into #internal-announcements, with links to projects and issues where more context can be found and questions can be asked
  • Thanks can go into #thanks and #internal-thanks
  • Product Kickoff ("what we're working on this week"), which is currently livestreamed, has limited value to the community as it's not actionable. Getting community feedback on the upcoming roadmap is more effectively done through Office Hours, and the engineering team can learn about each others' issues in their (bi-)weekly Eng Sync.
  • Release Party & Demos is still valuable, and this can directly follow the Social Call without the Kickoff in between. These still need to be documented: Document synchronous release call before/after company kickoff in handbook #54

As it's still good for department leads to make sure their priority boards are up to date each week, and for the team to know what departments are working on to push the company priorities forward, leaders will be expected to post updates in #internal-announcements every Monday. These can just be a link to the appropriate GitHub project with 1-4 issues highlighted.

@DouweM DouweM self-assigned this Jul 25, 2022
@aaronsteers
Copy link
Contributor

aaronsteers commented Jul 25, 2022

@meltano/leadership

For each Dept. head's announcements, what do folks think of setting up Geekbot prompts and pings similar to how we have #virtual-standups for the engineers? I'm happy to help set that up if others would like to use it.

I prefer this approach because it feels like a nice balance of structure and ad-hoc and we can program in the right prompts without writing free-hand each time. (As an aside, Geekbot also seems to pickup retroactive edits which is nice for fixing typos after the report is published.)

@tayloramurphy
Copy link
Contributor

@aaronsteers I quite like that - having an automated reminder will be super useful. What do you think of having a ping on Friday and an additional ping on Monday morning?

@aaronsteers
Copy link
Contributor

aaronsteers commented Jul 25, 2022

@tayloramurphy - Yeah, that sounds great. I'll set it up. With the caveat that we can iterate on it and see what works well (or doesn't) for each team.

UPDATE: I've started a automated report with Geekbot here: https://app.geekbot.com/dashboard/standup/119541/view

And I've started a thread in #leadership for further discussion.

@DouweM
Copy link
Contributor Author

DouweM commented Aug 1, 2022

@therebbie Can you please update the handbook as appropriate? I think it would be good to mention this on the Leadership page, and refer to the Geekbot bot that asks for updates. And the strong recommendation to include links to the GitHub project and specific issues.

@DouweM DouweM assigned therebbie and unassigned DouweM Aug 1, 2022
@therebbie
Copy link
Contributor

PR on the above changes...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants