November 30, 2011
by Max Davis-Johnson
Over a month ago I did a “Max’s Minute” video blog on “Three Keys to Roadmap Success.” As I said in the video, I want to dive deeper into the three keys, or “pillars,” for Roadmap success. I am going to discuss the second pillar here – The Unified Web Experience, or “UWE.”
What is the Unified Web Experience?
The UWE is a unified, individualized web experience for students, faculty, and staff. The UWE will know who you are, and will display information (including personal data) that is relevant to you.
The UWE will be an iterative project with additional features and functionality constantly being added. The UWE will provide academic information and administrative services for students, faculty and staff. It will be a one-stop shop for your University web (and mobile) experience.
The Student UWE Experience
Students will access their class information, BroncoMail apps, tasks, University announcements, and more in the UWE environment. They’ll find information specific to the courses in which they are enrolled, to-do items, or any holds requiring attention. Students will also see quick links for the Library, Career Services, the Office of the Registrar, tutoring services, technical support, and many other essential student services.
Employee UWE Experience
Faculty and staff will quickly and easily access their HR, financial, and research information, and make use of dashboards, reports, and University-related workflow.
You will sign in to the UWE with your BroncoWeb username and password. You should only have to log in once to access all your services, information, and data. The intent is to have a robust, consistent, and individualized web and mobile experience while accessing Boise State online services and information.
The UWE Design
Intuitive and clean navigation following effective web design principles are all part of the overarching objectives of the UWE design, along with web accessibility. Focused user experience testing and feedback will be a big part of the implementation process.
Key design principles include:
- Don’t make users think – get rid of the question marks; get rid of the decisions users need to make consciously, considering pros, cons and alternatives.
- Focus user attention – understand screen real estate and what attracts attention to the human eye.
- Expose features cleanly – let users clearly see what functions are available.
- Strive for simplicity – remember, users are looking for information despite the design.
- Consistency is our friend – it reduces the learning curve and gains user confidence and trust.
- Test early, test often – by the actual proposed users, providing critical insights into usability.
Amazonification
Not all these features and functions will be available initially, but will evolve over time. We will adapt a concept called amazonification. Ever notice when Amazon rolls out a new release or version? The answer is “NO.” But when you do go there, you see new features all the time. There are constant adjustments to user navigation, dynamic content, and more. That is what we need to do. Keep adding. Keep improving. Our web (and mobile) experience needs to be a continuous cycle of improvement. It needs to be flexible, individualized, dynamic, and relevant.
Most of the students, faculty, and staff will access and interact with enterprise systems and data by using the individualized Unified Web Experience. In a couple of years, the UWE will be a big piece of the perception of how well we did on the Roadmap Project. The UWE is fundamental, it is key, and it is core to the success of the Roadmap.
- Max
Public and private comments are welcomed and encouraged. Please comment on the blog posts or email me at maxdavis-johnson@boisestate.edu.
The Roadmap Project is more than just updating our enterprise systems – HR/Payroll, Financials, and Student. We will be: implementing a research administration system to support our rapidly growing research mission; expanding our data warehouse and business intelligence use; developing an individualized unified web experience; evaluating our basic accounting structure – the chart of accounts (COA) – to better align HR/Payroll, Financials, and growing Research needs; evaluating and implementing operational and organizational best practices for both technology and functional processes; improving and streamlining identity management and security; and, expanding and improving document management. We will also be putting in place the University policies, practices, and governance necessary to advance, sustain, and support enterprise systems.