Comments on: Matrix Communication not Matrix Management http://www.elilopian.com/2009/04/06/matrix-communication-not-matrix-management/ Creating better software Fri, 20 Aug 2010 20:27:04 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Eli Lopian http://www.elilopian.com/2009/04/06/matrix-communication-not-matrix-management/comment-page-1/#comment-35140 Eli Lopian Thu, 16 Apr 2009 07:38:37 +0000 http://www.elilopian.com/2009/04/06/matrix-communication-not-matrix-management/#comment-35140 Wouldn't it be great if there is real empowerment. This is what I am suggesting. Using Integrity, Team A can now tell their manager, We won't do a-b-c, but we will do Team-B's addition. The manager can then tell his manager, and he will tell his manager, who might say: "Great initiative" or he might say "To reach our goals, it will be better for the company to do <something-else>". There isn't the immediate: "No, we can't do it" but a positive "This is how we can do it" Wouldn’t it be great if there is real empowerment.
This is what I am suggesting. Using Integrity, Team A can now tell their manager, We won’t do a-b-c, but we will do Team-B’s addition. The manager can then tell his manager, and he will tell his manager, who might say: “Great initiative” or he might say “To reach our goals, it will be better for the company to do “.
There isn’t the immediate: “No, we can’t do it” but a positive “This is how we can do it”

]]> By: Travis Illig http://www.elilopian.com/2009/04/06/matrix-communication-not-matrix-management/comment-page-1/#comment-34956 Travis Illig Mon, 13 Apr 2009 21:52:09 +0000 http://www.elilopian.com/2009/04/06/matrix-communication-not-matrix-management/#comment-34956 I think the only flaw in this story is the discussion between Team A and Team B. What I've seen is it usually goes: ... Team B: "This is critical for our development, but we can use it only for ourselves" Team A: "The company will benefit from it, but we are already overstretched and have no bandwidth to accomplish what you're asking for. You will have to wait or request management to re-prioritize projects." Team B: "Will you let us modify the code?" Team A: "No, because we are ultimately responsible for the health, features, and performance of that particular library." Team B: "...um..." The happy path conversation of easy re-prioritization just between the two groups only happens in small companies where there's no heavy process or ownership. Again, that's just my experience. I think the only flaw in this story is the discussion between Team A and Team B. What I’ve seen is it usually goes:

…
Team B: “This is critical for our development, but we can use it only for ourselves”
Team A: “The company will benefit from it, but we are already overstretched and have no bandwidth to accomplish what you’re asking for. You will have to wait or request management to re-prioritize projects.”
Team B: “Will you let us modify the code?”
Team A: “No, because we are ultimately responsible for the health, features, and performance of that particular library.”
Team B: “…um…”

The happy path conversation of easy re-prioritization just between the two groups only happens in small companies where there’s no heavy process or ownership. Again, that’s just my experience.

]]>