Our readings on site maps and flowcharts both mentioned that how you organize and design them can determine how well they are interpreted and used. The authors mentioned making sure that the design you pick matches the structure of the web site you are representing. For example, using a hierarchical site map for a hierarchical site, a web-like site map for a site that has many different offshoots, or a clustered sitemap for a site that has several different groups of products.
The second portion of the Brown (2011) articles go into how to properly present your design in a meeting. Depending on the audience, one design or perspective might explain your goals for the site more clearly. For example, in my site map I highlighted all the pdfs in gradient color in order to get an idea across the whole site of how many there were, and whether that was too many for the user to deal with. As I was working through the flowchart (as a user that wanted to learn more about the Downtown Bloomington Inc. organization), I found that one of the aspects I thought needed to be taken out (because it was listed on 2 separate pages) really needed to be left in. I discovered that completing flowcharts from many user perspectives can help you make sure you are meeting the user’s needs, even if they do not visit all of the site’s pages.