I am wondering what people use for terminology regarding sitemaps/interaction flows in regards to communicating deliverables to people who don't have an interaction design/information architecture background. I am using sitemaps/interaction flows both and I find that the PM's are getting confused on what the terminology is, so I just want to settle on one term to simplify things for them.
I always associate site maps with "content" and associate interaction flows with "application design" or "transactions". However, essentially there can be a lot of interchange between the two, particularly if you have an application within the context of your content. Regardless of what type of design I am doing,
I still use the same notation for both sitemaps/interaction flows (I've settled on Jesse James Garrett's visual vocabulary notation, which is excellent by the way) and they are both communicated to the product manager/development/profressional services in the same format, and often mixed, particulary if the content has a transaction in it. They are often mixed, depending on what the content is (we have a hierarchy for an ecommerce storefront and transaction for purchasing content).