BLOG

Reskilling and Upskilling: Workforce Transformation in the Age of AI

Reskilling and Upskilling: Workforce Transformation in the Age of AI
Qulak EditorOctober 31, 20262 viewsblog
Strategic Market Gap and Procurement · BoFU

Reskilling and Upskilling: Workforce Transformation in the Age of AI

Before rushing to bring in talent from outside, address skills visibility, learning design, and governance together to prepare existing employees for next-generation roles.

AI should be viewed not as a technology that “reduces” the workforce on its own, but as a transformation that redistributes tasks and the skills they require. In the World Economic Forum’s 2025 report, employers expect an average of 39% of existing skills to change or become outdated between 2025 and 2030. The same report identifies the skill gap as one of the most significant barriers to job transformation [1]. This landscape makes moving internal experience into new roles a strategic option alongside hiring externally whenever a new need arises.

The goal here is not to turn everyone into a software developer. It is to make visible which tasks will be affected by automation, which human skills will gain value, and what learning steps can prepare existing employees for new responsibilities. That is why reskilling and upskilling are not just matters of training catalogs; they are workforce planning, internal mobility, and procurement decisions.

Executive summary

The right sequence is: define critical roles, measure the skill gap using evidence, align learning with real tasks, establish human oversight, and procure a platform only if it can make this framework sustainable.

What do reskilling and upskilling address?

Upskilling, deepening an employee’s skills so they can take on more advanced responsibilities in their current role. For example, developing a sales operations specialist’s data literacy, process automation, or AI-assisted analysis skills is upskilling. Reskilling is acquiring a new set of skills so an employee can move to a different role because the distribution of tasks has changed. Preparing the same specialist for a role as a learning analytics coordinator or process designer could be an example of reskilling.

This distinction clarifies where to invest. If the core of the role remains intact while the tools change, upskilling is needed; if the purpose or responsibilities of the role change significantly, reskilling is needed. According to the OECD, advanced AI skills are not a fundamental need for most employees; using, analyzing, and interpreting data, along with problem-solving, creativity, and management skills, remain important for a broad range of workers [2].

Upskilling

Develop new tools, methods, and decision-making skills while remaining in the current role. The goal is to increase the role’s capacity.

Reskilling

Prepare for a transition to another role in response to changing business needs. The goal is to enable internal mobility.

Internal mobility

Connect the learning outcome to a real work opportunity through an open role, project, job rotation, and manager support.

A roadmap for transforming internal talent instead of hiring externally

Internal workforce transformation does not begin with a general “let’s provide training” campaign. First, the business goal and role requirements are identified. Then, employee data is turned into evidence of skills within the boundaries of privacy and fairness. The checklist below helps an organization progress as far as designing a pilot.

  1. Select critical roles: Identify roles whose tasks will change because of AI or automation, that are important for growth, or that are difficult to fill.
  2. Break tasks down into skills: Define the role’s day-to-day outputs, not its title, as well as the technical, digital, analytical, and human skills required.
  3. Measure skills with evidence: Do not treat self-assessment as sufficient on its own. Use work samples, manager observations, project outputs, and structured assessments together.
  4. Match adjacent transitions: Identify employees whose existing experience is closest to the new role. Use this matching to prioritize human review, not to make automated decisions.
  5. Connect learning to tasks: Design a pathway comprising short-form content, practical tasks, coaching, and team feedback. Do not treat content completion rates alone as a measure of success.
  6. Establish a pilot and an appeals mechanism: Start with one job family. Define a process through which employees can challenge a recommendation, correct their data, and see the reasoning behind a decision.
  7. Track business outcomes: Alongside skill acquisition, track indicators such as transition into the role, independence in the role, quality, employee experience, and manager observations.

How should next-generation role examples be considered?

A department’s introduction to AI does not mean simply hiring a new “AI specialist.” Hybrid responsibilities may emerge, such as data quality ownership in finance, workforce analytics literacy in human resources, AI output quality control in customer operations, and process-data coordination in manufacturing. In designing these roles, domain knowledge, ethical judgment, communication, and exception management are as important as technical skills.

The procurement decision: What problem should a platform actually solve?

At the BoFU stage, instead of asking “which product offers more features?”, ask “which workflow will it make measurable and auditable?” A solution should not become a black box that automatically scores employees while making their skills visible. The vendor should be able to explain the data sources, matching logic, human approval, appeals process, and how records can be exported.

