Case Study 24 Notes - Austin McGwire and Ken Casey

Case Study 24: Austin McGwire and Ken Casey

Overview of the Case Study

  • Authors: I. Andrew Teasdale and Sean R. Tangney

  • Main Characters: Brian Joseph, Austin McGwire, Ken Casey.

The Context

  • Brian Joseph: Manager of a restructured engineering department in a manufacturing company.

  • Engineering Department: Responsible for building large dies used in manufacturing-formed sheet metal, costing between $1 million and $3 million.

Purpose of the Training Request

  • Brian initiated a request for a new training course due to:
      - Significant changes in tools, personnel, and processes resulting from departmental restructuring.
      - Several projects in the engineering department significantly overrunning their budgets.

  • Objective of the Training:
      - Update die engineers on necessary information for job performance.
      - Guidelines to keep projects on time and within budget.
      - Recommendations for managing projects experiencing time or cost overruns.

Roles in the Project

  • Austin McGwire: Lead designer from the training department.
      - Charged with integrating web-based components into training interventions due to a shift towards "e-business".

  • Ken Casey: Developer of the training project, contracted from an external training firm.
      - Background in classroom-based course development, new to web-based development.

Training Initiative

  • Encouragement from management for e-learning initiatives to:
      - Reduce classroom time and deliver content asynchronously over the company's intranet.
      - Implement blended learning approaches (classroom and online).

  • Strategy Meeting Participants:
      - Brian Joseph, Austin McGwire, Ken Casey, three subject matter experts (SMEs):
        - Program Timing Expert (oversees die development milestones).
        - Investment Report Expert (tracks project spending).
        - Part Management System Expert (tracks various die parts).

Proposed Intervention

  • An intervention consisting of:
      - Blended Approach: Classroom instruction combined with an intranet-based performance support system.
      - Classroom portion to teach new tools/processes and introduce the performance support system.
      - Performance support system to provide all course content and additional information accessible during job tasks.

Concerns Raised During Planning

  • Ken and Austin push for preliminary needs analysis with die engineers to ensure actual needs are addressed.

  • Brian dismisses this, claiming he knows what engineers need.

  • Concerns about potential factors beyond knowledge impacting performance:
      - Project management issues inadequately addressed by Brian who responds cryptically about managing projects better.

  • Ken and Austin express concerns about the aggressive project timeline, lack of access to resources, and potential technology problems in web development.

Project Development Stages

Week 1-2

  • Ken and Austin outline interventions despite Brian's rejection of the engineers' input.

  • Commitment to a rapid prototyping approach to accommodate feedback and ownership in the design due to weekly meetings.

Week 3

  • Focus on design and content evolution.

  • Preliminary prototype of the performance support system organized by:
      - Timeline sections (Project flow, milestones, deliverables).
      - Tool sections (Investment and part management systems).
      - Supporting information (FAQ and course outline).

  • Positive reaction from Brian on the preliminary design.

Week 4

  • Development of performance support system continues, with real-time updates during meetings.

  • Use of audiotaped meetings assists in developing classroom participant guide.
     

Week 5

  • Content delivery issues arise, with Ken and Austin emphasizing the need for timely input from SMEs to avoid pilot delays.

  • Acknowledgment from Brian of an unrealistic timeline and necessary adjustments.

  • Development of the performance support system proceeds smoothly despite content delays, with improvements in Ken's technical skills.

Week 6

  • Further enhancements made to usability and navigation of the performance support system after browsing competitor systems.

  • Changes in scope are accepted, allowing for more thorough development.

Pilot Phase

  • The pilot occurs two months later than initially planned, with Brian as the instructor.

  • Testing of the performance support system proves successful, encountering minor technical issues.

  • Feedback reveals mixed reactions to the use of the support tool; some participants prefer traditional methods over the new system.

  • Discrepancies in response to the tool raise concerns about usage and engagement.

Six Months Later

  • Overall satisfaction with classroom experiences and consistency in evaluations, but concerns about lack of user engagement with the performance support system.

  • Austin suspects low usage may indicate issues with the system’s design.

  • Need for improved feedback mechanisms to gauge actual usage and efficacy of the support tool.

Preliminary Analysis Questions

  1. Access Denied to Target Audience: Considerations for pursuing the project without direct input from users.

  2. Aggressive Timeline Concerns: How team dynamics influenced the management of deadlines.

  3. Adapting to Timeline Changes: Strategies to accommodate shifts in project objectives.

  4. Engagement with Technology: Strategies for incorporating participants hesitant to use computers in learning environments.

The case study revolves around Brian Joseph, who manages a restructured engineering department in a manufacturing company that creates large dies costing between $1 million and $3 million. The department has undergone significant changes, prompting Brian to request a new training course aimed at updating die engineers on essential skills, managing project budgets, and addressing time overruns.

Austin McGwire, the lead designer from the training department, and Ken Casey, an external developer, are tasked with creating a web-based training program amidst challenges such as resistance to input from engineers, aggressive timelines, and concerns about technology integration.

Key issues include Brian's dismissal of preliminary needs analysis, inadequate addressing of project management factors, and an unrealistic project timeline which fostered significant content delivery challenges. Feedback during the pilot phase indicated mixed reactions to the new performance support system, with concerns about engagement.

Preliminary Analysis Questions Addressed:

  1. Access Denied to Target Audience: The absence of direct input from die engineers compromised the project’s relevance and effectiveness, highlighting the risk of developing training solutions disconnected from actual user needs.

  2. Aggressive Timeline Concerns: The ambitious deadlines strained team dynamics, causing a lack of thoroughness in prototyping and user inconsideration.

  3. Adapting to Timeline Changes: The team should implement a flexible project management approach focusing on iterative feedback and engagement to accommodate shifts effectively.

  4. Engagement with Technology: Innovative strategies, such as hands-on workshops and incentives, should be used to promote technology acceptance for participants hesitating to adopt new tools.

Implications for ID Practice in 2025: ID practitioners must embrace flexible and adaptive methodologies that prioritize user engagement and feedback throughout the design process. Utilizing emerging technologies and blended learning approaches can ensure that training interventions are not only relevant but also successful in meeting the learners' evolving needs.