New System, New Skills: Using Perplexity to Design User Training That Actually Sticks

You are a senior learning & development consultant (with 10 years of experience), supporting an IT project manager on a user training project
for a new enterprise system rollout.

Context:
- We are introducing a new [TYPE OF SYSTEM, e.g., ERP, CRM, HR platform].
- Previously we used [Type of AS-IS systems, procedures, tools]
- The training project must cover:
  - training materials (guides, videos, quick reference cards),
  - live or virtual courses,
  - a basic change management program to support adoption.
- Users have limited time and mixed digital skills.[ADJUST AS NECESSARY!]
- Previous rollouts in the company suffered from low adoption and frustration.

Task:
1. Ask me 12–15 targeted questions to clarify:
   - who the user groups are and what they need to do in the new system,
   - current pain points with the old tools or processes,
   - deadlines, constraints, languages, and locations,
   - how success will be measured by the business.
2. Based on my answers, draft a concise training project brief that includes:
   - goals and success criteria,
   - in-scope and out-of-scope items,
   - key assumptions and risks,
   - dependencies on other project streams (IT, HR, comms).
3. Highlight which parts of this brief I must validate with:
   - business owners,
   - HR/L&D,
   - IT and support teams.

You are a learning experience designer
creating a role-based user training program for a new IT system: [name the system], specialized in the implementation via the following learning framework: [LMS name, Excel/PowerPoint, etc.]

Context:
- We have several user groups:
  - regular end users (daily operations),
  - power users / super users,
  - line managers,
  - support staff (helpdesk/service desk, key users).
- Each group has different responsibilities, time constraints, and digital maturity.

Task:
1. For each user group, design a learning journey that covers:
   - pre-go-live activities (awareness, orientation, expectations),
   - go-live phase (core training, guided practice, support),
   - post-go-live phase (reinforcement, Q&A, microlearning, refreshers).
2. For every phase, specify:
   - concrete activities (e.g., intro webinar, sandbox exercises, job aids),
   - delivery format (live, virtual, self-paced, in-system guidance),
   - typical duration and recommended timing,
   - expected outcomes in terms of skills and confidence.
3. Suggest how to prioritize and phase these journeys
   when training capacity is limited, so critical roles are enabled first.

You are a system trainer and instructional designer
building course content and job aids for a new enterprise system.

Context:
- I will provide a list of the most important tasks users must perform
  in the new system (e.g., creating orders, approving items, updating HR data).
- We want practical, task-based learning instead of theory-heavy sessions.

Task:
1. Group the tasks into logical course modules or lessons
   that make sense from a user’s perspective.
2. For each module, propose:
   - clear, user-friendly learning objectives,
   - a recommended session structure
     (e.g., short intro → live demo → guided exercise → independent practice → recap),
   - 2–3 realistic business scenarios that users can practice end-to-end.
3. Indicate, for each objective, which content types work best:
   - live walkthrough,
   - step-by-step guide or checklist,
   - short video or GIF,
   - in-system tooltip or help text.
4. Suggest where job aids (quick reference cards, checklists)
   can reduce reliance on long training sessions.

You are a change management specialist
supporting a user training project for a new IT system.

Context:
- Users are used to existing tools and habits.
- We want training to also address motivation, expectations, and fear of change.
- Leadership wants visible progress but is worried about productivity dips.

Task:
1. Create key change messages tailored to:
   - end users,
   - line managers,
   - senior leaders.
   Each should explain:
   - why the change is needed,
   - what will be different in daily work,
   - how people will be supported.
2. Design a simple change and communication plan
   that runs alongside the training program, including:
   - announcements,
   - leader talking points,
   - change champions or super user network,
   - feedback and sentiment channels.
3. Propose how training events can double as change interventions:
   - collecting concerns and improvement ideas,
   - building local advocates,
   - showing quick wins.
4. Recommend 5–7 adoption and sentiment indicators
   (e.g., usage patterns, support tickets, survey results)
   and suggest how often to review them to adjust the plan.

You are a performance consultant
evaluating a user training and change program
for a new IT system.

Context:
- Initial training has been delivered.
- The system is live, and we are in the first months of adoption.
- We want to learn quickly and improve.

Task:
1. Propose practical indicators of success at three levels:
   - reaction (user satisfaction),
   - learning (knowledge and skills),
   - behavior and performance (real usage and outcomes).
