Comments on post “Quip Chat Rooms”
Jordan Cooper
@jordancooper · CEO, Wildcard
Well, I'll start by saying that Quip is my favorite product. I use it every single day and it's my command center. That said, I'm not sure if I'm in the minority, but for me quip is definitely and intentionally an asynchronous environment and use case. Creating documents requires uninterrupted thought and attention...it is an exercise of minutes or even hours, not seconds...and i think the collaboration model prior to today honored that element of the use case. to me chat is a synchronous use case that doesn't really fit into my use case and mindset when using quip. @btaylor how does chat, as opposed to the prior messaging/collab features, supposed to fit into the document creation workflow?
5sharetweet・
Bret Taylor
@btaylor · CEO, Quip
@jordancooper That is a very insightful question - it's something we talked a lot about in building this product.
In our experience, teams use a combination of asynchronous, thoughtful, permanent forms of communication (wikis, documents, etc) and synchronous, ephemeral forms of communication (chat).
With Chat Rooms, we tuned the way notifications work to recognize the differences between the two modes of communication. You can have tens or hundreds of Chat Rooms without being overwhelmed. But the power comes in the integration. You can have an ad hoc chat discussion about a new design and, with the click of a button, start a design doc with everyone in the chat. We think the experience is greater than the sum of its parts because both forms of communication are important, and we think they should work seamlessly together.
2sharetweet・