IT departments can be great places to get experience as a project manager. Much business change involves an element of technology and that’s why I’ve written in the past about there being no such thing as an IT project.

Projects with an IT element are wide-ranging. Any kind of software refresh, upgrade, app development, new functionality and so on involves a broad group of stakeholders. The group that often gets forgotten is the IT Helpdesk.

You might know them as the Service Desk, the Technical Support Centre, Tech Services, IT Support or something else but they are the people who are responsible for dealing with user queries when something isn’t working with your computers. The log your problem and fix it if they can, passing it off to another specialist team if they can’t do it themselves.

They are the people who will be fielding calls from the users of any IT application or system that you are putting in. They need to know the basics of your project so they can better respond to queries. Ideally, they need to know everything possible about it so they aren’t just logging calls, they are solving the problem there and then, on the call.

Why You Need the IT Helpdesk on Your Project

You might have done a fantastic job as the project manager during the project, involving everyone, setting up training, using your communications plan to inform and educate your stakeholders and end users. That effort stops when you leave the project.

For projects with an IT element, the IT bits will be picked up by an operational team. You should be involving them in the project life cycle, from solution design to delivery and all the bits in between, but they won’t be the first line support for your end users.

If you want your project to be a success longer term, you need the IT Helpdesk on side. If you want users to embrace the IT changes and get the most out of the system you poured months of your life into delivering, you need the IT Helpdesk.

You need them to understand, be sympathetic, fix problems and maintain credibility in the system by helping users to get back up and running again as quickly as possible when they hit an issue.

Here are 5 tips for working effectively with the IT Helpdesk on your project.

1. Involve Them Early

Don’t wait until you are at the point of handover to operations during the Closure phase of your project to involve the IT helpdesk.

Start talking to them as early as you can so that you are building up their knowledge and awareness of what is coming their way. Scale up their involvement over time. Ideally, by the end of the project they should be able to lead on many of the productionising elements, or at least be very directive about the best way to approach the handover.

The graph below shows how this can work in practice.

2. Get A Single Point of Contact

This doesn’t need to be the helpdesk manager. You could work with a helpdesk analyst as the single point of contact. This person is the workstream lead for introducing the project’s deliverables to the support environment.

Having one person to go to makes sense as you don’t know exactly what is going to be involved. It’s a good opportunity for IT helpdesk staff members to see how projects work and for them to get a taste of what goes into making a new service ready for launch.

3. Delegate Planning

Once you have identified (or the helpdesk manager has identified) the right person to lead their involvement in the project, you can delegate the planning of their tasks and engagement to that person.

This is the same as you would do for any other workstream leader. Your workstream leader should establish the IT helpdesk responsibilities as they relate to the project. They can plan this out with their colleagues and, of course, you can be there to help as you would with other team members.

4. Plan The Go Live

Plan the launch of your new IT solution together. There are two aspects to this: the go live of the actual deliverable, which is likely to be supported by the project team from Day 1, and the go live of the IT helpdesk process whereby users are asked to stop calling the project team and to route queries to the helpdesk instead.

You might have it set up smoothly enough to have both those happening on the same day, but often you’ll want to transition into support gradually, for example if you have a pilot period running. The support offered from the helpdesk during the pilot could look different to the role you expect them to play longer term.

Either way, make sure that you are involving your helpdesk colleagues in the go live planning. At the very least, the helpdesk needs to know your go live milestones in case any calls come through to them that are about your project.

Even if users aren’t supposed to be ringing them yet, you can guarantee that someone won’t have got the memo. Don’t make your helpdesk team look stupid by not giving them information they need to respond to the basic queries.

5. Don’t Walk Away Too Soon

Now that you’ve invested so much time into making your handover so smooth it’s tempting to bail out of the project as soon as you can. Your aim should be to walk away, but not before you are confident that everything is working as expected and that the operational team can manage without your involvement. So don’t walk away the day after go live.

This takes some planning because your manager or the PMO team might be keen to pull you off that piece of work as soon as the last milestone is hit and onto a new project.

Make sure that you’ve put ‘transition into live service’ or something similar in your project plan and it is baked into your schedule. You might not need all the time you’ve allocated if the IT helpdesk transition is smooth (which is should be, if you’ve invested time and effort into making it successful up to this point). In that case, you can step away earlier.