Industrial and Commercial Bank of China (Asia) Limited
Technology Project Management System
Technology Project Management System is fully compatible to a traditional model of waterfall project management and an incremental approach of agile methodology, which This customised project management system is used to define processes and software development life cycle to ensure the end product is of high quality. This system aims at enhancing work efficiency, clarifying development structure, reducing operation cost and simplifing document handling.
To comply with my confidentiality agreement I have omitted and appropriated confidential information. These designs are a reinterpretation of the original.
My Role
I was the only designer in the team and responsible for the experience strategy and interface design of the entire system. I was solely responsible for collecting and analysing user journey, determined the sitemap and created high‐fidelity prototype to our development team and usability testing within 1 month. I worked alongside a project manager and three software developers.
The First Phrase
Within three months, the first phrase of system was launched for all departments to apply projects during their routine work. Under the department policy, the system was updated and various functions are added to the system after the first phrase of production.
The Requirements
Designing for what users are willing to know, do and feel
In order to well organise and cooperate with the team, site architecture and system workflow were taken as first task in my priority list.
The system roles were redefined from seven to four, so that the authorization control were simplified and allowed a single user to own multiple rights without switching the role.
By the primary research, most of the users claimed that the submission procedure and process status were not clear. Thus, I decided to set a "Milestone" & "Recent Update" block to show the progress transparency and reduce the risk of advancing projects in their daily work.
The Discovery
Analysing personas to better understanding users' needs
The discovery phase allowed us to define project direction, audit the existing work, review the site architecture, understand our client's vision, and achieve research into user requirements, behaviours and pain‐points. We also kicked off a technical discovery phase to understand feasibility and constraints.
After designating persona types, we were able to prioritise what functions we would be focusing on supporting in the early stages. We interview our personas constantly throughout the project to validate design assumptions, priorities, and dig out the part we had neglected.
The Framework
Proposing the design direction by wireframing and prototyping
Grey scale wireframe was used to depict the ideation of the entire system and confirm the project direction.
High-fidelity prototype kept the design process in transparency. It intensified the trust from our system owner and user. I always prefer to create prototypes by coding, which allow me to obtain feedback and approval from both user and development team early on.
Feature 01
Tag function is added to
facilitate the search engine
Since a part of user mentioned that they were difficult to search a project through search engine, so that I suggested adding "Tag" to define different project groups and provide "keyword" search with dynamic results to enhance the usability and lower time cost.
Feature 02
Keeping all documents as electronic records
In order to reduce the repetitive documentation and well keeping data, all of documentation was filled in on system platform. On the other hand, we communicated with the development team to enhance the database which was stable to keep all electronic records.
Feature 03
Providing flexible parameter maintenance set up
Different project types might be followed and processed with distinct approval stage. A flexible parameter maintenance setting allowed user to rearrange it under the latest business policy or special conditions.
Feature 04
Building up a common test case library
A common test case library was established to facilitate the progression of user testing. The library covered Interface testing, functional testing, stress testing, performance testing, and automated testing.
Feature 05
Managing UAT issues and tracking project risk
Users could create issue and arrange to developer for debugging when they faced any problems in UAT. This assisted to track team workload to adjust tasks and resources. It also maintained high performance of the production and followed up the feedback coming from customers to enhance the experience.
The Impact
Prompt users to respond and give more measurable answers for refinement
After running the system out of six months, a user survey was held to collect data, satisfaction and gather meaningful insights for further optimization.
The survey was contained 28 questions with closed-ended and open-ended types. It covered three different parts of the entire system to evaluate the usability and acceptance, which contained to the overall situation, project life cycle, optimization comments and the impression of the UI & UX in the system.
