Reading and writing fill in the blanks

A report, blog, podcast or document- sharing repository could handle the amount of information, but each would have some feedbacktake-offfast-trackdrawbacks drawbacks . Reports are good for large amounts of data but are not interactive in nature. Podcasts would also be good for the first viewing, but they are static, and the information is not searchable. A blog could be a good answer because it could become a “living” document for team members to defendappenddependsuspend append as more information about the competitor’s product become available. The drawbacks of using a blog in this sceneryscenariooccasionoccasional scenario would be managing hundreds of such blogs being used for multiple topics as well as quickly finding the blog you want in the corporate wiki. The same drawbacks could be in play with standard document-sharing technology when you have hundreds or thousands of emails or documents to handlepaddleriddledeal handle .