Organizational Development: A Manual for Managers and ... - FPDL
Organizational Development: A Manual for Managers and ... - FPDL
Organizational Development: A Manual for Managers and ... - FPDL
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Chapter 1.4 Structure <strong>and</strong> Procedures<br />
The author of this manual had never faced more ‘secret’ things in organizations than their<br />
structures. While the <strong>for</strong>mal construction of an organization is usually known (though not always),<br />
nobody knows how the components actually interrelate <strong>and</strong> interact. The charts of administrative<br />
subordination never give a correct picture even of subordination itself. The real balance of power<br />
<strong>and</strong> influence may be very different. Sometimes the charts reflect what bosses think about who<br />
should report to whom; sometimes even this is not the point.<br />
For many years my younger fellow consultants <strong>and</strong> I did an obligatory job in any organization<br />
be<strong>for</strong>e we designed an intervention <strong>for</strong> it. This job was describing structures. It required<br />
considerable time, but always justified itself. Our consultants usually conducted a lot of interviews,<br />
discussing with each member of the organization (or several representatives of each position if<br />
there were too many <strong>for</strong>mally in the same positions) what he or she was responsible <strong>for</strong>, <strong>and</strong> what<br />
his/her boss was responsible <strong>for</strong>, <strong>and</strong> what his/her subordinates, if any, were responsible <strong>for</strong>. We<br />
asked them to answer how it actually is, not what is written in any <strong>for</strong>mal instructions (which were<br />
often totally irrelevant <strong>and</strong> useless). Of course, the answers were never the same - sometimes to<br />
the extent that not a single point coincided between what the boss was thinking about<br />
responsibilities <strong>and</strong> powers of a subordinate <strong>and</strong> what the subordinate thought about their own<br />
responsibilities <strong>and</strong> powers. So, we used to draw two structures <strong>for</strong> any organization – the one that<br />
we’ve called ‘a view from the top’, <strong>and</strong> another one called ‘a view from the bottom’. Comparison of<br />
these two pictures always gave us very fruitful ideas, <strong>and</strong> allowed us to go straight to the most<br />
tangled <strong>and</strong> vulnerable things that should be sorted out first.<br />
43