This Blog presents my "Thoughts About" and "Experiences In" ... ISD and HPT... to Improve Performance Competence ... for the sake of the Stakeholders. - Guy W. Wallace, CPT
I have been publishing and presenting on ISD and HPT - Instructional Systems Design and Human Performance Technology - topics and methods since the early 1980s. Many, but not all of my Blog Postings here are sourced and reworked/recycled from those. For a complete listing of my published articles, chapters and books and my presentations at professional events, please go to www.eppic.biz/about.htm

Saturday, November 29, 2008

1st Three School of PACT Video Podcasts Now Available.

The School of PACT - is "in VIDEO PODCAST session" - anytime you need it/ want it/ gotta have it!















We begin the series with a Podcast Introduction to The PACT Processes. Then a Podcast overview of the 4 Phases of a CAD effort. Then another Podcast with an additional level of detail about "7 Steps for processing of the analysis data" in the Phase 3 - Design - DTM: Design Team Meeting.

All are presented in Blog Post form: with instructional design wrapped around the Video Podcast in terms of preparation for viewing, and what one might do post-viewing. To learn and master and someday coach others. And all are available on Google Video so one might download their own personal copies.

There are over 12 planned in the series.



















PACT is: ISD/ ID/ SAT - Instructional Systems Design/ Instructional Design/ Systematic Approach to Training. PACT includes and is much more than A-D-D-I-E.

PACT is based on a data logic, reducing the wasted efforts at unfocused analysis and design and development - reducing/eliminating "unnecessary costs" - both first costs and life cycle costs.
















My book: lean-ISD covers the PACT Processes for T&D/ Learning/ Knowledge Management - and is available as a free 404-page PDF at http://www.eppic.biz/




















A PDF copy of the first national presentation of the CAD methods using a Group Process, from 1985, is available here.



















Cheers!

# # #

Friday, November 28, 2008

School of PACT 02b - Lesson & Video Podcast - 7 CAD Design Steps















This is the next in a continuing Video Podcast Plus series - "The School of PACT" - on the PACT Processes - and additional related concepts, models, methods, tools, templates and techniques.

There are 7 Design Steps in the CAD Design Team Meeting.

























There are 5 steps to the suggested Learning approach - if you will...but do it any way you choose...

1- Pre-Video Reading Assignments
2- Video Podcast Review
3- Post-Video Readings Assignments
4- Post-Video Application Assignments
5- Review Free Resources Available

You'll need the book lean-ISD - which is available at Amazon.com as a hardbound and/or as a Kindle book - and/or free as a 404 page PDF here.

Note: There are also many PACT resources at the EPPIC Web site and at the PACT Wiki.


School of PACT #02b- 7 CAD Design Steps

1- Pre-Video Reading Assignments
If you've been following this series, read Chapter 12 again - but know that what is described there is slightly different from the Video Podcast.

I'd suggest having read Chapter 1-7 before any of this - IF you haven't done so already.

And then watch the V-Podcast.

2- Video Podcast Review
Here is the Video Podcast - 15:39 minutes/seconds:

video


3- Post-Video Readings Assignments
If you did not do this already in Step 1 - read chapter 12 of lean-ISD.

4- Post-Video Application Assignments
Start listing and organizing your questions. Start a Learning Log (or Blog). Network with others.

Start thinking about the "Beginning-of-the-Beginning/On-Boarding" T&D Path concepts and how that would play out/look for a Target Audience or two that you are focussed on.

5- Review Free Resources Available
At http://www.eppic.biz/ there is a related set of PACT Audio Podcasts available. Also - there are articles and presentations in the Resource tab at that same site.

And the free 404-page book PDF: lean-ISD...

# # #

Thursday, November 27, 2008

Have a safe and happy Thanksgiving! Now, later or every weekend with family and friends!











# # #

Guy W. Wallace’s PACT Facilitation Guidelines: Series Wrap Up & Close

I don't know who started the false rumor that the "group-process" methods were inspired by Deming. I've heard this several times recently. Hmmmm.

Aaarg!!! Pirates covering their trail....

But that is just not true. My quality exposure to Deming was limited in my early years - I was more influenced by Geary A. Rummler, Joe Harless and Bob Mager than by Deming or Juran or Crosby. Especially in what became CAD and then all of the PACT Processes.

And "Group Process" for me goes back to a stalled Video-based Training project in 1980 at Wickes Lumber in Saginaw Michigan - where I was on my 7th version of the Script - when I had reached that point of frustration - so aptly put by Popeye in his immortal words: "That's all I can stands - cause I can't stands no more!"

Here is a Blog Posting about that "origin" for a group process approach to my personal approaches to ISD/ ID/ SAT.

The first two published articles about CAD - Curriculum Architecture Design - both published in 1984 - one in Training Magazine and the other in NSPI's (now ISPI's) P& I Journal - for Performance & Instruction - later becoming Performance Improvement.

Both articles were written in late 1983 and then published in the fall of 1984. That's how long the "submit-to-read it cycle" used to be - back in the day.

















Training Magazine emphasized the Group Process in their version of the article - as they published it - always different from what one submitted - and the P&IJ article focused on the analysis part of the CAD methodology - as I had not developed the formal ADDIE-level of PACT at this point. That happened in 1989/1990. That became MCD - Modular Curriculum Development/ Acquisition.

















Then - back to the early 1980s - I did a presentation at the local Chicago chapter about CAD in 1984 - I then went national and presented at NSPI in 1985: "Curriculum Architecture Design Via a Group Process" - and I did so every-other year for about a decade. Click on the graphic below for a link to that in PDF form.

Then I stopped doing CAD presentations and branched out to other relevant topics to ISD and Performance Improvement. Recently - in the past 5 years - I've done 2.





















I started writing what would much later become lean-ISD - back in the early 1980s. It was originally titled The Curriculum Managers Handbook. In the late 1980s it was titled The Curriculum Product Managers Handbook.

Then I read The Machine That Changed the World - and I saw that what I had done to ISD - as compared to what was being practiced at all of my Client's T&D functions - was to have "leaned" it.

"Reduced it to practice" is what one colleague exclaimed after seeing an internal SWI presentation on it for our recently expanded consulting staff.

I finally got serious about the book in late 1997 and put nose-to-the-grindstone and got 'er done in late 1998 - and then went through a fairly exhaustive review with about 12 early readers/reviewers, including the late Geary A. Rummler - who invested his personal time and energies in developing a different book cover and title - and then surprising me with it. He thought my version of the book cover was too busy - and not to a simple, quick point.

We put it to a vote of our CADDI quarterly newsletter readers - and his version of the book cover won out over mine. The rest is history.

Here is a link to that quarterly newsletter - see pages 18-19 where we announce the contest. Can't get you any closer. And here is a link to my original cover - see page 16. Here is the newsletter where we announce the book going to press. Note the photo of Geary Rummler 2nd to last page. All three of those newsletters were from 1999.

And none of them include references that include Deming. Not linked to PACT, CAD or the group process, or the data architecture of PACT. Those were inventions of mine. And those inventions and reductions to practice happened over time - beginning in 1982 - and were field tested in many projects by myself and others.

Hundreds if not thousands of ISD/ ID/ SAT efforts.





















The 12 Rules/Guidelines for PACT facilitators that I covered in this Blog series - was "sourced from" my writings from back in 1998 in lean-ISD - in Appendices C. And that was sourced from my field experiences in having conducted hundreds of Group Process analysis and design meetings.

The 12 Rules/Guidelines for PACT Facilitators are - and the links to the prior 12 Blog Postings are:

1. Go Slow to Go Fast.

2. Be Declarative.

3. Write Stuff and Post It.

4. Be Redundant by Design.

5. Use the Four Key Communications Behavior Types.

6. Review and Preview.

7. Write It Down and Then Discuss It.

8. Use Humor.

9. Control the Process and the Participants.

10. Be Legible on the Flip Chart.

11. Beware of Group-Think.

12. Assign Parking Lot Valets.

This Blog Post series embellished the original content already published in lean-ISD.

Of Note
In 2002 lean-ISD was recognized by the ISPI Awards of Excellence committee and received an Outstanding Communications Award.

I had also been invited to speak about "lean-ISD" at an ISPI Masters Series session the year before in 2001.

That invitation presentation was also written up as an article by me for publication in 2001 in the PI Journal of ISPI. 17 years after that first Training Magazine article.


















