Oracle HCM Talent Management Cloud —
100 Interview Questions & Answers

Oracle Profile Management is a centralised talent repository within Oracle HCM Cloud that stores and manages structured talent data about workers and positions. It serves as the backbone for all talent modules — enabling skills tracking, performance assessments, succession planning, and career development from a single data store.

• Person Profiles: Capture skills, competencies, qualifications, education, certifications, languages, work history, and career preferences for each worker
• Position Profiles: Define the requirements (skills, competencies, education) expected for a given job or position, enabling gap analysis
• Profile Content Library: A centrally managed dictionary of content items (competencies, skills, degrees) shared across the organisation
• Integration Point: Feeds into Performance, Succession, Career Development, Recruiting, and Learning modules for consistent data usage

• Person Profile: Belongs to an individual worker. It records what the employee currently has — their skills, qualifications, experiences, and certifications. Updated by the worker, manager, or HR admin. Used in performance reviews, succession, and learning recommendations
• Position Profile (Job Profile): Belongs to a job, position, or job family. It records what is required — the minimum and desired competencies, education, and certifications for that role. Created and maintained by HR and used for gap analysis, recruiting job descriptions, and succession readiness assessment

These are the building blocks of how profile information is structured:

• Content Type: A category of talent data. Oracle delivers standard content types such as Competencies, Skills, Degrees, Certifications, Languages, Work Experience, and Licenses. Customers can also create custom content types
• Content Section: A grouping of one or more content types assigned to a Profile Type. For example, a "Core Competencies" section might include the Competencies content type, while an "Education" section includes the Degrees and Certifications content types
• Profile Type: The template that defines which content sections (and thus content types) appear on a profile. Separate profile types are configured for Person Profiles, Job Profiles, and Position Profiles

Creating a custom content type involves several steps in Setup and Maintenance:

• Step 1: Navigate to Setup and Maintenance → Workforce Development → Profile Management → Manage Profile Content Types
• Step 2: Click Create and define the content type name, code, description, and whether it applies to Person profiles, Job profiles, or both
• Step 3: Define the attributes for the content type — these are the data fields displayed when a user adds an item (e.g., Skill Name, Proficiency Level, Date Acquired). Attributes can be text, date, number, or lookup-based
• Step 4: Set the rating model if proficiency levels are needed (e.g., a 1–5 scale for skill rating)
• Step 5: Add the new content type to the appropriate Content Section within a Profile Type so it appears on worker or job profiles

A Rating Model defines the scale used to measure proficiency levels, performance ratings, or competency scores in Oracle HCM. It is a central configuration component shared across Performance Management, Profile Management, and Goal Management.

• Components: Rating levels (e.g., 1-Novice, 2-Developing, 3-Proficient, 4-Advanced, 5-Expert), numeric values, short names, and descriptions for each level
• Usage in Profiles: Attached to content types (e.g., Competencies) so workers and managers can rate skill proficiency when updating profiles
• Usage in Performance: Also attached to Performance Document Templates to define how overall ratings and section ratings are calculated
• Configuration path: Setup and Maintenance → Workforce Development → Performance Management → Manage Rating Models

Profile Comparison is a feature that visually matches a worker's Person Profile against a target Job or Position Profile to identify competency and skill gaps. It is used across several talent processes:

• Succession Planning: Compare a succession candidate's profile against the profile of the role they are being considered for — highlighting gaps that inform development plans
• Career Development: Workers and managers compare the person profile against aspirational roles to understand development needs
• Recruiting: Candidate profiles can be compared to job profiles during the candidate selection process to evaluate fit
• Implementation Consideration — Content Alignment: For comparison to work accurately, the same content types and rating models must be used on both the Person Profile and the Job Profile. A mismatch in content types means comparison is impossible
• Implementation Consideration — Completeness: Profile comparison is only as valuable as the data quality. Implementations should include a profile completion strategy — nudges, manager reviews, and mandatory fields — to drive adoption

• Content Library: The master dictionary of available items within each content type — e.g., all available competency names, all skills, all certification types. It is shared organisation-wide and drives consistency
• Content Sections: Structural groupings on a Profile Type — they define which content types appear and in what order, but they do not contain the actual items (which live in the Content Library)
• Governance Recommendations for Large Organisations:
• Assign a Profile Administrator role responsible for approving new content library additions — preventing duplicate or inconsistent entries
• Use Content Item Approval Workflows (available via AME rules) to route new competency/skill requests through HR for review before they become available to users
• Conduct periodic content library audits — archive retired skills and competencies rather than deleting to preserve historical profile data
• Align content library items to an industry framework (e.g., SFIA for IT, O*NET for broader use) to enable benchmarking

• Oracle Learning Integration: Learning recommendations can be driven by profile gaps. If a worker's profile shows low proficiency in a required competency, Oracle Learning can surface relevant courses to close that gap. Skills acquired through completed learning are auto-populated back to the person profile
• Oracle Recruiting Integration: When creating a job requisition, recruiters reference the Job Profile to auto-populate the job description with required skills and competencies. This creates a direct link between the talent dictionary and job postings, ensuring consistent language
• Apply Flow: Internal candidates applying via the career site can have their existing person profile data used to pre-fill application fields, reducing friction

A Profile Subscriber is a configuration setting that controls which Oracle HCM modules are allowed to access and use a specific Profile Type or Content Type. It determines where profile data appears and is used.

• Common subscribers include: Recruiting (uses job profiles for requisitions), Performance (uses competencies for evaluations), Succession (uses person and job profiles for readiness assessment), and Career Development (uses both for gap analysis)
• When configuring a new custom content type, you must set the appropriate subscribers; otherwise, data entered in that content type will not be visible in the intended module

• Content Library First: Before migrating profile items, load all content library items (competencies, skills, certifications) using the HCM Data Loader (HDL) or spreadsheet loaders. These must exist before person profile items reference them
• Person Profile Migration: Use HDL with the PersonProfile business object to load profile items (competencies, qualifications, work history) against each worker
• Data Cleansing: Legacy systems often have inconsistent competency names — map legacy values to the new content library taxonomy before loading. A mapping spreadsheet is essential
• Rating Conversion: If the legacy system used a different rating scale, define a conversion matrix (e.g., legacy "3 out of 4" maps to "Proficient" in Oracle)
• Validation: After load, run profile comparison reports for a sample population to confirm data accuracy

Oracle Goal Management allows organisations to set, cascade, track, and evaluate goals at the organisation, department, team, and individual worker level. It aligns individual effort with strategic business objectives.

• Organisation Goals: Strategic goals set at the company or business unit level — typically by HR or senior leadership. These are cascaded down to departments and individuals
• Individual / Worker Goals: Personal goals set by employees or their managers. They can be linked to organisation goals to demonstrate alignment
• Development Goals: Goals focused on professional growth, learning, or skill acquisition — often linked to career development plans
• Performance Goals: Goals that are evaluated during the performance review cycle and contribute to the worker's overall performance rating

• Goal Plan: A structured collection of goals for a worker for a defined time period (e.g., 2024 Annual Goals). It groups goals together, defines the review period, and tracks overall goal completion. A worker can have multiple goal plans simultaneously
• Performance Document: The formal review document used during a performance cycle. It contains sections for rating goals, competencies, and overall performance
• Relationship: When configuring a Performance Document Template, you select which Goal Plan(s) to pull goals from. At review time, the worker's goals from the linked plan automatically appear in the Goals section of their performance document — avoiding double-entry

Goal cascading is the process of pushing organisation-level strategic objectives down through the management hierarchy to align individual goals with corporate strategy.

• Top-Down Cascade: A senior leader creates an Organisation Goal (e.g., "Increase customer satisfaction score to 90% by Q4"). They cascade this to direct reports. Each recipient can then create their own supporting goal that is linked to (and inherits context from) the parent organisation goal
• Manager Cascade: Managers can push a goal directly to one or more of their direct reports' goal plans. Workers receive a notification and can accept or request modification
• Worker Self-Alignment: Workers can also manually link their personal goals to published Organisation Goals, demonstrating bottom-up alignment without a manager initiating the cascade
• Goal Alignment Tracking: HR dashboards show the percentage of workers with at least one goal aligned to strategic objectives — a key indicator of cascading success

Goal weighting allows assigning relative importance to individual goals, so that higher-priority goals contribute more to the overall goal achievement score in a performance review.

• Manual Weighting: Workers and managers manually assign a percentage weight to each goal. The sum across all goals in a plan must total 100%
• Equal Weighting: The system can be configured to auto-distribute equal weight across all goals, so if there are 5 goals, each receives 20%
• Weight Enforcement: Administrators can make weighting required (goal cannot be saved without a weight) or optional
• Section Weighting: In the Performance Document Template, the Goals section itself has a weight (e.g., 60% of overall rating). The goal weights determine the score within that section, which is then multiplied by the section weight
• Configuration Path: Setup and Maintenance → Goal Management → Manage Goal Management Business Processes to set weight options

End-to-end Goal Management setup involves:

• 1. Configure Goal Management Options: Enable/disable features such as goal sharing, goal assignment from manager, goal weights, and private goals via Manage Goal Management Business Processes
• 2. Define Goal Plan Templates: Create Goal Plan Templates specifying the plan name, review period dates, eligibility, and which goal types are allowed (performance, development, organisation)
• 3. Set Up Mass Assignment: Use Goal Plan Assignments to roll out goal plans to all eligible workers in a population (by business unit, department, or eligibility profile)
• 4. Configure Organisation Goals: Create top-level Organisation Goals and publish them so they are visible for cascading and alignment
• 5. Link to Performance: Map goal plans to Performance Document Templates so goals auto-populate in performance reviews
• 6. Set Up Notifications: Configure Bell and BPM notifications for goal assignment, cascade, completion status changes, and review period deadlines
• 7. Security: Assign Goal Management duty roles to relevant job roles (Employee, Line Manager, HR Specialist)

