The Chronicles of Rocket Boy

Expert Perspectives

(If you have trouble printing this page, you can save the document and print from any word processor:   Under the "File" Menu, select "Save As," "Format:Text," and a location on your computer for the document."

We are fortunate to be able to offer two Expert Perspectives on "The Chronicles of RocketBoy." These perspectives were developed to encourage you to consider other ways to think about the case issues.

We recommend reading these perspectives AFTER you've responded to the case. And remember, there are multiple defensible ways to respond to every situation...


  • David Jonassen, Ph.D.

    David Jonassen is Professor of Instructional Systems at The Pennsylvania State University. Dr. Jonassen has previously taught at the University of Colorado, the University of North Carolina at Greensboro, Syracuse University, Universiteit Twente, and Temple University and consulted with businesses, universities, and other institutions around the world. He is working on his twentieth book and has published numerous articles, papers, and technical reports. His current research focuses on designing constructivist learning environments, cognitive tools for learning, knowledge representation methods, problem solving, computer-supported collaborative argumentation, cognitive task analysis, and individual differences and learning.

    Dave has been an active supporter of the ID case event, serving as a Judge in 1996 and sponsoring teams in 1996 and 1997.

  • Ellen Wagner, Ph.D.

    Dr. Ellen Wagner is Vice President of Consulting Services for Informania, a performance improvement consultancy based in San Francisco. She is responsible for directing and supervising projects and staff dedicated to assessment, design, development, implementation, and evaluation, which are the core of Informania's activities. Ellen also serves as Informania's lead instructional design consultant, and works closely with Informania staff and clients to ensure that their custom performance improvement interventions are valid, reliable, engaging, and effective.

    Before joining Informania, Ellen was Associate Professor and Chair of the Educational Technology Program at the University of Northern Colorado (UNC). She also held positions as UNC's Coordinator of Instructional and Research Technologies in the Office of Academic Affairs, and was Director of the Western Institute for Distance Education. From 1991 to 1993, Ellen was a Visiting Scholar at the Western Cooperative for Educational Telecommunication, where she served as a technology consultant to universities and colleges in the 15 western states served by WICHE.

    Ellen has used "The Chronicles of RocketBoy" as a staff development tool at Informania.



Expert Perspective From David Jonassen, Ph.D.

My Interpretation:

I'm not sure that RocketBoy is as much of a performance support/training problem as Cynthia, Jason, and others at DAI think. Let me explain.

I believe that needs assessment is critical here. Unfortunately, Jason sounds like he is going to wrap up his needs assessment in a day or so, based only on five-minute interviews and using a traditional discrepancy model of analysis. However, it is not clear to me how he is going to establish optimals and actuals in order to perform the discrepancy analysis without getting much more serious about needs assessment. What I would recommend at this point in the process is a complete workflow analysis within and among workgroups all along the Pipeline. That would probably require observations and think-alouds. From the workflow, I would identify (perhaps through interview, think-alouds, or teach-backs combined with performance audits) exactly where most of the problems occur. For each problem, I would try to identify the cause. Is it a software problem or a workflow problem? It sounds to me as if a problem oriented needs analysis may be more productive than a discrepancy analysis.

Only a brief learner analysis is needed. This is a bright, highly motivated, extremely creative group of individuals for whom time is life. Immediate relevance is the only issue that training must address, which makes it sound like an EPSS solution.

However, as I said before, I do not believe that this is a training problem. Rather, this is a problem of forming more effective practice communities. That is why we must examine workflow within and between groups (communities). If you treat this as a performance training problem, you will be developing software training for a rapidly moving target. The software changes so rapidly that attempting to develop new training for every innovation would be impossible and probably ineffective (even if you could do it). Why? First, until the groups implement the software into practice, you have no idea which software will likely cause problems. Second, it may fail because of the belief structures of the participants. Let me explain.

A great deal of the problem, it seems to me, is cultural. DAI has attempted to integrate at least two groups of workers from two different generations who have two substantively different world views. While completing a workflow needs assessment, I would assemble each of the workgroups with an effective facilitator to work through their conceptions of the process, working to see how each workgroup could work more synergistically. Essentially, you want to develop more cohesive practice communities. These practice communities consist of talented, energetic, and committed people, many of whom probably sport substantial egos (or alter-egos, as the story indicates). Negotiating (socially co-constructing) a common view of the process will be essential. If each group developed a common conception of their task and collaboratively designed or selected a software support system to support that process, they would necessarily become more efficient as a group. When new software is introduced, the group should evaluate its applicability to the process that they have articulated. The same process should occur among workgroups, presumably with the workgroup head as members of that planning community.


Expert Perspective From Ellen Wagner, Ph.D.

Some Thoughts from the Trenches:

(I've raised a number of points that I would ask your design teams to consider before they move ahead with their designs. And, in the spirit of working within the context of the case, I'd like to suggest to Jason, that he keep his resume current. I'm wondering if he can see the warning signs...)

The capital investors (Media World Pictures) sound like they are running out of patience with the freewheeling spending and non-accountable management style of DAI. It also sounds like the DAI management is starting to wake up to this fact, at least a bit. However, the concern hasn't really penetrated with DAI's creative departments. It also sounds like the training department hasn't caught a clue, either. I'm a bit surprised that the DAI management hasn't already implemented some fairly explicit cost-accounting mechanisms in place to show the capital investors that they are taking the profitability concerns seriously. My sense is that any day now, the MWP management is going to restructure DAI, from the mission statement on down. DAI seems a bit too focused on taking care of DAI, and not so focused on providing customers/clients with excellent service - and certainly not on making the parent organization profits, which is what business is all about. Like it or not, that is the bottom line.

At the very least, the training department should expect a "wake-up call" from the executive management of DAI any time now. Think about this from a financial officer's position: DAI hasn't been profitable for two years. The training department wants to implement an expensive training initiative that will not be rolled out for at least another nine months (and you do need to factor in time for rollout delays - it happens, so you need to plan for it). It will take at least 6 - 9 months from the time the initiative is rolled-out to show any possible bottom line impact of the EPSS intervention. Given the number of variables that may confound the financial analysis, it might be hard to attribute increased efficiencies directly to training. So we're looking at probably 18 - 24 months to turn things around via training, with no guarantees of success. That sounds very scary to me.

Let me put it this way: The company will turn a profit faster if they eliminate direct spending. I would think that the training department will want to walk very carefully if they don't want to find themselves cut back to bare bones, depending on outsourcing for meeting the essential training needs of the company.

Training departments are often perceived as a great organizational "black hole" of cost, unless the training staff management is very, very good at showing a direct significant impact of their interventions on bottom line company financials. And this is very, very hard to do. Remember that internal training typically doesn't generate revenue. And temper what you've heard about demonstrating organizational value by improving productivity - when push comes to shove, unless you can show that you are making money, or directly saving money for your company, you are at risk when cost-cutting efforts come down. And cost cutting always comes down. That's part of the ebb and flow of business. (This has a lot to do with why people at DAI are let go at the conclusion of a project - it's because they don't have anything billable to do, and the company won't absorb the cost of keeping them on until the next activity "peak" hits.)

Training efforts typically have costs for staff, resources, vendors, equipment and facilities. Training typically pulls staff away from their jobs. While training may eventually get people up to speed on essential skills for performing at peak levels, training can also decrease efficiencies as people begin to implement new skills in practice. Is the workflow such that you can afford to have people NOT working at peak efficiency? Sometimes it is more efficient to let unqualified or less people go and hire other, more qualified people than it is to train those who are not "up to speed". Also keep in mind, in highly competitive businesses, employers absolutely HATE spending money on building an employee's skill capacities, only to have that highly skilled staff member lured away by another company. Sometimes it is better to find the highly skilled person and invest less money in keeping them current than it is to really train someone to do work your way and then have them get swept up by the competition.

IF the DAI training staff want to be sure to get this EPSS project funded, they need to think about positioning the initiative as part of a performance improvement initiative that is championed as a strategic imperative by central DAI - or even MWP management. This means collaborating directly with executive staff, and letting the executive staff push the initiative throughout the company. And THIS means not emphasizing the intervention, but to instead focus on the result. What I see is that the training department (which operates its own little fiefdom) is planning on providing the creative departments (who operate as their own independent fiefdoms) with tools that the training department thinks they need. These are NOT tools that the creative departments themselves have asked for. Remember, creative departments (or engineering, or product development or product sales, or whoever is involved in the core business activities of a company) don't typically hold training staff in particular high regard. You can see this by the very limited amount of time Jason was provided when interviewing the company decision-makers. In some organizations, the creative / engineering / product development / product sales staff will actively plot and scheme for ways of getting training budgets reallocated to their own projects! So designers need to be aware that not everyone in their organziation is interested in their success. I also notice that there wasn't a single executive stakeholder included among Jason's interview subjects - I don't know if that's intentional or an oversight, but strategically it's not going to serve this effort very well. My sense is that the training department is going to have to be a lot more strategic in how they position this initiative within DAI if they want to see it come to fruition, and to be successful.

Training is not as universally popular with employees OR with employers as one might think. Increased productivity certainly is a good thing; increased proficiency on the job is also good, as is learning how to do cool new things with new technology. But internal corporate training programs and courses are not necessarily the best way that these results are achieved. Remember that training pulls people away from the job for which they are being paid. In the midst of a big project like "Rocket Boy" getting people away from their jobs at all is going to be really, really hard. The pipeline staff will be busy and their managers will go ballistic if there is even a hint of pulling someone off-task when a deadline is staring everyone in the face. (For this reason it IS a good idea that the training staff is leaning toward an EPSS - but I want to come back to this in just a bit...)

About the time allocated to this effort - Nine months may not seem like very much time to implement a project like this. Just keep in mind that in highly competitive industries, nine months can represent two or three new product cycles. That means that, in those competitive settings, training may be expected to have been revised two or three times in that same nine months. (On a personal note, nine months for project implementation sounds like an incredible luxury to me...). Just be aware that if the work can be done in less time, and can show impact sooner rather than later, that would be a very good thing.

We also really need to take a look at Jason in all of this, as well. From the sounds of it, his last two jobs were oriented much more toward development than design. This has afforded him the opportunities to play a more "creative" role than may be expected of a "lead designer". Lead designers are as often as not a project's manager. Lead designers may get involved in some of the storyboarding and coding and scripting, but they need to play a very different project role than do their developer colleagues. It's really helpful that Jason has an affinity for the entertainment industry, and that he may be able to develop basic proficiencies with some of the equipment that his training designs will need to feature. Nevertheless, Jason needs to remember that HIS job is to make sure that he constructs a design that responds to the needs of his stakeholders, funders, the intended audience(s) and his own supervisory staff. He needs to be sure that he engages the participation of key subject matter experts - including unit "opinion leaders" who will "bless" the integrity of the resources he develops by virtue of their participation.

He also has to be sure that the technical writers, artists, programmers, coders and QA staff working under his direction to create his EPSS will be able to get their work done. He sure isn't going to be producing this EPSS on his own - not in this environment, and not with the audience(s) he is going to have to satisfy. Does Jason have any real project management experience? Does he understand the importance of setting expectations? Does he really understand who his clients for this project really are? (I've noticed that Jason's two previous jobs have been as part of an internal training and development team. Does he have any real experience working with clients? Even internal clients?) Does Jason have an intact EPSS development team, or will he need to go outside the company to find that kind of talent? Does he know how to select staff? Does he know how to build a team from a crew of individual contributors? Does he know how to manage project scope, and to manage for "scope creep"? Does he know how to implement project change management procedures?

Now, to the anticipated EPSS: I would hope that Jason recommends a Discovery Audit (that's what we call it in my company) to determine what the real performance problems are before he starts lining up his EPSS team - even if he does it informally. There is no point in getting his own training supervisors all cranky, but there is also no point in marching down the path they have selected for him if he is the one expected to be successful. (As a mentor of mine once told me, "Don't take on responsibility unless you also have authority to make necessary decisions.") It does seem as if an EPSS may be called for, looking at preliminary indicators. However, I think Jason will be much better served if he:

  • Understands what the performance problems really are.
  • Understands how training is going to make a difference in profitability.
  • Prioritizes who is going to be served by whatever intervention he recommends.
  • Knows who the project stakeholders are.
  • Knows who needs to come "on board" for the project to be successful.
  • Can articulate what the success factors for this project actually are.
  • Identifies the project contingencies (timeline, budget, staff restrictions, access to SMEs, and so on).
  • Knows what risks he is likely to encounter, and how he plans to mitigate against those risks.
Once he get all this figured out, then it's time to start drawing up his proposal. He should be sure to factor all of these questions into his formal needs assessment component of his design proposal.



Return to the 1998 ID Case Event
Click here to
return to the top
of this page