The Group Process is also described in my Chapter (#11) in the 3rd edition of the Handbook of Human Performance Technology in terms of generating both Performance data and Enabling Human Knowledge & Skills/ Attributes/ Values for Performance Improvement - as part of an ISD effort - or not. PACT is a sub-set of my performance improvement methods: EPPI - Enterprise Process Performance Improvement.

And that - EPPI - did not come from Deming either.

Deming didn't use Performance Model and K/S Matrices (or tables, or whatever), and other Attributes/Values - including Consequences (which is part of the Environment and not the Human side of the assests equation in the EPPI models/methods). Nor did he used Event Specs and Module Specs and Lesson Maps and Instructional Activity Specs - by those or other names/labels.

I did. I created all of those - and used those - and linked those - and ...reduced all of that to practice.

In an ISD/ ID/ SAT sense.











While I believe that the 12 Rules/Guidelines of the 12 prior posts in this series are extremely important, there are many other knowledges and skills a great facilitator requires...

Other Tools for Your PACT Facilitator Toolkit
I’ve covered many of the facilitation styles and skills required for conducting PACT Process team meetings. But being a successful facilitator requires other knowledge and skills.

Some of those include having a command of the following mini-processes, often used within larger processes and sometimes used by themselves.

The ones that I’ve found key for my repertoire include
• Process modeling or mapping
• Systematic problem solving
• Systematic root cause analysis
• Systematic decision-making
• Systematic thinking in general

Other key knowledge and skills of a successful facilitator can include general knowledge about how businesses organize, operate, and keep score. This includes general business knowledge on the various functions and organizational structures typical of a modern business.

For example, somebody has to think up a product, somebody has to design and then produce it, and somebody has to process the money transactions and keep the books. In the meantime, others are planning it, hopefully strategically, and continually monitoring it and readjusting the processes and resources as needed.

Knowledge of how businesses are organized might center around the following functions:
• R&D
• Marketing
• Merchandising
• Engineering
• Manufacturing
• Materials
• Purchasing
• Sales
• Distribution
• Service
• Finance
• Human resources
• Legal
• Public affairs
• Customer satisfaction measurement
• Business financial knowledge
- Income statements
- Balance sheets
- Cash flow

Of course, there are many other ways to organize a picture of the business of business. So pick or create one that works for you and your assignment.

Summary
It took me years to develop the PACT Process - beginning in 1982, so that my consultant staff and business partners and contractors could all operate in a common and consistent process manner - with predictable costs, schedules and quality of output/product.

The fact that some of those I have taught directly or indirectly years ago have now chosen to refer to these methods, which I freely share, and have freely shared with Clients since the mid-1980s, as their proprietary methods - and they put their copyright marking on them - and do not acknowledge their real source - is sad.

I know that many do honor my copyrights - for I have seen examples of that that they have sent me. And for that I am thankful.

Thank you to all who do!!!

Cheers!

And - Happy Thanksgiving everyone - whether you are celebrating it today or not!

Again...
This series was sourced and edited/embellished from Appendices C of: "lean-ISD" - a book by Guy W. Wallace - published in 1999 and made available as a free 404 page PDF in 2007 - by Guy W. Wallace, the owner and author of the PACT Processes - at http://www.eppic.biz/


The lean-ISD book's cover was designed by the late Geary A. Rummler in 1999.


# # #

Guy W. Wallace’s PACT Facilitation Guidelines: # 12 - Assign Parking Lot Valets











Guy W. Wallace’s PACT Facilitation Guidelines: # 12 - Assign Parking Lot Valets

I call these “The 12 Rules and Guidelines of Proactive/Confrontational Facilitation for the PACT Processes for T&D.”

They are:

1. Go Slow to Go Fast. 2. Be Declarative. 3. Write Stuff and Post It. 4. Be Redundant by Design. 5. Use the Four Key Communications Behavior Types. 6. Review and Preview. 7. Write It Down and Then Discuss It. 8. Use Humor. 9. Control the Process and the Participants. 10. Be Legible on the Flip Chart. 11. Beware of Group-Think. 12. Assign Parking Lot Valets.

The 12th and last of these is covered in more detail in the following text.

Read them. Use them. Experiment with them. Make them your own.

12. Assign Parking Lot Valets
In a very structured process, it’s a good idea to use a “parking lot” for issues that may not be timely. Post a flip chart on the wall and write “Issue Parking Lot” or something similar on the top, and then add things that are premature, that we don’t intend to address in the meeting, or that we don’t want to forget.

At the end of the meeting, or sooner as appropriate, address them and close them out. Those that remain open will have to be addressed and resolved some other time and some other way.

I usually have two parking lots, one for open issues and one for closed issues, so everyone can see progress in addressing those that can be addressed in our meeting.

But I hate being the parking valet! It seems that I spend so much time parking everyone’s issues that I run myself ragged from one flip chart to another.

So I’ve hit on this device―an improvement if you will. We hand out “stickies” and ask everyone to jot down their own issues and self-park them. On the 1st parking lot - for OPEN Issues.

Then at every review/preview checkpoint, we review what’s new in the open parking lot, and we take the time to see what can be parked in the other lot. Because it has been covered - and we test to see if that is true first. And then as appropriate - we move the "item" to the CLOSED Issues parking lot. I do those myself - or sometimes call on someone else to do that from that side of the room.

And of course - you can do this via electronic means for distance meetings - depending on the "tool/system" that you use!

Try it.

It gets your group more involved, makes them articulate their issues themselves, and gets them out of their seats on occasion, which may be the most beneficial aspect of the self-parking lot concept.

So - assign everyone as a valet for the 1st parking lot!


Next we'll summarize the 12 rules/guidelines as they apply to the PACT Processes for T&D/ Learning/ Knowledge Management!

Cheers!

- Sourced and edited/embellished from Appendices C of: "lean-ISD" - a book by Guy W. Wallace - published in 1999 and made available as a free 404 page PDF in 2007 at http://www.eppic.biz/

Book cover by the late Geary A. Rummler.

# # #

Guy W. Wallace’s PACT Facilitation Guidelines: # 11 - Beware of Group Think














Guy W. Wallace’s PACT Facilitation Guidelines: # 11- Beware of Group Think

I call these “The 12 Rules and Guidelines of Proactive/Confrontational Facilitation for the PACT Processes for T&D.”

They are:

1. Go Slow to Go Fast. 2. Be Declarative. 3. Write Stuff and Post It. 4. Be Redundant by Design. 5. Use the Four Key Communications Behavior Types. 6. Review and Preview. 7. Write It Down and Then Discuss It. 8. Use Humor. 9. Control the Process and the Participants. 10. Be Legible on the Flip Chart. 11. Beware of Group-Think. 12. Assign Parking Lot Valets.

The 11th of these is covered in more detail in the following text.

I encourage you to: Read them. Think about how you'll use them. Practice with them. Adapat them to your style and the needs of the process and the needs of the group.

11. Beware of Group-Think
Group-think is a danger. It is usually caused by one or more variables.

• A single dominant participant who intimidates everyone else, such as a high-level manager to whom most everyone else in the room reports

• Multiple dominant participants who are aligned

• A docile, lazy group easily dominated and that doesn’t want to work too hard

• A group of timid participants, unsure of themselves, and afraid of going against the grain of the stronger personalities

The key cause could be poor selection of the group members for the meeting. This is sometimes avoidable and sometimes is not.

It is more likely that group-think is caused by a facilitator who has lost control of the process and has let someone else facilitate from the other side of the U-shaped tables. Bad. Bad. Bad.

When I feel that group-think is happening, I stop the process and confront the group. I ask them to go over their last inputs and give me their personal rationale for their decisions.

I tell them (being declarative of course) of my concern and ask them to speak for themselves.

Then I back up and go over the last inputs very slowly, and reconfirm their responses and their rationale.

If that doesn’t stop it, maybe nothing will, unless we change the entire nature of the group process. It may be avoided initially by making sure that the folks chosen for the group effort are strong enough to not fall into the group-think trap.



Summary

In the near future we'll cover the remaining rule/guideline and then a summary of all 12!

And how these are especially used throughout the PACT Processes by the PACT Practitioner in facilitating/conducting the many group meetings that can occur in PACT.

I hope these are of some benefit to you in your facilitated processes for ISD or for any "ends" that you desire/need!

Cheers!

- Sourced and edited/embellished from Appendices C of: "lean-ISD" - a book by Guy W. Wallace - published in 1999 and made available as a free 404 page PDF in 2007 at http://www.eppic.biz/.

Book cover design by the late Geary A. Rummler.

# # #

Guy W. Wallace’s PACT Facilitation Guidelines: # 10 - Be Legible on the Flip Chart










Guy W. Wallace’s PACT Facilitation Guidelines: # 10 - Be Legible on the Flip Chart

I call these “The 12 Rules and Guidelines of Proactive/Confrontational Facilitation for the PACT Processes for T&D.”

They are:

1. Go Slow to Go Fast. 2. Be Declarative. 3. Write Stuff and Post It. 4. Be Redundant by Design. 5. Use the Four Key Communications Behavior Types. 6. Review and Preview. 7. Write It Down and Then Discuss It. 8. Use Humor. 9. Control the Process and the Participants. 10. Be Legible on the Flip Chart. 11. Beware of Group-Think. 12. Assign Parking Lot Valets.

The 10th of these is covered in more detail in the following text.

Read them. Practice them. Reflect on them Adopt and/or Adapt them. Use them.

10. Be Legible on the Flip Chart
Another of my favorite rules is: “Neatness does not count; legibility does.”

Maybe it just suits my personality best, being somewhat messy.





Those who know me usually think differently. I’m a very structured person―I love structure and hate chaos. But once I get on a roll with the group, or more importantly, once they get on a roll, I don’t take a lot of time to write down their inputs so carefully that I slow them down.

I try to write fast. To keep up with them!

In fact, I write so fast and furiously that I have to make sure I don’t violate the legibility rule that means so much to whomever has to word-process my work afterward. Even when I have word-processed my own charts later, I have found that I was not always able to recall what the words were in my attempt to clean up my own mess. Or it "took a while" to do so.

So if you can’t do both, at least be legible if not always neat!



Close Enough?


I also try to walk around the room to "see" from the vantage points (or disadvantage points) of the attendees - what do the flip chart pages look like from their seats? Am I writing large enough? Do they have a pray of readuing my writing?

And then I adjust as necessary.

That often means pulling their tables/chairs closer to the action - my writing in response to their answers/statements to my questions. Whatever can be done to increase their visibility of the written words and line drawings.

Summary
Think about your attendees. Can they read what you write? Can you move them closer to the flip chart easle? Can they hear what you say - if they cannot get close enough (are there too many in the room for easy viewing?)?

In the future we'll cover the remaining 2 rules/guidelines one-by-one!

Cheers!

- Sourced and edited/embellished from Appendices C of: "lean-ISD" - a book by Guy W. Wallace - available as a free 404 page PDF in 2007 at http://www.eppic.biz/

Book cover design by the late Geary Rummler in 1999.

# # #

Tuesday, November 25, 2008

From Dave's Whiteboard - 1st in a series based on the book "Improving Performance"

from...
Dave’s Whiteboard
Interests, ideas, notions, tangents
Rummler and Brache: Improving Performance
November 25th, 2008
Series: Managing the White Space

Following the recent death of co-author Geary Rummler, I’m reading Improving Performance: How to Manage the White Space on the Organization Chart. This post is the first in a series based on that book and on the implications of that white space.

*** *** *** ***

Thanks Dave!

# # #

Press Release: SyberWorks e-Learning Podcasts: Episode #26: “Interview with Guy Wallace on His e-Book, ‘Management Areas of Performance.’ ”

A new Audio Podcast now available...from SyberWorks...

**** **** **** ****

SyberWorks e-Learning Podcast Series #26: Interview with Guy Wallace
By Dave Boggs on SyberWorks e-Learning Podcast Series
Here is our latest press release and e-Learning Series podcast:

Press Release:
SyberWorks e-Learning Podcasts: Episode #26: “Interview with Guy Wallace on His e-Book, ‘Management Areas of Performance.’ ”

Podcast:
Episode 26: “Interview with Guy Wallace on His e-Book, ‘Management Areas of Performance.’ ”

Dave Boggs, CEO of SyberWorks, states, “Today’s podcast is an interview with Guy Wallace, Certified Performance Technologist and the President of EPPIC, Inc. Guy has written an e-Book, ‘Management Areas of Performance,’ which presents a comprehensive scheme for managing performance in an organizational context.”

**** **** **** ****

Thanks Dave and company!

The book was originally published by me in early 2007 - after laying dormant for a couple of years - and then "went straight to video" so-to-speak - and was made available by me as a free book PDF - to share versus sell - Management Areas of Performance is available for free at http://www.eppic.biz/

# # #

Sunday, November 23, 2008

Most Recent Formally Developed PACT Practitioners - November 2008


Last week I delivered a PACT Practitioner combo-session on three key PACT Practitioner skills areas: Analysis, CAD Design and MCD Design.
My 6 session participants, part of my staff, included manager Margaret Ward, and her staff: Kathy Storberg, Bobbie Bell, Shonda Martin, Melissa Hinzman and Chantel Fashano.
Those who have been in these sessions might sympathize with this graduating class. They covered all 3 of these areas in 5 days, after 5 weeks of homework readings and assignments, and a intense 3-day session 6 weeks earlier. Before that they were supposed to have read part of the lean-ISD book, but I'm not sure that all had.
In this 5-day session we covered facilitating a group of Master Performers and other relevant Subject Matter Experts generating the Areas of Performance for the scope of the analysis - here it was for a CAD and therefore the "whole" job of the Store Manager...

We were using my case company: TMC Stores - as in: The Most Convenient Stores. And focused on the Store Manager job...or was it the Assistant Manager job, right?
Always be careful about the group-think/assumptions.
Then after the AoPs are established and "tested" - the team is facilitated to produce the Performance Models - per the AoP framework...


Those Performance Models identify both ideal performance and document a gap analysis against that ideal - AoP by AoP - Output/Task-Cluster by O/T-C.
The the Performance data is used to systematically derive the enabling Knowledge/Skills...
Then all of that data is used to Assess Existing T&D for its re-use potential...
Then in CAD Design we learned to process the analysis data in the CAD Design Team Meeting's 7 step process...to eventually produce Event Specs (books) and their Module Specs (chapters) on a "T&D Path"...
...a module is a combination of the analysis data...
...and then is sequenced in a "suggested sequence" for the Learner/Performer and their management. PACT T&D Paths are "as rigorous as required and as flexible as feasible."
Those Event Specs - specify gaps that are part of the current curriculum - and would be the courses in your "course catalogue/sub-set of your LMS offerings" for the one target audience...should you put them into place via development/acquisition...
Then in MCD - Event Maps are produced using the analysis data...




The walls are papered...
We needed room to spread out...

Margaret Ward works on her MCD "Appo" - and produces her Performance Model Chart...








Lesson Maps follow Event Maps...













Then each Instructional Activity on the Lesson Map is documented...




During the week we also discussed Project Planning at three levels of granularity...












We discussed the Portfolio/Program management concepts we were going to implement...













We discussed my Module (and Lesson/Instructional Activity) Numbering scheme...to inventory the "Objects" of PACT design...











We discussed PACT's "Truth In Titling" approach...










We discussed "keeping everything EVERGREEN" and the roles of a governance/advisory system to govern what gets done and maintained...


At the end we discussed the RADD version of PACT - which is PACT sans formal meetings with the Project Steering Team, just a meeting with the Client - someone with the Master Performance knowledge to assist in carrying out the first 7 or 8 of RADD's 9 steps. The challegne is to use all of the PACT anlysis and MCD design concepts and tools and in one meeting with the cleint - conduct the analysis and design steps - and perhaps begin actual development - deployment mode depending. They will all need to be able to go really fast with PACT. And it can be done.
It was an exhausting week...and we are not done with development.
Just resting for the holidays.
Thanks Margaret, Kathy, Bobbie, Shonda, Melissa and Chantel!!!
You guys did excellent!
# # #

Give Credit Where Credit Is Due



Enough said.

# # #

Guy W. Wallace’s PACT Facilitation Guidelines: # 9 - Control the Process and the Participants

Group Process isn't easier - but it is faster and better. And can be cheaper.
















Guy W. Wallace’s PACT Facilitation Guidelines: # 9 - Control the Process and the Participants

I call these “The 12 Rules and Guidelines of Proactive/Confrontational Facilitation for the PACT Processes for T&D.”

They are:1. Go Slow to Go Fast. 2. Be Declarative. 3. Write Stuff and Post It. 4. Be Redundant by Design. 5. Use the Four Key Communications Behavior Types. 6. Review and Preview. 7. Write It Down and Then Discuss It. 8. Use Humor. 9. Control the Process and the Participants. 10. Be Legible on the Flip Chart. 11. Beware of Group-Think. 12. Assign Parking Lot Valets.

The 9th of these is covered in more detail in the following text.

Read these. Use these. Reflect on these. Balance these.


9. Control the Process and the Participants
The facilitator can never let one individual, or a small group within the larger group, dominate the meeting. That would certainly be a disservice to everyone else involved.

The best thing to do if this begins to happen to you is to thank the person for their input and then ask someone else for theirs.

Then shift your style to aim specific questions at specific individuals. “Bob, what do you think the next set of tasks are for this output?”

If that doesn't work - call for a break - and take the offenders aside and explain that you need a balance of inputs to ensure a consensus is forming. While you appreciate their contributions, you hope they understand what you’re doing.

Usually they get the message and back off. Maybe they’ll need another reminder or two.

Sometimes none of these tactics work.

It is rare, but I have had to “disinvite” participants from my meetings. I think it has happened twice. A long time ago.

I now see the warning signals much earlier and can "head it off at the pass" quicker now-a-days.

That means I’ve been at the point - in the past - where someone's participation was so dysfunctional - that I asked them to leave.

I had to. They were disrupting the Process by inhibiting/intimidating the other Participants. The prior conversations/warning-shots-across-their-bows were ignored - or the behavior got worse instead of better.

If/when they resisted my de-invitation, I suggested that I would call their boss to insist to that person that they be requested to return to the office. That’s when they either drastically changed their behavior, or they left. I had no choice. They were so disruptive that they were wasting the time and productivity of everyone else.

Of course, I’d given the disruptive participants plenty of warning.

Prior Steps
Prior to dismissing them, I had taken them aside during a specially called break and warned them of my next move (which would be insisting that they depart the process).

Prior to that I had taken them aside during a regular break to discuss their participation style and the effect on the group and our progress.

Prior to that I had tried to manage their behavior during the meeting by asking out loud that they let others participate more.

Prior to that I had tried to get the group to help me self-manage the problem participant by asking for their opinions in response to the one individual’s points.

"When you can't stands no more"
To borrow a phrase from Popeye.

I had exhausted all possibilities. I had tried, I was done, and so were they.

When push comes to shove, I have to shove back.

I am the person that the group looks to to control the process and continue our progress. It's my job.

I can’t blame "their" hesitancy to act. It's not their job. I must act.

Otherwise, I am allowing someone (or more than one person) to waste all of our collective time and energies.

Don’t let this happen to you. Take charge, take action. It isn’t pleasant, but it is the job of the facilitator―at least in my view of the role of the proactive facilitator.

And it may on rare occasion be necessary for you to act. Hopefully never.

Pray for the best. Plan for the worst.


In the future we'll cover the remaining 3 rules/guidelines one-by-one!

Cheers!

- Sourced and edited/embellished from Appendices C of: "lean-ISD" - a book by Guy W. Wallace - available as a free 404 page PDF at http://www.eppic.biz/

# # #

Shrinking My World - My Network World - My Net World

The Global Village Shrinks ... at least for me ... and I deliberately did it to myself...


I remember when networking was meeting up at an annual conference with people you had met there years earlier, making phone calls a couple of times of year - with no particular purpose other than to just "check in." That was how it was done.

You collected business cards, and even wrote letters initially and sent them via snail mail to remind the other party of your meeting. Of course, I started in business after college in 1979. This is how it was done. You found time and ways to keep connected.

The words and promises from those Management Information Systems (MIS) people back then, in the late 1970s and early 1980s, that computers would change everything - have mostly come true.

MIS is now IT - Information Technology, and it and the Internet chave indeed hanged everything, and continues to change everything. And will continue to change everything.

Now not only do I not remember any one's phone number anymore - I don't have to remember where anyone currently lives. Ah! - technology.


For now I can find most everyone I know or would like to know via the Internet. One way or another. Sometimes they are easy to find. Sometimes much more difficult.

To make myself easier to find - I did join facebook last weekend - and I've posted 6 of my videos there in the last couple of days.

Also, to those friends/colleagues that don't have a photo of themselves along with their name - especially when they can see if there are many others with the "same name" as you - please post your photo so that I can find you in this digital haystack.

Or continue to hide behind some graphic persona and miss a possible connection - which may be your point.









I was dragged into facebook by about 15 people in a two week span a little less than a month ago, or so.

It was first a former client, and then a bunch of ISPI'ers, and a couple of friends from the past. I felt compelled. I was being ganged up on. Some of them were also pinging me via Linkedin.










So that caused me to up my game/profile on Linkedin.

I did that - and then posted several professional Presentations there.


And then all of that last week led me to write my Post on The Fine Art of Wastin' Time.

For I do worry a bit about getting sucked into these potential distractions, as valuable as a professional tool as they may be.

They can also be a "big time" "time sponge" - if one let's that happen to themselves.

When I was a kid I had the time to waste. As an adult, not so much. Maybe a little.

Life is a balance. Or needs to be kept into balance. Even if you are occasionally out in Second Life.

My best wishes for balance in your life - or lives - especially entering into this typically hectic holiday season that many of us experience this time of year.

Check in with me later - when you have the time!

Cheers!

# # #

Saturday, November 22, 2008

SyberWorks Audio Podcast with Guy W. Wallace on His "Management Areas of Performance" Book

From my friends at SyberWorks yesterday...

SyberWorks e-Learning Podcast Series #26 Preview
By Dave Boggs on SyberWorks News

Here's a sneak preview of our next SyberWorks e-Learning Podcast Series episode on Guy Wallace's new e-book, "Management Areas of Performance."

**** **** ****

That book - Management Areas of Performance - is available as a free PDF at www.eppic.biz

# # #

School of PACT 02- Lesson & Video Podcast - CAD - Curriculum Architecture Design










The Video Podcast below is merely a component to a blended approach to mastering PACT.

There are 6 steps if you will...but do it any way you choose...

1- Pre-Video Reading Assignments
2- Video Podcast Review
3- Post-Video Readings Assignments
4- Post-Video Application Assignments
5- Review Free Resources Available
6- Lesson Self-Debriefing

You'll need the book lean-ISD - which is available at Amazon.com as a hardbound and/or as a Kindle book - and/or free as a 404 page PDF here. There are also many PACT resources at the EPPIC Web site and at the PACT Wiki.

I've been writing/publishing since 1984 on CAD and presenting since 1983 (Chicago NSPI) on these CAD methods and the other two methodology-sets of MCD and IAD - and the use of a group process to develop Performance Models and K/S Matrices for Curriculum Architecture Design.

The Target Audience Data, the Performance Model and the K/S Matricies and the ETA: Existing T&D Assessment elements are my contributions to the analysis portion of PACT.

The CAD-MCD-IAD Design models, methods, templates/tools are also mine as well.

I cleared all of that with the late Geary Rummler in 1999 when we met for two days to review the book and the methodology - for his approval/sanctioning.

The first Video Podcast in this series includes his review of both.

School of PACT # 02 - CAD - Curriculum Architecture Design

Lesson 02- Objectives-
You should begin to "get/see" the CAD level of ISD in PACT - and can explain its purposes and its 4 Phases. You should begin to see how the approach to processes the analysis data in this one level of ISD in PACT's 3 levels of ISD. The systems engineering/architectural level of ISD in PACT.


1- Pre-Video Reading Assignments
I'd suggest re-reading chapter 3 of lean-ISD - and then watch this Video Podcast.

You could re-reads 1-7 or just chapter 3 - and then read chapters 8-13, and then watch the V-Podcast. But perhaps it would be better to read chapters 8-13 after the Video for you. Or do both!

The reading and /or the Video may help you mentally frame the CAD level of ISD in PACT and the common Analysis and Project Planning & Management aspects of the systems engineering/architectural level of ISD methodology in PACT.

2- Video Podcast Review
Here is the Video Podcast - 15:54 - minutes:seconds...

video


3- Post-Video Readings Assignments
If you did not do this already Step 1 - read chapters 8-13 of lean-ISD.
This is somewhat of an advanced organizer for CAD - the highest level of overview.

4- Post-Video Application Assignments
Start listing and organizing your questions. Build a table that captures your own questions, the answers and the sources for the answers that you found.

Start a personal Learning Log (or Blog).

Network with others. Start a club/social network - and/or join The PACT Practitioners Guild (a SN).

Find a buddy at work - or at a local professional society chapter!

5- Review Free Resources Available
At http://www.eppic.biz/ there is a related PACT Audio Podcast available. Also - there are articles and presentations in the Resource tab at that same site.

And check out that PACT Wiki for additional free resources/references, tools and templates.

Please maintain my copyright markings. You'd do so for Bob Mager or Joe Harless - wouldn't you?

6- Lesson Self-Debriefing
You should begin to "get/see" the CAD level of ISD in PACT - and can explain its purposes and its 4 Phases. You should begin to see how the approach to processes the analysis data in this one level of ISD in PACT's 3 levels of ISD. The systems engineering/architectural level of ISD in PACT.

If so - you are ready for the next Lesson and Video Podcast - coming soon!

And don't forget to get your free PDF copy the book: lean-ISD...available at http://www.eppic.biz/

Adopt-Adapt?/Rigor-Flexibility?
Adopt what you can - and adapt the rest.Adjust as needed for each effort/application. Always.Be as rigorous as required - and as flexible as feasible!

Always do the smart thing given your goals, resources and constraints.

Future Additions to this Post and Others in the Series
Note: I will add addition Videos to each post in this School of PACT series over time. These will tend to add additional details - or dig deeper into the details of the PACT methods.

I will put them here - at the end of every SoP Blog Posting.

Final Note: The SoP - School of PACT Series will cover...

1- Intro to PACT - 3 levels of ISD and common Analysis and common Project Planning & Management concepts, models, methods, tools, templates and techniques

2- CAD - Curriculum Architecture Design - to design the performance-based learning continuum for a targeted job/process

3- MCD - Modular Curriculum Development/Acquisition - the ADDIE level of PACT

4- IAD - Instructional Activity Development/Acquisition -the Knowledge Management level of PACT

5- PACT Analysis -the 4 types of analysis required in PACT's CAD - MCD - IAD "design" methods

6- PACT Project Planning & Management - common project planning and management concepts, models, methods, tools, templates and techniques

7- 5 PACT Roles and 5 Client Teams -defining the roles and responsibilities of the 5 Client teams and the 5 PACT Practitioner roles

8- PACT Process Technology Transfer -how to logically transfer/intake the PACT Processes

9- PACT is a Sub-set of EPPI - Enterprise Process Performance Improvement - a look at PACT as a sub-set of a broader improvement methodology - beyond instruction

10- Segue from Training to Performance via PACT and EPPI - how to move from performance-based Training/Instruction/Learning/Knowledge Management to Performanc eSupport and Improvement

11- T&D Systems View of the Processes of ISD/PI Functional Organizations - The EPPI organizational concepts - of the LCS Model of AoPs/Processes - applied to a T&D function/department.

12- Management Areas of Performance - A Framework for Analysis of Performance Competence Requirements From the Department Rolled Up to the Enterprise

13- Performance-based Employee Qualification/Certification Systems - Develop the System and Processes to implement and operate a function to qualify/certify targeted jobs/tasks for Risk/Reward reasons.

Plus others in the School of PACT series - beyond these first 13 - all TBD!

# # #

Thursday, November 20, 2008

Guy W. Wallace’s PACT Facilitation Guidelines: # 8 - Use Humor















Guy W. Wallace’s PACT Facilitation Guidelines: # 8- Use Humor.

I call these “The 12 Rules and Guidelines of Proactive/Confrontational Facilitation for the PACT Processes for T&D.”

The 12 "hints at how to do PACT Facilitation" are:

1. Go Slow to Go Fast.

2. Be Declarative.

3. Write Stuff and Post It.

4. Be Redundant by Design.

5. Use the Four Key Communications Behavior Types.

6. Review and Preview.

7. Write It Down and Then Discuss It.

8. Use Humor.

9. Control the Process and the Participants.

10. Be Legible on the Flip Chart.

11. Beware of Group-Think.

12. Assign Parking Lot Valets.

The 8th of these is covered in more detail in the following text.

Read them. Adapt them. Use them. Tweak as needed.


8. Use Humor
Or - use of humor.

Humor, done right, sets the stage.

The message sent by your use of humor - and which can also be said instead out loud in a declarative fashion - is that while our goal is serious, let’s not take ourselves too seriously.

Let’s loosen up a bit. You, me, everyone in the process.

Unless of course it is a "life or death" situation.

As always - it depends.

Otherwise - loosen up. De-Stress everyone. Do everyone a favor.

As facilitator - it's your job. Do it.

**** ****

You As The Bozo
Self-deprecating humor is best. It offends no one, because you (the facilitator) are the butt of most of it. Or all of it.

Use of yourself as the “bozo on the bus” is effective because you can make points and laugh at yourself. And if you later inadvertently make someone else the butt of your jokes or points, or they make a fool out of themselves, you and they can recover by you turning it back on yourself.

For example, after an obvious mistake by someone on the team being facilitated:

“Oh, that was smart! . . . I guess you’re joining me in the dumb-dumb club.

Hey, but I’m still president.”

















When you are facilitating a complex set of process steps - such as in the CAD or MCD "processes" mistakes are inevitable. By you and anyone else!

How will you handle the situation?

Will you deflect attention from the mistake making person to something else to get them off the hook?

Non-Examples
When providing examples and non-examples, use yourself as the non-example and others in the room as the example. “Pete is competent and will get the training, and if he does well, he’ll get the raise. Guy is still screwing up, and if the training doesn’t take hold or he doesn’t use what he learns, he’s outta here!”

Don’t use off-color humor, sexist, racist, age-ist, or any non-PC (politically correct) humor. Make sure the butt of your jokes is most often you. Or always you.

Who could complain?

After establishing myself as the biggest bozo on the bus, I might include others in my other jokes/wisecracks―but only if I am darn sure that they’ll be okay with it, for example because they have started picking on me (in fun of course), or they have made fun of themselves in some way.

Again, this is tricky and you’ve got to be sure of what you’re doing.

















Naturally - Or Not!?!
Well?

Does It Come Naturally to YOU?
If humor doesn’t come naturally to you, experiment/ practice/ try this first at your next family outing before you attempt to foist any humor on a group or team you are asked to facilitate.

Or somewhere someway. Just - don't leave home without it - practicing until safe I mean.

See what kind of reaction you get from people who know you and love you much better - than this possible group of strangers who won’t be quite sure where you’re coming from. And as forgiving as might be needed should you "screw up humor" (a technical phrase).

So before you can inadvertently offend anyone - apologize in-advance, and have practiced. practiced, practiced beforehand!














In the future we'll cover the remaining 4 rules/guidelines - one-by-one!

Cheers!

- Sourced and edited/embellished from Appendices C of: "lean-ISD" - a book by Guy W. Wallace - available as a free 404 page PDF at http://www.eppic.biz/

The title was suggested and the cover of "lean-ISD" was designed by the late Geary A. Rummler who wrote:

“If you want to ground your fantasy of a ‘corporate university’ with the reality of a sound ‘engineering’ approach to instructional systems that will provide results, you should learn about the PACT Processes.

If you are a leader of, or a serious participant in, the design and implementation of a large-scale corporate curriculum, then this book is for you. This system could be the difference between achieving bottom-line results with your training or being just another ‘little red school house.’”

Geary A. Rummler, Ph.D.
Performance Design Lab


Others who wrote reviews in 1999...

“This highly structured and detailed process for instructional design provides excellent guidelines for advanced students and practitioners. The focus is on improving training and development processes and products in business and industry.”

James D. Russell
Professor of Instructional Design, Purdue University

**** ****

“Guy Wallace is giving away the magic. This book provides a model and methodology to help a training function link its long-term outputs to the business needs of the organization. The PACT Processes help introduce the voice of the customer into any training organization whose mission is to improve performance.”

John M. Swinney
Manager of Curriculum Design and Development, Bandag, Inc.

**** ****

“This book is not an easy read, it is something much better. It is a book written for people who share Guy Wallace’s passion for development training that adds value, for people who are so committed to competence for themselves and for the people they serve that they are willing to do what it takes to develop training that adds value. The best way to use the book is as a guide in doing projects . . . it describes the why and the what and offers many wise and useful suggestions about how.”

Dale M. Brethower, Ph.D.
Professor of Psychology, Western Michigan University

**** ****

lean-ISD takes all of the theory, books, courses and pseudo job-aids that are currently on the market about Instructional Systems Design and blows them out of the water.

Previous “systems” approach books showed a lot of big boxes and diagrams which were to supposedly help the reader become proficient in the design process. Here is a book that actually includes all of the information that fell through the cracks of other ISD training materials and shows you the way to actually get from one step to another. Guy adds all of the caveats and tips he has learned in over twenty years of ISD practice and sprinkles them as job aids and stories throughout the book.

However, the most critical part of the book for me was that Guy included the project and people management elements of ISD in the book. Too often ISD models and materials forget that we are working with real people in getting the work done.

This book helps explain and illustrate best practices in ensuring success in ISD projects.

Miki Lane
Senior Partner
MVM The Communications Group

**** ****

“I’ve found lean-ISD to be a very useful reference tool and resource. After having been involved with Guy Wallace on a large-scale application of the methodology at my last firm, I’ve taken on several recent projects in my new company using many of the methods, tools and templates of the PACT Processes for Training & Development. The book is designed so that I was quickly able to access the information I needed to provide my clients practical, timely and quality approaches to tackling their business issues.

I highly recommend this book as a guide for business professionals challenged by either training and development, learning, knowledge management, or human competence development projects.”

Randy Kohout
Director, Knowledge Management
Fireman’s Fund

**** **** **** **** ****

Again, all quotes from 1999.

My book: lean-ISD covers the PACT Processes - land it leverages the expertise of your Master Performers - and upskills all to get closer to their levels of performance.

By modeling Performance and deriving the enabling knowledge/skills in a systematic and controlled manner.

Some might call the process bench-marking. Others might call it best practices. It's similar to a group doing process mapping - but much more. More disciplined. Much more produced. Much greater impact potential.

And...

More predictable - in terms of time and schedule. And - quality of data - besides that quantity.

And the analysis data should/ could include lessons learned and warnings about typical gaps and causes!!!

And other architectural/outline/segmentation of tasks and topics.

All to enable Process/ Workflow/ Performance at the individual, process, organization, enterprise and societal levels.

What is the relevance of anything else?

# # #

Guy W. Wallace’s PACT Facilitation Guidelines: # 7 - Write It Down and Then Discuss It















Guy W. Wallace’s PACT Facilitation Guidelines: # 7 - Write It Down and Then Discuss It.

I call these “The 12 Rules and Guidelines of Proactive/Confrontational Facilitation for the PACT Processes for T&D.”


They are:

1. Go Slow to Go Fast.

2. Be Declarative.


3. Write Stuff and Post It.


4. Be Redundant by Design.


5. Use the Four Key Communications Behavior Types.


6. Review and Preview.


7. Write It Down and Then Discuss It.


8. Use Humor.


9. Control the Process and the Participants.


10. Be Legible on the Flip Chart.


11. Beware of Group-Think.


12. Assign Parking Lot Valets.


The 7th of these is covered in more detail in the following text.


Read them. Think about them, reflect on when/ where/ what you've experienced about the topics/methods. Use them. As appropriate. One size does not fit all.


7. Write It Down and Then Discuss It
One of my first rules or guidelines to new facilitators is: Write down the first thing that someone says!

Why this ended up 7th on the list? - I don't recall.

Turn words "floating in the air" into something black and white (depending, of course, on your paper and pen color).

This almost always forces a reaction from the remaining members of the group you are facilitating. At least they can focus on the words you wrote down - versus their "cognitive take-away" from what they recall you saying. They now have a prayer.

I always tell the group that this is exactly what I’m going to do.


If someone will be so brave as to volunteer a response to my question or statement, I’ll write it down to prompt their reaction. Either it stays, or someone takes exception to it and the group dialogue begins. Do we have a consensus or not?















Until I write it down, I’m not always sure. It’s the reaction of the group, verbally or nonverbally (those clues and cues again), that tell me.

I tell the group that today they are on the payroll to provide the inputs according to my process. They own the content, I own the process. And it is up to them to make sure that I capture their consensus accurately.


They should all be okay with not being in total agreement, and they must be okay with questioning and challenging each other. We are usually in a hurry and need to accomplish plenty, and time is a wastin’.


The best way to keep the process moving is to seek what you’re looking for, write down the first response, and then ask for group confirmation, questions, comments, and concerns.
















If the facilitator asks and then does nothing with the response, he or she seems to be waiting for the "correct answer."


That tends to inhibit the free flow of responses that you may be seeking. I always write the response down, unless it is so wrong that I don’t want to overly embarrass the individual who volunteered the wrong stuff. Then I rephrase my question so drastically, or shift gears and go into something that I may have forgotten, or fake forgetting something - and then ask again usually with an example or two of what I’m looking for.

Or more simply, "let me rephrase that."

Of course some may know exactly what I’ve done and will usually appreciate it. They bet that if they make a similar faux pas, I’ll help save their face, too. This fear-reduction technique is especially important when the group being facilitated is not totally comfortable with each other.

Again, this is not passive facilitation, which might be the appropriate route to take for your assignment. This is aggressive, confrontational, proactive facilitation. This is the quickest route to getting the most data out of a group process. You need to decide the appropriateness of this method for your needs and for your personality style.


Again, it always depends. Sorry.



















In the future we'll cover the remaining 5 rules/guidelines one-by-one!

Cheers!

- Sourced and edited/embellished from Appendices C of: "lean-ISD" - a book by Guy W. Wallace - available as a free 404 page PDF at http://www.eppic.biz/

# # #

Wednesday, November 19, 2008

Guy W. Wallace’s PACT Facilitation Guidelines: #6 - Review and Preview
















This is nothing new. Review and Preview.

It is somewhat of an advanced organizer if you will.

Back to that later.

Background on this series first: this is 6th in a series of posts on what I call the “The 12 Rules and Guidelines of Proactive/Confrontational Facilitation for the PACT Processes for T&D/ Learning/ Knowledge Management.”

The PACT Processes are a set of ISD methods with 3 levels of ID/ISD - instead of just thinking of ADDIE - which I think of as a NPD - New Product Development Process - for Instruction - PACT has an "systems engineering/architectural-level" and the NPD-level (ADDIE) and a component level.

PACT is Accelerated and Customer/Stakeholder-driven "via" its use of designated teams to do designated things (produce designated stuff). These teams are FACILITATED to get their jobs done. You can read the Training Magazine article from September 1984 on this - particularly the use of a "Group Process" that I and 3 others wrote back in 1983. I'd been using a group process instead of an individual interviews/observations since 1979.

The Facilitator in PACT is critical.

And the facilitator's role in PACT is not one of reflective commentary on group dynamics. When needed. In PACT the facilitator drives the process, and "owns the process" while the folks being facilitated "own the content" generated by the process.

The 12 rules/guidelines/suggested based on learnings from burnings - when I've been burned I've tried to learn (from it) - are:

1. Go Slow to Go Fast.

2. Be Declarative.

3. Write Stuff and Post It.

4. Be Redundant by Design.

5. Use the Four Key Communications Behavior Types.

6. Review and Preview.

7. Write It Down and Then Discuss It.

8. Use Humor.

9. Control the Process and the Participants.

10. Be Legible on the Flip Chart.

11. Beware of Group-Think.

12. Assign Parking Lot Valets.













The 6th of these is covered in more detail in the following text.

Read them. Use them. Practice them. Reflect on what's working what doesn't. Tweak.

Adapt if you cannot adopt.

6. Review and Preview
I start with a “review/preview” at the beginning of every new day of a multiday meeting, at any midmeeting agenda/process change, and often at the return from every big meeting break - or even the little breaks. I do it as often as my "face polling" suggest that I should.

Some might call it a progress check. “How are we doing, is everyone comfortable with what we have captured, etc.?”

I do that within the context of “where have we been, and where are we going.” I like to think of it as “recalibrating” the group. And I can also appreciate the value of it to them to perhaps recalibrate me. Really.

Off Process?
The group members are often simply along for the ride, and they are not all that interested in learning the process we are using for developing instructional content, so they often forget the process in mid-process (often to the facilitator’s amazement. But hey, this is our world―this facilitation stuff―not theirs). So I need a way to remind them continuously of what we are doing and where we are going and how it all fits together.

Participants may do very well in responding to our prompts, giving us their feedback when asked. But do not be fooled into believing that after one, two, or even three days they will remember exactly how and why we did each step of our process. Some will, some will not.

Our process in PACT for capturing and analyzing data is probably somewhat alien to them.

The data produced in the AoPs - Areas of Performance - often frames the task/ job/ process/ workflow/ etc. and portrays it - often, in a very very different "depiction" from their own mental model - or models -of how their job looks. And they may struggle with that and comment on that discomfort/ fight adopting the new emerging model.











Or comment on how we facilitators should be doing our job - because they would do it differently and/or they don't like what is emerging from the Group Process we use in PACT. They may "play along" with us without completely giving up their mental model. Or their thoughts of how they would accomplish my/our task.

They may still be quite comfortable with their views on what and how and not with the new views one just emerging from the process they would change. The problem then is that the group is not of as close to one mind, in consensus, as to the data we are seeking at each step of the PACT Processes.

I also find that one or two people or the whole group often somehow forgets what we are doing and how we are doing it - and before I know it - revert midstream to something else (I often know not what), and I need to again recalibrate the group to both what we are trying to do right now, and the process we are using to do that.

In fact, I now try to do it - the recalibration - proactively - before it really becomes apparent by the team being facilitated that it is needed (by me looking for those early cues and clues! Early and often).

Reviewing and previewing gives us a chance to recalibrate the group, to re-establish the process, models, the templates and terms, and just as importantly, give the group a place to blow off any steam or frustrations that may exist.

Give the Team a Chance to Push Back/Critique the Process/Blow Off Steam
Blowing off steam is critical. Or rather having a chance to blow it off is. If the group needs an outlet, they’ll either do it on your schedule or when, in the immortal words of Popeye, “when they can’t stands it no more.” That might be "untimely." And avoidable by "heading them off at the pass." Get there first!

You should have seen it coming, in the clues and cues for which you are constantly looking. The reviews and previews are a safety outlet designed in to my process checks.

“Please do it now and be less disruptive to the main process,” I think.

The reviews/previews are the time and place for blowing off steam and airing any and all frustrations. Remember, it’s either done on your schedule or theirs. You can try to stop it, but I bet you often won’t be able to stop it at all. You may only make it worse. You may be able to control this to your advantage, but only if you try. It is often (but not always) yours to control.

Sometimes someone just needs to be heard. Use Active Listening after your open or targeted questions.


Review/Preview Summary
Think of this “review/preview” as a combination of...
• Slowing down temporarily in order to go fast again
• Being declarative
• Redundancy by design
• A progress/process check
• A place for questions to be asked/clarifications made
• A place to blow off steam/express frustrations/be an outlet for almost anything

Don’t be afraid to do this several times a day and at the beginning and ending of each day. The review should cover our project purpose, meeting purpose, outputs/outcomes so far, and feedback and inputs.

That's the advanced organizer part. Do it early and do it often.

The preview covers where we are, where we are going, how we’re progressing against the clock (are we on schedule or not?), and how the remaining agenda items fit into the overall scheme of things.

Then hit them with one or more open questions intended to elicit their feelings/thoughts/etc.


















lean-ISD book cover design by the late Geary A. Rummler back in 1999.

The quote above that I correctly attributed to Popeye - is a quote that I remember Geary using often back in the days of MTEC (1981-1982). Even the "In the immortal words of Popeye" preface part. Geary always included that. It's a cultural reference for those of us who grew up watching Popeye. Plus Geary would also say: "I yam what I yam."

He was cool. Very cool. And cool about being cool. Humble.

Peace Geary.

Post Summary & Close
In the future we'll cover the remaining 6 rules/guidelines one-by-one!

Cheers!

- Sourced and edited/embellished from Appendices C of: "lean-ISD" - a book by Guy W. Wallace - available as a free 404 page PDF at http://www.eppic.biz/

# # #

Sunday, November 16, 2008

Video Podcasts Now On Google Video For Downloading

You may have already seen the 1st Blog Post and Video Podcast of the School of PACT series - 13 planned - and with many, many additional relevant topics/tasks for me to tackle regarding the PACT Processes for T&D/ Learning/ Knowledge Management.

I will put out a new one every 2-4 weeks- or more. I am also intending on posting them on Google Video as I Blog about them - the Blog Postings intended to both present the Video Podcast - and to frame a "Learning Process/Progression/Path" - both adopt-able and adapt-able - as needed of course - for you - the reader/learner/potential Performer.

I use Google so that everyone that wants one can have a personal copy. I treasure my copies of old videos (Rummler, Rackham, etc.) and audios - I have Rackham speaking on SPIN from 1981 somewhere. They and others always freely shared. So shall I.

The list below will be constantly updated - as this post will be used as "link transition points" to both those Google Videos and the Pursuing Performance Blog (PP Blog) Postings - from a link on the Blog's static but active portion of the layout template.

Note that there will be "other video links" here on topics related to performance-based Instructional Design, Instructional Systems Design, Systematic Approach to Training, ID, ISD, SAT, etc. from myself and from others.

In most-recent-first order:
Videos from Guy W. Wallace...

School of PACT 02b - 7 CAD Design Steps - at Google Video - on the PP Blog - next released Video Podcast in the School of PACT series - focused on the the detailed "7 Design Steps" used to "process the PACT analysis data" in the Design Team Meeting in Phase 3 of CAD - Curriculum Architecture Design - of the PACT Processes for T&D/ Learning/ Knowledge Mangement. This particular Video Podcast augments Video Podcast #2 - CAD.

School of PACT 02 - CAD - Curriculum Architecture Design - at Google Video - on the PP Blog - 2nd in the series of at least 13 Video Podcasts planned. CAD is the macro-design level of PACT's 3 levels of ISD design. CAD is the systems engineering/architectural set of ISD/ID methods for developing a T&D Path/ Learning Continuum for one or more Target Audiences. CADs lead to MCD efforts (the ADDIE-level of PACT). This Podcast on CAD will be augmented by several other Podcasts with topics closely related/intertwined with the CAD level of PACT, to provide more details.

Changing Tires on a Moving Truck - at Google Video - on PP Blog Post - please indulge my silliness with this 1:42 (m:s) Video that plays out some thought given to "parallel processing" for some types of change. Where you cannot stop, change, and then restart. As clients stated their challenge to be akin to "changing the tires on a moving truck." Probably a total waste of your time for most of you - unless you plan/manage multiple workstreams of systems in transition and change. It's how I might represent a divide-and-conquor approach to complex change.

Enterprise Wiki Architecture - at Google Video - on PP Blog Post - thoughts about how I'd architect the structure of wikis for every process, for every performer's use. 7:42 (m:s).

School of PACT 01 - PACT Intro - at Google Video - on PP Blog Post - The first in the series. 10:00 (m:s). Overview of the 5 methodology-sets of PACT, the customer-teams and ISD-roles, and the resources available.

Videos from others/of others - that are my personal favorites - and that I'd like to share with others interested in PACT...


Dr. Richard E. Clark and Allen Munro - Learning Research at the Center for Cognitive Technologies - web link - Part of the Rossier School of Education Brown Bag Series, Richard Clark and Allen Munro discuss topics such as: cognitive load theory, instructional design, direct instruction, cognitive task analysis, creative technology, see one, do one, teach one, mental simulation, tactical planning/instructional/assessment tools. 1 hour and 2 minutes. Excellent! From May 2008.


Dr. Ruth Clark - Leveraging the Virtual Classroom for Effective Learning - web link - 1 hour 18 minutes from Dr. Clark - part of the University of Maryland Baltimore Campus (UMBC) series of ISD- November 2008. Excellent!

Clive Shepherd - Welcome to the Virtual Classroom - web link - An excellent 9+minute introduction to the basics of Virtual Classrooms - November 2007. Excellent!

Thiagi- Rapid Instructional Design - web link - PP Blog Post on this Video Resource - from 2008 from UMBC University of Maryland Baltimore Campus. 1:47 (hour:minutes). Excellent!

Neil Rackham - Instructional Design Criteria - web link - PP Blog Post on this Video Resource - from 1981. 10 design criteria are talked through by Neil for MTEC. Excellent!

Geary Rummler - Performance-Based Training - web link - PP Blog Post on this Video Resource - from 1981. Another MTEC video. Excellent!

*** *** *** *** *** ***
Audio Podcasts from Guy W. Wallace...

1 - Intro to PACT

2 - The CAD Process

3 - The MCD Process

4 - The IAD Process

5 - Building PACT Capability & Capacity

6 - Practitioner Qualification Certification

7 - PACT Flexibility - 6 Case Studies

8 - From ISD to HPT with PACT and EPPI

9 - PACT and the ECA and the WELL

10 - PACT and Customer Collaboration

11 - PACT Project Acceleration Strategies for Rapid ISD

12 - PACT Project Predictability

To be completed later...

Audio Podcasts from others...
xxx


My lean-ISD book as a free 404-page PDF.

I hope that you find these of value for your "distance learning" on Instructional Design/Instructional Systems Design - and the PACT Processes.

Additional free PACT resources from Guy W. Wallace and EPPIC Inc. are available at http://www.eppic.biz/

# # #

Saturday, November 15, 2008

Changing Tires on a Moving Truck? Can't Stop to Change?

video

Just a quick, meant-to-be-fun - 1:40 minute :seconds - video regarding that age old problem/opportunity...change and changing things when things are complex. With many moving parts. When you can't stop what you are doing to change what you are doing.

If you can't stop, make the change, and then start up again - because you got to keep moving - how can you do that? This little video clip suggests one approach. Temporary overlap. By design.

# # #

The Fine Art of Wastin' Time - Keeps Evolving


All within about 10 days I get 20 invitations to join facebook and link to others at LinkedIn.

And the endless temptations to join Second Life and escape this first life.

Made me think back to a step-son's friend's father's quote about their break dancing. He called it the current "Fine Art of Wastin' Time" and I concurred.

The only folks on the planet who don't get to experience this in their youth is almost everyone besides those of us in the very well Developed nations. And even some in our midst do not have time for distraction - daily shelter and food are the focus.

Not whiling away their day without real purpose.

But back in the day for me - a child of the far south suburbs of Chicago - my distractions from the drudgery of childhood boredom?

In the days of my youth...
  • Cartoons on TV
  • Playing baseball
  • Collecting Baseball Cards
  • Candy and bubble gum and ice cream
  • Shooting Marbles
  • Riding my bike everywhere
  • Tonka Trucks

In the days of my adolescence time...
  • Reading Boys Life and various kid books
  • Playing baseball
  • Playing football
  • Riding my bike all over town and - taking it across log jams in the nearby creek with friends to merely "get to the other side" to further explore our small town universe
  • The Beach Boys, Jan and Dean, Animals and then the Beatles via my little transistor radio

In the days of my High School time...
  • Girls
  • Work
  • Girls
  • Driving
  • Girls
  • Cruising
  • Girls
  • Music
  • Girls
  • Movies
  • Girls
  • Pizza

In the days of my College time...
  • College girls
  • Tennis
  • Poker
  • Risk
  • Movies
  • Work
  • Cruising
  • Music

In the days of my US Navy time...
  • Reading
  • Tennis
  • Photography
  • Touring the Pacific coast and Pacific Rim on an all paid 3-year tour
  • Reading
  • Music

In the days of my early career...

  • Ironing my dress shirts
  • Yard work
  • Weekend work at work
  • Movies
  • Music

In the days of my mid career...

  • Weekend work at work
  • Reading business books
  • Reading novels for fun
  • Music
  • Golf
  • Golf
  • Golf
  • Skiing
Today...I waste/invest my time in...
  • Grandchildren
  • Blog Surveillance on T&D/ Learning/ Knowledge Management and Performance Improvement
  • Generating content for my own Blog Postings/Wikis/SNs
  • ISPI
  • Facebook
  • Boating
  • Boating
  • Golf
  • Music
  • Grandchildren

Is any of it a waste of time? Depends on your personal needs and your personal views.

To each their own!

Unique and Shared

But think of all of the lack of "shared experiences" that future generations will experience.

We all know where that "3-hour tour" phrase that I adapted above - comes from. Don't most of us in the USA? Because we shared the fine art of wastin' time back in our day. We shared TV and Radio and Rock music - nation-wide - almost as one.

And now - those days are over. Or would seem to be - initially.

But they are not. Not really.

Because won't the future generations have facebook, etc. as their shared experiences?

# # #

Other Current Web Comments About Geary Rummler's Passing

Just a Few




http://www.daveswhiteboard.com/archives/884



http://blog.gartner.com/blog/bpi.php



http://gramconsulting.com/2008/11/geary-rummler-and-my-performance-improvement/



http://www.topix.com/motorcycles/harley-davidson/2008/11/geary-rummler-workflow-harley-davidson-education



http://tdblog.typepad.com/td_blog/



http://www.wikio.co.uk/news/Terkel



http://learningvoyager.blogspot.com/



http://tech.jsys-soft.jp/media/15/20081106-file_20081106T181740004.htm



Photo above of a casual Geary Rummler - from PDL.

# # #



Photos from a Working Session with Dr. Rummler in 1982.

My former boss at MTEC - Motorola's Training & Education Center caught up with me yesterday via email - and shared these 4 photos from 1982.

After 9 months of skip-level reporting to Bill Wiggenhorn beginning in the spring of 1981, Bill finally found a Functional Manager for the Manufacturing/Materials/Purchasing areas I was focused on - and it was Paul Heidenreich.

Paul lived/worked in Phoenix while I worked at the Motorola HQ campus in Schaumberg Illinois - about 30 miles west of Chicago's lake front. Here in these photos I was out to visit/work with him in Arizona, and with Dr. Rummler, on some "forgotten project" - according to Paul's email.

But I think I see a clue in one of the pictures - and I wish I could read what's on that flip chart.

The first photo is of Marilyn Desser, my boss' secretary. Yes that's what they called the job in 1982. Note the IBM Selectric on the desk...















You can see we were a little business causal about 6 years before that was in vogue. That's Paul in the Superman T-Shirt. See the word "kit" on the shirt? That's my clue as to what we were meeting about.














And Geary Rummler at the flip chart...














And that's Geary and Guy sitting in Paul's Camel Square office, coffee cups at our sides in 1982. I was a sponge. Imagine - working with a Rummler, Deming, Juran, day-after-day-after-day.

I learned so much - it's hard to sort through it all and create a timeline. Geary taught me much, generously bought books for me to read - both work books and casual reading - he was a big fan of mystery novels and the Travis McGee series back then. I think he also turned me on to Tony Hillerman - long ago.















Thank you so much Paul for sharing these!

I hadn't heard from or seen Paul in almost 25 years. I had kept up with what was going on with him through my interactions with Geary, as he and Geary were soon best of friends - after meeting at MTEC - once Paul joined our group in early 1982. And their wives were close. They were a close four-some. So I always kind-of knew what Paul was up to post-Motorola and then into retirement.

It was Paul who took my thoughts, documented in a 1982 White Paper) about combininding/ blending Process (ala Rummler), TQM tools (the 7 basics and 7 advanced and lessons from Deming and Juran), and Communications Styles/Behaviors (from the Huthwaite/Neil Rackham approaches) - and developed the idea of a Do-It-Yourself Geary-Rummler-Consulting Kit - that I contend morphed into the OPS course that morphed into a working/training session using Quality Tools and Geary's Process-Orientation - that eventually morphed into Six Sigma.

