ntoll.org

(Everything I say is false...)
home | about | articles | presentations | cv | contact

The World's Easiest Candidate Management System

Thursday 02 November 2006 (03:48PM)

The Economist magazine recently contained a survey of current trends in the Human Resources (HR) field. One article, "Everybody's doing it", examined how companies organise and manage "talent". The authors explained that "[c]ompanies are also trying to give their people-managers better tools" and that "the market [for talent-management technology] will nearly double by 2009." They make it explicit that companies of all sizes are focusing more resources on attracting, retaining and managing "talent".

Why is this interesting? Well, for the past twelve months I have been contracted to produce bespoke vacancy / applicant management systems. My impression of this market (as a technologist on the inside) is that the products on offer are overly complex, difficult to use, expensive and cumbersome. Informal conversations with various HR professionals confirm this opinion.

So an opportunity presents itself: there exists a relatively large yet growing market, serviced by immature or inappropriate applications that users don't feel meet their needs.

As a result I'm going to develop a web-based candidate management system that is:

The desire for simplicity and elegance should come as no surprise to those who are familiar with my development philosophy. However, it is important to understand that simplicity does not mean lacking in features. Rather, that the most useful features are easy to use and do exactly what the user expects in a well presented manner.

Simplicity also brings about ease of use and the need for little (if any) training. There is nothing worse than an unintuitive application that requires an incomprehensible manual and various training days (when users should be getting on with ‘real' work).

That companies won't have to pay for training will save money. That the application will be web-based means there won't be distribution costs. That updates and patches will be applied instantly means there won't be expensive re-deployments. That the software will be delivered as a service means customers will only pay for it when it is required.

Simplicity also leads to agility and adaptability. Most companies have very different recruitment processes – yet these all derive from two simple generic processes; the standard funnel and reverse funnel. Implementing only these processes in a flexible way means that customers build upon the application's features rather than battle against them. In other words, the system is designed so users can extend and define their own requirements for the recruitment process.

So without further ado, let me introduce…

TalentTool.com

TalentTool.com is a tool for managing talent (where "talent" represents potential candidates and the ".com" identifies it as a web-based application). The name is also the project's customer facing web-site.

TalentTool.com will organise and manage the various important pieces of information required for recruiting candidates by utilising the two most common processes for recruitment: the afore mentioned standard funnel and reverse funnel.

Standard Funnel

A specific need is identified and a vacancy is created with matching requirements. The cohort of applicants is reduced in size by a series of generic filtering processes until a final candidate is chosen. The need is considered fulfilled when the final candidate is placed in role.

The filtering processes are usually of the following three types falling in the following order:

  1. Shortlisting – involves filtering the raw application forms / CVs against the vacancy's requirements.
  2. Assessment – in the form of tests and other means of measuring performance against the vacancy's requirements.
  3. Interview – where candidates are invited for face-to-face assessment and possible trial work activities matching the vacancy's requirements.

Reverse Funnel

HR professionals pro-actively recruit candidates with in-demand skill-sets that are required to meet an anticipated need or match general roles or specific current positions. Candidates are:

  1. Profiled – usually by examining experience, qualifications, career interests and availability.
  2. Interviewed – often using a structured format or general behavioural model.
  3. Assessed – in the form of tests and other means of measuring performance against their profiled skills.

If successful, a list of roles that the candidate is interested in and qualified to fulfil is drawn up.

If they are interested in immediate work then they are matched to current vacancies. If they show an interest in career development then further analysis is undertaken and a training curriculum devised to meet the mutual needs and goals of the company and candidate.

Information

The two most important types of information that a candidate management system is concerned with relate to vacancies and candidates.

Vacancy Information

In addition to the job-title, description of duties, location and salary/benefits package a vacancy will have the following details associated with it:

Candidate Information

Candidates obviously have personal and contact information. In addition, the following details provide a fuller picture of their capabilites:

Conclusion

The essence of TalentTool.com is to match candidates and vacancies by utilising one of the two "tunnel" processes in the simplest and most elegant way possible.

What measure do I use to know that I am developing a tool that will be a success? Well, the root of the application's success depends on how easy and useful the end users find it.

As a result, the primary concerns during the development process are the needs of the user and their interaction with the application. To them the user interface (UI) is the application. It enables how the user usefully uses the capabilities of the system. It is also the part of the system that projects elegance and simplicity. With this in mind, the roadmap for developing this application involves the following steps:

  1. Initial requirements analysis – complete and summarised above.
  2. Application mock-up and testing – the creation of easily modifiable screen-shots organised as a "story board" of the application. Feedback sought from target users and a focus group of interested parties.
  3. Development / Testing cycle – using the final version of the Application mock-ups as the basis of the technical specification. Throughout this stage development will be shared with the focus group so feed back and changes can be implemented.
  4. Beta-testing – feedback sought from target users after "real-world" usage. No new features to be added at this stage (project to be branched into development and release versions).
  5. Release and maintenance cycle of version one.
  6. Development of version two to integrate most popular requested features.

In addition to the above steps, a business plan that encompasses the marketing strategy, costs and pricing structure will need writing. I'll deal with that aspect of the project in a future article.