Information Flow and Blogging

Common Statements from the Workforce I wish I knew what else was going on within the organization I wish I knew what was going on with certain key projects I wish I knew how I fit into our technical vision

I wish I knew what else was going on within the organization

I wish I knew what was going on with certain key projects

I wish I knew how I fit into our technical vision

Constraints Workforce members must Complete their tasks Communicate with customers Communicate with management Workforce does not have to Communicate with “outsiders” Keep track of the technical vision

Workforce members must

Complete their tasks

Communicate with customers

Communicate with management

Workforce does not have to

Communicate with “outsiders”

Keep track of the technical vision

Information Flow Currently Other Workforce Team Workforce Team Customer Management No communications required to get job done

Information Flow required to share information Other Workforce Team Workforce Team Customer Management Project blog The project blog is based on a subset of the information shared with the sponsor

Information Flow - side benefits Other Workforce Team Workforce Team Customer Management Project blog Unanticipated contributions from others familiar with similar technologies Opportunities for collaboration Applications of your work elsewhere

Unanticipated contributions from others familiar with similar technologies

Opportunities for collaboration

Applications of your work elsewhere

Information Flow costs Workforce Team Customer Management Project blog Writing a blog is more than just posting project emails Will most likely require a project Wiki entry to describe the basics of the project

Writing a blog is more than just posting project emails

Will most likely require a project Wiki entry to describe the basics of the project

Is it worth it? Can you provide integrated solutions without these interactions?