Hacker News Reader

Agreed. Providing structure around an existing workflow for a target group is exactly what the doctor ordered... but even that's a tough nut to crack. One of our hopes in exploring existing workflows is to identify both winners and losers around specific use cases. Thanks for the thoughtful response.

View on HN

The problem with this approach is that there are as many workflows as there are organizations/people?

There are, yes.

But there are lots of common patterns (i.e. email to discuss details with colleagues after a new updated document is published). Supporting each individually would never work but observing and supporting the most common workflows within a group or diverse groups is a great way to create a compelling product imho.

Reply on news.ycombinator.com