Below you'll find a list of all posts that have been tagged as “requisite organization”
When last we left them, the three union men Glacier Metal Company managers had burst upon Elliott Jaques with the brilliant solution that had come to them while drinking: the reason why some people got paid more than others had to do with how long it took to get paid. My fictionalization aside, what made this any more brilliant than …
Let’s face facts: Requisite Organization (RO) means that a lot of people (1) aren’t as “smart” as they think they are, and (2) the system in which they have succeeded is built on sand. And that’s a big reason why RO doesn’t succeed. When people read about work levels and Requisite Organization — especially Bioss’s Career Path Appreciation (CPA) and …
While reading the excellent and highly recommended book by Heath & Heath, Made to Stick, I came upon this passage about Maslow’s Hierachy of Needs: Imagine that a company offers its employees a $1,000 bonus if they meet certain performance targets. There are three different ways of presenting the bonus to employees: Think of what that $1,000 means: a down …
You would think that when you install a successful total quality management (TQM) program, you would see some great side-effects going throughout the organization. But that’s not always true. Installing any new system is tricky and sometimes doing something “good” leads to performance problems.
What happens when people in a meeting are different stratum (per Elliott Jaques’s requisite organization theory), knowing each other well enough to have some experience of each other’s capacity? Who leads? If certain people talk, does the conversation die? Does the meeting have to be facilitated by the highest stratum person? Will it be regardless, at least effectively? This got …
While I indeed met some people who just quite simply don’t understand high mode issues (do they understand mode at all? Cason apparently does which is a great reason for me to one of these days sit down and talk to her. John Morgan, the pastor using RO in Pinon Hills, met with her this week and raved about her.), …
I wrote the following for another site. It will be pretty heavily edited and changed prior, but I’m pretty pleased with it as is. So I’m posting it here for y’all’s enjoyment. I will upload the image files later. They aren’t necessary but you get a good idea of the structural changes that this company underwent. When Mike Thieneman and …
One the biggest problems facing outsourcing projects stems from the cost savings themselves. Most companies determine the size and level of a project or work by its cost. They don’t assign work based upon its strategic value or (following Dr. Jaques and Lord Brown) on a measure of complexity. They simply assign it based on cost. Let’s look at what this does for outsourcing work.
John C. Maxwell provides a great explanation, albeit unknowingly, of what we call “The Theory of Real Boss” in “The 21 Irrefutable Laws of Leadership”.
Software development groups almost always form a shadow hierarchy or pecking order of merit. Elliott Jaques’s theory of Requisite Organization explains why.
