Requisite Organization – Endlessly Misunderstood
By Michelle Malay Carter on April 21, 2009
Requisite Organization is a meta-model created by Elliott Jaques.? When people oppose it, I generally find their opposition to be based upon misunderstanding.
A client who is undergoing a Requisite Organization implementation received the following question from an employee, and I helped craft a response.? Hierarchy bashing is en vogue these days, but what is the basis for it?
With more companies moving away from hierarchy-type organizations, how is a deeply more pronounced hierarchy at ClientCompany going to make it more effective?
What Requisite Organization is NOT
This question is based upon an untrue but common?perception. ?Requisite Organization is not about creating a more pronounced hierarchy. Too many layers within an organization slows down decisions and confuses people, but too few layers is not the solution?either.??Having too few layers?impedes understanding and leaves some lost and others left to cover multiple layers of work.
What Requisite Organization IS
Requisite Organization is about understanding hierarchy and building one that will facilitate work and communication.? If you are in the Carolina area, why not join me for a three hour introductory Requisite Organization course on June 6?
I will post my specific response tomorrow.? I’m OK.? You’re OK.? Let’s fix the system.
Are you confused about Requisite Organization?
Filed Under Organization Design, Personal Observation, Requisite Organization
Subscribe in a reader