Idea Central

With any project the importance of a central idea/collaboration site is crucial.

1. Establish a central idea store for ideas, questions, requirements, and ramblings. In my past engagements I've used Confluence,  Alfresco, and SharePoint.  Pick something that is easy to use/setup, has integration capabilities with other tools (plugins for issue tracking/management systems, code repository, email, IM, etc), and keep an eye on the license structure (is it 2 dollars a person till you get to 10 users where the vendor  charges $5000 for a license?).
2. Create the layout of the idea store.  If you don't spend the time up front to decide on where notes, design docs, meeting notes, and general ideas will be stored you will end up with a disorganized website where no one can find relevant information.  Create a quick site map or hierarchy diagram of where things will 'live'.  Based on the type of site(development, project, team) the content hierarchy will be different.
   
3. Get the team using it!  Provide a quick training (or create a walk through video and post it for the team to view at their leisure).   Monitor what is being posted to the site, what it is, where it is going, and are there any changes necessary for the structure or labeling used for pages. Pay close attention to how the 'other' communication technologies are being used.  Are folks still sending information directly related to development/requirements over email or IM?  If so, remind the team about the site and where this type of information should live.  The HABIT is the hardest thing to change, if folks are used to communicating all over Lync or IM it is a mindset change, but once the information is available and easy to find weeks or months down the road the whole process will improve.
4. REVIEW the site regularly.  Are things still organized?  Is there information which is outdated and should be moved or reordered?   People change, process change, technology changes make sure you are improving your site over time.

Here is an example site layout  a development team may use to get started:

Team/Project Homepage
    - Development Documentation
              - Architecture/Design Documentation
              - Development Process Document
     - FAQ Page
     - How To Articles
              - how to login to Time System
              - etc
      - Meeting Notes
              - Meeting on 01/01/2016 for Product Vision
              - etc
       - Retrospecitves
              - Retro for Sprint 99
              - etc
        - Links
        - Product Requirements
               - Turn the green button blue
               - etc
        - Scrum/Sprint Documentation
               - Sprint Roadmap Page (showing objectives for next few sprints with linkage)
               - Definition of Done
               - Team Rules