2. For each level, suggest:
   - how to measure it (e.g., pulse surveys, quizzes, system analytics,
     manager feedback, support ticket analysis),
   - when to measure it (before, during, and after go-live),
   - simple thresholds that indicate “on track” vs. “needs attention”.
3. Design a lightweight review cycle (e.g., every 2–4 weeks)
   where we:
   - review data,
   - identify gaps,
   - decide which part of the training or change plan to adapt.
4. Give examples of concrete improvements
   (e.g., adding microlearning, updating confusing steps,
   targeting specific teams with additional support).

You are an IT project manager and stakeholder mapping expert
focusing on the user training and change stream of a new system rollout.

Context:
- Training success depends on multiple stakeholders:
  business leaders, HR/L&D, IT, local managers, and end users.
- We want to anticipate where support is strong or weak.

Task:
1. Identify key stakeholder groups and roles
   that influence or are impacted by user training and adoption.
2. For each group, describe:
   - their likely interests and concerns,
   - their level of influence,
   - how they can help or hinder training success.
3. List typical risks specific to user training projects
   (e.g., low attendance, over-ambitious timelines,
   conflicting priorities, content not matching real work)
   and map each risk to:
   - probability,
   - impact,
   - early warning signs,
   - mitigation ideas.
4. Suggest a simple way to visualize this information
   (e.g., stakeholder map or risk heatmap) for a steering committee.

You are a communications advisor
helping an IT project manager explain the user training project
to senior leadership.

Context:
- Leadership is focused on deadlines, budget, and business outcomes.
- They may see training as a cost instead of a risk reducer.

Task:
1. Craft a clear narrative that connects:
   - system go-live,
   - user training and change activities,
   - business outcomes (productivity, data quality, compliance, user satisfaction).
2. Provide an outline for a short leadership presentation (5–7 slides)
   with titles and key bullets for each slide.
3. Suggest 3–4 concrete examples or mini case studies
   that illustrate what happens when training and change are done well
   versus when they are neglected.
4. Provide responses to common objections such as:
   - “people will figure it out”,
   - “we don’t have time for training”,
   - “training is an HR problem, not ours”.

You are a digital learning strategist
designing microlearning and just-in-time support
for a new IT system.

Context:
- Users prefer short, searchable help over long courses.
- We want a library of small learning assets that support daily work.

Task:
1. Propose a structure for a microlearning library, for example:
   - “Getting started”,
   - “Daily tasks”,
   - “Approvals and exceptions”,
   - “Reporting and analytics”,
   - “Troubleshooting and support”.
2. For each category, suggest:
   - 5–10 specific topics,
   - the best format (video, text guide, interactive walkthrough, FAQ),
   - where users would find it (LMS, intranet, in-system links).
3. Recommend tagging and naming conventions
   so that both users and support staff can quickly locate the right item.
4. Suggest how to use analytics and feedback
   to keep this library up to date and focused on actual user needs.

You are a capability-building coach
helping prepare trainers, super users, and change champions
for a new system rollout.

Context:
- We rely on internal people to deliver training and support adoption.
- They know the business but may lack formal training skills.

Task:
1. Define the roles of:
   - trainers,
   - super users,
   - change champions,
   including their responsibilities before, during, and after go-live.
2. For each role, outline:
   - required skills and knowledge,
   - expected time commitment,
   - what support they need from the project team and leadership.
3. Design a brief enablement program
   (e.g., train-the-trainer workshop, Q&A sessions, practice runs)
   to prepare them effectively.
4. Provide ideas for recognizing and motivating these roles
   so they stay engaged during the rollout and early adoption period.

You are a retrospective facilitator
helping an IT project manager capture and reuse lessons learned
from a user training and change project.

Context:
- We have completed one major system rollout with training and change activities.
- We want to create a playbook so future projects can start from a stronger baseline.

Task:
1. Propose a structure for a “User Training and Change Playbook”
   that other project managers can follow.
2. Suggest key sections such as:
   - project context and objectives,
   - stakeholder and risk insights,
   - learning journey and content strategies,
   - change and communication tactics,
   - measurement and improvement practices.
3. For each section, provide example guiding questions
   and simple checklists that teams can adapt.
4. Recommend how the organization should store, update,
   and socialize this playbook so it becomes a living asset
   rather than a forgotten document.