YC W21. Better collaboration for product teams in multiple time zones. Exchange video, voice, and screen recordings with your team at the tap of a button.
According to RescueTime, the average knowledge worker checks Slack every 5 minutes 🤯
What a recipe for deep thought and productivity.
Really excited about some of the changes we're working on at PingPong to take this head-on.
https://t.co/XLSkSeLqCr
We're going to be announcing several new product improvements this week to cap off our team's 3-month internal accelerator.
Follow along here: https://t.co/PsCQXdOerZ
#PingPongLaunchWeek
People spend more time communicating at work than almost any other single activity. Don't let network effects decide what's the best solution for your company.
Slack is awful, and it's only getting worse as they load more and more features in it.
The problem is that Slack's essential philosophy is transparency, which is a good philosophy for documentation, not for messaging.
When we first started, our name was Girbil. The first version of the site is laughable: https://t.co/QSGjTUWXF1. @othercrimes helped make our #brand 100x better!
Today, we use https://t.co/yTJQoeTc1M for 50-75% of our team #communication. When we have to send a file or structured text, we use Slack. We love using our own #product to collaborate as we work on it together. #remotework#asynchronous
We wanted to build a communication product that better meets the needs of #distributed product teams like ours—designed first for #asynchronous teams across multiple time zones where it can be hard to get face time. Check it out and give us feedback! https://t.co/yTJQoeTc1M
In #synchronous work cultures, workers are used to having large portions of their day plugged into a flow of just-in-time information like a network. With #asynchronous cultures, workers are used to having large swaths of uninterrupted time to work deeply.
In #synchronous work, people expect contextual understanding in interactions as everyone absorbs context by osmosis in meetings/informal chats. In #asynchronous, it's better to assume little prior context in every communication and refer to documentation/lay it out specifically.
Slack & Teams are not built for #asynchronous teams. You can see this in #design decisions that promote a flow of shallow, quick-scan info demanding immediate responses: 'Enter' sends a message instead of line-breaking; notifications for every message can override do-not-disturb.