Tags:
create new tag
, view all tags

Email Eliminator

I'd like to use email for communication with external clients and move all internal communication to a wiki. Here are the assumptions - work is project driven, thus, once a project is started, all inter-company communication should be contained within a wiki instead of email. When questions arise in a project, a project manager generates a question from within a project page and it is sent to 2 places, 1) the project manager's personal page entitled "unanswered questions" and 2) to the person responsible for answering the question (manager, co-worker, etc.) personal page entitled "unanswered questions". When the person responsible for answering the question provides an answer, they mark the question as done and it disappears from their "unanswered questions" page, this same question also automatically disappears from the project manager's "unanswered questions" page and the original question along with the answer now appears on the project manager's page entitled "answered questions". When the Project Manager now views his "answered questions" page, they can review the answer, mark it "done" and it disappears from the "answered questions" page and now the answer appears on the project page. If a task or another question is generated based on an answer, another question or todo can be done from the project page. The reason that the "answers" should not go back directly to the project page is that you have no way of knowing if an answer was provided unless you check the project page, or an email is generated when an answer is provided....but I don't need any more emails:), so this is why the answers all go to a single page for an initial review. That is, the need for "unanswered questions" and "answered questions" pages is to keep all asked and answered questions out of my email inbox clutter. These "questions" pages should have filters - project, from, due date, etc.

If something like this has already been implemented, please let me know how it is done. Thank you.

-- DonCrawford - 28 Nov 2005

Please remember, in its essense, a wiki is more edit-and-refine, than it is send-and-forget. If you are after something which handles "questions" and "answers", a wiki might not be the right tool.

For ticket-type stuff in large volumes, I have had success using RT (http://www.bestpractical.com/rt/) - it can be both e-mail centered or web-centered, according to your preference, and if you are not going to refine anything, just handle small bits of information, it tends to be a rather quick way of handling things. Bugzilla (http://www.bugzilla.org/) is another way to go, named persons are the center of everything with this tool.

If you think you might want to go in a edit-and-refine way still, try visiting the Bugs web of the Dakar release at http://develop.twiki.org/~develop/cgi-bin/view/Bugs/WebHome, or other twiki based bug webs, i.e. http://www.lavrsen.dk/twiki/bin/view/Motion/BugReports for inspirations on a solution.

-- SteffenPoulsen - 28 Nov 2005

BasicForm
TopicClassification BrainstormingIdea
TopicSummary Replace inter-company project related emails with wiki. Questions, answers and other correspondence related to projects are kept in wiki, not in email.
InterestedParties

RelatedTopics

Edit | Attach | Watch | Print version | History: r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r2 - 2005-11-28 - SteffenPoulsen
 
  • Learn about TWiki  
  • Download TWiki
This site is powered by the TWiki collaboration platform Powered by Perl Hosted by OICcam.com Ideas, requests, problems regarding TWiki? Send feedback. Ask community in the support forum.
Copyright © 1999-2017 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.