A neat development, and I am consistently intrigued and impressed by collaboration tools for teams. As an internal tool, I could see it being constructive in some limited scenarios. If anybody can mention instances where using something like this or Google Docs with multiple people at the same time, I'd love to hear your stories to level-up my understanding of use-case scenarios.
But...in my business experience with teams across a few different industries, however, I'd say "No" so fast you'd think I had some kind of inherent bias.
Well, I think I do. The modern conference call, speed of data transfer, and online presentation tools that exist should - and do - work just fine when there is one expert at the controls. Usually that expert was me. Taking disparate pieces from different people and getting them in right, often in real-time, was part of my job. Another part of my job was helping people "talk through" what they intended to communicate, and help phrasing and spelling along the way.
Examples include responses to RFPs in a Word template, or any one of the development phases in a PowerPoint 11x17 or slide deck. These would eventually be client-facing, and could be done on the fly if so desired (rather than input/output versioning, often hosted on SharePoint). Then, when finished, it was suitable for production.
I don't see how Paper is an improvement on this process, but rather, a situation of allowing too many cooks in the kitchen. Again, I'm only speaking from my realm, and take pride in learning about new things (like JamKazam) that are still developing or even ahead of their time. YMMV.
But...in my business experience with teams across a few different industries, however, I'd say "No" so fast you'd think I had some kind of inherent bias.
Well, I think I do. The modern conference call, speed of data transfer, and online presentation tools that exist should - and do - work just fine when there is one expert at the controls. Usually that expert was me. Taking disparate pieces from different people and getting them in right, often in real-time, was part of my job. Another part of my job was helping people "talk through" what they intended to communicate, and help phrasing and spelling along the way.
Examples include responses to RFPs in a Word template, or any one of the development phases in a PowerPoint 11x17 or slide deck. These would eventually be client-facing, and could be done on the fly if so desired (rather than input/output versioning, often hosted on SharePoint). Then, when finished, it was suitable for production.
I don't see how Paper is an improvement on this process, but rather, a situation of allowing too many cooks in the kitchen. Again, I'm only speaking from my realm, and take pride in learning about new things (like JamKazam) that are still developing or even ahead of their time. YMMV.