**Author:** [[3. Resources/Authors/Steve Rosenbaum, Jim Williams|Steve Rosenbaum, Jim Williams]] # Book Overview ![[Learning Paths Visual.excalidraw]] ## About the Author Steve Rosenbaum and Jim Williams began collaborating in 1996 when Jim joined GE to lead training for one of the GE Capital businesses. Jim Williams spent over twenty years in training and development at IBM and GE, serving as Chief Learning Officer for GE's Business Process Outsourcing work in India and setting up GE's learning function in Eastern Europe. He developed award-winning sales training at GE Capital and pioneered distance learning for technical training at IBM. Steve Rosenbaum worked for twenty-three years as an external consultant and instructional designer with companies including Disney, DuPont, GE Capital, Ceridian, IBM, and Carlson Companies. He's the author of two other books: *Managing and Measuring Productivity* and *Fair Employment Interviewing*. The collaboration gives the book a double perspective -- Jim's "inside out" view from running corporate training functions, and Steve's "outside in" lens from consulting across industries and company sizes. ## Central Thesis The core argument is disarmingly simple: the thing that matters most about employee training isn't whether people pass the final exam -- it's how long it takes them to become independently productive on the job. Rosenbaum and Williams call this "Time to Proficiency," and they argue it's the single most important metric the training function can deliver. The gap between "Graduation Day" (when formal training ends) and "Independence Day" (when an employee actually performs at an average level without supervision) is where organizations bleed money, lose customers, and burn through new hires. Most companies don't even measure this gap. They assume training ends when the classroom session does. The book builds a six-step methodology around this insight: select a function, measure current Time to Proficiency, map the existing Learning Path (everything from day one to proficiency, not just the course catalog), find quick improvements, reengineer the path using twelve accelerated learning principles, and then implement, maintain, and report results. The whole thing is designed around what they call the "30/30 Plan" -- a thirty-day sprint to reduce Time to Proficiency by 30 percent. ## Why This Book Matters Most training literature focuses on instructional design quality, learning theory, or training ROI calculations. This book does something different: it treats time as the primary variable. Every day an employee isn't proficient costs the organization money in errors, lost productivity, and customer friction. By reframing training around time rather than content coverage, Rosenbaum and Williams give training leaders a metric that executives actually care about. A CFO who doesn't care about Kirkpatrick's four levels of evaluation will pay attention when you tell them you can get new salespeople productive six weeks faster, which translates directly to revenue. The book also confronts a reality that most training programs ignore: people don't become proficient through classroom training alone. They need structured practice, on-the-job coaching, and real experience. The analogy the authors use is golf -- you can take a three-week golf course, but the difference between shooting 100 and shooting 75 is roughly 85,000 practice balls. Training curriculums rarely account for this practice gap. Learning Paths do. --- # Chapter Summaries ## Chapter 1: From Graduation Day to Independence Day The book opens with a call center scenario that frames the core problem. A 500-person call center with 50% attrition needs to train 200-300 new employees per year. Official training lasts about sixty days, but actual Time to Proficiency -- measured by performance data, not by supervisor estimates -- runs two to three times longer. Three factors drive this gap: front-loaded classroom training creates a "data dump" that's mostly forgotten by week three, organizations underestimate how much practice it takes to master skills, and post-classroom on-the-job training is inconsistent and unstructured. The chapter introduces the golf analogy to illustrate the practice gap and defines the six-step Learning Path Methodology and the 30/30 Plan. The most useful concept here is the distinction between Graduation Day and Independence Day -- and the "mystery period" in between where real learning happens in a completely unstructured way. ## Chapter 2: Getting Started A practical setup chapter covering the Readiness Assessment (a fifteen-question diagnostic of organizational support and capability), function selection criteria (pick revenue-generating, customer-facing jobs with high headcount and a willing executive champion), Learning Path team assembly (seven roles from executive sponsor to quality leader), and the kickoff meeting agenda. The case study introduces Generic International Inc. (GII), a fictional company with a 500-person customer service call center and 40% turnover. The key practical insight: overweight the "management support" factor when choosing where to start. A function with moderate need but a strong champion will outperform a function with urgent need but no sponsor. ## Chapter 3: Measuring Time to Proficiency The measurement chapter is where the methodology gets teeth. The authors walk through establishing baseline proficiency measures (calls per hour, error rates, sales per day), tracking individual employees from hire date to the point they reach average performer levels, and computing average Time to Proficiency across classes. They distinguish between survey-based estimates (which are always optimistic) and actual performance data. The chapter also introduces the idea of measuring proficiency by call type or task -- finding, for instance, that booking air-only reservations reaches proficiency in days while cruise calls take eighty practice repetitions. This granularity lets you target the specific areas that drag out the Learning Path. The business results section is straightforward: if you reduce Time to Proficiency for ten salespeople from sixty days to forty-five, the additional sales during those fifteen days are directly attributable to the initiative. ## Chapter 4: Mapping Learning Paths This chapter covers research (job shadowing, collecting training materials, interviewing incumbents and managers), preparing a findings report that advances the team's starting point beyond obvious knowledge, and the actual mapping session where the team fills in a Learning Path template with four columns: Day, What, How, and Materials. The template structure is more granular than a course catalog -- it includes on-the-job activities, specific numbers of repetitions (take 25 incoming calls, make 3 cold calls), and coaching sessions. The process typically takes two to three sessions, and the authors warn against shortcuts that result in a Learning Path that just looks like a training program's table of contents. ## Chapter 5: Finding Quick Hits The fastest wins come from three places. First, cut anything outdated, redundant, or wrong -- products no longer sold, processes that have been automated, duplicated presentations by different trainers. Second, add tests and milestones to monitor progress and catch problems early. Third, restructure the post-training period with formal coaching rather than leaving new employees to figure things out alone. Other quick hits include pre-hire requirements (moving basic skills training to community colleges), converting classroom lectures into directed self-study, and creating job aids like checklists and reminder cards. The case study shows GII reducing classroom training from fifteen to twelve days but adding the saved time to structured nesting, and extending coached on-the-job training until proficiency is actually reached rather than stopping at an arbitrary date. ## Chapter 6: Accelerating Learning Paths The most substantive chapter. It presents twelve principles for reengineering a Learning Path: (1) managers must be trainers, not just supporters; (2) reserve classroom time for practice and discussion, not lectures; (3) all self-study must be "directed" with manager review, tests, and integration into the path; (4) teach the whole job, not parts -- sequence training around tasks from simple to complex rather than topic by topic; (5) require mastery, not just participation -- accepting 75% on a test means accepting 25% errors; (6) connect training to current business needs through regular business needs analysis sessions; (7) embrace technology for speed and cost reduction; (8) prioritize quantity over production quality -- a digital video shot in an afternoon beats a $50,000 professional video that takes six months; (9) use design templates to speed development; (10) write content down rather than leaving it in experts' heads; (11) use proficiency models instead of competency models; and (12) build in motivation through relevance, early wins, and varied formats. The practical application sequence: reduce classroom time, replace classroom with on-the-job practice, substitute job aids for training, combine topics to reflect real job tasks, and re-sequence from simple to complex. ## Chapter 7: Transition and Maintenance Covers the logistics of switching from old training to the new Learning Path, including phased-in approaches where both run in parallel for a time, communication strategies for trainers and managers who may resist the change, and maintenance planning to keep the path current. The reporting section provides templates for presenting results to management, including Time to Proficiency trends, business impact, and comparison between old and new paths. The authors stress that maintenance is ongoing -- a Learning Path that isn't updated becomes just as stale as the curriculum it replaced. ## Chapter 8: Managing Learning Path Projects A project management chapter covering common pitfalls (scope creep, perfectionism, legal review bottlenecks), building internal support through early wins and champion relationships, development process and tracking templates, review committee management (don't add new members mid-project), pilot testing, and editing standards. The virtual teams section, while dated, recognizes that distributed teams building Learning Paths face coordination challenges. The most practical advice: keep review committees fixed from start to finish. Adding new reviewers mid-stream torpedoes projects because they insert their own agendas into work that's already been agreed on. ## Chapter 9: Building Proficiency Models Distinguishes between traditional competency models (lists of individual skills and knowledge) and proficiency models (combinations of skills, knowledge, and attitudes as they're actually used together on the job). The key insight: a customer service rep doesn't use phone skills, computer skills, and product knowledge separately -- they use all three simultaneously. Training that teaches these in isolation takes longer to produce proficiency than training that integrates them. Proficiency models also include measurable standards: not just "prospect for new business" but "identify and qualify sufficient leads to get five new appointments per week." The chapter provides a practical process for cross-referencing Learning Paths against proficiency models to find gaps and redundancies. ## Chapter 10: Developing Top Performers Extends the Learning Path concept beyond new hire onboarding. The chapter covers paths for average-to-top performer development, remediation for below-average performers (walk them through the Learning Path to find what they missed), accelerated paths for experienced new hires who can test out of basics, manager/leadership development paths, and one-person Learning Paths for small functions where a single employee holds all the knowledge. The top performer analysis involves researching what 5-out-of-5 performers do differently and building that into a developmental Learning Path. The leadership path examples are particularly concrete -- showing week-by-week progression from observing a project to leading one, with structured manager coaching at each stage. ## Chapter 11: Connecting to Business Needs Argues that the learning function leader needs to move from a tactical to a strategic role by conducting annual Business Needs Analysis sessions with senior management and quarterly updates. The Proficiency Planning Process maps business changes to their workforce impact: a new product launch requires these proficiencies, which require these training changes, by this date. The Learning Path Planning Process then translates proficiency needs into specific Learning Path modifications across multiple functions. The chapter also covers Learning Paths and ROI, organizational initiatives like outsourcing and mergers, and how to use the methodology when business changes are happening faster than training can be developed. ## Chapter 12: Capturing Content A brief practical chapter on techniques for getting expert knowledge out of people's heads and into usable formats: transforming PowerPoint presentations into directed self-study, using screen capture software to document computer processes, creating digital video walkthroughs, and process mapping. The emphasis on low-cost, fast content capture methods (grab a digital camera, record the plant manager doing a tour) reinforces the book's bias toward speed over production quality. ## Chapter 13: Selecting Training Methods Evaluates training delivery methods across three factors: effectiveness, cost, and speed/flexibility. Ranks methods from self-study (cheapest, fastest to update, but needs manager involvement to be effective) through classroom (most expensive, hardest to change, but best for practice and group interaction) with on-the-job coaching, e-learning, and video in between. The key argument: no single method is best -- the right answer is a blend that matches the content type to the most appropriate delivery method, weighted by cost and speed constraints. ## Chapter 14: Establishing Managers as Coaches Perhaps the most ambitious chapter in terms of organizational change required. The manager-as-coach role spans five functions: motivator (creating an environment that supports learning), teacher (delivering structured on-the-job training), debriefer (reviewing real situations after they happen), training meeting leader (running short, focused practice sessions), and evaluator (providing formal observation-based feedback). The chapter includes a process for coaching the coaches -- training managers in how to teach, evaluate, and give feedback -- and a coaching guide template. The honest tension here is that most managers don't see coaching as their job and aren't rewarded for it. ## Chapter 15: Building Directed Self-Study Provides a development process and instructional design template for converting classroom lectures into structured self-study with learning objectives, content sections, practice activities, and tests. The emphasis on "directed" means every self-study assignment has a manager review step, a discussion component, and a connection to the next activity on the Learning Path. Self-study without these elements is just reading -- and the authors acknowledge that people won't do it without structure and accountability. ## Chapter 16: Creating the New Classroom Experience Redefines classroom time as practice-focused rather than lecture-focused. Covers team building activities, real-situation practice (using actual customer scenarios rather than made-up ones), games for compliance topics, and follow-up processes. The compliance section is pragmatic: some topics must be classroom-delivered for regulatory reasons, but that doesn't mean they must be boring lectures. The overall thrust: if you've moved knowledge acquisition to self-study and on-the-job coaching, classroom time becomes the most expensive and valuable learning time -- spend it on things you can only do in a group. --- # Key Takeaways ## Key Takeaways 1. Time to Proficiency -- the gap between day one and independently productive performance -- is the most meaningful metric for training effectiveness, and most organizations don't measure it at all. When they do, the actual number is typically two to three times longer than managers estimate. 2. The "mystery period" between the end of formal training and actual proficiency is where the real learning happens, and it's almost always unstructured, inconsistent, and invisible to the organization. Formalizing this period with structured coaching, practice targets, and milestones is where the biggest gains come from. 3. Traditional topic-by-topic training design (learn the phone system, then learn the computer, then learn the process) is fundamentally slower than task-based design (learn to handle a simple call using all three together, then move to complex calls). Training the parts in isolation doesn't teach people to use them simultaneously. 4. The 30/30 Plan is a smart adoption strategy: show a 30% improvement in thirty days to build credibility and executive support before attempting the larger reengineering effort. This political sophistication is as important as the methodology itself. 5. Managers must be actively involved in training delivery and coaching -- not as a nice-to-have, but as the primary mechanism for bridging the gap between classroom learning and job performance. Training that managers don't support or understand will be undermined on the job. 6. Proficiency models (what does the whole job look like when performed at standard?) are more useful for Learning Paths than competency models (what individual skills and knowledge are required?). The distinction sounds academic but has real design implications. --- # Notable Quotes > "Every day an employee is not fully up-to-speed costs the organization money in terms of lost productivity, increased errors, and often lost customers." > "The major difference between someone who shoots as low as the 90s and an A-level player shooting in the 70s is about 85,000 practice balls." > "You're even likely to get a coach who says, 'Forget about what you learned in class. I'll show you how this is really done.'" > "If you asked supervisors in the call center how long it takes a new employee to get up-to-speed, they would probably say sixty days. However... if you actually looked at performance measures you'd find that it can take two to three times longer." --- # Connections & Further Reading - [[Execution]] by Larry Bossidy and Ram Charan -- Bossidy's insistence that leaders must be personally involved in core processes parallels the Learning Paths argument that managers must be trainers. Both books attack the tendency to delegate the most important work. - [[The First 90 Days]] by Michael Watkins -- Watkins focuses on leadership transitions, but the underlying question is the same: how do you reduce the time it takes someone to become effective in a new role? - [[High Output Management]] by Andy Grove -- Grove's concept of training as the manager's highest-leverage activity directly supports Principle #1 (managers need to be trainers). - [[Peak]] by Anders Ericsson -- Ericsson's deliberate practice research provides the scientific foundation for the practice-intensive approach Rosenbaum and Williams advocate. The 85,000 practice balls argument is essentially deliberate practice applied to corporate training. - [[The Lean Startup]] by Eric Ries -- The 30/30 Plan shares DNA with lean methodology: build a minimum viable version, measure results, iterate. Ship something that works in thirty days rather than perfecting something over six months. - [[Atomic Habits]] by James Clear -- Clear's systems-over-goals framework connects to the Learning Path idea of building structured, repeatable processes rather than relying on individual effort and motivation. --- # Personal Reflection ## What surprised me? The sheer size of the gap between estimated and actual Time to Proficiency. When the book presents data showing that managers think it takes six weeks to get up-to-speed but actual measurement reveals ten weeks, that's not a small error. It's a systematic blind spot. Organizations are making staffing, budgeting, and customer service decisions based on numbers that are 40-60% too optimistic. The fact that nobody bothers to check the actual data is the most damning part. Also surprising: how much of the typical Learning Path improvement comes not from better training design but from simply eliminating outdated content and formalizing the post-classroom period. The "quick hits" -- cutting training on products that no longer exist, removing duplicate presentations, adding structure to the nesting period -- don't require any instructional design sophistication. They require someone to actually look at what's happening. ## What challenged me? The book's insistence that managers must become trainers challenged my assumption that training is best left to specialists. The argument is compelling -- training that managers don't deliver or understand gets contradicted on the shop floor -- but the organizational change required is enormous. Most managers aren't rewarded for coaching, don't see it as their job, and aren't good at it. The book acknowledges this but may underestimate how hard the cultural shift really is. I'm also not entirely persuaded by the proficiency-over-competency distinction. The examples make it clear that proficiencies are more useful for training design, but the difference sometimes feels like relabeling rather than a genuine conceptual advance. A well-constructed competency model that includes performance standards looks a lot like what the authors call a proficiency model. ## What will I apply? The Time to Proficiency metric is immediately useful for any onboarding or training situation. Instead of asking "did people complete the training?" ask "how long until they're performing at standard?" and then actually measure it. This reframes every training decision around outcomes rather than inputs. The practice gap concept -- the distance between what classroom training covers and the amount of real repetitions needed for mastery -- translates to any skill development context. Before building more training content, ask: have we built in enough structured practice? The answer is almost always no. The 30/30 Plan as a change management strategy is smart and portable. Don't try to overhaul everything at once. Pick a function, show a 30% improvement in thirty days, use that credibility to fund the next iteration. This works for any organizational improvement initiative, not just training.