Knowledge Management is a never-ending process; continuous development in your organisation means the knowledge base must be constantly updated with new information. It's important to regularly measure the health of your knowledge base. How do you do this?
As probably everyone knows by now, there's been an ever-growing interest in Self-Service and automation the last few years. And that's great! It has a ton of benefits for Service Desk. But some questions still arise: Does it create new work? Will it take away my work? I want to address a few concerns:
Research shows happy employees lead to happy customers. And happy customers lead to increased revenue. So how do you keep your fellow employees happy?
New responsibilities and dozens of new faces at the same time: a first day can be quite overwhelming. As part of the HR team (or another Service Department), you play a big role in onboarding. With the right preparation you can quickly create a homely environment for a new colleague.
Want to exceed your customer’s expectations yet again in 2018? Take one step back. Create a sound foundation by taking away all obstacles your customers might have. How? With Workforce Enablement.
Who owns the Knowledge Base at your Service Desk? The politically correct answer is probably “it’s a joint effort”. But in real life, isn't the Knowledge Manager the one doing most of the writing, editing and publishing? This happens quite a lot, it's not optimal, and this is what to do about it.
Better Knowledge Management is incredibly important to improving your Service Delivery and Customer Satisfaction.
So, you want to set some targets for your department. But where do you start? You’ve done some research and everybody who is anybody seems to be saying that KPIs are the way to go. But what exactly are KPIs, what can they do for you - and perhaps more importantly, what can’t they do?
I recently visited the IT department of an educational institution to advise them about their contract management. Three months later they’d saved one million euros for the coming two years. Just on IT contracts. And guess what? It wasn’t even that hard.
Introducing an agile way of working means a culture shift at your IT department. Some embrace the change, others might not be so eager to change the way they work. What reactions can you expect from your IT employees? And how do you deal with these reactions?
Page 1 of 11