Procurement criterionQuestion to ask in the demo and specificationsDecision signal
Business goal and role modelCan the role, task, and skill dictionary be adapted to the organization’s context?A pilot workflow that validates the organization’s role architecture rather than relying on preset labels.
Data minimizationWhich data fields are mandatory for employee matching, and which are optional?The minimum data appropriate to the purpose, with clear retention and deletion policies.
Human oversightWho approves the recommendation, and how can employees challenge it?An explainable recommendation, authorized approval, and a record instead of an automated decision.
Integration and portabilityHow is the connection to the HR system, identity management, and learning data established, and how is the data exported?Documented interfaces, role-based access, and exports that reduce vendor lock-in risk.
Total cost of ownershipWhat are the costs of implementation, content, integration, support, and change management beyond the license?Assumptions are documented, the proposal is comparable, and the pilot scope is clear.
Evidence and measurementWhich indicators are used to track the impact of learning outcomes on work?Reporting that tracks internal mobility and job performance and does not rely on a single metric.

Under what conditions can Qulak be considered? If your organization wants to prepare existing employees for new roles alongside external hiring, and address role and skill visibility, learning pathways, and management decisions within the same transformation agenda, Qulak can be shortlisted. However, the decision should be based not on general trust in the brand, but on a pilot tailored to your organization. During the pilot, the role-matching logic, data access boundaries, human approval, integration scope, report portability, and total cost should be verified in writing. If these conditions are not met, alternative providers should be compared against the same criteria.

First, identify the right question for your internal talent transformation

Speak with the Qulak team to jointly frame the critical job family, existing skills data, and procurement criteria that need to be validated in a pilot. The discussion is intended to clarify the scope specific to your organization; the final selection should be made through a comparative evaluation.

Discuss Internal Talent Transformation

Boundaries for AI use: data, people, and governance

Employee skills data may contain personal data. For this reason, data minimization, purpose limitation, access permissions, retention periods, and, where necessary, deletion processes should be part of the design. The Personal Data Protection Authority’s guide on the use of generative AI tools in workplaces notes that using public tools based on individual choices, outside corporate strategy and policy, can make monitoring and management more difficult [3]. Directly submitting an employee’s résumé, performance review, health information, or confidential customer information to a public model should not be an acceptable default.

The NIST AI Risk Management Framework recommends extending trustworthiness assessments of AI systems across the design, development, use, and evaluation lifecycle [4]. In practice, this means knowing what data is used, checking for errors and bias, limiting access, keeping incident records, and periodically reviewing model outputs. Particularly for high-impact decisions such as hiring, promotion, role changes, or termination, AI output should not be the final verdict; a human should be able to interpret the output, question its rationale, and disregard it when necessary. Your organization’s legal, information security, human resources, and employee representatives should work together to document the boundaries.

A practical decision framework to get started

Do not try to transform the entire organization at the first step. Select one job family and answer these four questions: Which tasks are changing in this role? Which skills already exist internally? Which skill gaps can be closed through training, projects, and coaching? At what point is external hiring genuinely necessary? If you cannot support your answers with data, first improve the skills inventory and role description.

The same discipline applies when choosing a platform. Test the provider’s demo using a real job family, a sample competency dictionary, and your organization’s data policy. Qulak can be considered if it meets the visibility and governance controls you need in this pilot; if it does not, it is healthier to defer the decision or choose another solution. Procurement success depends less on the number of features than on the organization’s ability to mobilize internal talent safely and fairly.

Frequently Asked Questions

What is the difference between reskilling and upskilling?
Upskilling means developing an employee’s skills to take on more advanced responsibilities in their current role. Reskilling means acquiring different skills to move into a new or changing role.
Why should internal workforce transformation be considered before external hiring?
Internal candidates already know the organization’s processes and work context. If a competency gap can be closed through training, practice, and manager support, internal mobility may be a more controlled option. However, the external market, timeline, and risks should be compared for every role.
Should AI automatically determine employee promotions or role changes?
No. AI can help organize skill signals or generate learning recommendations. High-impact decisions such as promotion, role changes, and termination should be made by authorized people using explainable criteria and appeals mechanisms.
Under what conditions can Qulak be considered?
If your organization wants to address internal talent transformation, skills visibility, and learning pathways together, Qulak can be shortlisted. The decision should be made after validating data controls, human oversight, integration, portability, total cost, and pilot findings.

Content review and methodology: Qulak Content Team

This article addresses reskilling and upskilling in the context of workforce planning, internal mobility, data minimization, and human oversight. Product features and performance claims should be validated through a pilot tailored to your organization and a review of the contract.

Related Qulak guides

Sources

Evaluate internal talent transformation comparatively

Share your critical job family, skill gap, and data governance boundaries with the Qulak team. Clarify the pilot scope, procurement criteria, and points that need to be validated together.

Start a Conversation with Qulak