No kidding!

That morphing story, which happened after I left MTEC in October 1982 - is covered in Alan Ramias' article on The Mists of Six Sigma. Like Paul and myself, Alan worked at MTEC in those early years. When I left Motorola it was Alan who inherited many of my projects.

The Clue?
The "Kit" on Paul's T-Shirt in the photo above - I believe - is the clue that we were there in 1982 working on that D-I-Y G.R. Consulting Kit concept.

That made me sit back for a few moments.

White Papers were big back in the late 1970s and early 1980s.

There was the famous one on Japan - which was rocking/knocking the USA manufacturing boat back then (along with the prime rate being 21%).

That NBC White Paper "video" can be ordered here. Motorola was then waking up to the challenges of its future. Just as Detroit was doing at the same time - and is doing once again.

Talk about Deja Vu all over again!

Motorola was struggling (something natural and to be predicted) in the early 1980s with implementing a new culture: PMP: Participative Management Program. My White Paper addressed that - and how the "new stuff" I was learning about from all of our guru consultants Bill brought into MTEC - might be blended and applied.


Geary Rummler had already brought "process" into the Training world - and he was about to do so with the Quality/TQM world in a couple of years. Changing that world forever.

Reading Paul's email this morning - brought back a flood of memories.

Geary, Paul and I spent a lot of time together once Paul got hooked by the Rummler process logic. Which was almost immediately. We 3 spent many days and days together in IL, NJ and AZ. And at major MTEC client sites of ours in FL and TX.

