
I like my business models to be good for both ANALYSIS and for DESIGN. To capture what is and/or to describe how it ought to be. I also like them to be scalable, and work from the micro to the mid to the macro. The little picture to the big picture.
So in the graphic above the framework on the left is what is scalable from the entire Enterprise - down to the department - to teams lower than that - whatever. Top to bottom. Where the top and mid levels are simply "roll-ups" from the lowest level you start at. And IF you eventually applied this everywhere in your Enterprise - and I don't think that is typically wise ROI-way - you'd be able to roll up or slice and dice the data any which way.
Whether we're at the level of Enterprise, Business Unit/Division, Function, Department, Team, Sub-Team, etc., etc. - the data set for each job/position/role is framed the same way. Only the specific data in the frame vary. The frame starts by layering the data into that relevant to Leadership, Core Processes
both performance and management, and Support areas - see the next graphic.

In the model there are Enterprise "Systems" made up of multiple "Processes" made up of Stages/ Phases/ etc. The term AoP can exist at any of these levels. The "AoP - Area of Performance" thing is a concept for dividing the whole into logical segments - a divide and conquer tactics if you will, when the strategy calls for segmentation.
Here is the next level of definition for those 4:

Here is the place where I start - but not end - in terms of analyzing for - the chunks of work that the Target Audience is involved in - in Task Performance - where they own some responsibility to contribute to an Output. An Output for which we have defined the formal and/or informal "measures" that all Master Performers have pretty much figured out.
Here is the big picture of that framework/model used for analysis and/or design.

When you look at the Leadership level - you see things that are typically the province of upper management.

When you look at the Core level you see two workstreams going on: management's and the individual contributor/ teams/ x-functional team. In fact that second workstream in gold in the next graphic may be owned by the department being modeled - or owned by some other department - and the department being modeled is simply providing support.

In the graphic above the focus (in gold) is on the
processes being managed - where the graphic below the focus (in gold) is on the
management of those processes. These are more typically "the province" of first line supervision/management.

The last level - the Support level - is the province of middle management.
And all levels of management are involved in some small or big way in each level of the model.

I simply use this with groups, orienting them to it as one way to divide their world up. The acid test for them - that I've learned to facilitate - is the likelihood that the LEADERSHIP, the CORE Management, and SUPPORT TRAINING would probably be the same for everyone - and the Core PROCESS TRAINING would be unique to each department, team, sub-team and/or individual contributor.

Does the model pass your acid test for looking at Leadership and/or Management from a process performance perspective?
If it works for you - you might like my free PDF book: Management Areas of Performance - available at
http://www.eppic.biz/
Early Book Reviewers Wrote:
Mark Graham BrownLarge government and corporate organizations continue to spend money on canned or custom-developed leadership programs that fail to produce effective managers. This book presents a proven methodology for determining the specific management competencies needed for success in your own organization. By using this approach, based on studies of your most effective managers, you will build the foundation of a program that will allow you to select and train a large cadre of effective managers and leaders.
John ConéOne of the great strengths of the book is that it is NOT about competencies.
You make an outstanding point that there is more to the job than just
possessing (or even exhibiting) competencies.
I really liked the book. Now, I have to be honest with you - it surprised
me that I did. I have never been a fan of "workbook" type books that
require me to do a lot of introspection and homework. Maybe that's because
I'm lazy, or maybe because they require me to accept the models in the book
as I go along rather than deciding after I have read it all how well they
will apply to my world. Whatever the case, when I saw how your book was
organized, I figured I wouldn't like the format and then I'd have to figure
out how to tell you that.
But it didn't happen that way.
I think it is because of the way the book is organized, and perhaps also because you keep things relatively simple. You don't ask me to buy into a complicated and unusual model; but one that is pretty straightforward and logical. I also think that using the technique of directing people to the chapters that apply to them the most (as you do in Chapters 4 and 18, for example) prevents us from having to slog through work that we are not sure goes to the heart of our concerns. That is a brilliant move, and I wish more authors used the approach.
Thanks for the chapter summaries. They keep the reader on track and tell us
what you as the author think are the key points of each chapter. The intros
also do a great job of keeping us oriented.
The book reads easily and is very clear and concise.
Judy HaleI do like the way you have grouped the areas of performance. You have developed a useful tool and process to help identify, define, and evaluate managerial competencies.
Margo MurrayHow I spent my holiday weekend ....Actually several enjoyable hours of it were spent reading your new book! Congratulations on completing this comprehensive treatment of an essential subject. Here are some general impressions:
► It will be very useful as a handbook and desk reference for managers, especially newer ones
► I like the flexibility to access and use the sections most relevant to a current role or responsibility
► Some chapters will serve as excellent checklists, for example the troubleshooting ones
I found myself many times thinking, "I wish I had written this book when my management experiences were being tested and improved."
Joe Sener
I like the model. It will help organizations on several levels:
► Clarity of what should be the responsibility of each level of management
in the organization.
► The recognition that different individuals will be better at some of
these AoP's than at others -- and that is not only OK but that diversity
adds strength to the organization.
► A detailed description of the skills required of each role at the
individual contributor line as well as an assay of those skills at the
organizational level.
► A recognition of the time required at the Management Support level which
is seldom, if ever budgeted for by the organization but is just assumed
that we will find the time for it. I believe that upwards of 40% of my
time is spent just managing Human Assets.
Darlene Van TiemTremendous performance management tool! Competence is key to inspiring, challenging, and coaching employees. Every leader should require Management Areas of Performance as part of a performance assessment empowering their managers to develop competencies, thus improving competitiveness and organizational effectiveness.
Comprehensive, well organized, and motivational.
Actually, I think that it is a terrific succession planning, career development, and employee development piece. You have presented, in detail fashion, the full set of competencies. You have not glossed over issues and made it a simple book.
Frank WydraI like where you are going with Management Areas of Performance and I believe it will prove a useful workbook for many who are trying to move beyond training and development and into the bright, glowing work of human performance technology. You can quote me on that, if you so choose.
# # #