Ask Pipedot: small office collaboration/messaging

by
in ask on (#2V33)
Here's the situation: you've got a small office of 8-20 employees who work in a consulting business and whose main products/deliverables are reports, spreadsheets, occasional CAD drawings, Gantt charts, project plans, and the like. Not only do they produce those things, they receive reports for which they produce comments/observations. Much of what they produce is collaborative or iterative (ie, not necessarily 'live editing' of spreadsheets, but several people must all contribute to a doc over the space of a week or so). To do so, they need efficient means of communication, discussion, versioning, etc.

Needs: document repository, shared editing of many types of documents, a messaging system for internal office communication, "sharing" system that permits clients to upload or download large files, a managed-content "front page" web site, an internal intranet, shared calendars, contacts lists, some sort of system to produce and maintain office policies and procedures, and otherwise manage internal communications and office admin. Some considerations for discussion, so I'm intentionally not specifying: (1) ideally, systems are usable by different OSes. Obviously there are going to be problems ensuring total OS independence. (2) ideally, the system doesn't require full-time online presence. Should a consultant wind up in a basement office with no internet, he won't be totally lost (again, not perfect). Note: no obligation for Free/Open Source software, although they are preferred. The goal here is an office that communicates and collaborates efficiently.

Ten years ago, you'd be sitting in a cube farm, using Microsoft Office and a shared drive and emailing documents back and forth. Later they'd have added Sharepoint. These days, there's been a ton of innovation in these areas, and there's consensus that collaboration-by-email is not fun. And there are lots of new approaches to these age-old problems.

So, how would you do it?

Any comments on alternatives to email? (Score: 1)

by zafiro17@pipedot.org on 2014-11-18 11:32 (#2V40)

Was thinking that actually, Usenet technology is good for team collaboration on a project. With email, you only have access to the messages sent to you since you've arrived on the team, and you miss out on all the history. With an internal NTTP spool, all project conversation winds up in a single location, everyone has access to every message ever sent, and any new employee simply has to take the time to read through the history to see "how we got here." It also eliminates huge problems of attachments (impossible: post them to the doc repository and send a link), storage/replication of multiple mailboxes, and more. On the downside: 80 char hard wrapped, fewer and fewer useful clients, and it's different for a lot of workers who are used to Outlook + Reply All.

"Slack" is supposed to operate the same way, but doesn't thread its replies, which is inexplicable to me. I've found no other good substitutes other than perhaps a good mailing list with archive. Any suggestions for mail archive?
Post Comment
Subject
Comment
Captcha
How many colors in the list white, yellow, pink, brown, sock and snake?