Paul was an Engineer, a Manufacturing Engineer - which meant that he didn't just design things - he got them up and running and kept them running and kept up their maintenance. He saw the logic of what Geary was not just talking about, but doing.

Paul liked Geary a lot (in my mind back then) because Geary wasn't just full of theories - he too got things done.

And I guess that's also one of the many things about what "I liked" most about Geary - he got things done. Of course, before Geary changed his focus at the University of Michigan - and got his MBA - he was an engineering student. So their heads worked a lot alike.

I'm still grieving. And that's I guess to be expected. I hope you don't mind me sharing these thoughts.

Thanks again Paul! My best to you and Barbara! And - please take good care of Margaret. I know that the 4 of you were very close over the past 25 years.

# # #

Wednesday, November 12, 2008

Update About the Late Geary A. Rummler

from an email today from the late Geary Rummler's partners at PDL...


Our Sad News
To the great sorrow of everyone at The Performance Design Lab (PDL), our Founding Partner, Geary A. Rummler, passed away on October 29, 2008. Geary had an enormous influence on the field of performance improvement, and his loss to his family, to us, to our clients, and to his many, many students, colleagues, friends and admirers is beyond measure.

Geary A. Rummler
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
At the time of his passing, Geary was, as usual, brimming with ideas and as busy as ever thinking, writing, and building new concepts, tools and approaches, and the Partners at PDL have every intention of staying in business and continuing his work.

At the time of his death, Geary was working with the PDL partners on two books. One is about the process improvement and management "movement" and is intended as a follow-up to Improving Performance: How to Manage the White Space on the Organization Chart, the 1990 groundbreaking work about process that became popularly known as the "White Space" book. The other book addresses management and the design and operations of an effective management system. Both of these books are well underway, and the remaining Partners of PDL do intend to finish and publish them, in Geary's honor and to continue the spread of his ideas to organizations that have benefited so much from him.

Organization Founder
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Dr. Geary A. Rummler was the founding Partner of the Performance Design Lab (PDL), where he was continuing his life-long work on organizational performance improvement in complex systems. During this period he wrote Serious Performance Consulting - According to Rummler for persons interested in "Serious" Performance Consulting.

Prior to founding the Performance Design Lab, Geary was the founding partner of The Rummler-Brache Group, an organization that became a leader in the business process improvement and management business in the 1980's and 1990's. Prior to that, Geary was President of the Kepner-Tregoe Strategy Group, specialists in strategic decision making; co-founder (with Thomas F. Gilbert) and president of Praxis Corporation, an innovator in the analysis and improvement of human performance; co-founder (with George S. Odiorne) and director of the University of Michigan's Center for Programmed Learning for Business.

Geary was a pioneer in the application of instructional and performance technologies to organizations and brings this experience to the issue of organization effectiveness. His clients in the private sector included the sales, service and manufacturing functions of the aircraft, automobile, steel, food, rubber, office equipment, pharmaceutical, telecommunications, chemical and petroleum industries; as well as the retail banking, and airline industries. He also worked with such federal agencies as IRS, SSA, HUD, GAO and DOT. Dr. Rummler's research and consulting took him to Europe, Japan, Korea, Malaysia, China and Mexico.


Accomplishments
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In addition to consulting, teaching and presenting at conferences, Geary published a steady stream of articles and a variety of books ranging from labor relations to the development of instructional systems and his articles appeared in numerous professional and management journals and handbooks.
In 1988, he co-authored Training and Development: A Guide for Professionals, with George S. Odiorne. In 1990, he co-authored Improving Performance, How to Manage the White Space on the Organization Chart with Alan P. Brache.
Geary received his MBA and Ph.D. from the University of Michigan and served as:
• The national president of the International Society for Performance Improvement (ISPI)
• A member of the Board of Directors of the American Society of Training and Development (ASTD)
• A member of the Editorial Board of Training Magazine
Geary's professional accomplishments include:
• Induction into the Human Resource Development Hall of Fame in 1986
• The Distinguished Professional Achievement Award from ISPI in 1992
• The Enterprise Re-engineering Excellence Award from Enterprise Re-engineering Magazine in 1996
• The Distinguished Contribution Award for Workplace Learning and Performance from ASTD in 1999
• The Life Time Achievement Award from the Organization Behavior Management Network in 1999

He will be greatly missed by all who knew him.

To Honor Geary
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Geary's immediate family held a private ceremony in his honor, but did not wish to have a traditional funeral, in accordance with Geary's own wishes. Instead, a public remembrance is being planned for sometime in the Spring of 2008.
Details about that event will be published on our web site.

We have been touched by those of you who have already written to us to express your feelings and the many wonderful stories of how Geary and his work have had an impact on you personally and professionally.
We have added a special place on our website where you can to share your feelings about Geary or his relationship to you.

Those wishing to express private condolences may send them to The Performance Design Lab, P.O. Box 215, Belmont, MI.
Those wishing to honor Geary with a gift may make a donation in his name to his alma mater - the University of Michigan:

Stephen M. Ross School of Business
University of Michigan
Attn: Terri Janni (734-615-4215)
tparks@umich.edu
701 Tappan St., W3700 Wyly Hall
Ann Arbor, MI 48109-1234



PDL Contact Information
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Performance Design Lab
Phone: 616-881-2488
# # #

Tuesday, November 11, 2008

School of PACT 01- Lesson & Video Podcast - PACT Intro

This is the start of an intended Video Podcast Plus series on the PACT Processes and additional related concepts, models, methods, tools, templates and techniques.

"Plus" in that the Video Podcast is merely a component to a blended approach.















There are 6 steps if you will...but do it any way you choose

1- Pre-Video Reading Assignments

2- Video Podcast Review

3- Post-Video Readings Assignments

4- Post-Video Application Assignments

5- Review Free Resources Available

6- Lesson Self-Debriefing



You'll need the book lean-ISD - which is available at Amazon.com as a hardbound and/or as a Kindle book - and/or free as a 404 page PDF here.

There are also many PACT resources at the EPPIC Web site and at the PACT Wiki.

I've been writing/publishing since 1984 on CAD and presenting since 1983 on these CAD methods and the other two methodology-sets of MCD and IAD - and the use of a group process to develop Performance Models and K/S Matrices for Curriculum Architecture Design.

The Target Audience Data, the Performance Model and the K/S Matricies and the ETA: Existing T&D Assessment elements are my contributions to the analysis portion of PACT.

The CAD-MCD-IAD Design models, methods, templates/tools are also mine as well.

I cleared all of that with the late Geary Rummler in 1999 when we met for two days to review the book and the methodology - for his approval/sanctioning. The Video Podcast includes his review of both.


School of PACT #1 - Introduction to PACT Processes for T&D/ Learning/ Knowledge Management

Lesson 01- Objectives
- You should begin to "get/see" the 3 levels of ISD in PACT - and can explain their purposes, their functionalities. Each!

- You should know when you would do one versus the other two.

- You should see how the same/common approach to analysis exists within each of those 3 levels of ISD.
And that the same/common project planning and management approaches, tools and templates are applicable across all 3 levels of ISD.


1- Pre-Video Reading Assignments
I'd suggest reading the very first chapter of lean-ISD - and then watch this Video Podcast.

You could read ahead and cover the first 7 chapters and then watch the V-Podcast. But perhaps it would be better after the Video for you.


The reading and /or the Video may help you mentally frame the 3 levels of ISD in PACT and the common Analysis and Project Planning & Management aspects of the methodologies.

2- Video Podcast Review
Here is the Video Podcast - 10:00 - minutes:seconds...


video




3- Post-Video Readings Assignments
If you did not do this already in Step 1 - read chapters 1-7 of lean-ISD. This should then position you for the next 5 Video Podcasts in this series of 13 or more Lessons/Videos.

These are your advanced organizers - the highest level of overview. Next - the details.

4- Post-Video Application Assignments
Start listing and organizing your questions. Build a table that captures your own questions, the answers and the sources for the answers that you found.

Start a personal Learning Log (or Blog).

Network with others. Start a club/social network - and/or join The PACT Practitioners Guild (a SN). Find a buddy at work - or at a local professional society chapter!


5- Review Free Resources Available
At http://www.eppic.biz/ there is a related PACT Audio Podcast available. Also - there are articles and presentations in the Resource tab at that same site.
















And check out that PACT Wiki for additional free resources/references, tools and templates.

Please maintain my copyright markings. You'd do so for Bob Mager or Joe Harless - wouldn't you?


6- Lesson Self-Debriefing
Do you "get/see" the 3 levels of ISD in PACT - and can you you explain their purpose, their functionality?

Do you know when you would do one versus another?

Do you see how the same/common approach to analysis exists within each of those 3 levels of ISD? And that the same/common project planning and management approaches, tools and templates are applicable across all 3 levels of ISD?

If so - you are ready for the next Lesson and Video Podcast - coming soon!

And don't forget to get your free PDF copy the book: lean-ISD...available at http://www.eppic.biz/




















Adopt-Adapt?/Rigor-Flexibility?
Adopt what you can - and adapt the rest.

Adjust as needed for each effort/application. Always.

Be as rigorous as required - and as flexible as feasible!

Always do the smart thing given your goals, resources and constraints.

Future Additions to this Post and Others in the Series
Note: I will add addition Videos to each post in this School of PACT series over time. These will tend to add additional details - or dig deeper into the details of the PACT methods.

I will put them here - at the end of every SoP Blog Posting.


Final Note:
The SoP - School of PACT Series will cover...

1- Intro to PACT - 3 levels of ISD and common Analysis and common Project Planning & Management concepts, models, methods, tools, templates and techniques

2- CAD - Curriculum Architecture Design - to design the performance-based learning continuum for a targeted job/process

3- MCD - Modular Curriculum Development/Acquisition - the ADDIE level of PACT

4- IAD - Instructional Activity Development/Acquisition -the Knowledge Management level of PACT

5- PACT Analysis -the 4 types of analysis required in PACT's CAD - MCD - IAD "design" methods

6- PACT Project Planning & Management - common project planning and management concepts, models, methods, tools, templates and techniques

7- 5 PACT Roles and 5 Client Teams -defining the roles and responsibilities of the 5 Client teams and the 5 PACT Practitioner roles

8- PACT Process Technology Transfer -how to logically transfer/intake the PACT Processes

9- PACT is a Sub-set of EPPI - Enterprise Process Performance Improvement - a look at PACT as a sub-set of a broader improvement methodology - beyond instruction

10- Segue from Training to Performance via PACT and EPPI - how to move from performance-based Training/Instruction/Learning/Knowledge Management to Performanc eSupport and Improvement

11- T&D Systems View of the Processes of ISD/PI Functional Organizations - The EPPI organizational concepts - of the LCS Model of AoPs/Processes - applied to a T&D function/department.

12- Management Areas of Performance - A Framework for Analysis of Performance Competence Requirements From the Department Rolled Up to the Enterprise

13- Performance-based Employee Qualification/Certification Systems - Develop the System and Processes to implement and operate a function to qualify/certify targeted jobs/tasks for Risk/Reward reasons.


Plus others in the series - beyond these first 13 - all TBD!

# # #

A Salute to All Veterans - Veterans Day USA - 2008















A salute from one veteran to all veterans! This day is for you!

And it is a day to think about our current military personnel and their current burdens and sacrifices for all of the rest of us. And for us to think about their near-term and long-term futures.

And then think about the VA - Veterans Administration, and their individual, process and organizational Performance Competence requirements.

What's at stake?

Keeping our honor. Keeping our commitments. Keeping faith with those who have served.

Support the VA. Push the VA. Expand the VA. Improve the VA.

# # #

Sunday, November 9, 2008

Wiki Structure - Per Process/Area of Performance

Here are my thoughts on: Wiki Micro-Structures...for an Enterprise Context...















If they are part of the system of Instruction/Information intended to enable Process/Workflow Performance Competence - then Wikis need to be macro-organized/aligned to the organization and its processes.

This is a follow up on to my prior post on the EWA - Enterprise Wiki Architecture - here.

But after that framework is done/in place - then what?

The answer to that my friend is blowing in the wind...to borrow/liberate a Bob Dylan phrase from the 60's. I think the answer is quite arbitrary. Too many good answers/approaches.

Arbitrary - but once decided and in place and in operations - there are many downstream implications that should have been part of the Design Criteria derived from the analysis efforts/data/insights that drove the structure before it was put into place - and then tested.

Focus on the processes and then on the enablers - unlike the current Competency movement - focus on the specifics first and then on what can be generalized. At least then the generalizations have a real-world context to back into when you need someone to learn them - to be trained in/on them.

Management Areas of Performance - AoPs
Here is my frame at the Departmental level. And at the Functional and on up levels (see that prior Blog Posting for more on that).

