Escalation: Difference between revisions

Escalation (view source)

341 bytes added , 22 May 2018

no edit summary

82,891

edits

Revision as of 10:34, 21 March 2018 (view source) Amwelladmin (talk \| contribs) No edit summary ← Older edit		Revision as of 08:08, 22 May 2018 (view source) Amwelladmin (talk \| contribs) No edit summary Newer edit →
Line 5:		Line 5:

	Usually as a result of some wild goose chase convened by [[sales]] to chase [[revenue projection\|illusory revenues]], and the fact that they've come to you means they've failed to persuade a more cautious soul and they think you’re a soft touch.		Usually as a result of some wild goose chase convened by [[sales]] to chase [[revenue projection\|illusory revenues]], and the fact that they've come to you means they've failed to persuade a more cautious soul and they think you’re a soft touch.

			Working theory: the '''fact''' of an escalation—the very interposition of an approval step in, itself, in which one piece of the [[meatware]] shunts a problem to another piece of the [[meatware]]—causes more in aggregate delay, confusion, aggravation and second-order bureaucracy than is ''ever'' solved by the resolution it delivers.