I have been asked the question today
Will releasing a new intranet to IT staff before all other users be detrimental to future user groups?
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 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.
Please share your experiences and outcomes.
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.
I have rephrased the question above.