The "boxes" in the Core AoP area are TBD - To Be Determined. As they are unique to each and every department - in terms of the Processes that they own.

But any box (Process/AoP) in the Leadership and Support AoPs might be organized the same way across and up-and-down the Enterprise. They might be.

That's also very arbitrary - but aren't we glad that libraries anywhere in America are organized the same way??? - thanks Dewey!














Here's one set of Wiki Structures - below - very arbitrary - that you might use to stimulate your and others' thinking to come up with your own.

Adapt if you cannot adopt!

Warning!
I think the connotations of each word/phrase are a "communications/clarity issue" as well. And I've labeled these to be clear to you - not for you to use with your stakeholders.

The Wiki Outline/Structure/Architecture
But here goes - again one for each "Process Box" on the Management AoP's Framework above:
  • Process Advanced Organizer/Overview
  • Stakeholders Requirements Table for Process Products and Processes/Workflows
  • Process Policies/Procedures/Guidelines and Heuristics
  • Process Maps
  • Calendar
  • FAQ
  • Best Practices and Awards/Recognition
  • Lessons Learned
  • Archives
  • Misc.

Got a Different View?
Again, this is very arbitrary. Take a shot! Make a comment!

Many Enterprises start with numerous pieces already in place - seldom with a blank slate - and so variance is inevitable - and appropriate!

The PACT Wiki is just one of several wikis I started/operate/manage.









I hope that you have found this to be useful!

Taking advantage of Web 2.0 performance enablers (too often referred to as Learning tools) is key to every one's futures!

Instruction should be used when Information is insufficient on its own. Otherwise default to Information.

And then hire people who can read - and will read - when/as necessary.

Hire those who will think versus blink.

# # #

Enterprise Wiki Architecture - For a Process/Workflow Orientation to Instruction and/or Information During and/or Before THE NEED.















Because - as always - it depends!

This post contains a new Video Podcast on an engineering/architectural scheme for an "Enterprise Wiki Architecture" for your Enterprise.

Adoptable- and - Adaptable.

Whatever fits for you!

The V-Podcast...

video



The 7:22 minute:second Video Podcast above tries to answer the question posed in the next graphic...
















Imagine a few years from now - when long after your IT organization had finally relented and everyone has wiki capabilities. And you - the single shareholder - go to investigate the returns on this investment and the current-run-rate for costs associated with operating it and maintaining it.

Or maybe you got sued because someone on the payroll used some old Best Practices that no longer squared with the laws/regulations. Use to. Not anymore. But it was still out there on your Intranet. And you lost and paid. Or you won and paid.
















How to organize? Processes first and employees second? Employees first and then Processes?

Actually, both together.

Using my Management Areas of Performance model. From my book of the same name. More on the book later. BTW- AoPs are a version of a WBS - Work Breakdown Structure. Only of performance at the Individual level, an AoP/Process level, an Organizational level/Enterprise level and at a Societal level.

At all 4 levels. That's Kaufman - not Kilpatrick.

All departments have their own processes that they own. Their people may work on not only those - but in processes owned by others.

I address this by focusing on the "Department level" for organizing my view of processes - which is scale-able from the department level all the way up to the Enterprise level. And captures all employees.
















Some processes that a Department's employees may work/perform in are shared - and not owned by their Department - the budgeting processes, the selection/hiring processes, the sales forecasting processes, etc. - but they must participate in them non-the-less.

















How can you capture the Unique processes of a Department as well as the Shared processes? Use this model as your initial frame.

















The Management Model is about Management - but also serves to frame all of the Processes - of an Enterprise.
















I think an Enterprise can be both functional-organized and Process-oriented. I don't think the Enterprise has to be Process-organized. That would not be efficient - unless the scale is small.

The functions in "operations" and "administration" and all other functions - can be looked at by their "owned Departments' processes" and any of their unique processes - at the Functional level - as well. That's their CORE: every thing below their level - they "accumulate" everything that reports up.

And they have shared LEADERSHIP and SUPPORT processes as well.
















Can you use this?
















And can you mashup these and use both the Management Areas of Performance framework and your Organization Structure in a blend - to architect all of your Enterprise Wikis - to address all of the processes/workflows and minimize gaps and overlaps?

And be more efficient with the shareholder equity you wish to invest?






















Why care about "architecting" wikis?

The advent of the "wiki" as one of the hundreds and thousands of Web 2.0 tools/functionality of the current version of web enablers - has great potential to be good or bad investment-wise. So skip this if you don't care about ROI or ROA or RO-something

And why an architecture?

Can't you just get corporate IT to buy into and install some hip-happening wiki capability and stand back for those "one-percenters" of content contributors - Hells Angels and wanna-be's move over - and enable it and they will do good? They will capture all that Baby-Boomer Know-How before it walks out the door - oh wait! - there's been a reprieve on early retirements - so there is still time!!! Still time! Whew!!!

Who will figure out the jumbled, hodged-podged-set of content that you've amassed. A collection of courses and more?

Or can you help your Enterprise avoid that - as it is anticipatible!

Random Lessons Learned and Best Practices for whomever. After a while you could have thousands. Sure - just search for them!

Good old Boolean logic. User friendly is not 38,345 responses/hits to my inquiry. Not even.





Can't this just be open, free, informal, non-restrictive?

Sure - unless you care about ROI, or any other number of business metrics where you typically have to measure results somehow someway to justify a cost before and/or after the fact. Some people have to predict - and some have to be accountable.

The costs side is easy - or easier. The returns side is harder.

The very best way I know about getting your customer/client/and other stakeholders to be clearer about your results - is to be very aligned with the processes of those stakeholders.

Here is a chance to align to both them and their processes/workflows.

Architecture - sounds so restrictive
Can't this be "the open range of free content" - and if you've good good search tools/methods you will survive the coming information tsunami - or did I miss its arrival being distracted as I am by the inflow of all-sorts-of-things needing my attention?

Because there is a lot of potential for overlaps and gaps in critical content. The low-hanging fruit might get addressed because that's always been easier. Pre-Web 2.0 and now here in Web 2.0.

The use of wiki as a repository of helpful - in a "I've got a job to do here" and "I've got a process to comply with here" and "I've got a law to comply with here" - JOB AIDS (EPSS) and Learning and Knowledge Management goodies, etc. cannot be understated. Video Clips (such as this), PDFs of almost anything imaginable. Good and bad. Current and Obsolete.

If you don't get ahead of this - you be like many of clients over the years who inherited a hodge-podge of content, collections of course I call them, and needed to reconcile them - they didn't have ownership issues and were open to "blow it up and start all over again (Tobacco Road)"....

So you need to create a rationale, scale-able, maintainable scheme for all of your various media-varied content. So that you simply don't create an avalanche for the Learner/Performer to later dig through.

Remember them?

How easy or hard have you made this for them now and for later? What can you do now to help them later??????????????????????????????????????????????????????????????????


Life-Cycle Costs and Returns
And if you don't care about costs - the potential to better enable process/workflow at cheaper costs over the entire life cycle - more than just first costs - because "IF YOU BUILD IT AND THEY DO COME - ARE YOU WILLING TO MAINTAIN IT?" - then don't worry about this at all. What's the worst that can happen?

It's more than just first costs and returns. It's a life-cycle full of costs for returns. Hopefully well worth it - IF you were the single shareholder how would you feel about this?

Wikis to enable Process-Workflow Performance?

Would you want it/them "open range" or "process/people-centric" for your dollar (or yen, ruble, etc.)?

I like Things Organized. Do I Need To Capitulate to the Inevitable?

I hope not. I hope to fight it by being as organized as I can. In all things.

I hope this is of value to you!

Get the free book PDF: Management Areas of Performance at http://www.eppic.biz/

As well as hundreds of other ISD/HPT - Instructional Systems Design/Human Performance Technology resources!

Cheers!



# # #

Saturday, November 8, 2008

Cost of Nonconformance and Conformance for ROI Calculations for Training & Development/ Learning/ Knowledge Management Projects

This post focuses on a simple method to justify training using the “business metric” with which management is familiar: ROI - Return on Investment.

And to calculate ROI we'll use two numbers - the CONC: Cost of Non-Conformance - which are the costs or values for problems/opportunities - and we'll use the COC: Cost of Conformance - which are the costs for getting the problem/opportunity addressed/resolved/etc.

To get your training/ learning/ knowledge management projects funded, you need to be able to state both what it will cost and what it will deliver for the investment in terms of increased or better performance, and then compare the two figures.

If you were the single shareholder for your Enterprise this is how you would want this approached!

Introduction
TRAINER 1: “Well, our program didn’t get funded. Management said it didn’t show enough results.”

TRAINER 2: “I don’t understand it! We clearly defined all of the learning and competency objectives and benefits.”

If you and your colleagues have ever lamented over your management’s failure to fund the training effort adequately, you should stop to consider whether or not you have been attempting to sell them using the business terms that they are familiar with or the training terms with which you are familiar.

No one cares about Learning Objectives - they care about Performance Objectives. It's not about Learning!!!

And don't even get me started on why we insist on slapping the Learning label on anything Web 2.0.

Give me a break. These are for fun or function and one will learn something using them just as one would learn something from climbing a tree or swimming across a lake. Why is about us - Learning - rather than "all about" our clients and stakeholders who see learning as a necessary means to the ends of their performance competence requirements?

You know - the ability to perform tasks to produce outputs to stakeholder requirements.

We enable.

These tools enable.

Performance-based learning/training/knowledge management systems and content enables.

Let's focus "on the non-FUN was our Intent collection."

These web 2.0 tools are performance tools, as in Enterprise Process/Workflow Performance tools. Don't call them Social Networks and expect the CEO to get excited. Call them Performance Tools and you might get your 30 second elevator speech in about ROI for Web 2.0.

But I digress.

We in training have a tendency to expect everyone to learn our jargon, and then we complain when no one will listen to us. We need to learn how to sell our training products and services from a business perspective. We need to become business champions first and training champions second.

We need to learn to think and speak in the language of business, using terms like ROI - return on investment. Management does not have unlimited resources, but they will spend their resources on a training project if it can be shown that the ROI for the training project is greater then the ROI for other potential investments.

You and your training project are in competition with all other investment opportunities of your Enterprise, including hiring additional personnel, buying machinery, developing computer information systems, or discounting the prices of the company’s products and services.

You need to prepare a business case that fully justifies the expenditure of corporate resources on your training project because it is a wise decision, not because training is the morally correct thing to do. Find any business case that was successfully used in your Enterprise and model your after that. Ask anyone in Finance to review your math.

But Do The Math!
An approach to the Math that might be useful for you...

A business concept that came out of the quality movement in the 1980s and popularized by quality guru Phillip Crosby is the concept of the “cost of nonconformance” (CONC). To determine the CONC, a business must look at what it costs the organization

• If its performance does not conform to standard
• To be less than perfect
• To have more than zero defects

The CONC is the dollar value of the difference between 100% proficiency and the current level of performance proficiency. To the advocates of performance technology guru Thomas F. Gilbert, this is the same as the PIP - performance improvement potential.

PIP = CONC

Because of the high-value visibility of the quality drive represented by Six Sigma and Lean (although Lean efforts should always go first), I suggest that you begin to use quality, productivity, and financial terms rather than performance technology terms when talking to or selling to your customers or management.

Performance technology already embraces all of the same concepts—we just use different labels, and that’s all we’ll have to give up! But we will have to translate our concepts, methods, tools, and results to the language of our customers-business terminology.

To use the quality/productivity concept of CONC, we need to be able to calculate the ROI for bringing performance in line with standards where the CONC gets as close to zero as practical. What is the ROI for eliminating or reducing the CONC?

ROI
To determine the return on investment for a training project intended to minimize or eliminate the CONC, we must look at the existing performance at which our training is targeted.

• Where is it at now?
• How much can it be realistically improved?
• What is the difference between the current value of performance and the potential value of performance? (This is the equivalent of the return, the PIP, or the CONC.)
• How much will it cost to fix it?

These figures will allow you to forecast what the return will be on the investment in dollars and the ROI percentage:














The CONC value, stated in dollars, is used within the ROI calculation in place of the return value.

Calculating the Potential Value of Performance
In its most simplistic view, calculating a CONC value requires two elements.

• The potential value of performance
• The actual value of performance









Figure: Calculating a CONC Value

Some jobs are easier to quantify and as a result, it’s easier to assign a dollar value to the difference between the actual and potential performance. Salespeople generate sales revenues in dollars. Widget assembly workers produce a number of widgets at fairly definable labor, material, and overhead costs. A singular focus or a highly repetitive set of tasks lends itself to easier measurement.

But for many jobs, there are too many variables and difficulties in measuring and assigning a dollar value to the performance. The elaborate measurement systems you need may not be in place, or the data you need may be hard to come by. These types of jobs could include secretaries, design engineers, managers, architects, computer programmers, materials expediters, etc. They are all somewhat problematic when it comes to establishing the dollar value of the performance.

When potential value of performance is extremely difficult to determine due to the number of variables or the lack of measurement systems data, one could use the cost of that performance as the benchmark - the labor dollars that it would cost to have 100 percent work proficiency (or whatever is feasible in the eyes of your management).

If we have a workforce of 100 widget workers, each earning $35,000.00 per year, our potential value is $3.5 million. This figure represents what it currently costs the organization for the potential of having 100 percent performance conforming to standards.

In most companies there is only a slight difference between what top performers and average performers earn. So the cost or value of the potential 100% job proficiency is approximately the equivalent of the performer’s total wages.

In our example, we have 100 performers earning a total of $3.5 million (figure below).

That’s the value to your top management. That’s our benchmark.








Figure: Calculating the Potential Value of Performance

If your organization pays for performance and the better performers get paid more for their superior contributions, your calculations would be more complex. But the benchmark for comparison will still equal the sum total wages for the entire group of performers.


Calculating the Actual Value of Performers
But what are we getting for our $3.5 million? Are we getting full value, 100 percent job proficiency for it? Or is some performance proficiency slipping through the cracks? What is the actual value received for the cost of performance?

What if our target audience performers were on average only 60 percent proficient? What is the CONC then worth to us?

To calculate the actual value of performance, again multiply the number of performers by the average salary, but this time, multiply by the average actual proficiency level...












Figure: Calculating the Actual Value of Performance

In this case, our actual value of performance is $2.1 million.

Calculating the Cost of Nonconformance (CONC)
The CONC is calculated by subtracting the actual performance value from the potential performance value...










Figure: Calculating the Cost of Nonconformance

So, in this case, the CONC is $1.4 million annually.

That’s $1.4 million left on the “performance table,” so to speak.

If your training could get everyone to perform at the 100 percent level, $1.4 million would be the return to be compared against the investment required to make that happen.

If 100 percent seems too “blue sky,” then consider the results if your training can get everyone to average or 75 percent, 80 percent, or 90 percent; respectively, you would still contribute $1.05 million, $1.12 million, or $1.26 million to the corporate bottom line! That’s the resulting “return” to the organization.

We’ll calculate the ROI percent later.

Although calculating the CONC using salary data as the benchmark can identify significant contributions, it doesn’t begin to capture all the other additional costs that might be incurred due to less than standard performance, such as

• Scrap/waste produced
• Extended or rework labor
• Extended or rework machine/equipment operating and maintenance costs
• Schedule slippages
• Lost opportunity for other work
• Etc.

If these additional “costs” were included, your CONC value would be even higher. The larger your audience, the greater potential CONC, making it even more worthwhile to address. These are numbers that can get your management’s attention!


Computing the CONC in More Complex Situations
The example we used above to calculate the CONC was quite simple: one type of performer earning the same salary, performing at approximately the same level. So, what do you do when the situation is more complex—where there are several types of performers earning varied amounts of money and performing at different levels of proficiency?

All that’s really needed is one or more charts like the one in the next Figure...

















Figure: Computing the CONC in More Complex Situations

This chart segregates the employees in the target population into ten different levels of proficiency. This may be too much. Four or five levels may suffice. Adopt or adapt.

Questions to consider include

• How many levels or classifications do you have or need for the proficiency of performance?
• Is ten levels, 10 percent through 100 percent, too many or too few?
• Could you use smaller increments of 25 percent? Four levels of 100, 75, 50, and 25 percent?

I suggest you try four or five, but in any event, it’s your management that has to finally agree with the segmentation scheme. The goal is to make it understandable to your management.

NOTE: Determining how much your organization is really getting for its salary dollars is a potential powder keg. Reputations and careers are potentially at stake. Move cautiously. It will be easier to move through this minefield if your organization has had or is expecting a major change in the business that has/will create this CONC situation. Fewer people might then be fearful of being blamed. Of course, if you have a politically “wired” project champion involved in your project from outside your training organization (i.e., a client desiring the project), you can follow their lead.

Calculating ROI
To determine the potential ROI for your training project you need two estimates.

1. CONC
2. Estimate of the training/learning/KM investment costs (I prefer "all in costs")*

This will allow you to forecast what the return will be on the investment. The formula is as follows:

ROI % = CONC – Investment Cost
Investment Cost

* "All In Costs" are the costs to be compared with "doing nothing at all."

This ROI percentage can then be compared to other opportunity ROIs by top management or even by the training function to determine where to spend their limited resources. Should it be on training for a particular group, or should it be for new capital equipment or buildings? Where is the biggest bang for the buck?

What would "a single shareholder want to do with their money?" Do like-wise.

Other data you should have is

• What is an acceptable percentage return?
• What kind of returns are management achieving lately?

Of course, other factors need to be considered in the decision to allocate resources. The overall level of assurance that you can achieve your claimed potential return is something your management will take into consideration.

Management Buy-in
Now that you’ve got your ROI, how do you get the organization to agree with your answers? What’s the best approach? The one most believable, even if not perfect?

Well, who has to believe it? The people you’re trying to sell—your management. How can you make it believable? Have them help generate the figures that go into the calculation. If they don’t like the end result, let them change the figures again and again until it becomes something that they can believe, explain, support, and defend.

Even if we in training had the absolutely correct equation, variables, and values identified, if management won’t buy it, what good is it? And if their answer doesn’t create a go-ahead for your project, maybe your project shouldn’t be done. Maybe there really is a better or more strategic use of the limited corporate resources.

Your next step is to package and present the data for making that decision.

Developing the Business Case
The business case is your formal case for training. Call it anything you’d like, but if you can’t prove it here, you’ve no business asking the organization for the resources. A business case for training should include sections detailing

• Project purpose and goals
• Project background and need
• Problem/opportunity statement
• CONC calculation
• Solution strategy alternatives and recommendations
• Solution recommendation implementation project plan and budget
• ROI calculation(s)

Try to obtain a copy or outline of a business case that has been used within your organization. Product and service management groups found in marketing may be a good source for this.

Summary
Training should never be done for simply the sake of doing training, even where you can clearly identify the need for it. It may cost more to provide the training than it could ever return to the business.

There may be better investment opportunities for the organization to promote productivity improvement or product/service quality (both internally and externally) and thus contribute to the financial viability and stability of the organization.

Don’t be a training or learning or knowledge management champion.

Be a business champion!

# # #

The Detailed Project Plan - in the PACT Processes

The 5 Ps of Planning: Proper Planning Prevents Poor Performance.

Which way to go? Just Blink - or - Really Think?





















Need a plan, Stan? Or are you just going to wing it? Process-free?


Or are you looking for more predictability?


This post is sourced from an article that was originally published in SWI - Svenson & Wallace, Inc.’s Management Update Newsletter, Summer 1992. That was based on a session I did for the Chicago Chapter of NSPI (now ISPI) back in 1983. And it is based on 13 years of actually planning ID/ISD projects by me at that point in time. At least 50 projects by then.


Also - there are Project Planning resources available at the PACT Wiki.

