Thread by @SergioRocks

I've been a Remote CTO for several years.

Many people have asked me what tools I use to manager my Remote Teams.

I rely on these 7 tools to make my team's work as async as possible.

A thread 🧵

I committed to "open source" my knowledge on Twitter in 2022.

I'll deliver it through frequent threads just like this one. Follow me to stay in the loop.

https://twitter.com/SergioRocks/status/1484569167466569731

These are the 7 core tools I use to manage my remote teams.

For context. As a Founder & CTO, my teams are mostly composed of:

- Software Engineers.

- Product Managers.

- Designers.

- Data Scientists.

- Occasionally I've managed also ops, customer success and sales teams.

- @NotionHQ -

As long term memory documentation.

For big and small things like:

- OKRs.

- Roadmap.

- Feature specs.

- Meeting notes.

- Standups.

- Release plans.

- Retros.

- Etc.

@NotionHQ - @MiroHQ -

For visual support in collaborative meetings and for static visuals to be linked in Notion.

Things like:

- Ideation and roadmapping.

- User journeys and interaction maps.

- Process workflow and such visual documentation.

- Anything that demands a "white board".

@NotionHQ @MiroHQ - @loom -

For screen recordings and product demos to be linked in Notion.

Things like:

- Product demos.

- Bug reports.

- Competitive analysis.

- Any onboarding materials that would required repeated 1:1 meetings otherwise.

@NotionHQ @MiroHQ @loom - @Jira -

For task level information.

- Feature specs from Notion, are broken down into stories in Jira, and assigned to team members.

- Planning poker happens async in Jira. Used to happen in Slack.

- Integration with Github for PR review nudges and dependency visualisation.

@NotionHQ @MiroHQ @loom @Jira - @Zoom -

For meetings in general.

- Meeting agenda should go in Notion.

- Meeting notes should be added live in Notion.

- Action items should go in Notion and assigned during the meeting.

- For meetings that look like a transfer of information -> Record and link in Notion.

@NotionHQ @MiroHQ @loom @Jira @Zoom - @github -

For anything code base.

- Repos

- CI / CD pipelines

- PR reviews

- Etc.

@NotionHQ @MiroHQ @loom @Jira @Zoom @github - @SlackHQ -

There are two main uses to Slack:

1. A communication platform, for both sync and async stuff. Info should be shared using Notion links. Slack is not a long term memory!

2. A notifications central. Tags on Github, Jira and Notion should trigger slack notifications.

@NotionHQ @MiroHQ @loom @Jira @Zoom @github @SlackHQ If you enjoyed reading this thread, please retweet the first tweet, so that more people can learn from it.

@NotionHQ @MiroHQ @loom @Jira @Zoom @github @SlackHQ I'll be sharing my knowledge on twitter, by publishing frequent tweets and threads.

Follow me and stay in the loop 👉twitter.com/SergioRocks

Follow us for daily tweets and threads on remote work!