• Shared Goal: A goal created by one worker that is voluntarily shared with peers for visibility and collaborative alignment. Other workers can choose to add a copy of the shared goal to their own goal plan. Sharing promotes transparency but does not force adoption
• Assigned Goal: A goal pushed by a manager to a worker's goal plan. The worker typically does not have the ability to remove an assigned goal (depending on configuration). It represents a management directive about what the worker must focus on
• Key Difference: Consent and authority — shared goals are voluntary; assigned goals are mandatory directives from the management chain

• Goal Editing During Active Review: By default, workers cannot edit goals once a performance document is in progress. Administrators can configure whether goal edits are allowed, restricted, or require manager approval during the review period
• Adding New Goals Mid-Year: New goals can be added to the goal plan, and if the performance document is in the right status, they will appear in the Goals section. Configure the performance template to allow goal additions during the review period
• Recommended Approach: Define a clear "goal freeze date" in project governance — after this date, no new goals are added. For changes, use the goal Comments or Additional Information fields to document context without altering the original target
• Cancelled / Deleted Goals: Deleting a goal mid-cycle removes it from the performance review. Use status = Inactive instead of deleting to preserve the record while marking it as no longer active

Measurement attributes define how goal success will be quantified. Oracle HCM provides several options for configuring goal measurement:

• Target Completion Date: The deadline by which the goal should be achieved
• Percent Complete: A manual or calculated field showing progress (0–100%). Workers update this as they progress toward the goal
• Measurement Type: Can be Numeric (e.g., achieve 95% satisfaction score), Boolean (achieved/not achieved), or Qualitative (descriptive)
• Start Value / Target Value: Numeric goals can have a baseline start value and a target value, with progress tracked as movement between them (e.g., start: 80%, target: 95%)
• Success Criteria: Free-text description of what "done" looks like — useful for qualitative goals

• Performance Document Template Link: The Goals section of a Performance Document Template is configured to pull goals from a specified Goal Plan. When the performance cycle opens, Oracle automatically populates the Goals section with all active goals from the worker's linked plan
• Goal Rating in Performance Review: During the self-assessment and manager review steps, each goal can be rated individually. The individual ratings are then aggregated (weighted average, if weights are set) to produce a Goals Section score
• Overall Rating Calculation: The Goals Section score is combined with Competency Section scores (and other sections) using the section weights defined in the performance template to produce the final overall performance rating
• Goal Progress Visibility: Percent complete and notes entered on the goal are visible within the performance document, giving reviewers context without navigating away

• Hierarchical Goal Structure: Set global corporate goals at the enterprise level, then create sub-goals at the business unit or regional level that cascade from the corporate goal while reflecting regional priorities
• Goal Eligibility Profiles: Use eligibility profiles to control which organisation goals are visible to workers in which business units or countries. Workers in APAC should see APAC-specific strategy goals, not EMEA-specific ones
• Multiple Goal Plan Templates: Create separate goal plan templates per business unit or region if goal structures, review periods, or measurement approaches differ significantly
• Goal Categories: Use Goal Categories (custom lookup values) to tag goals by strategic theme (e.g., Customer Focus, Digital Transformation, Sustainability) enabling cross-regional reporting on category alignment
• Reporting: HR analytics dashboards can show goal alignment percentage by region, business unit, and strategic theme — giving leadership visibility on strategic execution

A Performance Document Template is the master configuration object that defines the structure, content, process, and participants of a performance review. Every performance document created for workers is based on a template.

• Sections: The content blocks that make up the review — Goals, Competencies, Overall Summary, Development Recommendations. Each section can have a weight for rating calculation
• Process Flow / Roles: Defines who participates and in what sequence — typically Self-Assessment → Manager Review → HR Review → Approval → Final Sharing
• Rating Model: The rating scale used for section and overall ratings (e.g., 1–5 scale)
• Calculation Rules: How section scores are aggregated to produce the overall rating (sum, average, weighted average)
• Questionnaires: Optional competency-based or open-ended questions added to sections
• Eligibility Profiles: Define which workers are eligible to receive a performance document based on the template

Oracle delivers several standard process flows that organisations can configure. Each flow defines the sequence of steps and responsible parties:

