About Project

Since it’s inception in 2004 the MyStoreNet portal has grown organically and in an uncontrolled manner despite the attempts by the Store Communications team and Boots IT stakeholders. The aim was to have better information architecture for the MyStoreNet application. This was a consultancy piece of work engaging with the various Boots stakeholders to produce usability findings and report and a series of potential mock-ups providing industry best practice and recommendations.

Research / Design

VIew Details

  •   1.Research
  •   2.Design
  •   3.Develop
  •   4.Deliver

1 - The findings from my user research indicate a time consuming and confusing experience which falls short of the necessary productive gains expected when MyStoreNet was initially launched in 2004. It is difficult to create an engaging front-end, when the back-end management is a painstaking process that is not flexible or robust enough to support the knowledge management required in an organisation such as boots.

A review of the current feature-set and/or existing implementation is, therefore, a necessity for the correct implementation and use of the current or future MyStoreNet Extranet System. If the problem lies on the system, which has been rendered obsolete since its implementation in 2004; alternatives should be sought in order for Boots to position MyStoreNet.

Key problem area findings
- Speed
- Search Functionality
- Broken Links
- Multiple authentications
- Outdated content
- Frontend Visually unappealing/disconnected from Boots brand
- Content structure (Navigation and taxonomy)

2 - In order to future proof the MyStoreNet application it is fundamental to allow the access through several touch points which may soon be considered in order to streamline the workflow within boots retail stores. It is agree by the stakeholders that such a scenario must be considered, as long as the main actual form od access is still considered as primary. In order to achieve a greatest degree of cross-compatibility, great advantage if the new Extranet could be accessed on tablets and mobile phones as well as via the web. It widely accepted in the industry that to achieve this aim, the best approach is what is called Responsive/Adaptive Design methodologies.

The following areas were identified as design priorities:
Fast and reliable
Easy to use
Streamlined journeys where possible to minimise effort and simplify content structure.
Easy to maintain - Enhanced backend (admin) experience
Cross device compatible - web, tablet and mobile
From a Frontend perspective, technology choices should be vendor-agnostic and flexible enough to be implemented in whichever platform the business may choose.
Single interface to all system actors

3 - I recommended Bootstrap as front end technology. Over the last few years, Bootstrap has become an increasingly popular front-end development framework. During this phase I supported the development team by iteratively refining a design and adding detail, throughout the development cycle.

I work in an agile development model for this project. I attended the daily scrums and get assigned tasks working on stories, but I do not have my time allocated—to avoid distorting coder resource planning or velocity calculations. I try to do my design work one sprint ahead of the team, working with product management and solution leads to develop high-level scenarios and mockups.

4 - My final deliverables for Boots My Store were:

a) Wireframe and specification document
b)Visual design of key screens
c) Assets such as icons, images etc.
d) Delivered Interaction details and visual comps.
e) Style guide and best practice guide.

View Wireframes and Visual Design

Related Projects