Piloting end-to-end UX process for IT staff on intranet

27 Jan 2012 - 9:10am
2 years ago
3 replies
1399 reads
digikev
2009

I have been asked the question today

Will completing an end-to-end UX process for IT staff on the proposed intranet as an initial pilot cause any detriment to future user-centred design on the system?

This is an enterprise intranet and it has been estimated that there will be around 10 processes that will take place. It will have transaction points that will include the following:

  • Business process management
    For instance document approval or inventory tracking — which can be set up to pull together processes, people, services, information and systems into a single application that helps drive business. Then, what's been built can be used like building blocks to assemble new applications
  • Integration with SharePoint file management
  • Search configuration
  • Knowledge base
  • Records management
  • CMS integration
  • Line of business (LOB) integration

To your knowledge, are you aware of any issues that could occur in first doing an end-to-end user-centred process for IT staff (we can safely say these will be power users) as a pilot before looking at the process for other staff?

Please share your experiences and outcomes.

Comments

27 Jan 2012 - 11:21am
bdore
2010

Hi,

in my experience no, it wont affect your research process later on if you keep things in prespective.

I have done some intranet work and whenever the interest (objectives, tasks, think broadly) of different user groups conflicted with one another I had two measures to decide what to do:

- Which group is the end client? IT usually is a service provider inside corporations so even if they have whatever reason to disagree with your findings you should optimize your solution to the area being served, not the contrary.

- Which problem left unsolved will have the biggest impact (time, money) down the process? Sometimes the IT effort is so big its just not worth going against it.

 Based on these two points I would decide which path to take.

[]'s

27 Jan 2012 - 12:07pm
digikev
2009

Okay, pleased to hear that it sounds like there was some miscommunication here, even after I relayed the question back to the team for clarification. We have just plotted the project out in high-level along a gantt chart and in actual fact, the first people that the new intranet will be released to will be the IT staff for feedback. However, the design and usability testing of wireframes/prototype will still have been done prior to, or in conjunction with this release to the IT staff.

 

The reworded question

Will releasing a new intranet to IT staff before all other users be detrimental to future user groups?

To your knowledge, are you aware of any issues that could occur in releasing the intranet to IT staff before any other user group? UX design processes and usability testing will have/be taking place on prototypes for the other user groups.

27 Jan 2012 - 1:47pm
bdore
2010

I've never done this sort of sleective release myself but I guess it would be detrimental in a personal satisfaction way: "Why does IT get to use it before I do"? You may claim a "system stabilization" phase...why not.. ;)

If you do the research part right, consulting every stakeholder in the project, I dont think the intranet itself will suffer with a selective release.

Syndicate content Get the feed