Public

Key Business Problems and Trends

Below is a list of common business problems faced during the implementation of these customers:

Change resistant

These customers can be change-resistant and not open to best practices. Processes are often embedded deeply into the organization over long periods of time. This brings opportunity for "quick wins", however, the organisations will need to be won over before they will consider such changes.

Cross-business awareness

Many Government and University customers will operate in a centralized model, however, this often means there is a disconnect between teams. HR will often feel in a tug-of-war with the rest of the organisation, having to cater for the stakeholder expectations and hiring manager needs. Likewise, it can be difficult to gain constructive input from the wider business as each department or faculty may have their own 'process'.

Technology

These customers are not always tech-savvy, and due to the technology used in-house, there can be issues with browser capability to support our software. This also means they may not be able to access the resources that Professional Services use throughout the project implementation. It is also important to confirm if there would be any firewalls which could prevent subpages within PageUp from loading, we recommend whitelisting all URLs ending in pageuppeople.com to ensure the software is optimised.

Project Considerations

The following list covers areas that should be considered ahead of an implementation:

Culture

When working with these customers, it is important to understand their culture, the key drivers and constraints unique to the specific organisation, and finally, understand how they want to work to ensure cohesiveness between PageUp and the client. Some Government or University customers, for instance, are excited for the simplification that technology will bring and may appreciate best practice guidance and challenging of their current processes. Other customers, however, have strict project oversight and change management procedures and hence would prefer a more subtle approach to process improvement.

Rollout

Customers in this industry often consider "pilot" launches before releasing the system. Commence these discussions early on in the project to ensure adequate communication is given to relevant stakeholders.

Stakeholders

Ensure the right stakeholders are engaged from the start of these projects, i.e Marketing and IT. Due to the nature of the industry, engaging these teams can take time and push out project time frames.

Time frames

Making decisions is a slow process due to the structure. Ensure an extra 20% is added to the time frame for these customers.

Features and Configuration

The following points cover common features and functionality commonly used by Government and University customers:

• Application Forms: Often include flags, rules, and scoring to simplify the screening process.
• Approvals: These often include many steps (some up to 10!) for compliance purposes.
• Booking and Events: Governments and Universities often enjoy the simplification of the interview booking process - a big improvement over paper-based processes.
• Competencies: These are often included as part of the Job Description, but can also be used within the Panel functionality within the Job Card for Selection Criteria purposes.
• Panel/Search Committee: Often used to review applicants in bulk for compliance purposes.
• Reporting: Usually important for compliance purposes. University customers in the USA, for instance, need to produce an Equal Opportunity report for all recruitment activities.