fred_h

3 ms·

1. 1.▲
   by fred_h 2y ago

   :wave: Great to hear from you, Jesse — and so interesting that we’re both still thinking about these same challenges all these years later. Collaboration is tough to get right, and we’ve definitely heard plenty of painful stories along the
2. 2.▲
   by fred_h 2y ago

   We do! In theory, we support infinite nested threads within conversations. In practice, we found that most folks don't go deeper than 3 levels. However, the functionality is there.
3. 3.▲
   by fred_h 2y ago

   Thanks for flagging this use case for us and agree that Zoom/Teams are better suited for presenting vs supporting. To your specific points: #1 makes a lot of sense and I sense the "low friction" part of this is the key distin
4. 4.▲
   by fred_h 2y ago

   Appreciate the feedback on this. We do want to focus folks on the product's value prop and remove distractions. I wouldn't say we are attached to the animations by any means and will have a chat with our team. Cheers.
5. 5.▲
   by fred_h 2y ago

   Thank you for the feedback. That’s exactly the idea. We see it as "write once, share everywhere." Conversations, meetings, and decisions can generate useful context, and having summaries automatically show up right where people ar
6. 6.▲
   by fred_h 2y ago

   Appreciate you reaching out about the summarization feature. Teams have been making use of it to save time. They like jumping directly to key moments of the meeting and also outright skipping meetings.
7. 7.▲
   by fred_h 2y ago

   Thanks! We’ve definitely put a lot of thought into making emdash feel smooth, intuitive, and frictionless. We are constantly looking at all the seams where pieces connect and making sure they fit tightly. We probably over-invested in some d
8. 8.▲
   by fred_h 2y ago

   Hi, Fred here – I’m one of the founding team members. Thanks for the comment. First, to the question about team sizes. We view "Startups" as generally teams with <25 users, followed by small/mid-sized "Growth" co