A TCP/IP metaphor

Rob threw me an idea the other day.  It's about the reasons why different project team members need to communciate with different business stakeholders.

He equated project communications to the different levels of communications going on in a TCP/IP process.

TCP/IP?
Think this through: you write a message, software breaks up your message and distributes it, and other layers of the process physically carry electrons pulsing around the globe to your reader where tings are re-assembled, formatting and all.

So what's going on in projects?

Project manager & Sponsor 
Talk about goals and strategy

Analyst & SME/middle managers
Talk about features and process

Developers & users 
Talk about user experience

What's your take on this model?

Photo by skoop CC @ Flickr