Planning-Schlamming
What's the big deal about Planning?

I believe that trainers need to plan well to help ensure that a training project meets all of the internal training organization’s and external customer’s criteria. However, many trainers resist developing plans detailing their projects. The rationale? The plan is too subject to change to be worth the effort of planning at a detailed level.

My personal view is that most (not all) Project Plans that are subject to many changes were probably not very good plans in the first place. Or, if they were good training Project Plans, they were poorly communicated/sold to the customer, and changes occurred in the plan because the plan was not really the customer’s plan as well.

It’s fact that many trainers either avoid making detailed plans or making any plans at all. However, I believe in detailed planning because the process forces me to think through

• All of the key tasks required
• The prerequisite activities for key tasks
• The key outputs/deliverables

These are critical for the planning process.

With a good plan, I can better anticipate potential issues and problems. I can build strategies and tactics right into the plan to preemptively deal with those issues and problems. My Project Plan is critical for spelling out the details of the intended project—all the whats, whens, wheres, whos, and whys.

Most trainers are able to conduct a detailed task analysis; they should very easily be able to construct a detailed list of tasks to conduct one of their own projects. A trainer could even pretend to be conducting a task analysis exercise on him- or herself, being both interviewer and interviewee.

What is a detailed plan good for? It can

• Provide direction to all personnel involved in the project, including the customer’s personnel.
• Allow tracking of the planned schedule and costs in close to real time.
• Help the project get back on track if something starts to derail it.

Most importantly, if approached correctly the planning process can be used to get customer buy-in. The best way to do this is to create a rough draft of the plan after obtaining the customer’s input. Let the customer review and edit the plan. Let the customer own the plan. We should think of the project as the customer’s project and ourselves as implementers of the project.

Eight Sections of a Detailed Project Plan
The Project Plan should contain the information described in the eight sections below. The content can be organized and presented in many different manners, but plans containing this kind of detail have served us well as we’ve completed training projects over the years.




















Figure: The Eight Sections of a Detailed Project Plan

1. Purpose
This section deals with the what of the project. It presents a very short statement reflecting the ultimate end objective(s) for the project, expressed in a manner such as, “The purpose of the proposed project is to . . . (fill in the blank).”

2. Background
This section expands on the rationale for conducting the project, the why. Why this project, why now, why for this target audience(s), etc.? This section usually ties the project to the business conditions and initiatives driving the project.


3. Scope
This section identifies the who of the project, the target audience(s) that will be addressed. It also establishes the breadth and width of the project, including the project boundaries. The scope must be well understood early in the project so as not to create false expectations.

It is vital that this section of the plan be easily understood by all customer segments (including executive management). Poorly managed customer expectations at this early stage almost certainly guarantee disappointments at the end of the project.

4. Approach
This section outlines the various methodologies and mechanics to be employed in conducting the project. What is the general or primary method to be used? What are the secondary methods? How will these methods be used—for data gathering, data reviews, design efforts, design reviews, etc.?

If you intend to use surveys, individual interviews, group-process interviews, document reviews, and so forth, spell those out here. Use this section to avoid surprises as to how you conduct the project.

5. Project Phases and Milestones
This section provides an overview of the phases and milestones used in the Project Plan. We use the six phases shown in the diagram below for our ADDIE-level in the PACT Processes: MCD - Modular Curriculum Development/Acquisition.











Figure : Project Phases for PACT's MCD (ADDIE-like) Methods

Shown in this way, it’s apparent that we’re dealing with a process. Our detailed plans are one way we maintain control over the course development process, specifically control over

• Quality
• Cost
• Schedule

In fact, we use detailed plans in all our projects, not just for training development projects.

6. Outputs/Deliverables
This section outlines the specific, key outputs to be produced during the project. A detailed description of each output should be included. The use of the output during the project and after the project should be spelled out.

7. Roles and Responsibilities
This section presents the roles and corresponding responsibilities for all groups or teams involved in the project. Typical roles and responsibilities are shown in the sample page for Section 8 on the following page. (Of course, not all projects are organized by group or team. In those cases, the roles would be changed and the responsibilities assigned to other individuals or parties.)

8. Project Tasks/Roles/Schedule
For all project phases, this section presents the project tasks, estimated time requirements per role, and the estimated schedule for tasks. A sample page from this section is shown below.

















Figure: Sample Page, Plan Section 8

The toughest thing for most is to get good a planning both "task touch time" and "cycle time" - and "tightly versus loosely" planning for the inevitable - the Murphys in the world - as in Murphy's Law: "Anything that can go wrong probably will." But you cannot always give your self a yard/meter when you only needed a few inches/centimeters. That would cause a lot of down time - not good if you care about utilization/efficiency of your resources.

Is Detailed Planning for You?
My clients have told me that this planning process is one of the things that differentiated us from other consulting and training organizations. In fact, some clients have adapted this approach and format for their own use. Once they had one or more copies from a couple of projects - it was something that they could easily replicate. Adopted - or adapted.

In our experience, the detailed Project Plan serves trainers well. It can help trainers and customers alike come to a clear, consensus view of the project and its intent. Which is important. Shared understanding, etc.

My advice?

Plan for the details. Plan for execution. Plan for Murphy. Plan for success.

# # #

Guy W. Wallace’s PACT Facilitation Guidelines: # 5 - Use the Four Key Communications Behavior Types

I call these “The 12 Rules and Guidelines of Proactive/Confrontational Facilitation for the PACT Processes for T&D.”















This is 5th in a series. The 12 are:

1. Go Slow to Go Fast.

2. Be Declarative.

3. Write Stuff and Post It.

4. Be Redundant by Design.

5. Use the Four Key Communications Behavior Types.

6. Review and Preview.

7. Write It Down and Then Discuss It.

8. Use Humor.

9. Control the Process and the Participants.

10. Be Legible on the Flip Chart.

11. Beware of Group-Think.

12. Assign Parking Lot Valets.

The 5th of these is covered in more detail in the following text.

Read them. Learn them. Use them. Practice them. Reflect on them. Grow with them.

5. Use the Four Key Communications Behavior Types
The single most powerful insight I have gained in my evolution as a facilitator was from my exposure to a “communications behavioral model” from a “Win-Win Negotiating” course and a “SPIN®” sales training course from Huthwaite, Inc.

I feel most fortunate to have been involved in those training courses in 1981-1982 while I was a Training Project Supervisor at the Motorola Training & Education Center (MTEC―the forerunner of Motorola University). There I worked for Bill Wiggenhorn and along with John Cone, Alan Ramias, and 9 other TPSs.

The model identifies four key verbal communications behaviors. I use to almost always categorize my verbal expressions into these four, even as I was saying them. And I use to typically “see” others’ verbal expressions falling into these categories, even as they speak!

That was a long time ago - and now I probably operate more at an Unconscious Competence level - which of course can easily slide 3 levels to Unconscious Incompetence if not watched carefully. That's what coaches are for. That's why Tiger Woods has them. To watch carefully what he is doing so that they may correct elements of his game.

But I digress.

The four types are
1. Giving Information
2. Seeking Information
3. Testing Understanding/Summarizing
4. Defend/Attack

When I learned this - back in 1981 - these 4 were part of a larger set of "communications behaviors" that were part of the larger set of Huthwaite methods for both SPIN and Win-Win Negotiations. In SPIN there were 11 such CBs - and in the Negotiating model there were 13 CBs. None of this was later "visible" in the courses - it was more embedded.

I learned these directly from Neil Rackham and John Carlise who trained both Barbara Warbritton and myself in preparation for a Pilot-Test session of a Negotiating class I was project managing. Barbara and I got certified by them as "observers" who would observe a dialogue between two or more people - and we would track peoples behaviours and give them feedback later.

The premise was that early in the dialogue (sale or negotiation) the behaviors were a certain subset of the full list - and in the middle there would be a different pattern of behaviors - and at the end yet another pattern. They had tens of thousands of such observations - and they knew the different patterns used in sales calls for short-cycle sales versus long-cycle sales - what is today referred to as transactional sales and consultative sales. Pretty cool.
















I've also built these four behaviors into training sessions for Product Managers, Program Managers, Project Managers, and Sales and Sales Management in a way that they learned to "see their own behavior patterns" in the role plays we would put them through as they focused on some other task-set while parallel processing about how they were doing the verbal part of the role/process performance targeted.

Again, the four types are:
1. Giving Information
2. Seeking Information
3. Testing Understanding/Summarizing
4. Defend/Attack

Giving Information
The “giving information” communications behavior is straightforward and important. When facilitating PACT Processes, giving information is the place to begin. Generally, you may need to first give some information before you “find things out,” but you should soon be shifting gears into the next type.

Seeking Information
The “seeking information” communications behavior also is simple. It’s typically in question form, either open-ended or closed-ended, depending on what you’re trying to accomplish.

Knowing how you balance these first two types of communications behaviors is important in assessing your success and failure as a communicator, but nothing beats the next communication behaviors.

Testing Understanding/Summarizing
The “testing understanding/summarizing” is actually a combination of two behaviors, but I often combine them to simplify their use. However, they are different.

Testing understanding is making statements or asking questions for the purpose of testing what you think you’ve just heard or what you think you know. Most of us know this as a form of “active listening.”

One of the best ways to test understanding is to paraphrase what was said. Putting it into another set of words, rather than simply parroting it back just as you heard it, allows the sender to better check your receipt of their message. If you parrot it back, all we know is that you remember the words. The further your paraphrasing takes the original words away from the words you use, the easier it is to test for understanding.

It is also best to be somewhat declarative of what you’re doing when you test understanding. I often announce, “I am testing here” and then make a statement or ask a question. Then listen for the response, and always read the clues and cues of nonverbal facial and body language. You can also say, “Let me see if I’ve got this. You’re saying that x, y, and then z. Is that right?” Work on your own set of phrases to test understanding. Play with it!

The second part of this behavior is summarizing. Again, it’s best to provide your own clues and cues to your group. Say, “Let me try to summarize this,” and then do it. If your words stray from the original (but not too far), then it’s easier for the group to react.

Summarizing is very much like testing understanding, just done in a different mode. You are looking for feedback from the group that you are either right on, just off, or way off. Again, don’t let your ego get in the way! I tell groups, “As a facilitator, I can’t be afraid to be wrong because it’ll slow us down. In fact, I’m often wrong. So get used to it! Your job here today is also to correct me and keep me on the straight and narrow path!”

Testing understanding and summarizing are critical to ensure that we understand the meanings behind the words that others are using. As a colleague of mine once remarked: “It not just semantics, it’s always semantics!”

Testing understanding and summarizing helps us receivers comprehend the intent of the message sender. Testing understanding can be a very powerful tool for a facilitator. (Of course, Socrates used this technique way back when, so be careful! Watch out for hemlock.)

Defend/Attack
The “Defend/Attack” behavior is also a combination. Defending is typically in response to a real or perceived attack. No matter how it starts, it usually degenerates into a defend/attack spiral that won’t end until someone interrupts the spiral. The best interruption is to test understanding and summarize―something on the order of, “So you’re saying that this proactive facilitator stuff is just a bunch of hooey, and that the author must be a real jerk to perpetuate this garbage by committing it to paper and then disseminating it to the public?”

Usually a short string of tests and summaries are sufficient to defuse the situation and end a defend/attack spiral. All that the irate usually want is to be heard (and understood). Get the conversation back to more civilized ground and reduce the heat.

In my mind, the power of testing understanding and summarizing cannot be underestimated. Try it yourself. Try it on the kids. Try it with your significant other. (But stay away from gang fights!)

Using the Four Key Communications Behavior Types
Once I learned the four communications behavior types, I began to “see” all of my own verbal utterings as falling into one of the four categories.

I learned to first give information, maybe a little or a bunch, and then to soon test understanding. Do they get it? For example, “I want us to list all of the outputs for this Area of Performance and then identify all of the key measures of performance for each. Are we all clear on what I mean by performance outputs?”

Or, “We need to identify the typical performance gaps, if any, for this output.”

Or, in response to the group’s input, I test understanding for my benefit. “So the typical gap is that they are almost always late in turning in the monthly report?”

I also test understanding in response to their statements. “Let me test this out. You’re saying that there are indeed typical gaps, but they don’t sync up with any of the key measures we have currently listed.”

I learned to seek information and then summarize. “What gap do you think there is, and what key output measure would reflect that gap?” I would respond to their response with, “So we seem to be saying that it would be both a time to complete as well as a timeliness measure.”

I learned that the best way to break a defend/attack spiral is to first test understanding/summarize and then either give information or seek information. “So you think that global T&D dropped the ball and didn’t get the vendor into the effort soon enough, driving up your costs due to all of the overtime that was incurred trying to catch up?”

I learned that the more I test understanding and summarize the more it benefits the group, because they are sometimes hesitant to appear stupid. Again, I can’t afford to let my own ego get in the way of potentially appearing stupid, slow, etc. I’ve learned that the really smart people in the room will quickly figure me out and that I won’t appear stupid at all, no matter how hard I might appear to be trying with all of this testing understanding behavior.

Summary & Close
This is great stuff. It made me more comfortable to have these communication behavioral tools at my disposal when I first started, and I believe it has made a big difference in my approach and style. It has made me a much better facilitator.

I hope that you find these something that you can adopt and adapt as needed.



















In the future we'll cover the remaining 7 rules/guidelines one-by-one!

Cheers!

- Sourced and edited/embellished from Appendices C of: "lean-ISD" - a book by Guy W. Wallace - available as a free 404 page PDF at http://www.eppic.biz/ - along with 3 other related books on ISD via PACT (lean-ISD) and Enterprise Process Performance Improvement - also available as free PDFs.

# # #

Thursday, November 6, 2008

Guy W. Wallace’s PACT Facilitation Guidelines: # 4 - Be Redundant By Design















I call these “The 12 Rules and Guidelines of Proactive/Confrontational Facilitation for the PACT Processes for T&D.”

They are:

1. Go Slow to Go Fast.

2. Be Declarative.

3. Write Stuff and Post It.

4. Be Redundant by Design.

5. Use the Four Key Communications Behavior Types.

6. Review and Preview.

7. Write It Down and Then Discuss It.

8. Use Humor.

9. Control the Process and the Participants.

10. Be Legible on the Flip Chart.

11. Beware of Group-Think.

12. Assign Parking Lot Valets.

The 4th of these is covered in more detail in the following text.

Read them. Learn them! Practice them! Use them.


4. Be Redundant by Design
All marketers know that for a message to penetrate the psyche of the receiver and convey the intent of the message, it will need to be repeated . . . and repeated . . . and repeated.

Enough said?

I don’t think so.

If you’ve said it once, you’ll probably need to say it again.

And then repeat it again.

This becomes a problem for those who are quicker on the uptake. Just as group-paced, traditional training is usually held hostage by the slowest in the group, so too are meetings. More on this later.

