4 ms·

Async Google Docs > async Slack > meetings You can setup a template with all they main points and checklists already in place, then get people to fill it out a

Async Google Docs > async Slack > meetings You can setup a template with all they main points and checklists already in place, then get people to fill it out and collaborate on it. Here's an example with the headlines, each would become it's own section: - Problem summary - Impact - Measure of success - “Why does this happen?” - Current solutions - Ideal scenario - Constraints and needs - Unknowns - Proposed change - Alternatives And checklists for the writers: - On what level, and how detailed I want to describe things? - Did I write details into unrelated sections? - Who is this document for? Do they really know all that stuff I assume? - What impact would this change have on the business? - Can we quantify it? - How do we measure that the change solved the problem? How does winning look like? (ROI, proof of impact) - What is the root cause? (“Why? Why? Why? Why? Why?”) Are we solving the right problem? - Can we break up the solution into smaller chunks to reach the goal faster? - Are we trying to solve a general problem before something specific? - How do people solve this already? - Did we talk to them yet? etc. Then you offloaded all the questions you would have asked anyway to a document.

wcarss 6y ago
This is a great template! I have a personal theory about extending what you wrote above: Async verbal meetings > Async Google Docs > async Slack > meetings ...and I'm writing an MVP for a tool to do it[1]! I hope that a lot of people will run async verbal meetings and do team-wide chats via asynchronous audio in the near future, because it's much more convenient and comfortable than long, synchronous video chats or laboriously editing text messages for technical content and tone. In most ways, my MVP is just like IRC or slack, but it lets you also send audio, and it auto-transcribes the audio as a chat message, with a play button beside it. I think meetings are one of the biggest use cases for a tool like this, so building some default structures like the above and publishing them out as artifacts is certainly in the milieu of ideas I'm trying out. 1 - https://heysync.chat https://heysync.chat

wcarss 6y ago

This is a great template! I have a personal theory about extending what you wrote above: Async verbal meetings > Async Google Docs > async Slack > meetings ...and I'm writing an MVP for a tool to do it[1]! I hope that a lot of people will run async verbal meetings and do team-wide chats via asynchronous audio in the near future, because it's much more convenient and comfortable than long, synchronous video chats or laboriously editing text messages for technical content and tone. In most ways, my MVP is just like IRC or slack, but it lets you also send audio, and it auto-transcribes the audio as a chat message, with a play button beside it. I think meetings are one of the biggest use cases for a tool like this, so building some default structures like the above and publishing them out as artifacts is certainly in the milieu of ideas I'm trying out. 1 - https://heysync.chat https://heysync.chat