82,891
edits
Management consultant: Difference between revisions
no edit summary
Amwelladmin (talk | contribs) No edit summary |
Amwelladmin (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
One of those people with an [[MBA]] who profoundly deaf to the assertion that it is easier said than done, largely because a [[management consultant]]’s role is to say, while some other poor sap is expected to do. | One of those people with an [[MBA]] who profoundly deaf to the assertion that it is easier said than done, largely because a [[management consultant]]’s role is to say, while some other poor sap is expected to do. | ||
In ordinary Euclidian [[space-time]], there is a simple formula — not quite as elegant as ''E = MC<sup>2</sup>'', but close to it — which sets an immutable bound on the minimum time (''t'') required for a management consultant’s output ('' | In ordinary Euclidian [[space-time]], there is a simple formula — not quite as elegant as ''E = MC<sup>2</sup>'', but close to it — which sets an immutable bound on the minimum time (''t'') required for a management consultant’s output (''∞'') to be implemented<ref>Careful: a management consultant’s output is ''never'' in called a “recommendation”: The art of [[management consultancy]] is to carry out countless chargeable hours precisely ''without'' doing that: the key is to elicit ideas ''from your client'' as to what to do, responsibility for which, when inevitably they fail, can safely be laid at the client’s own door.</ref>, which must be longer than the maximum theoretical length (''L'') of the management consultant’s engagement (''e'''). | ||
:''T∞L > e''' | |||
Therefore, the management consultant will be long gone and onto the next job well before it becomes clear that the implemented changes are a disaster, and you won’t see him for dust. | |||