• Worker Self-Evaluation: Worker completes self-assessment; manager reviews and rates; manager shares final document with worker
• Manager Evaluation Only: Manager rates the worker directly without a self-assessment step — simpler flow for some organisations
• Worker and Manager Evaluation: Both complete evaluations, then a manager review step consolidates ratings before sharing
• HR Review Step: An optional HR intermediary step can be added after the manager review for HR quality checks before the document is finalised
• Skip Level Review: Configuration allows a skip-level manager (manager's manager) to review before finalisation
• Matrix Manager Review: In dotted-line structures, a matrix manager can provide input that the primary manager considers

Rating calculation in Oracle Performance Management involves two levels of weighting:

• Item-Level Weighting: Within a section (e.g., Goals), each individual goal or competency can have a weight. These are combined (typically weighted average) to produce the Section Score
• Section-Level Weighting: Each section (Goals 60%, Competencies 40%) has a weight. The section scores are multiplied by their respective weights and summed to produce the Overall Performance Score
• Calculation Method Options: Administrators choose from Sum, Average, Weighted Average, or Band-based calculation for both section and overall ratings
• Rating Rounding: The numeric score is mapped back to a rating label based on rounding rules defined in the rating model (e.g., 3.5–4.4 maps to "Exceeds Expectations")
• Manual Override: Managers can override the calculated overall rating with a manual rating accompanied by a justification comment (if enabled in the template configuration)

Performance Calibration is the process where a group of managers collectively review and normalise performance ratings to ensure consistency and fairness across teams before ratings are finalised.

• Calibration Meetings: HR admins create Calibration Meetings — sessions where a facilitator (usually HR) reviews preliminary ratings for a population of workers on a single screen
• Configuration: In the Performance Document Template, enable the Calibration step. Define who can facilitate calibration meetings and whether workers can be moved between rating levels during calibration
• Calibration View: A grid showing all workers, their managers, current rating, and any proposed changes. Facilitators can adjust ratings, add notes, and compare rating distributions
• Distribution Guidelines: Organisations can configure target rating distributions (e.g., no more than 10% should receive "Outstanding") to guide calibration discussions
• Status Flow: After calibration, performance documents move from Calibration in Progress to Manager Approved status, allowing managers to share final ratings with workers

• 1. Configure Rating Models: Create or confirm rating scales (e.g., 1–5) with descriptors for each level
• 2. Set Up Performance Document Template: Define sections (Goals, Competencies, Overall), weights, process flow, rating models, and questionnaires
• 3. Link Goal Plan: Associate the relevant Goal Plan with the Goals section of the template
• 4. Configure Eligibility Profiles: Define which workers receive this performance document (by job family, business unit, employee type)
• 5. Set Up Performance Document Batch: Use Mass Create Performance Documents to generate documents for all eligible workers simultaneously
• 6. Configure Due Dates and Notifications: Set step due dates and configure BPM/Bell notification rules for overdue reminders
• 7. Optional Calibration Setup: Enable calibration in the template; configure calibration meeting participants
• 8. Security Roles: Ensure Line Manager and Employee roles have the correct Performance Management duty roles assigned
• 9. Test End-to-End: Create test documents for sample workers, execute each step, validate calculation results

• Definition: A set of structured questions added to a Performance Document section to capture qualitative feedback. Used for open-ended performance comments, development suggestions, or 360 feedback
• Types: Single choice, multiple choice, text (short and long), rating scale, and date questions
• Configuration Path: First create the questionnaire in Setup and Maintenance → Questionnaires, then attach it to a section in the Performance Document Template
• Section Assignment: Questionnaires can be assigned to specific sections (e.g., attach a "Strengths and Development Areas" questionnaire to the Overall Summary section) and configured to appear for specific roles (worker only, manager only, or both)
• Scoring: Questions can contribute to section scores if configured with numeric weights, or they can be purely qualitative

Oracle HCM supports Continuous Performance Management (CPM) — a shift from once-a-year reviews to frequent feedback and check-ins throughout the year:

• Check-Ins: Structured conversations between worker and manager. Configure Check-In Templates with topics/questions. Workers or managers initiate check-ins from the Check-Ins work area. Frequency can be weekly, monthly, or ad hoc
• Anytime Feedback: Workers and managers can request or give feedback at any time via the Give Feedback feature. Feedback can be requested from peers, direct reports, or managers and is visible on the worker's profile
• Configuration Steps: Enable CPM features in Manage Performance Business Processes. Configure Check-In templates and which roles can initiate check-ins. Enable feedback visibility settings
• Integration with Performance Documents: Anytime feedback and check-in notes can be surfaced within the formal performance document, providing a year-round narrative for the manager review step
• Touch Points: Oracle's Touch Points feature (separate module) extends this further with structured topics and action tracking

Eligibility Profiles are rules that determine which workers qualify to receive a specific performance document. They prevent incorrect performance documents from being assigned to ineligible populations.

• Common Criteria: Employee type (full-time only, exclude contractors), job family, business unit, grade, location, hire date (exclude new hires in probation), and employment start date (minimum service period)
• Configuration: Created in Setup and Maintenance → Benefits → Manage Eligibility Profiles (reused across multiple modules), then attached to the Performance Document Template
• Evaluation: When mass-creating performance documents, Oracle evaluates each worker against the eligibility profile and only creates documents for those who qualify

• Matrix Manager Review: In the Performance Document Template process flow, add a "Participant Review" step assigned to the Matrix Manager role. The matrix manager receives a notification and provides ratings/comments that the primary manager can see before finalising
• Peer Feedback (360): Add a "Participant Feedback" step in the process flow. The worker or manager nominates peers. Each nominated peer receives an email notification with a link to submit their feedback questionnaire. The primary manager sees aggregated peer feedback before completing their review
• Configuration: In the template, set Participant Role = Peer or Matrix Manager, define whether participation is mandatory or optional, and set the due date for their step
• Anonymity: Peer feedback can be configured as anonymous (peer name hidden from worker) or attributed — a key design decision with significant cultural implications

Mass document creation failures require a structured diagnostic approach:

• Check Eligibility Profile: Run the Check Eligibility process to see which workers fail the eligibility criteria and why. Common issues: hire date too recent, wrong employee type, excluded business unit
• Assignment Manager: A worker without an active line manager assignment will not receive a performance document. Check the worker's manager assignment in Core HR
• Duplicate Documents: If a document already exists for the worker in the same period, a new one cannot be created. Check for existing documents in draft or completed status
• Process Monitor: Review the ESS (Enterprise Scheduler Service) job log for the mass creation process — it lists workers excluded with a reason code
• Employment Status: Workers on leave, or with a termination date in the performance period, may be excluded depending on template configuration
• Security: Verify the HR Specialist running mass creation has data access to the worker population via data roles and HCM data security profiles

Oracle Talent Review is a module that enables leaders and HR to conduct structured talent review meetings — assessments of their workforce population across dimensions such as performance and potential, resulting in talent classification and targeted action plans.

• Business Problem: Organisations need to identify high performers, high-potential employees, flight risks, and gaps in the talent pipeline — but this data is scattered across performance reviews, manager opinions, and informal conversations. Talent Review brings it together in a structured, data-driven process
• Key Output: Talent classification (9-box placement), identification of succession candidates, employee risk ratings (flight risk, loss impact), and follow-up development actions
• Participants: HR Business Partners, Senior Leaders, and Line Managers collectively review a population and discuss placements, supported by Oracle HCM data

The 9-box grid is a talent segmentation matrix that plots workers on two dimensions — typically Performance (X-axis) and Potential (Y-axis) — creating 9 categories that describe talent segments (e.g., "High Performer / High Potential" = Star).

• Axes: Each axis corresponds to a rating dimension. Common combinations: Performance vs Potential, Performance vs Risk of Loss, or custom dimensions defined by the organisation
• Box Labels: Each of the 9 boxes can have a custom label (e.g., "Rising Star," "Solid Contributor," "Needs Improvement") configured by the HR administrator
• Configuration Path: Setup and Maintenance → Workforce Development → Talent Review → Manage Talent Review Configuration. Define the X and Y axes, rating sources, and box labels
• Data Source: The placement of workers on the grid is pre-populated from performance ratings (linked to completed performance documents) and potential ratings (set by managers or HR)
• Manual Adjustment: During a Talent Review meeting, facilitators can drag and drop workers to different boxes to reflect discussion outcomes

• Talent Review Template: The configuration blueprint for a Talent Review meeting — it defines what data is shown, how the 9-box is configured, which actions are available, and who participates
• Box Chart Configuration: Select the X and Y axes rating models (performance, potential, risk), define box thresholds and labels
• Population: Define which workers are included — by hierarchy level, business unit, job family, or a custom population rule
• Data Columns: Select which talent data columns appear in the participant summary (e.g., performance rating, potential rating, key position indicator, retention risk, years in role)
• Available Actions: Configure which talent actions can be triggered from the meeting — nominate to succession plan, assign development goal, flag as flight risk, request job change
• Participant Roles: Define who can view the meeting data (all participants) versus who can edit placements (facilitator, HR admin)

• What is Potential: Potential is a manager's assessment of a worker's capacity for future growth, expanded responsibility, or advancement — distinct from current performance
• Where it is Set: Managers set the potential rating on the worker's talent profile or within a Talent Review meeting. It can also be a step in the performance document if configured in the template
• Rating Model: A separate rating model is configured for potential (e.g., 1-Low, 2-Moderate, 3-High) — this should be distinct from the performance rating model to avoid confusion
• Manager vs HR: Depending on configuration, potential ratings can be set only by HR (to avoid manager bias) or by the direct line manager. Some organisations use a separate calibration meeting specifically for potential ratings
• Talent Profile Display: The potential rating is visible on the worker's talent profile, alongside performance history and succession plan membership

• Action During Meeting: While reviewing the 9-box chart, the facilitator can select a worker and trigger an action — e.g., Add to Succession Plan for a specific key position, or Create Development Goal
• Succession Nomination: The nomination is immediately reflected in the Succession Plan for that position. The nominated worker appears as a candidate with their current readiness rating drawn from the Talent Review data
• Development Plan: The Assign Development Goal action creates a development goal in the worker's goal plan and optionally a development plan entry — visible to the worker and manager after the meeting is concluded
• Post-Meeting Actions: HR admins can review and finalise all proposed actions from the Talent Review Actions tab before they are committed — allowing a review buffer between the discussion and data changes going live
• Implementation Tip: Define a clear governance process for who reviews and approves Talent Review actions before they are actioned in the system — this is a sensitive process with significant HR implications

• Performance Rating: Pulled from the most recently completed performance document matching the configured source in the Talent Review Template
• Potential Rating: Pulled from the worker's talent profile (set by manager or HR prior to the meeting)
• Risk of Loss / Impact of Loss: Set on the talent profile — typically manager-assessed values updated during talent planning cycles
• Succession Plan Membership: Indicator of whether the worker is already named as a succession candidate for a key position
• Years in Role / Years at Company: Derived from Core HR assignment and hire date data
• Key Position Flag: Whether the worker currently holds a position flagged as a key/critical position

• Challenge: When regions use different rating models (e.g., EMEA uses a 4-point scale, APAC uses a 5-point scale), normalising ratings for a global Talent Review is complex
• Option 1 — Normalised Rating: Create a normalised performance rating field on the talent profile (e.g., Low/Mid/High) that HR manually assigns after reviewing actual ratings. The 9-box then uses the normalised field rather than the raw performance score
• Option 2 — Separate Templates per Region: Create separate Talent Review Templates per region — each mapped to the appropriate regional rating model. Conduct regional reviews first, then aggregate outcomes at a global leadership level
• Option 3 — Global Standardisation: As part of the implementation, harmonise on a single global performance rating model. This is the cleanest long-term solution but requires significant change management
• Implementation Recommendation: Recommend Option 3 during the design phase, with Option 2 as an interim solution if full harmonisation cannot be achieved for go-live

• Risk of Loss: A manager's assessment of how likely a worker is to leave the organisation voluntarily in the near future. Typically rated as Low, Medium, or High. Informed by factors like engagement, market demand for their skills, career trajectory, and manager relationship
• Impact of Loss: How significant the loss of this worker would be to the team or organisation if they were to leave. Also rated Low, Medium, High — based on criticality of the role, uniqueness of skills, knowledge dependencies, and succession pipeline depth
• Usage: These two fields create a "retention risk" view within Talent Review. Workers with High Risk of Loss AND High Impact of Loss are immediate retention priorities. HR can use this data to prioritise counter-offer conversations, development investments, and succession planning urgency
• Where Set: On the worker's Talent Profile, typically updated by the manager during the talent planning cycle before a Talent Review meeting

• Meeting Participant List: Only workers explicitly listed as participants in the Talent Review meeting can access meeting data. Configure the participant list carefully — typically limited to HR BPs and senior leaders
• Data Security: Oracle HCM data security profiles control which workers' talent profile data is accessible. HR Business Partners should have access only to workers in their assigned population
• Post-Meeting Data: After the meeting is concluded, box chart placements (9-box positions) are saved to the talent profile. Configure whether line managers can see their direct reports' 9-box placement — many organisations restrict this to HR only
• Audit Trail: All changes to talent profile data made during or after a Talent Review meeting are logged with a timestamp and user ID — important for GDPR compliance and audit readiness
• Worker Visibility: Explicitly ensure workers cannot see their own 9-box placement unless the organisation has made a conscious decision to share this — configure the talent profile "Hide from Worker" flags appropriately

This is a common first-year implementation challenge. The recommended approach:

• Manager Pre-Population Campaign: Before the first Talent Review meeting, HR runs a targeted campaign asking all line managers to set potential and risk ratings for their direct reports via the My Team's Talent page. Set a clear deadline 2–4 weeks before the meeting
• HR Admin Bulk Entry: For large populations, HR can use HCM Data Loader (HDL) to bulk-load manager-provided ratings into talent profiles using an Excel collection exercise
• Incomplete Data Strategy: Configure the Talent Review Template to show workers without data in a dedicated "Unassessed" section rather than excluding them — this creates visibility of gaps and encourages data completion
• Phased Rollout: Conduct the first Talent Review meeting for senior leadership population only — smaller, more data-complete. Use the meeting output to demonstrate value and build momentum for broader rollout in subsequent cycles
• Post-Meeting Enrichment: Actions agreed during the first meeting (potential assignments, succession nominations) populate the system for future cycles

Oracle Succession Management enables organisations to identify, develop, and track potential successors for key roles — ensuring business continuity when critical positions become vacant through retirement, promotion, or attrition.

• Business Value: Reduces risk of critical role vacancies, accelerates time-to-fill for key positions by having pre-identified candidates, supports employee retention by giving high-potential workers visible career pathways
• Key Objects: Key Positions (the roles being planned for), Succession Plans (the structured plan for each position), Succession Candidates (workers nominated for consideration), and Readiness Ratings (how soon the candidate could step into the role)
• Integration: Connects with Talent Review (nominations come from meetings), Career Development (development plans close readiness gaps), Performance (performance history informs candidate assessment), and Profile Management (profile comparison shows skill gaps)

• Key Position: A position or job that is deemed critical to the organisation — either due to the strategic impact of the role, the uniqueness of skills required, or the risk associated with its vacancy
• Flagging as Key: Positions are flagged as "Key Position" in Oracle HCM via the Manage Positions page in the Workforce Structures work area — simply enabling the "Key Position" toggle on the position record
• Criteria for Identification: Typically identified through an organisational risk assessment — roles where: (a) incumbent departure would have high business impact, (b) replacement timeline is long, (c) external talent market is thin, or (d) institutional knowledge is unique
• Succession Plan Trigger: Once flagged, HR can create a Succession Plan specifically for that position, naming succession candidates and tracking the pipeline depth

• Readiness Rating: An assessment of how quickly a succession candidate could move into the target role if the position became vacant today. Commonly: Ready Now, Ready in 1–2 Years, Ready in 3–5 Years
• Configuration: Readiness levels are configured as a Lookup value set in Setup and Maintenance → Common → Manage Standard Lookups → SUCCESSION_READINESS_LEVEL. Organisations can add custom levels or rename existing ones
• Assignment: When a candidate is added to a Succession Plan, their readiness rating is set by the HR admin or talent review facilitator. It should be reviewed and updated at each annual or bi-annual succession planning cycle
• Pipeline Health Metric: Organisations use readiness data to calculate "pipeline coverage" — what percentage of key positions have at least one Ready Now and one Ready in 1–2 Years candidate

• Navigate to: Succession Plans work area within the Talent module, or access via a worker's Talent Profile → Succession Plans section
• Create Plan: Select the plan type (Position-based, Job-based, or Incumbent-based), name the plan, select the target position/job, and set the plan status
• Add Candidates: Search for and add succession candidates. For each candidate, set their Readiness Rating, any development notes, and whether they are an "Interim" candidate
• Profile Comparison: Oracle automatically shows a profile gap comparison between the candidate and the target position profile — surfacing skills and competency gaps that inform development planning
• Ongoing Management: Review and update readiness ratings at least annually. Archive candidates who are no longer viable. Add new candidates identified through Talent Review meetings
• Incumbent Notification: Configure whether the current incumbent can see their succession plan (generally a sensitive decision — many organisations restrict this)

• Key Metrics: Coverage Ratio (% of key positions with at least one candidate), Bench Strength (average number of candidates per key position), Ready Now Ratio (% of candidates rated Ready Now), Diversity of Pipeline (gender, ethnicity representation in succession pools)
• Oracle HCM Analytics Workbooks: The Succession Management subject area in OTBI (Oracle Transactional Business Intelligence) provides pre-built reports on pipeline depth, readiness distribution, and candidate demographics
• Key OTBI Reports: Succession Pipeline Coverage, Candidates by Readiness Level, Key Positions Without Successors, Succession Candidate Promotion History
• Workforce Analytics (Fusion Analytics): Oracle Fusion Analytics Warehouse includes pre-built Succession dashboards with visualisations of 9-box distribution overlaid with succession plan membership
• Custom Reports: Use OTBI with the Talent Review and Succession subject areas to build executive dashboards showing succession health trends over multiple review cycles

• Position-Based Plan: The succession plan is anchored to the position or job — it persists regardless of who currently holds the role. When the incumbent changes (retirement, promotion, resignation), the succession plan remains intact and planning continuity is preserved. Recommended for most organisations
• Incumbent-Based Plan: The plan is anchored to the current person in the role. If the incumbent changes, the plan is associated with the new incumbent. Less common — used when the criticality is driven more by the person's unique expertise than the position itself
• Job-Based Plan: Similar to position-based but anchored to the Job (a broader classification) rather than a specific headcount position — useful in organisations without highly defined position management
• Recommendation: Position-based is the preferred approach as it aligns succession with the organisational structure rather than individuals, providing more stable planning continuity

• Remove Promoted Candidate: The promoted worker should be removed (or archived) as a successor on the plan they were promoted into — they are now the incumbent, not a candidate
• Review Remaining Candidates: With one candidate removed, reassess the readiness levels of remaining candidates. If the previous "Ready in 1–2 Years" candidate is now the most senior, consider updating their rating to "Ready Now"
• Add New Candidates: Triggered by the change, HR should proactively identify and add new lower-readiness candidates to maintain pipeline depth. This often connects back to the most recent Talent Review outcomes
• Former Incumbent's Position: The vacancy created by the incumbent's promotion also now needs a succession plan or its existing plan needs refreshing — triggering a cascade of succession planning updates
• System Configuration: In Oracle, the promoted worker's Assignment in Core HR is updated. The succession plan is updated manually by the HR Succession Administrator — Oracle does not auto-remove candidates on promotion

• Highly Confidential Data: Succession plans contain sensitive information — who is being groomed for leadership, who is rated high potential, who is a flight risk. Data access must be tightly controlled
• Role Access: Only HR Talent Management Specialists, HR Business Partners, and Senior Leaders should have full succession plan access. Line managers should have read-only access limited to their own direct reports' profiles
• Worker Self-Service: Workers should generally not be able to see if they are on a succession plan or their readiness rating — configure "Hide from Worker" flags on sensitive talent profile fields
• Data Security Profiles: Use HCM Data Security to restrict which HR users can see which worker populations' succession data (by business unit, department, country)
• Audit: Enable Oracle's audit framework for talent profile and succession plan changes — all modifications should be logged for GDPR and governance purposes

• Profile Gap as Input: When a worker is added to a Succession Plan, Oracle performs a profile comparison between the candidate's Person Profile and the target Position Profile, revealing competency and skill gaps
• Development Plan Creation: Based on the identified gaps, HR or the candidate's manager creates a Development Plan with specific learning activities, stretch assignments, mentoring, and development goals targeted at closing those gaps
• Development Goal Integration: Development goals in the plan are linked back to Career Development and Goal Management — ensuring they appear in the worker's goal plan and performance review
• Readiness Update Trigger: As development activities are completed and profile data is updated, the succession candidate's readiness rating is reviewed and updated — demonstrating the link between development investment and succession pipeline health
• Oracle Learning: Learning recommendations can be surfaced directly on the Development Plan, auto-suggesting courses mapped to the competency gaps identified

• Phase 1 — Foundation (Month 1–3): Identify key positions (workshop with CHRO and business leaders), configure the succession module, set up position profiles with required competencies, run manager training on talent profile data entry
• Phase 2 — Data Population (Month 2–4): Managers complete potential and risk ratings for their teams. HR loads historical performance data. Conduct first Talent Review meeting for senior leadership to identify initial succession candidates
• Phase 3 — Plan Creation (Month 3–5): HR creates succession plans for all identified key positions, adds candidates from Talent Review outputs, establishes readiness ratings based on profile comparisons
• Phase 4 — Development Alignment (Month 4–6): For each succession candidate, create a development plan tied to identified competency gaps. Link to Oracle Learning where available
• Phase 5 — Operating Rhythm: Establish bi-annual succession review cycle, train HR BPs on maintenance, set up OTBI pipeline health dashboards for leadership review

Oracle Career Development (part of Oracle HCM Talent Management) helps workers explore career paths, identify development needs, and build actionable plans to achieve their career aspirations within the organisation.

• Development Plans: Structured plans containing development goals, learning activities, mentoring, stretch assignments, and target completion dates — owned by the worker with manager and HR visibility
• Career Path Exploration: Workers can explore defined career paths (lateral, vertical, or cross-functional moves) and see the skills and competencies required for roles along those paths
• Role Exploration: Workers can explore any job in the organisation, compare their current profile against the job profile, and identify gaps to address
• Career Preferences: Workers set career preferences (willingness to relocate, target job family, desired management level) that inform internal mobility and succession targeting
• Mentoring: Oracle supports mentoring relationship management within Career Development — workers can search for and connect with mentors based on skills and experience

• Development Plan: A holistic career development document that outlines a worker's long-term growth journey. It contains development goals, learning activities, mentoring connections, stretch assignments, and notes about the worker's career aspirations. Typically spans 12–36 months and is career-focused
• Goal Plan: A structured collection of performance or operational goals for a defined review period (usually 12 months). Goals in a Goal Plan feed into the performance review and are evaluated for compensation and rating purposes
• Key Difference: Goal Plans are primarily performance-accountability tools tied to the review cycle. Development Plans are growth-focused, longer-horizon documents not directly evaluated in performance ratings (though development goals can be surfaced in reviews as evidence of investment in growth)
• Integration: Development goals created in a Development Plan can be linked to Goal Plans, allowing them to appear in performance reviews if the organisation values development alongside performance

• Career Paths: Pre-defined sequences of jobs or positions representing typical growth trajectories within the organisation. For example: Analyst → Senior Analyst → Manager → Senior Manager → Director
• Configuration: Navigate to Setup and Maintenance → Workforce Development → Career Development → Manage Career Path. Define the path name, description, and sequence of jobs/positions in the path
• Lateral Paths: Career paths can also define lateral moves — e.g., a Finance Analyst can move to a Business Operations Analyst role as a horizontal development step
• Visibility: Workers see career paths relevant to their current job in the Career Development work area. They can select a target role on the path and immediately see a profile comparison showing current gaps
• Job Profile Dependency: Career paths rely on well-defined Job Profiles. If job profiles are incomplete, the gap analysis shown on the career path will not be meaningful

• Career Preferences: Self-declared data workers enter on their profile expressing their career aspirations and constraints — e.g., target job family, target geography, willingness to travel, desired level (individual contributor vs management), short/long-term career goal narrative
• Where Stored: On the worker's Person Profile in the Career Development section — visible to the worker, their manager, and HR
• Internal Mobility Use: HR and hiring managers can search the talent pool for workers who have expressed interest in a particular job family or location when filling internal positions — supporting internal first hiring strategies
• Succession Integration: Career preferences feed into succession planning by enabling HR to identify workers who aspire to leadership roles — a natural source of succession candidates
• Manager Conversations: Career preferences are designed to be shared with managers to enable honest career conversations. Managers can see their direct reports' preferences and use them to guide development assignments

• Design Principle 1 — Worker Ownership: Development plans must be worker-owned, not HR-imposed. The system should make it easy and rewarding for workers to invest time in their own plan
• Career Path Library: Build a comprehensive library of career paths across all major job families — minimum 2–3 paths per job family covering vertical and lateral options. Invest time in the job profile content library
• Manager Enablement: Train managers to have regular career conversations using the Development Plan as a discussion guide — not just an annual checkbox. Integrate with Touch Points for quarterly career check-ins
• Learning Integration: Connect Oracle Learning to the development plan — when a worker adds a development goal related to a skill gap, recommend specific courses automatically via Oracle Learning Recommendations
• Internal Mobility Programme: Use career preference data to power an internal talent marketplace — workers with the right preferences and profile are matched to internal opportunities before external recruiting
• KPIs: Measure development plan completion rate, promotion from within rate, internal mobility rate, and compare engagement survey scores between workers with active development plans vs those without

• Mentoring Programmes: HR can create structured Mentoring Programmes in Oracle — defining the programme objectives, duration, eligibility criteria for mentors and mentees, and matching approach (self-select, admin-matched, or system-suggested)
• Mentor Profiles: Experienced employees register as mentors, listing their areas of expertise. The system surfaces potential mentors to workers based on skills alignment with the mentee's development goals
• Programme Management: HR tracks programme enrolments, active relationships, and completion. Automated notifications support regular check-in cadences between mentor and mentee
• Development Plan Integration: A mentoring relationship can be added directly to a worker's Development Plan as a development activity, with the mentor name, programme, and notes recorded
• Configuration Path: Career Development → Manage Mentoring Programs in Setup and Maintenance

• Skill Gap → Learning Recommendation: When a worker identifies a target role and sees a competency gap on their Career Development page, Oracle Learning Recommendations (powered by AI) surfaces relevant courses, certifications, and resources mapped to that competency
• Development Goal → Learning Enrollment: A development goal can include a specific learning activity. Workers can click through from the development plan directly to the Oracle Learning catalog to enroll in the recommended course
• Completion Writeback: When a worker completes a learning activity tied to a competency, the completion can be configured to automatically update the relevant competency proficiency level on the worker's talent profile — closing the feedback loop between learning and profile
• Oracle Grow: Oracle's Grow feature provides a unified career development experience where learning, skills, and career exploration converge — workers see personalised recommendations combining career path suggestions with directly relevant learning content
• Implementation Tip: Map Oracle Learning catalog items to competencies and skills in the content library. This metadata is what enables accurate cross-module recommendations

• Explore Roles: A self-service feature in the Career Development work area that allows workers to browse any job in the organisation's job catalog, not just those on their defined career path
• Profile Comparison: When a worker selects a role to explore, Oracle immediately shows a side-by-side comparison of the worker's current profile against the job profile — highlighting strengths (matching competencies) and gaps (required competencies the worker has not yet developed)
• Add to Development Plan: From the Explore Roles view, workers can add the explored role as a career goal and auto-generate development goals for the identified gaps — directly in their development plan
• Internal Job Postings: Workers can also see if there are currently open internal job postings for the explored role and apply directly

• View and Comment: Managers can view their direct reports' development plans in the My Team work area and add comments on individual development goals
• Add Development Goals: Managers can add development goals to a worker's development plan — useful when a manager identifies a specific growth area during a performance review or career conversation
• Approve Development Activities: In some configurations, manager approval is required before certain development activities (e.g., external training with a cost, stretch assignment to another team) are added to the plan
• Progress Reviews: The development plan is a natural agenda item in Touch Points and regular 1:1 meetings — Oracle's Touch Points module provides a dedicated space for reviewing development plan progress in the context of a structured conversation
• HR Visibility: HR Business Partners can also view development plans across their worker population to identify development investment patterns and gaps at the team or department level

• Career Preferences as Talent Pool Data: Ensure all workers are prompted to complete career preferences. This data becomes searchable by HR for internal talent sourcing when positions open
• Skills Visibility: Configure Dynamic Skills to populate worker skill profiles automatically (from LinkedIn, project history, learning completions). Richer skill data improves internal matching accuracy
• Internal Posting Strategy: Configure Oracle Recruiting to post all or a defined set of roles internally first for a set period (e.g., 2 weeks internal-only before external posting)
• OTBI Talent Pool Searches: HR can run OTBI queries against the talent pool — e.g., "workers in Finance with expressed interest in Operations and proficiency in data analytics" to source internal candidates before recruiters open external searches
• Gigs / Short-Term Projects: Oracle Workforce Management supports gig assignments — short-term projects that workers can sign up for, allowing cross-functional development while meeting business needs. Link these to development plans to formalise the learning intent

Oracle Touch Points is a structured conversation management tool within Oracle HCM that facilitates regular, meaningful check-ins between managers and their direct reports — beyond the formal annual performance review.

• Business Need: Research consistently shows that employees who have regular career and development conversations with their manager are more engaged and less likely to leave. Traditional annual reviews are too infrequent to support continuous development and feedback
• Key Features: Structured conversation topics, shared agendas, action tracking, conversation history, integration with performance and career development, and reporting on conversation frequency
• Who Uses It: Both managers and workers initiate and participate in Touch Points. Either party can create a Touch Point, add topics, and log notes from the conversation
• Oracle HCM Positioning: Touch Points is part of Oracle's Continuous Performance Management (CPM) strategy — enabling more frequent feedback loops to complement formal review cycles

• Touch Point Topics: Pre-defined conversation subjects that appear on the Touch Point agenda. They guide managers and workers in having structured, purposeful conversations rather than open-ended catch-ups
• Standard Topics (Oracle Delivered): My Goals, My Development, Well-Being, Recognition, Feedback, Workload and Priorities, Career Aspirations
• Custom Topics: HR Administrators can create organisation-specific topics that reflect the company's culture and priorities — e.g., "Team Collaboration," "Innovation Ideas," "Safety and Wellbeing"
• Configuration Path: Setup and Maintenance → Workforce Development → Performance Management → Manage Touch Point Topics
• Topic Assignment: Topics can be made available globally or targeted to specific populations. Mandatory topics can be configured to always appear on Touch Points
• Integration: When the "My Goals" topic is selected, the worker's active goals are surfaced directly in the Touch Point interface for review — eliminating context switching

• Initiation: Either the manager or the worker can create a Touch Point from the Touch Points work area or from the My Team page (manager view). A date and optional topics are set when creating
• Pre-Conversation: Both parties can add notes, questions, and topics to the shared agenda before the meeting — enabling preparation and ensuring neither party arrives unprepared
• During Conversation: Notes can be added in real time against each topic during the meeting using a mobile or desktop browser. The interface is lightweight and mobile-friendly for this use case
• Post-Conversation: Actions and follow-ups are logged and assigned to either party with due dates. The Touch Point status changes to "Completed" when both parties are satisfied
• Action Tracking: Actions created in Touch Points have a distinct tracking list. Both manager and worker receive reminders for outstanding actions via Bell notifications
• History: All completed Touch Points are stored in history — accessible to the worker and manager, and to HR for audit and reporting

• Goals Integration: When a worker adds the "My Goals" topic to a Touch Point, their active goal plan goals are automatically displayed within the Touch Point interface. Progress updates and notes from the conversation are stored with the touch point, not on the goal — maintaining a clean separation of conversation records from performance data
• Performance Document Context: When managers complete the formal performance review, they can reference Touch Point history to provide evidence-based, year-round feedback rather than relying on recent memory. The performance template can display a summary of Touch Point frequency and topics discussed
• Feedback Aggregation: Notes from Touch Points contribute to the "anytime feedback" record visible during performance reviews — providing longitudinal evidence of the worker's performance and development throughout the year
• Development Plan: Development plan items can be reviewed in Touch Points via the "My Development" topic — tracking progress on development goals and learning activities in the context of a manager conversation

• OTBI Subject Area: Touch Points data is available in the Workforce Management — Performance Real Time subject area in OTBI. HR can build reports on Touch Point frequency by manager, department, or business unit
• Key Metrics: Average Touch Points per worker per quarter, % of workforce with at least one Touch Point in the last 30/60/90 days, average time between Touch Points, most frequently discussed topics, outstanding action completion rate
• Manager Effectiveness Indicator: Touch Point frequency is a proxy for manager engagement behaviour. HR BPs can identify managers with low conversation frequency and target coaching interventions or training
• Correlation Analysis: When combined with engagement survey data and attrition data, Touch Point frequency can be correlated with employee engagement scores and flight risk — demonstrating the ROI of regular conversations
• HR Dashboard: Build an executive HR dashboard showing conversation health metrics alongside performance rating quality and development plan completion rates as part of a Talent Health scorecard

• 1. Enable Feature: Ensure the Touch Points feature is enabled in Setup and Maintenance → Workforce Development → Performance Management → Manage Performance Business Processes
• 2. Configure Topics: Review and customise Touch Point Topics to align with the organisation's conversation culture. Add any company-specific topics
• 3. Assign Security Roles: Ensure the Employee and Line Manager abstract roles include the appropriate Touch Points duty roles — Use Performance Management as Worker and Use Performance Management as Manager
• 4. Notification Configuration: Set up BPM or Bell notifications for Touch Point creation, upcoming due Touch Points, and outstanding action reminders
• 5. Manager Training: Develop manager guidance materials on how to use Touch Points effectively — the technology is simple; the culture shift requires change management
• 6. Communication: Include Touch Points in the go-live communications plan. Workers and managers need to understand the expectation around frequency and purpose

• Shared Nature of Touch Points: By design, Touch Points are a shared space — both the worker and manager can see the topics, notes, and actions. This transparency is intentional, reinforcing trust and accountability
• Private Notes: Oracle Touch Points supports a concept of private notes — notes the manager adds that are visible only to themselves and HR but not to the worker. These might include sensitive observations about performance concerns or succession considerations
• HR Access: HR Business Partners and HR Specialists with the appropriate data access can view Touch Point records for workers in their population — providing oversight and supporting HR BP conversations with managers
• Configuration Decision: During implementation, confirm with the client whether private notes should be enabled and who has access. This is a change management decision as much as a configuration one — worker trust is essential for Touch Points adoption

• Leadership Sponsorship: The shift to continuous conversations requires visible executive sponsorship. HR must position Touch Points as a leadership priority, not just a new system feature
• Manager Training: Run targeted training sessions — not on how to use the technology (which is simple), but on how to have effective career and development conversations. Provide conversation guides and talking points for each Touch Point topic
• Set Clear Expectations: Define an organisational standard (e.g., "all managers should hold at least one Touch Point per month with each direct report") and communicate this in HR policy
• Gamification / Recognition: Surface manager conversation frequency in HR dashboards visible to HR BPs and managers' own managers — peer pressure and visibility drive behaviour change
• Integrate with Performance Review: Make Touch Point history a required reference in the performance review process — managers who have no Touch Point history have less evidence for their review comments, creating a natural pull
• Phased Rollout: Start with voluntary adoption among engaged managers, build visible success stories, then gradually escalate expectation levels across the broader manager population

• Action Creation: During or after a Touch Point, either party can create an Action — a specific follow-up task with an owner (manager or worker), description, and target completion date
• Action Types: Actions can include things like "Complete the data analysis training by end of quarter," "Manager to arrange introduction to the Strategy team," or "Review job posting for Senior Analyst role"
• Tracking: Actions appear in a dedicated My Actions list accessible from the Touch Points work area. Status updates (in progress, completed) are recorded and visible to both parties
• Notifications: Reminders are sent to the action owner as the due date approaches. Overdue actions trigger an escalation notification
• Carry Forward: Incomplete actions from one Touch Point can be carried forward to the next session's agenda automatically — preventing important commitments from falling through the cracks

• Visibility of Wellbeing: The Well-Being topic in Touch Points gives managers a structured prompt to check in on employee wellbeing — catching early signs of disengagement, burnout, or dissatisfaction before they become retention risks
• Career Conversations: The Career Aspirations topic allows workers to express career goals in a safe, documented space. Managers who actively engage with these aspirations and connect them to development opportunities significantly reduce voluntary attrition among high-potential employees
• Recognition: The Recognition topic creates a habit of regular positive reinforcement — one of the most cost-effective retention tools available to managers
• Early Intervention: Touch Point history, combined with risk of loss ratings updated in Talent Review, gives HR a rich picture of at-risk employees — enabling targeted retention interventions before resignation
• Psychological Safety: Regular Touch Points, when conducted well, build trust between manager and worker — creating an environment where issues are surfaced early rather than festering into disengagement

Oracle Dynamic Skills (also referred to as Oracle Fusion Skills or Oracle Skills Cloud) is Oracle's AI-powered, continuously updated skills intelligence layer within Oracle HCM Cloud. It represents a significant evolution beyond the traditional static content library in Profile Management.

• Traditional Profile Management: Uses a fixed, manually maintained content library of skills and competencies. HR administrators manually add, update, and curate skills. The library reflects what HR has defined, not necessarily the full skills reality of the workforce
• Dynamic Skills: Uses machine learning to automatically infer skills from workers' work history, job titles, learning completions, project participation, and even connected external profiles (like LinkedIn). The system dynamically suggests skills workers likely possess — reducing the burden on workers to self-declare every skill
• Oracle-Maintained Taxonomy: Oracle maintains a global skills taxonomy (drawing from labour market data, O*NET, and industry sources) that is continuously updated as the skills landscape evolves — without requiring HR to manually add emerging skills
• Skills Everywhere: Dynamic Skills powers skill inference across Recruiting, Learning, Career Development, Succession, and Talent Review from a single skills graph

• Skills Taxonomy: A structured, hierarchical catalogue of skills — organised by skill clusters, domains, and individual skills — with defined relationships between related skills. For example, "Data Analysis" is related to "Python," "Statistics," and "SQL"
• Importance: Without a common taxonomy, different people use different words for the same skill (e.g., "ML," "Machine Learning," "Predictive Modelling"). A taxonomy normalises language so skills comparisons, gap analysis, and talent searches produce accurate results
• Oracle's Taxonomy: Oracle provides and continuously maintains a comprehensive global taxonomy integrated into Dynamic Skills — organisations don't need to build their own from scratch. They can extend it with organisation-specific skills where needed
• Skills-Based Organisation: A skills-based organisation deploys talent based on skills rather than just job titles and hierarchies. A rich, accurate taxonomy is the data foundation that makes this possible

Oracle's AI models analyse multiple data sources to generate skill inferences for each worker:

• Job Title and History: The worker's current and past job titles, as stored in Oracle Core HR, are analysed. A worker with a job title of "Data Scientist" is likely to have skills in Python, R, Machine Learning, and Statistical Modelling based on the skills taxonomy
• Learning Completions: Courses completed in Oracle Learning are mapped to skills. Completing a "Project Management Fundamentals" course infers the "Project Planning" and "Risk Management" skills
• Education: Academic qualifications on the profile (e.g., MBA, Computer Science degree) are linked to associated skills clusters
• LinkedIn Integration: With worker consent, Oracle can connect to the worker's LinkedIn profile to import endorsements, certifications, and work experience — enriching the inferred skills profile significantly
• Worker Confirmation: Inferred skills are presented to workers for confirmation. Workers can accept, reject, or add proficiency levels to inferred skills. This human-in-the-loop validation improves data quality

• Mechanism: Oracle's AI compares a worker's Dynamic Skills profile (their confirmed and inferred skills) against the skills requirements embedded in open job postings and career path roles across the organisation
• Match Score: A skills match percentage is calculated — showing the worker which internal roles best align with their existing skills. High-match roles are surfaced as personalised recommendations in the worker's Career Development and Oracle Grow pages
• Adjacent Roles: The AI also recommends "stretch" roles where the worker has 70–85% of required skills — making visible growth opportunities that might not be obvious from job title alone
• Recruiter Use: Internal recruiters can also use Dynamic Skills to proactively identify internal workers who match open job requisitions — powering a true internal talent marketplace before external sourcing is initiated
• Configuration: Ensure job profiles for all key roles have skills populated (via the Dynamic Skills content library) and that requisitions in Oracle Recruiting are linked to these job profiles for the matching to function effectively

• 1. Enable Oracle Skills Cloud Feature: In Setup and Maintenance → Workforce Development → Skills Cloud → Enable Skills Cloud. This activates the Oracle-maintained skills taxonomy and inference engine
• 2. Configure Skills Library: Review and, where necessary, extend Oracle's taxonomy with organisation-specific skills. Map existing custom skills from the legacy content library to the Oracle taxonomy where possible
• 3. Enable Worker Skills Profile: Configure the worker Skills Profile (distinct from the traditional talent profile) — this is the new skills-focused view that aggregates inferred and confirmed skills. Set which sections are visible to workers, managers, and HR
• 4. Configure Skill Inference Rules: Define which data sources are enabled for inference — job history, learning completions, education. Optionally enable LinkedIn integration if the organisation supports it
• 5. Job Profile Skills Mapping: Ensure all key job profiles have their skills requirements populated using the Oracle Skills taxonomy — this is the target data that powers gap analysis and job recommendations
• 6. Learning Catalog Tagging: Work with the Learning team to tag all learning catalog items with relevant skills. This enables learning completions to contribute to the skills profile
• 7. Worker Communication: Launch a campaign to encourage workers to review and confirm their inferred skills profiles — data quality improves significantly with worker validation

• Job Requisition Skills: When creating a job requisition in Oracle Recruiting, the recruiter links the requisition to a Job Profile. The Job Profile's skills requirements (from the Skills taxonomy) are inherited by the requisition and form the basis for candidate matching
• Candidate Skills Parsing: When external candidates apply and upload a CV/resume, Oracle's AI parses the document and extracts skills — mapping them to the Oracle taxonomy. The candidate's skills profile is built from the parsed resume
• Match Score: Oracle calculates a skills match score between each candidate's extracted skills and the job's required skills — surfacing the best-matched candidates at the top of the recruiter's review queue
• Internal Candidates: Internal candidates already have richer skills profiles (from Dynamic Skills inference). Their match scores are more accurate and comprehensive than external candidates whose profile is limited to their resume content
• Diversity Considerations: Skills-based matching reduces the influence of educational pedigree and company name — potentially improving diversity in hiring pipelines by focusing on demonstrated skills over credentials

• Workforce Skills Inventory: Aggregate view of all confirmed and inferred skills across the workforce — enabling HR to answer: "How many workers have data analytics skills? How many have cloud architecture expertise?"
• Future Skills Analysis: Compare the current workforce skills profile against the skills required for the organisation's strategic direction (identified in job profiles for future roles). The delta is the organisation-level skill gap
• Strategic Workforce Planning: Dynamic Skills data feeds Oracle's Strategic Workforce Planning module — projecting skill supply and demand over 3–5 year planning horizons, informing build/buy/borrow decisions (develop internally, recruit externally, or contract for skills)
• Learning Investment Prioritisation: When skill gaps are identified at scale (e.g., "60% of the Finance team lacks Python skills which will be required for future finance digitalisation"), HR can commission targeted learning programmes through Oracle Learning
• OTBI Reporting: The Skills subject area in OTBI enables workforce skills heat maps — showing skill concentration and gap by department, geography, or job family

• Oracle Grow: A personalised career and learning experience for workers within Oracle HCM. It serves as a unified landing page that combines skills development, career exploration, and learning recommendations in a consumer-grade, engaging interface
• Dynamic Skills Integration: Oracle Grow is powered by Dynamic Skills. A worker's skills profile (inferred and confirmed) drives the personalised recommendations shown on the Grow homepage — relevant roles to explore, skills to develop, and courses to take
• Features: Personalised role recommendations based on skills match, skill gap visualisation for target roles, curated learning suggestions from Oracle Learning, career path navigation, and skills confirmation prompts
• Worker Experience: Grow transforms what was a manual process (worker navigates to Profile → Career Development → Learning separately) into a single, AI-guided experience — significantly improving adoption and engagement with talent development
• Implementation Note: Oracle Grow requires Dynamic Skills to be enabled. Implementations that skip Dynamic Skills will not benefit from the personalised intelligence in the Grow experience

• Skills Nexus: An analytical view within Oracle HCM that provides an aggregated, visual map of the organisation's skills landscape — showing the distribution of skills across the workforce, skill concentrations, and critical skill gaps
• Use Cases: HR leaders can use Skills Nexus to identify where critical skills are concentrated (e.g., a key technology skill held by only 2 workers — a risk), visualise skill trends over time as the workforce evolves, and compare skill supply against demand from open requisitions and strategic plans
• Input Data: Skills Nexus is fed by Dynamic Skills profiles — both inferred and worker-confirmed skills. Data quality directly impacts the reliability of the analytics
• Strategic Decisions: When combined with headcount and attrition data, Skills Nexus informs build/buy/borrow decisions at an organisational level

• Step 1 — Audit Legacy Framework: Inventory all existing competencies, skills, and ratings in the legacy system. Identify which are actively used vs. legacy unused items
• Step 2 — Map to Oracle Taxonomy: For each legacy skill/competency, attempt to map it to an equivalent item in Oracle's Dynamic Skills taxonomy. Document unmapped items for custom extension
• Step 3 — Rationalise: Use the mapping exercise as an opportunity to retire outdated competencies. Modern skills-based frameworks typically have fewer, more outcome-focused items than legacy competency frameworks built over decades
• Step 4 — Stakeholder Validation: Present the mapped skills framework to business leaders, HRBPs, and L&D — validate that the taxonomy covers the organisation's strategic capability requirements
• Step 5 — Parallel Run: Run Dynamic Skills in inference mode for a pilot population alongside the legacy framework for one cycle — compare inferred skills against legacy self-declared data to calibrate accuracy
• Step 6 — Full Migration: Load historical profile data using HDL (mapping legacy items to the new taxonomy). Activate Dynamic Skills inference for all workers. Decommission legacy content library maintenance
• Change Management: Workers and managers will see a different skills vocabulary. Communication and training on the new framework is critical for adoption

Oracle HCM Talent Management modules are designed as an integrated ecosystem, not standalone tools. A high-potential employee's journey illustrates the integration:

• Profile Management stores the foundation — skills, competencies, qualifications. Dynamic Skills continuously enriches this profile via AI inference
• Goal Management sets the performance objectives for the year, linked to organisation strategy via cascaded goals
• Performance Management evaluates achievement of goals and competency behaviours — resulting in a performance rating that populates the talent profile
• Touch Points provide ongoing conversation context throughout the year — capturing feedback, development progress, and wellbeing signals that enrich the performance narrative
• Talent Review uses performance and potential data to place the worker on the 9-box grid and identify them as a succession candidate
• Succession Management captures the nomination, shows profile gaps vs. the target role, and triggers development planning
• Career Development builds a development plan to close the profile gaps identified in succession, powered by Oracle Learning recommendations from the Dynamic Skills engine
• Dynamic Skills underpins all of the above — ensuring skills data is current, AI-enriched, and drives intelligent recommendations across every touchpoint

• Employee (Abstract Role): Includes duty roles for self-service talent — View Own Profile, Manage Own Development Plan, View Own Goals, Complete Own Performance Document self-assessment, initiate Touch Points
• Line Manager (Abstract Role): Adds duties for managing team talent — View Direct Reports' Profiles, Manage Team Goals, Complete Manager Review Steps, Access Team Touch Points, View Succession Plans for team
• HR Specialist / Talent Management Specialist: Full access to configure and manage Talent processes for their HR data security population — mass create performance documents, manage succession plans, run OTBI talent reports
• Human Capital Management Application Administrator: Full setup and maintenance access — configure Profile Types, Performance Templates, Goal Plans, Succession, Career Paths, Dynamic Skills settings
• Data Security: HCM Data Security Profiles restrict which worker population each HR role can access — critical for Talent Review and Succession where data confidentiality is paramount

• Cross-Module Usage: The same eligibility profile framework is reused across Performance Management (which workers get a review), Goal Management (which workers get a goal plan), and Succession Management (which workers can be succession candidates)
• Common Criteria: Employee type (Exclude Contingent Workers), Business Unit, Job Family, Grade, Location, Years of Service (minimum 6 months for performance review), Employment Status (Active only), Work Relationship (Primary Assignment only)
• Combination Logic: Multiple criteria in a profile use AND logic (worker must meet ALL criteria). Multiple profiles on the same template use OR logic (worker must meet at least one profile to be eligible)
• Testing: Always use Check Eligibility on a sample of workers before running mass processes. Common errors: workers on leave incorrectly excluded, probationers incorrectly included in annual review

• OTBI (Oracle Transactional Business Intelligence): The real-time reporting and analytics tool embedded in Oracle HCM Cloud. Provides pre-built and custom reporting across all HCM modules without requiring a separate data warehouse
• Key Subject Areas for Talent:
  • Workforce Management — Performance Real Time — performance document data, ratings, step completion
  • Workforce Management — Goal Management Real Time — goal plans, individual goals, alignment, completion
  • Workforce Management — Succession Management Real Time — succession plans, candidates, readiness levels
  • Workforce Management — Talent Profile Real Time — competencies, skills, education, certifications
  • Workforce Management — Career Development Real Time — development plans, goals, mentoring
• Common Talent Reports: Performance Rating Distribution by Department, Goal Completion Rate, Succession Pipeline Coverage, High Potential vs High Performance Grid, Development Plan Completion Trend

• HCM Data Loader (HDL): Oracle's bulk data loading tool for HCM Cloud — used to create, update, or delete large volumes of HR data using structured data files (DAT files in a ZIP archive) submitted via the HCM Data Loader work area
• Talent Management Use Cases: Loading Person Profile items (competencies, skills, certifications) from legacy systems, bulk-loading potential and risk ratings for the workforce, loading historical performance ratings, creating Goal Plan assignments in bulk, populating succession plan candidates
• Alternative — HCM Spreadsheet Data Loader (HSDL): For smaller volumes, HSDL provides an Excel-based interface to upload talent data without needing to construct DAT files — useful for HR admin-led data entry exercises
• Key Consideration: Always test HDL loads in a non-production environment first. Validate record counts, error reports, and data accuracy on a sample before running full loads

• Oracle Journeys: A guided experience framework in Oracle HCM that presents workers with step-by-step task checklists for significant HR processes — onboarding, role changes, returning from leave, development reviews
• Talent Management Integration: Journeys can be configured to guide workers and managers through talent processes — e.g., an "Annual Performance Review" Journey that walks the worker through completing their self-assessment, reviewing goals, updating their talent profile, and confirming their career preferences before the formal review window opens
• Configuration: Create Journey templates in My Journeys → Manage Journeys. Add checklist steps — each step can link to a specific HCM page, a questionnaire, an external resource, or a notification
• Value: Reduces the volume of employee queries to HR during talent review cycles by providing clear, guided instructions. Particularly effective for new managers experiencing their first performance review cycle

• Stakeholder Mapping: Identify all impacted groups — employees, managers, HR BPs, senior leaders, payroll (if merit pay is connected). Understand their current pain points and motivations for adoption
• Leadership Alignment: Talent Management only succeeds with visible leadership commitment. Secure executive sponsorship and ensure senior leaders are trained and actively using the system before broad rollout
• Communication Plan: Develop a communication plan for each phase — what is changing, why, how it affects each group, and what actions are required. Use multiple channels (email, intranet, team meetings)
• Training Strategy: Role-based training — employees, managers, and HR each have different workflows. Avoid one-size-fits-all training. Use Oracle's built-in guided learning aids (in-app help, tours) to supplement formal training
• Super User Network: Identify and train a network of Talent Management super users in each business unit — they become the first point of contact for process queries post-go-live, reducing HR admin support burden
• Phased Rollout: For global implementations, phase the rollout geographically or by business unit — lessons from Phase 1 improve Phase 2 delivery significantly

• Talent Profile (Traditional): The comprehensive profile built in Profile Management containing structured content sections — Competencies, Qualifications, Education, Work History, Languages, Certifications. Data is manually entered or HDL-loaded into a fixed content library structure. Used across Performance, Succession, and Career Development
• Skills Profile (Dynamic Skills / Oracle Grow): A newer, AI-enriched view of the worker's skills — populated via inference from job history, learning, and external sources, and confirmed by the worker. Uses the Oracle Skills taxonomy. Powers Oracle Grow, intelligent job recommendations, and skills-based matching in Recruiting
• Relationship: The two profiles co-exist in current Oracle HCM implementations. Oracle's strategic direction is to converge toward a unified skills-based profile powered by Dynamic Skills. Implementations should plan for both in the near term while positioning the skills profile as the long-term direction
• Recommendation: Enable both — use the Talent Profile for structured competency evaluations in Performance and Succession, and use the Skills Profile (Dynamic Skills) for intelligent recommendations and skills analytics

• Oracle HCM Behaviour: When a worker's manager changes in Core HR (a new Assignment Supervisor record), the ownership of in-progress performance documents does not automatically transfer to the new manager. The document remains with the original manager unless action is taken
• Transfer Document: HR Admins use the Transfer Performance Document process to reassign the document to the new manager. This is available in the Performance Administration work area
• Split Review Option: Some organisations configure a split review — the original manager completes a partial review for the period they managed the worker, and the new manager reviews the remaining period. Oracle supports this via the Mid-Period Review step
• Proactive Communication: Establish a process where HR is notified of mid-cycle transfers and immediately triggers document reassignment. Delays cause confusion and missed deadlines
• Goals Consideration: Goals created under the previous manager remain on the goal plan. The new manager should review these goals with the worker and adjust targets or remove obsolete goals if the role focus has changed

• Sensitive Talent Data: Potential ratings, 9-box placements, risk of loss, succession nominations, and performance ratings are all potentially sensitive personal data under GDPR — requiring a lawful basis for processing (typically legitimate interest or employment contract)
• Data Minimisation: Collect only the talent data that is genuinely needed. Avoid creating custom content types that capture sensitive personal information (e.g., health, family situation) in talent profiles
• Retention Policies: Configure Oracle HCM's data retention rules to align with retention policies — historical performance ratings from more than 5 years ago may need to be purged in some jurisdictions
• Worker Rights: Under GDPR, workers have the right to access their personal data. Oracle's self-service tools largely satisfy this — workers can view their own profiles, performance documents, and goals. For hidden data (9-box, succession), a formal HR process should be defined for subject access requests
• Audit Trail: Enable Oracle Audit on talent profile, performance, and succession data. GDPR requires demonstrating that data has been processed lawfully — audit logs support this
• Third Parties: If using Dynamic Skills LinkedIn integration, ensure the consent mechanism is GDPR-compliant — worker consent must be freely given, informed, and revocable

• Oracle HCM Environments: Oracle Cloud typically provides multiple environments — Development (DEV), Test/UAT, and Production (PROD). Configurations are built in lower environments, tested, and then promoted to Production
• Configuration Promotion: For Setup and Maintenance configurations (profile types, performance templates, goal plans), Oracle provides two main promotion mechanisms: (1) Manual re-entry in Production following a tested DEV configuration, or (2) Configuration Set export/import for supported objects
• Oracle Sandbox: Oracle HCM includes a Sandbox environment for Application Composer and Flex Field customisations — changes made in the sandbox are tested without affecting production, then published
• Release Management: Oracle HCM Cloud is updated quarterly. New features are released to lower environments first, giving customers time to test before the production update
• Change Control: All talent configuration changes in production should follow a change control process — documented, approved, tested in UAT, and deployed with rollback plans

• Fast Formulas: Oracle's proprietary formula language used to create custom business rules and calculations without coding. They are used across many HCM modules for configuration-level logic
• Talent Management Usage: Eligibility profiles for performance documents can use Fast Formulas to express complex eligibility rules (e.g., exclude workers where hire date is within 90 days of review period end). Goal plan assignment processes can use Fast Formulas to determine the correct plan for a worker based on multiple criteria. Performance rating calculation rules can use formulas for custom weighted calculations
• Usage Limitation: Fast Formulas in Talent are less common than in Compensation or Benefits — most talent configuration needs are met through the standard configuration UI. They are needed primarily for complex eligibility or custom calculation scenarios

• Multiple Performance Templates: Oracle supports multiple performance document templates — one per business unit, employee category, or process type if needed. This allows each population to have their own sections, weighting, and process flow while using the same underlying system
• Template Rationalisation: However, excessive templates create maintenance burden. During design, challenge requirements that seem to demand different templates. Often, 80% of differences can be handled through configuration within a common template (e.g., optional sections, conditional competency display using profile subscriber rules)
• Common Rating Model: Even if process flows differ, use a single, globally consistent rating model across all templates. This enables cross-business-unit performance comparison in calibration and talent review
• Governance: Establish a centralised HR COE that owns template management. Without governance, multiple business units request their own templates over time — leading to fragmentation and reporting complexity
• Recommended Design: Start with 2–3 template variants (Senior Leadership, Management, Individual Contributors) rather than one-per-BU. Differences within IC or management populations are typically smaller than stakeholders initially believe

• Performance Rating → Merit Increase: The most common integration. A worker's final overall performance rating from the performance document is passed to the Oracle Compensation merit increase process. The compensation matrix (merit grid) uses the performance rating to suggest a pay increase range
• Potential Rating → Long-Term Incentive: High-potential ratings from Talent Review can inform long-term incentive (LTI) eligibility in Oracle Compensation — ensuring high-potential employees receive appropriate retention incentives
• Succession Candidate → Compensation Review: Succession plan membership can flag workers for special compensation review — ensuring compensation is competitive to retain the succession pipeline
• Configuration: In Oracle Compensation, performance rating levels from the shared rating model are mapped to merit increase ranges on the compensation plan. The performance data must be finalised before the compensation cycle opens
• Timing: A common implementation issue is the performance cycle not completing before the compensation cycle opens. Design both timelines collaboratively and build buffer

• Mistake 1 — Replicating Legacy Complexity: Clients want to replicate their existing 50-page paper performance appraisal form. Avoid — use Oracle's implementation to simplify and modernise. Push back with data on what drives performance quality
• Mistake 2 — Poor Profile Data Quality: Launching Talent Review or Succession without ensuring profile data (potential ratings, competencies) is populated. Result: an empty 9-box chart. Fix: run a data population sprint before the first meeting
• Mistake 3 — Misaligned Dates: Goal plan dates not matching performance document evaluation period. Goals don't pull through to the review. Fix: validate date alignment in UAT before go-live
• Mistake 4 — Insufficient Manager Training: Managers see the technology as additional admin burden. Fix: invest in manager conversation training, not just system training. Show them what value they gain
• Mistake 5 — Ignoring Dynamic Skills: Implementing talent management without enabling Dynamic Skills — missing the AI intelligence layer. Fix: include Dynamic Skills as a core module, not a Phase 2 nice-to-have
• Mistake 6 — No Governance Model: Multiple teams requesting template changes post-go-live, leading to template sprawl. Fix: establish a Talent COE with change control process from Day 1

• My Team: A manager-specific dashboard in Oracle HCM that provides a single-pane view of all talent data for direct reports — an essential productivity tool for managers during talent management cycles
• Talent Cards: Each direct report has a Talent Card on the My Team page showing key talent data at a glance: current performance rating, potential rating, key position indicator, succession plan membership, years in role, and risk of loss
• Quick Actions: From My Team, managers can directly access pending performance documents, view team goals, initiate Touch Points, view development plans, and access the team's talent profile data without navigating to separate modules
• Aggregate View: Managers can see their team's performance rating distribution, goal completion rate, and Touch Point frequency — enabling data-driven talent conversations with their own manager or HR BP

• Bell Notifications: In-app notifications that appear in the Oracle HCM notification bell icon. Triggered by system events — performance document created, goal assigned, Touch Point action due, succession candidate added
• Email Notifications: Email alerts sent to participants for key events and deadlines. Managed via Oracle's BPM (Business Process Management) Workflow notification framework or Oracle Notifications (newer approach)
• Reminder Notifications: Configurable reminders sent N days before a due date (e.g., "Your self-assessment is due in 5 days"). Frequency and timing are configured in the process setup
• Configuration: BPM notifications are configured via BPM Worklist → Notification Preferences. Bell notifications are configured within the relevant module's business process setup. Some notifications use Oracle Journeys notification framework for Talent-specific events
• Best Practice: Over-notification leads to notification fatigue. Design a deliberate notification strategy — key milestones only, not every minor status change. Test notification content and timing in UAT to ensure messages are clear and actionable

A sample annual Talent Management calendar:

• January: Goal Plans assigned to all workers. Workers set individual goals (aligned to cascaded organisation goals). Touch Points cadence established for the year
• January–September: Ongoing quarterly Touch Points. Goal progress updates. Anytime feedback. Mid-year check-in (optional mid-year performance review for some populations)
• September–October: Potential and Risk ratings updated by managers on talent profiles. Preparation for Talent Review meetings
• October: Annual Talent Review meetings — 9-box placement, succession nominations, actions logged. High-potential workers identified for succession plans and development investments
• November: Performance document self-assessment period opens. Workers complete self-assessment. Development plans reviewed and updated
• November–December: Manager review step. Calibration sessions. Performance ratings finalised
• December: Final performance ratings shared with workers. Succession plans updated based on review outcomes. Development plans finalised for the new year
• January (Next Year): New goal plans cycle begins. Compensation cycle uses finalised performance ratings for merit decisions

• Oracle Grow: Unified personalised career and skills development experience powered by Dynamic Skills and AI — a significant UX improvement over the traditional career development pages
• Skills-Based Organisation Features: Enhanced skills inference, skills-based job matching in Recruiting, and skills-based Talent Review views are being progressively enhanced across quarterly releases
• AI-Assisted Performance Writing: Oracle HCM now includes AI writing assistance for performance review comments — helping managers write more structured, behaviour-based feedback. A significant adoption driver for less confident managers
• Continuous Listening / Pulsing: Integration between Oracle HCM and Oracle Surveys (via Oracle ME) allows pulse survey data to be surfaced alongside talent data in manager dashboards
• Oracle Touchpoints Enhancement: Continued improvements to the Touch Points interface, including richer action tracking and tighter integration with performance document history
• HCM Communicate: Targeted communications tool allowing HR to send talent-related communications to specific workforce segments — useful for driving awareness during talent review and performance cycles

A successful Talent Management implementation is measured across adoption, process quality, and business outcomes:

• Adoption KPIs: % of workers with active goal plan (target: 95%+), % of performance documents completed on time (target: 90%+), % of workers with at least one Touch Point in last 90 days (target: 80%+), talent profile completion score (target: 70%+ complete)
• Quality KPIs: Performance rating distribution vs. calibration targets (bell curve health), % of goals rated as "Achieved" or above, feedback quality score (length and specificity of review comments — can be analysed via AI tools)
• Pipeline KPIs: Succession coverage ratio (% of key positions with at least 2 candidates), % of succession candidates with an active development plan, bench strength (avg. candidates per key position)
• Business Outcome KPIs: Internal promotion rate (% of vacancies filled internally), voluntary attrition rate for high-potential employees, time-to-fill for key positions, correlation between performance ratings and business unit performance
• Skills KPIs: % of workforce with a validated Dynamic Skills profile, rate of skill gap closure for identified critical skills, reduction in external hiring spend as internal mobility increases