Build the PX Capabilities Your 2027 Priorities Need
“What will your team need to deliver in 2027, and do you have the PX skills and capabilities to make it happen?”
Your 2027 plan might include improving onboarding, simplifying employee services, or helping managers navigate a major change. Each priority comes with work to do and expectations to meet.
As planning conversations turn to resources, you face a practical question: what will your team need to deliver?
You might need training, access to a researcher or designer, or a dedicated role. You might already have capable people whose time is committed elsewhere. Choosing the right request starts with understanding the work, the skills it requires, and what is available to you.
People Experience draws on similar disciplines established in customer experience, user experience, service design, and product management. These provide practical ways to understand people's needs, design better experiences, deliver improvements, and assess whether they work.
For PX leaders, the planning task is to connect those capabilities to a priority that matters. That connection makes it easier to identify a meaningful gap and explain why closing it deserves support.
1. Identify the skills your priority requires
Start with a specific people journey or outcome. “Improve onboarding” gives you a direction. “Help new employees get the access, information, and manager support they need to begin contributing” gives you a clearer basis for deciding what work is required.
Consider this example onboarding situation. New employees receive plenty of information, but essential tech access arrives late, instructions conflict, and managers are unsure what they need to do. A communications refresh may help with part of the experience. Understanding and improving the whole journey requires several kinds of work.
Research and synthesis: understand what new employees and managers experience, compare perspectives with operational evidence, and identify where the problems arise.
UX and UI design: make employee-facing tools easier to navigate and use, with clear interactions, accessible interfaces, and testing with employees.
Content design: help employees find, understand, and act on the information they need through clear language, useful structure, and consistent guidance across channels.
Service and experience design: connect employee needs with the processes, systems, policies, content, and handoffs behind the end-to-end journey.
Journey and product management: establish ownership, decide what to address first, coordinate a roadmap, and manage improvements over time.
Iterative, agile delivery: work with the relevant teams to pilot changes, gather feedback, and refine them before developing and testing possible improvements.
Measurement: establish what to observe before and after a change, including employee effort, operational performance, and progress toward the intended outcome.
Digital, data, and AI fluency also matter where the work involves technology or automated services. PX leaders need enough understanding to work effectively with specialists, ask useful questions, and recognize when additional expertise is required.
Use this as a starting point for a focused conversation. What must happen to deliver your priority? Which skills will that work require? Who needs working knowledge, who needs to apply a method, and where do you need specialist depth?
The answer should reflect the complexity of the work. A small content improvement and a global journey redesign will need different combinations of expertise and support.
2. Inventory the capability you can actually use
Once you know what the work requires, look across your organization for the people who could help deliver it.
Expertise may sit in PX, CX, digital product teams, Data & Analytics, IT, HR Tech, Communications, Marketing, Branding, or another function. A useful inventory makes that expertise visible and tests whether it is available for your priority.
For each important task, ask:
Who can do this work, and what have they demonstrated?
How much time can they realistically commit, and when?
What tools, information, employee access, or specialist support will they need?
Who can approve changes and resolve dependencies?
Look at practical evidence. A completed course indicates learning, while a piece of applied work helps you understand how someone uses that learning. Ask a researcher about a study they designed, a journey owner about a prioritization decision, or a practitioner about a prototype they tested and changed.
In the example onboarding situation, you might discover that an internal research team can help, but has no capacity until the next quarter. HR colleagues may understand journey mapping yet need support to translate findings into service changes. IT may own access provisioning, while nobody has agreed who can resolve delays across the whole journey.
Those findings suggest different responses. You could negotiate research time, arrange coaching on an active project, and secure a sponsor for cross-functional decisions. Sending everyone to the same course would leave some of those constraints unresolved.
Focus the inventory on the gaps that most affect your priority. Consider the consequence of leaving each gap open, how soon it matters, and whether another team already has a workable solution. In a global organization, also check where regional needs or local requirements change the support needed.
The result should be a clear account of what is missing and why it matters to delivery. That is the foundation for your resource request.
3. Make a specific request to close the gap
With the gap defined, compare three practical routes: upskill, borrow or partner, and hire. A combination may be appropriate.
Upskill when the work will recur and developing existing people is a credible option. Include applied practice, coaching, feedback, and time to learn. Be explicit about what people should be able to do afterward and where they will use the skill.
Borrow or partner when you can access expertise from another internal team or bring in specialist support for a defined need. Agree the scope, availability, responsibilities, and handoff. If you need to sustain the work internally, include knowledge transfer in the arrangement.
Hire when recurring demand, required depth, and the need for continuity justify a dedicated role. Define the work and accountability first, then the role. Make clear which partners and decision rights the person will need to be effective.
Compare the options against urgency, available capacity, cost, recurring demand, and the capability you want to retain. Internal support still requires somebody's time. External support needs an internal owner. A new hire needs the conditions to do useful work.
Then frame a request stakeholders can act on:
Priority: What people and business outcomes are we trying to improve?
Gap: What capability or delivery constraint is limiting progress, and what evidence supports that diagnosis?
Recommendation: Which response do we propose, and why does it fit better than the alternatives?
Commitment: What time, funding, access, ownership, or sponsorship do we need?
Proof and trade-off: What will we review to judge progress, and what is the consequence of deferring the request?
For the onboarding example, the initial request could be a defined allocation of researcher and service designer time, participation from HR and IT, and a sponsor who can resolve cross-functional issues. The team would establish the current experience, test a targeted improvement, and review evidence before deciding whether to extend the commitment.
Keep the expected benefit credible. Explain how the work could improve access readiness, reduce employee effort, or support manager follow-through. Agree the measures with the people who own the relevant data and decisions. Avoid promising a retention or productivity result you cannot yet substantiate.
You can begin with one important priority and a focused request. Identify the work, establish the capability you can use, and make the gap clear enough for stakeholders to decide what support to provide. From there you can scale the approach to cover multiple priorities or a broader PX strategy.
That gives capability investment a concrete purpose: enabling your team to deliver the work that matters in 2027.
If you'd like help identifying the capabilities your priorities require or developing them through applied learning and coaching, let’s talk.
At Impact PX, we help organizations shift from process-led HR to product-led People Experience. Our team of former global heads of People Experience has successfully built and led PX transformations in complex, enterprise organizations. If you’re exploring this shift or want to assess your current maturity, we can help you take the next step with clarity and confidence.
…about proven ways to build or integrate PX Skills & Capabilities into your HR strategy and operating model.