How to Recognize Organization Structures: Balanced Matrix

| by Daiv Russell | February 22, 2008
Previously, before 1970, most large corporations were structured in departments. These departments were logical partitions of the company and any given groups of employees reported to the head of the department. After this point, companies began to restructure its employees into a matrix organization, mainly with the intent of developing project managing units.

Lots of different ways to create a matrix organization exist. In any given project, the organizational matrix chosen, aims to serve all managers involved in the project equally. The weak matrix, the strong matrix, and the balanced matrix are the three organizational matrices most often chosen for projects. Let's discuss the pros and cons of using the weak matrix organizational structure.

A Balanced Matrix Structure

There is a wise old saying; absolute power results in absolute corruption. Power struggles occur in all forms of matrix structures. Usually, the result of this type of power struggle will be detrimental to both groups who are struggling, the project and to the business organization as well. Sometimes these harmful effects may not be immediately visible. For example, if one project manager controls another manager and thus, forcing him or her to hand over important team members to aid in the completion of the project, the entire group suffers. It is imperative to find a manner with which to avoid this conflict.

One way to deal with this problem is to create limits in the organization which determines when a manager can control a worker. These strategies should be based on a specific set of circumstances. For example, keeping a rule where a worker will be managed exclusively by the functional manager if a project will last for less than a week's time. In case, the project will take longer than a week, the control will pass on to the project manager. Otherwise, a rule can be made in such a way that a worker should not be employed by a project manager to work on two projects in a row.

A variety of possible rules and structures may be imposed to achieve the goal of balancing power between project and functional managers so that a win/lose condition is avoided. Obviously, the balanced matrix takes its name from the balance of power that results in this structural format.

Daiv Russell is a marketing and management consultant with Envision Consulting in Tampa, Florida. Learn more about matrix management structure at project-management-course.info. Choose the right Project Management Software and optimize your Gantt Chart Use

Article Source: http://www.articleset.com



About the Author

Daiv Russell is a Software Engineering Strategist with Envision Software, a software project management and development outsourcing company committed to helping information technology organizations solve problems, increase revenues, and reduce costs by guiding software development teams through project management chaos. Envision publishes Luminary, a monthly software project management newsletter.
DRussell@EnvisionSoftware.com » Read more articles by Daiv Russell
You are welcome to publish or reprint this article free of charge, provided: