Organizational Development: A Manual for Managers and ... - FPDL
Organizational Development: A Manual for Managers and ... - FPDL
Organizational Development: A Manual for Managers and ... - FPDL
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
‘A procedure is a series of activities, tasks, steps, decisions, calculations <strong>and</strong> other processes,<br />
that when undertaken in the sequence laid down produces the described result, product or<br />
outcome. Following a procedure should produce repeatable results <strong>for</strong> the same input conditions.<br />
For this reason, <strong>for</strong>mal written procedures are usually used in manufacturing <strong>and</strong> process industry<br />
operations to ensure safety <strong>and</strong> consistency.’ (www.en.wikipedia.org).<br />
Procedure, as a kind of institutionalized stereotype behaviour, may be <strong>for</strong>mal or in<strong>for</strong>mal. It<br />
constitutes a part of the structure not because it is <strong>for</strong>mal, but because it is stable <strong>and</strong> it woks.<br />
Actual procedures may produce great differences in seemingly the same organizations. Imagine<br />
one department where a clerk, when he needs some supplies, may go to the store <strong>and</strong> get them,<br />
on his account <strong>and</strong> responsibility. In another department he should wait a week be<strong>for</strong>e the boss<br />
returns from a business trip <strong>and</strong> allows him to do so. Are these structures the same? Or, another<br />
example, in one organization a client can get a decision straight from the front desk officer, <strong>and</strong> in<br />
another firm he should apply to the boss when the boss has time to listen him. Is it different?<br />
Any organization possesses a number of procedures, which are more or less determined, <strong>and</strong> this<br />
‘organizational software’ is an important aspect of a structure.<br />
Formal <strong>and</strong> real structure<br />
Structure is vitally important because it predetermines the basic emergent features of an<br />
organization. That is true in terms of the actual physical structure of an organization, which<br />
encompasses both <strong>for</strong>mal <strong>and</strong> in<strong>for</strong>mal relations <strong>and</strong> interactions between components.<br />
No single <strong>for</strong>mal structure is relevant <strong>and</strong> specific enough to make an organization live. As in a the<br />
case of the ‘Italian strike’, any serious attempt to operate strictly in accordance with given <strong>for</strong>mal<br />
descriptions <strong>and</strong> instructions (<strong>and</strong> do nothing that is not provided in the instructions) would block<br />
natural processes <strong>and</strong> bring any organization to the verge of collapse. Organizations remain alive<br />
not ‘in spite of’ in<strong>for</strong>mal interaction <strong>and</strong> activities, but to a large extent due to them. The more<br />
primitive <strong>and</strong> irrelevant the <strong>for</strong>mal structure is – the more important the role of the in<strong>for</strong>mal<br />
structure remains. In some cases from our practice, the most effective urgent measure to help an<br />
organization at the edge of a catastrophe was just to abolish the <strong>for</strong>mal structure <strong>for</strong> a while, thus<br />
allowing natural self-organizational processes to accelerate <strong>and</strong> rescue the situation.<br />
Paradoxically, the <strong>for</strong>mal structure is usually given much more attention by top management. It is<br />
more or less defined, at least partly pictured in charts, with perhaps another part described in<br />
internal regulations <strong>and</strong> instructions. When something goes wrong, management, if not lazy, tends<br />
to revise this <strong>for</strong>mal structure <strong>and</strong> find a way to improve it. On the other h<strong>and</strong>, I’ve met many<br />
46