At my current gig we are developing IxD for a "bulletin board" feature that allows you to get to the same message record from several different areas of the site.
The current client wisdom is to store the target message pages in a subsection under tab "Z". You can get to message pages from source webparts that may be on several different pages under several different other tabs.
It is not possible to store the message as a part of the webpart (i.e. embedded in the source page) and the client will not open the target message in a separate browser window.
The UX result is that - when you drill down to the target message from Page "A" under tabfolder "X" - the target message is displayed under tabfolder "Z". When you exit the target message page, you return to Page "A" under tabfolder "X". Alternatively, you might get to the same target message from Page "B" under tabfolder "Y". Or even from Page "C" under tabfolder "Z". And so on...
So sometimes the tabfolder of the target message page changes - and sometimes it doesn't, depending on wheere you're coming from.
Does anyone have any insights on whether this "changing context" has any impact on the UX? Do customers get confused? Are there better solutions?