Active Listening - Applied to Facilitation
You know - paraphrasing what someone else said to "check for understanding" and/or "summarize" - so that you/someone can move on. So that they know that you know! And that everyone else knows too (this might require a round-robin of summarize your understanding - potentially putting everyone/someone on "the spot" - not a good practice for a facilitator.

Because the facilitator isn't the only one responsible for moving the meeting along.


Playing to the Quick or the Slow?
Back to Quick versus Slow.

Those who get it quicker will get irritated with you for thinking they didn’t get it sooner. Because you are being "so" redundant that YOU MUST THINK THAT THEY DON'T GET IT!!!

This is tricky.

Who do you play to: the quick or the slow?

I play to the slow. If I sense that some individuals are getting annoyed with me for this, I talk with them on break and enlist them in my efforts to get everyone else on board. They are usually way cool with it, because they’re in on it and know that I know it’s not them! (I told you this was tricky!)

Usually they will step in during my next bout of “redundantitis,” and help me explain my point.

Often they have better command of the group’s language and jargon and can provide better examples, non-examples, and analogies that may actually cause the cognitive breakthrough I was struggling to create. The whole group breathes a collective sigh of relief when they all get it or know that everyone else has finally gotten it and that I will quit beating them over the head with it.

I could let my own ego get in the way and not create the tension that redundancy by design causes by saying it once and moving on. But having been burned by that, I have learned to face the short-term wrath of the group in order to ensure that the train is moving ahead with everyone on board.

Also, some of your clients may feel that since they get it (they are often in our same business and naturally want and try to get it ASAP), everyone else must have, too. They may make the mistake of thinking that your redundancy is no longer tolerable because they see the quicker “learners” of the group squirming. But they aren’t often in a position to read the clues and cues in everyone’s eyes as you are from center stage. Balancing the clients’ needs to keep the group happy and see progress without getting impatient can be tricky.

You’ll need to determine when it’s safest to proceed―when you can leave someone behind conceptually. When will it do little or great damage to your next steps? Will it cause problems in these next steps, will it cause rework, will it cause greater frustration in the rest of the group, will it then destroy any group “teamness” that may be starting to form? Tricky, eh?

Next...or really...later...

In the future we'll cover the remaining 8 rules/guidelines --- one-by-one until done!

In the future we'll cover the remaining 8 rules/guidelines --- one-by-one until done!

In the future we'll cover the remaining 8 rules/guidelines --- one-by-one until done!

Cheers!

- Sourced and edited/embellished from Appendices C of: "lean-ISD" - a book by Guy W. Wallace - available as a free 404 page PDF at http://www.eppic.biz/

# # #

Wednesday, November 5, 2008

Another Rummler-ite? Dave?

from
Dave’s Whiteboard
Interests, ideas, notions, tangents

How Geary Rummler helped me get leaner
November 5th, 2008http://www.daveswhiteboard.com/archives/884

Geary not only influenced six sigma - but lean as well!!!

# # #

T&D/ Learning/ Knowledge Management/ Performance-Aids/ EPSS/ Etc. "Systems" - Results Oriented - Or Why Bother?














Much has been written about "Learning in the Workflow" - and while that is not only feasible and practical for many jobs - it doesn't fit all jobs. It's situational. As always, it depends.

Sometimes "learning in the workflow" is way too late. Way.

Sometimes "learning in the workflow" is needed after learning prior to the need. And then it is re-enforcing or a reminder-aid... a "job/performance aid" for use "in the workflow" after being oriented to the "aid" in both content-terms and systems-terms...PRIOR!

But in any event-the returns expected for the investments should drive resourcing. Or not.

Thus... the "80% of learning" job content being informal.

It's not all about Learning. Not in an Enterprise context.

It's about the CONC compared to the COC. As in: "Cost-of-Non-Conformance" and "Cost-of-Conformance." The "costs for leaving things as they are" and "the costs of fixing it."

That's why one should "bother" with performance and learning.

That's why the Enterprise should bother. For ROI - however one 's Enterprise calculates it. However THEY calculate it! Not how you calculate it!!! How they calculate it!

Learn that! Know that! Use that!

# # #

HR Matters - Yes Indeed!!! And So Does "Empowerment As A Process"












My thanks to the folks at HR Matters (published in the Asia-Pacific area) for publishing my EMPOWERMENT AS A PROCESS article in their September issue. The original was first published way back in 1995.

Readable online at: http://www.hr-matters.info/features/0406.htm.

I think it still holds true today! Let me know what you think.

# # #

Free PDF Book Download Status Updates











And you can purchase hardbound copies of both

lean-ISD and

T&D Systems View

from http://www.amazon.com/ - or for free at: http://www.eppic.biz/

# # #

The 18th Annual NS 1251 Golf Outing - NJ

I'm late in getting this up - but this is from the NS (AT&T Network Systems) 1251 Golf Outing.

1251 was an 8-day course (ILT in today's parlance). Number 18. We did it the weekend of September 20-21, 2008. In NJ.

Jim coordinated the weekend - thanks Jim!

That's Nancy and then me, and then Gerry Kaufhold and then Jim Costello. 18 years! Wow!

Gerry and Jim and I met in 1986 when I began a 6-7 year client-consulting relationship with the Marketing organization of what later became Lucent. The folks with Bell Labs.

Anyway we did a CAD for Gerry and his manager, Wayne Stewart for Product Management. For 4 then 5 business units. This use to be called Western Electric. The manufacturing arm of AT&T.

Jim worked for Gerry, before becoming a Product Manager elsewhere in AT&T himself. There are posts on NS 1251 from earlier - use the search function.

Anyway- I took up golf (or flog as I play it) late in life - at 39 - and they've both enjoyed every step of the futility. Although I did win one of two days this past outing.

The "fourth" has changed many times over the years. But the three of us have done them all. Nancy has done 2 of the last 3.

Thanks Gerry and Jim! And Nancy! I hope we make it to 30!!!

# # # -or- -30-

Sunday, November 2, 2008

lean-ISD

lean-ISD
from an article published in ISPI Performance Improvement journal in April 2001 in conjunction with a Masters Series presentation at the 2001 Conference.

John Swinney asked me to be a part of his Masters Series at the 2001 ISPI conference to tell the history of CAD. CAD is Curriculum Architecture Design, one of three levels of lean ISD design in what my firm calls the PACT Processes for T&D.

I have been doing CADs since 1982 and have done 74 to date. I have presented on CAD at more than ten ISPI conferences and at seven local chapter meetings in the past 25 years.


The PACT Processes for T&D are a set of instructional systems design/development (ISD) methodologies authored, practiced, and evolved since 1982.

They are performance oriented and practitioner honed.

If one could design a set of collaborative processes involving ISD customers and suppliers with

• A set of prescribed phases and tasks

• A robust set of tools and templates to quickly and efficiently engage the right people at the right time to produce high-quality, performance-improving training & development (T&D)

• An object/chunking design and development strategy of both shareable and unique modules for deployment in any mode—group-paced or self-paced or individually coached then you would have achieved what we also set out to accomplish with the PACT Processes.


THE CONCEPT OF LEAN
The concept of lean comes from the M.I.T. study in 1990 that looked at the worldwide automotive industry and practices and compared them all to Japan’s lean production system, in the book titled The Machine That Changed the World.

The lean approach is most prevalently applied to engineering and manufacturing processes, but it is not limited to those processes. The goals in these lean applications are to

• Use the best of mass and craft production methods.
• Reduce costs and cycle times.
• Improve product and process quality and customer satisfaction.

THE lean-ISD CONCEPT
The application of lean to the world of ISD should create a set of common, effective, and efficient processes for the entire ISD process that spans project planning and management, analysis, design, development, pilot-test deployment, and evaluation of T&D.

These lean-ISD processes would allow for

• Dividing the ISD project efforts across multiple T&D organizations, locations, and personnel while ensuring that all of the T&D pieces will fit together into a seamless learning experience for the target audience

• Planning and managing predictable projects with predictable schedules and resource consumption (peoples’ time and out-of-pocket costs)

• Developing both shareable and unique T&D Modules (T&D product subassemblies) that are components of a systems view of the entire T&D product line

• Reusing (with little or no customization required) the T&D products and subassemblies for various target audiences from across the organization

• Involving and collaborating with both upstream suppliers and downstream customers

THE STATE OF ISD TODAY
ISD is instructional systems design or instructional systems development, depending on your source. It’s been making the headlines lately. According to the press, the death knoll has been sounded. ISD is too slow and too ineffective for life at Internet speed.

Is ISD dead? I don’t think so. Is ISD dying? No. Is ISD hurting? Definitely.

ISD has been slowly evolving since its early days, when it was created for the U.S. military in the 1940s. Then the military and all of the industries it directed put it to use for mission-critical purposes, helping to ensure that tanks rolled, ships sailed, planes flew, and supplies reached troops all the way up to the front lines. Situationally, it was do or die. No kidding! Today? Today is different.

Too many things are just not thought to be that mission-critical in the enterprise operating at Internet speed today. And too often the wrong things seem and are deemed important.

Today too many enterprise initiatives are using Knowledge Management Systems to cram all sorts of “e” content into electronic warehouses wired to each and every employee. But they are doing it without regard to the total life-cycle costs of creating, administering, and then maintaining the thousands of knowledge module objects. Not good.

Readers should consider those life-cycle costs so that they don’t end up as a warehouse full of past-its-time thinking and models. In other words, only build it if they’ll log on and you’ll maintain it, or at least delete it when obsolete.

Will the Internet kill ISD? No. It will better enable it. It will help it get lean. But it’s not the only component in what EPPIC has labeled (and service marked for our newsletter and my book) lean-ISD. And by lean-ISD we mean performance-based lean-ISD.

The ultimate goal of ISD processes is to create instruction that is effective and efficient. Yes? Good ISD processes are also themselves effective and efficient. Yes? If you’re with me so far, then you’ll probably go for the notion that the ultimate goal of T&D is improved performance by the learners as measured by enterprise metrics. Metrics such as cycle times, deadlines met, costs, returns, lost opportunities, safety, and a myriad of other stakeholder satisfaction items are much more important than training days delivered alone.

These business metrics apply equally to both the suppliers and the customers of T&D. The customer uses these measures in those targeted operations, both pre- and post-T&D deployment. The supplier uses these same measures in their T&D development operations. But the supplier’s metrics only help us understand what it took to get the T&D there, available for deployment, and then to deploy it to its targets. That is the focus of lean-ISD: the supplier side. It’s about how to do performance-based T&D, and do it lean. But still the ultimate measure of T&D, lean or otherwise, is outside the T&D system box.

With T&D, it’s not really important that someone learned something, even to a very high proficiency, if what was learned had a miniscule impact on the enterprise given its costs.

All of the supplier and customer metrics lead to ultimate measures such as return on investment (ROI), economic value add (EVA), reduced future costs, and the potential returns on other reinvested savings. These are how T&D product quality are the best measures of T&D effectiveness and efficiency. Hey, a dollar saved is a dollar earned, a dollar generated with less than a dollar of expense expands the profitability of the enterprise, etc.

All T&D efforts incur a cost to produce a gain. Why spend $100,000 to gain back only $80,000? You wouldn’t if it were your money, so why would the corporation’s shareholders feel differently?

ISD MODELS
ISD is the label placed on efforts to plan, analyze, design, develop, implement, and evaluate T&D. There are various models in the literature that describe ISD, including the “big block diagram” (also known as “ADDIE”) from the work of Robert Gagne, Leslie Briggs, Robert Morgan, and Robert Branson.

There are many other ISD models—almost as many as there are ISD practitioners. Therein lies part of the problem for most organizations. In too many organizations, there are too many ISD models being followed. They are typically not common and not predictable in terms of the quality of the T&D outputs produced, or their costs and schedules, and they are not in control. They are often not visible to T&D management or to T&D customers.

This typically results in an ISD situation where

• Content of the product line elements (courses, WBT, on-the-job programs, etc.) are both gapped and overlapping in terms of their content.

• It is costly to produce in the first place, and more costly to maintain.

• It is costly to deploy.

• It is impossible to predict development schedules and costs and then predict ROI.

• The look and feel of the T&D varies across the product line, and chunks of potentially shareable T&D aren’t designed with reuse in mind.

Many organizations have a significant opportunity in recovering and reducing resource expenditures for their ISD processes for producing T&D. They need to re-engineer their ISD processes.

The ultimate goal of the T&D is improved performance by the learners. That is how T&D product quality is best measured. The ISD process goals are to create this quality T&D in a reduced cycle time and at reduced costs.

The T&D products must have the desired effect in terms of the incurred learning in the learning environment (whether classroom, CBT, or on-the-job) and, most importantly, the ability to apply those learnings back on the job. The ISD processes must get this job done quickly and cost-effectively.

PACT PROCESSES FOR T&D
Over the years since 1979, I have reduced to practice the prevailing ISD concepts, philosophies, methods, processes, and practices. These efforts to model the ISD process were driven by the same need that has driven many businesses to first model and then re-engineer their core processes: to improve quality and reduce both cycle time and costs.

Many T&D organizations have undertaken efforts to re-engineer their ISD processes to make them common across the organization, predictable in their schedules and costs, and ensure that the T&D produced is effective. I began in the late 1970s and in 1989 coined the term “PACT Processes for T&D” - processes which include

• Analysis: Performance Modeling and Knowledge/Skill Analysis
• CAD: Curriculum Architecture Design
• MCD: Modular Curriculum DevelopmentSM
• IAD: Instructional Activity DevelopmentSM
• PP&M: Project Planning & Management

The three ISD processes, or levels of ISD, of the PACT Processes are CAD, MCD, and IAD. Each operates at three distinct, different levels of ISD. Each is driven by the PACT Process analysis methodologies, including performance modeling and knowledge/skill analysis.

CAD — CURRICULUM ARCHITECTURE DESIGN
This methodology provides a structured, gated, in-control process for the fairly quick design of the overall curriculum architecture, or learning architecture. The design meeting may take two to four days and generate the macrodesigns for all of the T&D Events in the curriculum architecture.

The CAD analysis process outputs of Performance Models and Knowledge/Skill Matrices are used to drive the CAD design and ensure it results in a performance-based orientation instead of a content/subject matter-based orientation.

A CAD is built to support job performance. It creates an architecture of T&D Modules where shareable and unique modules of content are used to create performance-based T&D products such as courses; workshops; structured, on-the-job training; WBT programs; book reading assignments; project assignments; etc. These modules can be configured many ways, thus maximizing the shareability of content across various target audiences.

A CAD segments and organizes the content of training to ensure the greatest impact on an organization’s performance while minimizing life-cycle costs. It helps to prevent the allocation of resources to training that have little or no impact on job performance.
Many T&D Modules and Events are never developed/acquired because there are no positive returns or economic value add. So why bother? You wouldn’t if it was your money.

A CAD builds a design for a training curriculum with individual parts that add up to a logical whole within the context of a given job or category of position. It ensures that all training works together to produce the desired results by providing employees with all the knowledge/skills needed to perform.
A CAD’s modular design includes both shareable and unique modules creating the capability for infusing the enterprise with a more common language, viewpoint/perspective, culture, and the local unique needs. It contains generic content chunks and specific content chunks. Then the existing T&D can be assessed for fit, and gaps in the curriculum can be identified.

A CAD project engages the training customer in the prioritization of all training development efforts targeted to fill gaps in the overall architecture of T&D. All of the priority training content really required becomes visibly apparent to the training customer. The customer’s knowledge regarding the affect of training on specific areas of performance allows them to prioritize gap training development efforts that will help them meet their business needs. The collaboration creates many win-wins.

The CAD’s architectural design will help reduce the overall life-cycle costs of the entire T&D product line. Initial, “first costs” will be reduced by eliminating and minimizing redundant content development. “Life-cycle costs” will also be reduced because there will be no redundant content to maintain. This systematic approach to the modularization of training content will reduce maintenance and administrative costs.

The CAD’s macrolevel analysis and design outputs become guiding MCD inputs to the midlevel analysis and design efforts, and they are further leveraged in the IAD’s microlevel analysis and design activities.

CAD projects typically span a two- or three-month cycle, but small CAD projects can be conducted in as little as five days without formal documentation.

I and my staff have used this methodology to help a pharmaceutical company develop 90 days of technology transfer training for their proprietary processes after two days in analysis and two days in design.

Although the analysis and design data was very macrolevel, it guided the development efforts. The end results were very close to all initial estimates for both development time and deployment time. This project was also a hybrid effort of both the CAD and MCD processes. CADs almost always lead to multiple MCD projects, where there is a clear, key business priority. Many potential T&D products identified during the CAD process are never built because the ROI and EVA figures or the strategic value to the enterprise do not warrant the efforts and expenditures.

Just because T&D professionals are skilled at uncovering T&D requirements does not in and of itself warrant meeting those needs.

The PACT Processes can save the organization from low-value T&D and steer the resources to T&D with strategic, business-critical, high-payoff implications. And it can do it without overly complex ROI algorithms.

A number of methodologies are used throughout the CAD project; however, the most critical from both a quality and cycle time standpoint is the use of teams throughout all phases.

The use of appropriate company personnel on the designated project teams will ensure higher quality of both the project inputs and outputs. In addition, it will provide for a level of participation in the project activities that will create increased ownership of the results and more support for eventual implementation.

The project’s overall structure for key roles and the teams is as follows:

• Project Steering Team
• Customer-side project manager
• Supplier-side project manager
• Analysis Team
• Design Team
• ISD Team

4 CAD Phases

CAD Phase 1: Project Planning & Kick-off. In this phase, the project priorities, direction, and resources are defined. Potential issues and/or stakeholder requirements should be uncovered and planned for during this phase to ensure the success of remaining phases.

CAD Phase 2: Analysis. The purpose of this phase is to establish a common view of the positions, personnel, performance requirements, and knowledge and skill requirements. In addition, demographic information about the target population and information about existing training will be gathered. This common view will form the basis for the CAD and all priority-setting activities later in the project.

CAD Phase 3: Design. The purpose of this phase is to produce a CAD to address the performance tasks and knowledge/skills derived in the Analysis Phase. In this phase, tradeoffs may need to be made in order to maximize the return on investment for the overall corporation.

The intent is to create a CAD that is robust to future variation in job assignments; individual trainee experience, background, career goals; delivery facilities; and maintenance requirements. It also needs to be designed for content “updatability” and future adaptability to potential changes in the business (e.g., organization structure, competition, technology, etc.).

CAD Phase 4: Implementation Planning. In this phase, the priorities will be established by the Project Steering Team for all of the T&D Events (and T&D Modules) and will be translated into a CAD implementation “development/acquisition plan.” The plan could include deployment planning and other T&D systems and infrastructure requirements, depending on the situation within the T&D organization and/or the enterprise.

CAD Benefits
Quality, performance-based T&D exists exclusively to improve human performance, and that human performance exists within the context of business or organizational processes. Any other goal for T&D has almost zero ROI.

The CAD’s architectural design will help reduce the life-cycle costs of the entire T&D product line.

The T&D Modules can be configured many ways, but if they follow the “rules of modularity,” they will maximize the shareability of T&D content across various potential target audiences. They will create and/or reinforce common language across more target audiences, while also reducing the T&D suppliers’ costs by reusing content chunks over and over again (but only as appropriate!). Elsewhere in business, especially in design engineering, this is known as configuration control or platform design.

MCD – MODULAR CURRICULUM DEVELOPMENT
This methodology provides another structured, gated, in-control process for the fairly quick design, development, pilot testing, and revision/release of the T&D Modules and T&D Events of the CAD.

EPPIC uses a proprietary process that is designed to incorporate representatives from stakeholder groups into the overall project’s activities and tasks.

An MCD project is conducted in six phases using a team process. Figure 4 shows an overview of the PACT Process for MCD.

The MCD process allows the various concerns of management, job incumbents, and staff support groups to influence the design decisions. The project will be controlled by a Project Steering Team that will make the final decisions. Teams of top performers will be used to identify both the performance requirements and the associated knowledge/skills required. Additional teams will be used in the MCD process to ensure that all decisions reflect the needs/issues of the company.

The six-phase structure in Figure 4 provides the framework for the project activities, deliverables, and team structure.

MCD projects typically span a four- or six-month cycle, but small MCD projects can be conducted in much less time. We built and pilot tested, in a 90-day cycle, a four-day “labor relations” course with more than 50 percent of class time spent in intense simulation exercises/role-plays. Three ISDers were involved.

The CAD outputs of the performance modeling and knowledge/skill analysis process and the CAD design specifications are used within the MCD process to drive the design to ensure it results in shareable T&D Modules and Events.

The project’s overall structure for key roles and the teams is as follows:

• Project Steering Team
• Customer-side and supplier-side project manager
• Development Team
• Pilot-test participants
• Pilot-test instructors/administrators
• ISD/T&D Team

MCD Phases
Phase 1: Project Planning & Kick-off. Project priorities, direction, and resources are defined; potential issues and/or stakeholder requirements should be uncovered and planned for during this phase to ensure the success of remaining phases.

MCD Phase 2: Analysis. A common view of the personnel, performance requirements, knowledge and skill requirements, and appropriateness and completeness of any existing T&D is established; this common view will form the basis for the training design.

MCD Phase 3: Design. In this phase, the Design Team is facilitated through a systematic design process; some details are completed after the design meeting.

Note: The intent of the team approach to design is not “to design by committee” but to influence “the designers by committee” during the actual design activities.

MCD Phase 4: Development/Acquisition. In this phase, the training is developed and/or acquired/modified per the Design Document (produced in Phase 3).

MCD Phase 5: Pilot Test. In this phase, the training is delivered (pilot tested), and extensive evaluations are conducted.

MCD Phase 6: Revision & Release. In this phase, all materials are updated (per the “revision specifications” from Phase 5) and are released into the training system.

MCD Summary
The PACT Process for MCD is a powerful process, if populated with the right people to do the right things at the right times. The gates ensure that our customers and key stakeholders for our T&D product line are systematically engaged for our collective success—collaborative win-win.

MCD uses the multiteam approach to plan and conduct a predictable project to develop and test performance-based T&D. Whether preceded by a CAD or not, MCD takes a proactive approach, with tools and templates to accelerate and ensure the quality of both the analysis and design efforts.

The MCD methodology engages the right stakeholders at the right time for getting the right inputs and right decisions at the right time. It shortens the project time cycle and reduces costs for T&D projects. It increases the quality of the T&D product/service by focusing on desired performance as the terminal learning objectives. It structures T&D content into more shareable chunks, thereby reducing future costs.

The MCD methodology provides a gated process for working with all project participants in an accelerated manner to produce performance-based T&D. The T&D professionals retain control of T&D decisions, and the stakeholders in your marketplace gain and exercise control of all the business decisions inherent in T&D projects and resourcing.

IAD – INSTRUCTIONAL ACTIVITY DEVELOPMENT
This methodology follows the same six-phase approach as an MCD effort. It provides another structured, gated, in-control process for the quick design and development of various types of instructional components, including

• Knowledge Tests
• Performance Tests
• Simulation Exercises
• Performance/Job Aids
• Electronic (or Paper) Desk Procedures
• Instructional Content: awareness or knowledge level

This methodology produces outputs that could be part of a T&D solution, or could exist on their own. Our intent is to be able to build T&D components and wrap other T&D components around them later, as needs dictate/allow.

EVOLUTION OF THE PACT PROCESSES FOR T&D
Early in my career, I was introduced to the work of Rummler, Gilbert, Mager, and then Harless through ISPI (then NSPI). One of the first books I read on the subject was Bob Mager’s book Analyzing Performance Problems, and it really made sense!

I started climbing the learning curve of ISD and HPT and began applying a Rummler-like performance analysis approach as a front-end to the design and development of self-paced (paper-based and video-based) T&D for contractor sales, and then inside sales, and then inventory management.

In 1981 I started working at Motorola’s Training & Education Center (MTEC), the predecessor organization to Motorola University. Our leader, Bill Wiggenhorn, had us attempt a project to create a Geary Rummler Design Process. That process would help us produce performance-improving T&D as well as help the organization deal with those issues in the work processes that would not be affected by our T&D. The project became entangled in the 13 perspectives on “how I like to do it,” and it didn’t happen while I was there. Later, Jeff Oberlin, the design manager, did develop a methodology, but the Rummler-esque version I had craved didn’t materialize during my time there. Since then, it has always been my goal to do just that.

Our effort at MTEC failed. Too many cooks and not enough decisions imposed, and the team drifted and fought. But it was a great idea. My time at MTEC was very good for me, especially working for Bill Wiggenhorn. His vision inspired all who worked with him.

When I heard Deming say, “80 percent of all quality problems are in the control of management,” I smiled. We at ISPI knew that for a fact. We know it is not always the performer. We know that it’s not always the performer’s need for training that is the root of any performance issue. I’ve heard Rummler say it many times, “Put a good performer in a bad environment, and the environment wins every time.”

In 1982 I joined Ray Svenson at R.A. Svenson & Associates, and I began to look at T&D as more than a partial family of curricula for a job or job family. I began to look at it more holistically. We studied jobs and created end-to-end paths of curricula to create performance competence. It was here that I began formalizing what became PACT.

My first Curriculum Architecture Design project was done here, in 1982. It was a combination of the approach Ray Svenson had for curriculum architecture from The Bell System for Technical Education (BSTE of AT&T) and a Rummler-esque Performance Model and Knowledge/Skill Matrix to drive the performance orientation into the design of the modules of content.

During my 15 years at what evolved into SWI (Svenson & Wallace, Inc.) and then into CADDI (Curriculum Architecture Design & Development, Institute, Inc.), I evolved the CAD methodology into a four-phase process, with tools, templates, and standards. Next I added a T&D Module development methodology, which is now MCD. MCD picks up where the system engineering of the CAD approach leaves off. The high-priority “gaps” of the CAD are addressed in subsequent MCD projects using an ADDIE-like six phases. Again, task procedures, tools, and templates guide and streamline the process without shortcutting the real meat of ISD.

My most recent CAD project, number 74, was done in 2004. In 1999 I published my book: lean-ISD. I was happy with the reactions by people I really respected.

lean-ISD embodies a collection of many best practices from many business disciplines. The current, leading ISD concepts, models, methods, and tools included are intended to create an engineering practice of ISD.

Why? Because after all my years in the T&D business, my view of ISD was still a muddled mess. All the books and articles I read, and the workshops and presentations that I attended at ISPI, ASTD, Lakewood, and others, did not add clarity. They did not prescribe, which is exactly what the neophyte thirsts for. At least I did. Maybe today it is different. I think not.

lean-ISD SUMMARY
The ultimate goal of the T&D is improved performance by the learners. That is how T&D product quality is best measured. The ISD process goals are to create this quality T&D in a reduced cycle time and at reduced costs.

We believe in performance-based T&D, but only when the ROI and EVA are sufficient to warrant the investment. Otherwise, don’t bother. Our team and management approach facilitate the “for the sake of the business” only, no-nonsense nature of PACT projects.

Since 1979 I've reduce to practice many of the prevailing ISD concepts, philosophies, methods, processes, and practices. My efforts have resulted in the PACT Processes for T&D. Much of our ISD insight came from our affiliation with ISPI. For that we are very thankful. We hope you are thankful for our attempts to share over the years as well. Thank you for your interest.

This article was intended to overview what the PACT Processes are as an example of what lean-ISD is. This article is also intended to thank all those responsible for our opportunities to learn—and provide the history John requested.


lean-ISD, PACT Processes, Curriculum Architecture Design, Modular Curriculum Development, and Instructional Activity Development are service marks of EPPIC, Inc.

# # #

Geary A. Rummler - Update

My mentor and friend, Geary A. Rummler, passed away the night of Wednesday, October 29, 2008 of an apparent heart attack. Here is an earlier Posting.

In reaching out to many ISPI colleagues who were close/followers of Geary's to inform them of his passing, I have received in return expressions of their feelings of sadness and many comments about Geary the person, the consultant, the friend. But I do not feel appropriate to share those without their permission. So I'll work on that.

In the meantime I have heard from Geary's close friend and colleague since the early 1960s, Dale Brethower, who lives in Tucson near Geary and Margaret. I had sent him a note in email, asking how he and wife Karolyn were doing, as I knew they were very close. And, did he know of any service arrangments/etc., or was this to be more private, etc.? And had he seen Geary's references to him in the videos posted recently?

Here is his reply:

From Dale Brethower on Saturday November 1, 2008:
I really love the Motorola video. It is excellent Geary, looking about the way he did when I met him 20 years before that.

Karolyn and I took a Karolyn prepared meal to Margaret and sons Chris, Rick, and Matt last night A terrific family displaying wit, charm, caring, and character. They are doing well.

As you might know, Geary hated funerals and had no wish to participate in one as the main attraction; hence there is no funeral.

But Geary liked celebrations and, in his honor and for the many people who were touched by him, there will be a celebration in Tucson on Geary's birthday in April.

The sons are doing a great job with Margaret, instructing her in the wonders of cell phones and the like to be in touch whenever/wherever. They tease and share memories. No tears while we were there; I was afraid I'd break out in tears when I went into the house but those caring faces and smiles buoyed me up well.

Thank you for caring and for the videos. They could be great additions to the April celebration.

Dale Brethower

******************************************

I still do not have word/information about sending flowers/cards as many have inquired about with me. If I hear about that I'll let you know as well.

Like many, I am interested personally. But I am trying to give the family all of space and grace that I can. I will post what I know soon after I learn it.

Have you been touched by Geary in the past? Do you have your story or stories?

Think about them now for comfort!

# # #

Saturday, November 1, 2008

Who Sets Your Performance Competence Requirements? Who Are Your Stakeholders?

One of my stock phrases is in the graphic below.


















It reads: Performance Competence is the ability to perform tasks to produce outputs to stakeholder requirements.

One of my mental models about Performance and Human Performance is from Japan in the 1950s - the Ishikawa Diagram - also known as a "Fishbone Diagram" and a "Cause & Effect Diagram" - and it is the non-Politically Correct version from the 1980s that I share with you below.











I adapted that to the following - something that many in ISPI have wrongly attributed to Gilbert - but which really is attributable to Ishikawa.















The Process box of the Ishikawa has been scaled from one process to a department's set of processes (their system) - or imagine that box as the entire enterprise, a business unit, a function, a department (again) or a team - and their processes in an organized framework of Leadership Processes, Core Processes, and Support Processes.

Where the Core Processes are "owned by that function/department/etc." and are unique from other organizational entities - and thereby differentiate them from other organizational entities and their "owned processes." Unless their was redundancy by design happening - or inadvertent redundancy.

The Leadership Processes are shareable across the enterprise breath-wise and top-to-bottom-wise.

The Support Processes are shareable as well.

In my graphic below I show my view of "The Big Picture of EPPI - Enterprise Process Performance Improvement" - my version of Process Improvement - and by that I mean, more than just Human Performance Improvement as well as Process Improvement.

I show my 3-legged-stool of PERFORMANCE as 1-Processes and 2- Human Assets and 3- Environmental Assets.















Then my explicit understanding of the asset requirements would allow me to populate ERP Systems with performance-based data. And I could manage the enabling asset systems better.

My HAMS and EAMS in the graphic below might help with your mental imagery.















Process and Performance Competence
Key to Process is meeting the needs of the stakeholders. Or at least beating all of their other alternatives.

So back to my definition of Performance Competence:
Performance Competence is the ability to perform tasks to produce outputs to stakeholder requirements.

It, the definition, is applicable at the individual level, at the team level, at the process level, at the department level, functional level, business unit level and at the Enterprise level. So I think it provides one axis of an Enterprise-wide Requirements Matrix.

The other axis is framed and articulated/captured by knowing exactly who the Stakeholders are. And what they want and need.


Stakeholders - Include the Customers
But the Customer is King - Not.
...from the title that I originally wanted for an article that got published in 1995 - under a different title.

Who are these stakeholders? My graphic below portrays them in a hierarchy:



















Of course you may need to adapt this model to your situation, such as adding in a union, or an industry association, etc.

Here is a past Blog Posting of mine dealing with these stakeholders and some details on each category in the model.

Then once that set of categories is correct and the list of actual stakeholders and/or their internal representatives (so to speak) is accurate AND complete, you can complete the following matrix to build yourself a Stakeholder Requirements Matrix for each of your processes - so that you might better manage the whole slew of processes - and get not only your arms around them...















...but get a clear picture of them distilled for utility.

Processes vary in their rigidity or flexibility, the cycle times, their criticality, and their predictability.

Even stakeholders vary in their requirements rigidity or flexibility, their cycle times, their criticality, and their predictability.

Here in this adapted version of my Stakeholder Requirements graphic I suggest that customer needs may pull us (in a western sense "from the right") and so they lead in the graphic's portrayal...



















...and likewise our supplier's requirements might lag a bit. We may be held back by their requirements - or inability to meet ours at whatever six sigma level targeted/needed.

Or adapt the model further as you see fit - something that may better mentally resonate with your audiences!

# # #

lean-ISD via the PACT Processes for Training & Development/ Learning/ Knowledge Management

The ultimate goal of training & development (T&D)/ Learning/ Knowledge Management CONTENT - in an Enterprise context versus an Educational context - is improved performance by the learners as measured by business metrics.

With Enterprise T&D, it’s not really important that someone learned something, even to a very high proficiency, if what was learned had a miniscule impact on the business given its costs.

Business measures such as return on investment (ROI), economic value add (EVA), reduced future costs, and the potential returns on other reinvested savings are how T&D product quality are best measured. A dollar saved is a dollar earned, etc.

All T&D efforts incur a cost to produce a gain. Why spend $100,000 to gain back only $80,000? You wouldn’t if it were your money, so why would the corporation’s shareholders feel differently?

PACT
The PACT Processes for T&D are a lean approach to ISD—instructional systems design and/or development. The concept of lean is borrowed from the work of the mid-1990’s landmark M.I.T. benchmarking study of the global automotive industry and the best methods of production: The Machine that Changed the World, by James P. Womack, Daniel T. Jones, and Daniel Roos.

Lean production is a compilation of the best of both mass and craft production techniques—the best of both worlds. Production produces products, and T&D is just another product. ISD can be lean.

My book lean-ISD, covers the PACT Processes pretty extensively - although it is not a manual to guide one through each of the PACT Processes tasks (see the book's appendices) - it was intended as a companion piece to a workshop series that I have on - one for each of the 5 key PACT Practitioner roles: PACT Analyst, PACT CAD Designer, PACT MCD Designer, PACT Lead Developer, and the PACT Project Manager.

That book's analysis methods are derivatives of derivatives of the approaches of the late Geary A. Rummler. I first learned those initial derivative methods in the fall of 1979 at Wickes Lumber when I worked for and with a Rummler-ite/disciple (that's two of them) for 9 months - and then I worked for Geary's brother-in-law for the next 9 months, and then I spent two years at Motorola's Training & Education Center - and got to work with Geary on a dozen or so efforts - spanning internal process work on our own ISD methods based on Rummler's approaches (that effort pretty much failed due to internal politics - and after leaving I vowed to create one - and that became PACT - the subject of lean-ISD) - to actual Client work - where the end-game-goal from the git-go wasn't necessarily Training.

I left Motorola to join Ray Svenson's consulting firm - 26 years ago today - November 1, 2002. That's where I took Ray's concept of Curriculum Architecture (which he got from the Bell Systems Center for Technical Education) and formalized it as a precursor to ADDIE, with a Rummler-like performance analysis components - plus other analysis elements, and a phase-by-phase process-like approach to Instructional Design/ Instructional Systems Design. By formalized I mean: I reduced it to practice - as one colleague, Dick Hill, at SWI - Svenson & Wallace Inc. later phrased it when he joined our firm in 1994 as a consultant.


Other applications beyond "lean-ISD" and the application of my analysis methods to ISD/ID - I have a chapter (#11) in the 3rd edition of the HPT Handbook (more properly the "Handbook of Human Performance Technology") - which covers the application of my analysis methods beyond ISD to Performance - which ties to my EPPI - Enterprise Process Performance Improvement methods. PACT is a subset of EPPI. By design.

Again, greatly influenced by Geary A. Rummler.

The Life Cycle Costs of Learning
T&D has a complex marketplace with a diverse set of customer target audiences where one size T&D does not often fit all. Determining and then meeting the T&D needs of these complex audiences in a businesslike manner and incurring a cost to produce a gain is smart business and smart T&D. But too many T&D and learning organization executives focus on their first costs—those costs contained in the year’s annual budget.

Too few T&D executives focus on the total life cycle costs for the product line they bring to their internal markets.

And the total life cycle costs of the T&D product line are costly indeed.

After the initial T&D development costs are incurred, you must account for all of the T&D deployment/distribution costs to get your T&D to its respective marketplace customers. You also have to factor in the T&D participants’ incurred time, material, travel and living, and their lost opportunity costs.

And don’t forget there are probably T&D product maintenance costs to account for, because who would bring a product to market and then not keep it current, wasting the time and other out-of-pocket costs of the participants who were taught something that is not right?

There has to be a better way to approach ISD. A more businesslike approach. A more product-for-profit oriented approach. An approach where both the customer side and the supply side of the equation win. A lean approach to ISD.

The lean-ISD PACT Processes for T&D can create high-quality, performance-based T&D in a reduced cycle time and at reduced costs. Both first costs and overall life cycle costs.

Over the past twenty nine years, Guy W. Wallace of EPPIC has reduced to practice many of the best ISD concepts, philosophies, methods, processes, and practices and combined them with a lean, business and product management oriented approach to the business of T&D.

Those efforts have resulted in what I have been labeling as the PACT Processes for T&D since 1990.

P erformance-based
A ccelerated
C ustomer-/Stakeholder-driven
T &D

EPPIC’s five proprietary components of the PACT Processes for T&D link together to create a powerful, lean-ISD methodology. PACT includes 3 levels of ISD - Instructional Systems Design or ID - Instructional Design .

The PACT Processes for T&D include the following:

• PACT Analysis
• CAD – Curriculum Architecture Design
• MCD – Modular Curriculum Development
• IAD – Instructional Activity Development
• PACT Project Planning and Management


3 Levels of ISD
CAD - Curriculum Architecture Design
CAD is the macrolevel, performance-based, lean-ISD methodology at the systems engineering design level. A CAD project systematically designs the T&D product line, using a modular approach. A CAD effort...

• Configures content to increase shareability across many potential target audiences
• Reduces overall first costs for development
• Reduces life cycle costs for deployment and maintenance

The front-end Analysis data forces a performance orientation into T&D Events and Modules. CAD projects identify all the T&D that could be and prioritizes the T&D that should be, for resourcing MCD project for the T&D that will be.

MCD - Modular Curriculum Development/Acquisition
MCD is the most traditional ISD process within the PACT Processes for T&D. It is the process that develops or acquires T&D one course/instructional event at a time (or in small bundles or large concurrent efforts). MCD can be conducted with or without a prior CAD effort.

MCD is our ISD model, much like the ADDIE model from the work of Robert Gagne, Leslie Briggs, Robert Moran, and Robert Branson.

MCD is the closest of the PACT Processes to traditional ISD. This lean-ISD methodology provides a structured, gated, in-control process for MCD, with methodology that provides for the fairly quick analysis, design, development, pilot-testing, and revision/release of the T&D Modules and T&D Events of the CAD.

MCD uses a gated, predefined project management process that is designed to incorporate representatives from key customer and stakeholder groups into the overall T&D project’s activities and tasks for business decision-making.

MCD projects are conducted in six phases using a team process. The six-phase structure provides the framework for the project activities, deliverables, and team structure.


IAD - Instructional Activity Development/Acquisition
IAD is the microlevel, performance-based, lean-ISD methodology for the design and development of instructional activities found within each T&D Module’s lessons design. IAD outputs include

• Information
• Demonstrations
• Performance/job aids
• Case studies
• Simulation exercises
• Performance demonstrations
• Performance tests
• Knowledge tests
• Verbal or written content
• Etc.




Common Analysis & Planning Management Methods
PACT Analysis
The PACT Analysis methodologies that feed each of the three levels of ISD design include

• TAD – Target Audience Data
• PM – Performance Modeling
• K/SA – Knowledge/Skill Analysis
• ETA – Existing T&D Assessment

The key analysis methodologies of PACT revolve around the use of Performance Modeling and the systematic derivation of K/Ss in the PACT method for Knowledge/Skill Analysis. PACT is performance-based and will positively impact performers in business processes!


PP&M – Project Planning & Management
PACT project planning and management is facilitated by predefined teams, roles, phases and tasks, outputs, key management gate review points, templates, tools, and rules to help the ISD customer and supplier collaborate for a win-win. PACT is lean and accelerated due to its use of the best of both mass and craft production approaches.


Business Benefits and Rationale
The PACT Processes for T&D are systematic, gated, collaborative approaches between T&D customers and suppliers that are consistent with and reflective of many of the newer approaches and practices for managing the business processes of high-performing enterprises in a business-rational manner.


The PACT Processes provide a lean-ISD methodology producing improvements in the T&D quality, quantity, and return/cost.

The benefits to the organization for the adoption of the PACT Processes for T&D are increased quality and effectiveness of the T&D product line, with both reduced cycle time and reduced life cycle costs. This in turn provides a greater return on investment and a greater economic value add for T&D.

The PACT Processes for T&D approach ISD and learning with a better, faster, and cheaper approach than traditional ISD approaches. Traditional ISD often takes a course-by-course view and incrementally builds a T&D product line, ending up with a hodgepodge of overlapped and gapped T&D products that ensures inefficiencies all up and down the internal T&D/learning supply chain.

Comments on Common Processes/Methods
Common processes should always be "as flexible as feasible and as rigorous as required." What Tom Peters use to call Tight-Loose/Loose-Tight.

WIIFM?

Common is easier to learn, master and then be able to coach others.

Common is easier to plan, manage and monitor.

Think about share-ability of content - reuse - along with share-ability of process. I don't think you can have the former without the latter. I've been driven to improve reuse since my days at MTEC in 1981-1982. Due to the prime rate being 21% and the costs of inventory of raw goods and work-in-process were killing the company's cash flow - and the manufacturing-materials-purchasing worlds of Motorola who were my Clients - began applying IT to processess and MRP spawned MRPII which spawned ERP and CAD/CAM systems standardized parts invenntories and design processes and rules.

Common systems that are as flexible as feasible and as rigorous as required are the only way to drive out inefficiencies and improve operating margins.




The PACT Processes...
• Are always in control from a schedule and budget perspective, and are driven strategically by key line and executive management stakeholders.


• Focus squarely on the knowledge and skill enablers required by performers within business processes.


• Select the best mix of T&D deployment strategies, including the intranet/Internet, CBT, self-paced readings, videotapes, and audiotapes, as well as the most traditional approach: instructor-led classroom delivery.


• Create a macrodesign for a modular, performance-based library of T&D while salvaging all previous investments assessed as worthy for reuse.


• Greatly increase the shareability of the T&D Modules, thereby reducing the typical redundancy of the content produced separately for each audience and generating huge savings in first-time development costs, life cycle maintenance costs, and ongoing deployment costs.


• Enable prioritization for the gap T&D based on ROI, EVA, and criticality/impact to critical business processes and initiatives.



*******************************************



For more - download the free 404-page PDF book: lean-ISD - and many other free related resources at http://www.eppic.biz/



# # #

First (Second really) Presentation on the CAD Methodology - April 24, 1985

First (Second really) Presentation on the CAD Methodology - April 24, 1985
At the NSPI Conference - by Guy W. Wallace. These methods were evolved by Guy to become the PACT Processes for T&D/ Learning/ Knowledge Management - the subject of his 1999 book: lean-ISD. Was actually "first" publicly presented at the Chicago Chapter of NSPI in 1983.

The PACTWiki

Wikispaces

The PACTWiki 2

Wikispaces

The Performance-based Employee Qualification/Certification Systems Wiki

Wikispaces

PACT Study Aid - Can You Answer the ?s and Explain the Graphics and the Contents of the Documents ?

Take Control! Literally! Use the controls in the bottom panel of the Cellblock above! Change the speed, pause it, reverse it! Put it on your desktop with a larger screen!