Building IT Portals – what have we learned?

I was honored to lead a roundtable discussion at HDI Minnesota yesterday. Topics ranged from hiring practices to career paths for agents. Very involved discussion with a ton of experience and leaders in the room.

I loved being there and listening.

The topic I was ‘leading’ (which means asking questions) was on IT portals. Mostly every support team had a portal along with the challenges exist that have always existed.

However, I think our industry and software in general has come a long way to understanding the shortcomings of portals, adoption and experience.

I started off the session by asking who had a portal. And some hands flopped around uncomfortably. Maybe they don’t think their portals are good enough to call them portals.

One leader offered up his story about using Sharepoint as a portal and what that meant to the sharepoint service (when we upgrade we have some issues with our portal).

Several people noted that posting critical information on the portal was a huge win for both communication and contact avoidance.

Someone else noted that Knowledgebase access was a great feature to have (totally agree) – and went on to shock me that they even allow a forum feature for people to simply discuss anything (very innovative IMHO).

Then I asked the difficult question “what do your customers think about it?”  – – crickets.

“I don’t want another password” is what one end user cited for not using the portal.

Over the next weeks I will outline some of the heavy topics involved in department portals. I’m not going to focus on IT though, because I believe this is a challenge that all many-to-one relationships have. Meaning that any department, team, group, organization, or organization can learn from other groups’ failures and challenges to build an app to improve interaction, collaboration, service, and experience.

Subscribe in the right-hand margin to follow along ->

Or follow us on twitter to read as they are posted.

Leave a Reply

Your email address will not be published. Required fields are marked *