Homepages

People who use enterprise software have the benefit of powerful tools to do their work... often more powerful than they need. They often use small pieces of several different applications. Accessing the information in each of those applications is cumbersome and time consuming, not to mention that the information sits isolated within each separate application. 

The idea of a homepage is not new. Summary views of application information have been around for years. What is new is bringing data from distinct enterprise software applications into one place, enabling that data to be displayed in new and insightful ways, and presenting it in a cohesive interface that enables people to configure the content exactly how they want it.  

My Role
System concept, design direction, design guideline document, content strategy training

CONTENT ECOSYSTEM

The first part of this project for me was thinking about the system mechanics from a conceptual standpoint. What would it take to enable a user to benefit from an extensibility tool like this, and how can it scale at both ends of the system (content creation and consumption). The diagram above is the design I initially created. In the end, this is essentially how it works.

JOBS TO BE DONE

We framed up the three primary "modes" in which people would be using content on homepages as: managing, acting, and monitoring. For example, managing information, items, and performance would involve a proactive way of working, so  would need to enable people to anticipate what would need to be done. 

We designed homepages to be responsive. Widgets can be designed and developed at various widths, and users can resize and reorder on the page to fit their needs and preference.