My typical workflow:
Discovery, User Research and Business Research
Key Findings, User requirements and Product specifications
User Flow, Wireframes, Prototypes, Mockups, Design
Testing, Feedback, Iterations
UX Delivery, Collaborate, Communicate
I executed the following (E2E):
Research, breakdown and map out all 25 applications.
Research/Define all Personas involved in the platform.
Research/Document business use cases for each application.
From the user perspectives research the “what & why” (what do they really need and why do they need it to complete their job).
Based off my research, consolidate, deprecate, and adjust all applications.
Research, identify and solve UX problems using multiple UX tools.
Test/validate decisions, improve UX design and overall performance.
Approach project with a user first perspective to re-evaluate all applications’ future importance within core business needs.
Create/manage product specifications, requirements, UX deliverables, timelines, signoffs and product road maps.
Collaborated with 30+ colleagues while wearing multiple hats as needed to keep the project moving forward, organized and on schedule.
Platform Context/Navigation:
The Stratus platform is structured like a portal with all available (based off RBAC) applications grouped in the top navigation by business area with dropdowns to access specific applications. The 8 new Mantis applications will be in this navigation.
The mockups shown are of the first application completed (Demand Forecast). The Demand Forecast application uses a tabbed UI to access the multiple areas needed in the application. This layout will be used for all of the other Mantis apps. One of the ways I was able to reduce the number of applications is due to the tabbed UI.
* (Below visual) Showing a screen grab of the Demand Forecast in development (code).
Microsoft - SaaS migration to PaaS Platform
Background:
The Stratus platform (PaaS) supports Microsoft’s CSCP (Capacity, Supply Chain and Provisioning) group. The platform provides teams with Dev/UX support, a common controls library, developed design language with sample layout examples.
Engineering teams are directed to utilize the platform for engineering efficiencies rather than build custom siloed UX solutions.
Problem:
The Mantis platform hosted 25 applications, was a siloed engineering driven effort, used a one-off design language, custom UX (developed “as needed”) and was an independent platform. It suffered from poor performance, a growing backlog of usability issues and UX/Dev inefficiencies. The code base was also losing support. An executive decision was made to move the Mantis platform applications over to Stratus.
This project is about transformation, UX improvements and Product design/management/collaboration.
Solution:
Move all of Mantis front-end UX over to Stratus and deprecate the old Mantis UX. Backend architecture would remain in use. During the transition review all applications to identify UX improvement areas, deprecation opportunities and convergence benefits.
My Process:
As the single UX/PM resource (E2E), I started researching/documenting/breaking down all applications so I would have a solid foundation of what the applications do, who uses them and what the business needs are.
Next, I worked with users (multiple personas) to understand what they “actually” use, why they need it and what is not working for them. This resulted in a roadmap with dates, priorities, UX issues, roles/responsibilities and specs outlining the scope/future state of the entire project.
From here I built out UX deliverables per app (use cases, user flows, requirements, wireframes/mockups/prototypes and product specification documents). I tested, iterated, and validated my UX solutions with users throughout the entire process. I managed and led cross team collaborations, sprint planning and set/modify expectations as needed.
(below) Showing a page from the Master spec. In total there are nine individual product specification documents. Each app specific specification contained all project information and UX deliverables.
Result:
Using user-based data I was able to reduce the 25 original Mantis applications to 8 new applications to be transitioned over to the Stratus platform. This outcome was due to simplification, improving, deprecating and combining of user needs with improved UX across the board.
I built on the success of others, created efficiencies across the board and greatly improved user experience for Mantis users (business and engineering users). Future improvements will more efficient by utilizing the SaaS platform, established project structure and new UX patterns/processes.
The 8 new applications to transfer over to the Stratus Platform:
1. Demand Forecast
2. Model Selection
3. Forecast System Admin
4. Enrichments Collaboration
5. Spares Forecast
6. Data Transformation Capacity Planning
7. Data Transformation Finance
8. Engineering
(below) Shows the original Mantis dashboard listing applications.
