When you are working on getting the details right for your SharePoint projects, you need to produce, share and get feedback on a number of key artefacts. Things like wireframes, navigation maps, and content taxonomies.

SharePoint projects for large organizations can be a real political minefield.

In this week’s installment, you won’t see any Mind Mapping as I describe my approach to explaining the meaning and value of metadata to stakeholders (Site owners, content owners and contributors).

Brainstorming with MindManager. Once the context was set, we started a series of brainstorming workshops and targeted each workshop to a specific area such as collaboration or records management. Because there was a lot of overlap, we weren’t very strict about enforcing the topic areas

After my initial introduction to mind mapping with MindManager, last week I introduced the idea of using mind mapping techniques for Building Navigational Taxonomies

Here are the articles and events scheduled for this week at EndUserSharePoint.com.

I use Mindjet’s MindManager for Mind Mapping. There are other options out there, but I’ve been very happy with MindManager
Designing the navigation of your SharePoint site is a task that can be difficult and drawn-out. There are often competing visions of how the site should look and political pressures from managers who want to ensure that their place in the hierarchy is as prominent as possible. By default, there is often a temptation to have the structure of the site mirror the structure of the org-chart. This may seem easy at first, but will cause problems in the long run.

MindManager (MM) has changed my life as a SharePoint consultant, and I want to show you how you can use it for:
- Building navigational taxonomies
- Brainstorming requirements and project prioritization
- Building document and site taxonomies