VIEW PROJECTSummary:
Client: MNTN
Position: Head of Product Design
Summary
I came to MNTN in March of 2022 as in individual contributor. Moving from my previous role as the Director of UX for Newsday this was a big shift. It was a change that I embraced. To focus solely on design was an amazing gift.
At MNTN design was mostly a second thought, a tool to get the job done. Product managers and Engineers were not used to working with designers since they have always been a engineering led organization. Engineers were using the Ant-D component system to support new features and maintain the UI.
In order to assist with collaboration and infuse new out-of-the-box design solutions, I collaborated with the the organizations designers, engineers and product people on the team to create a workflow for product design & development.
The Workflow
This workflow is a visual representation of my years of experience working in product design and visual conveys the different phases of product development inclusive of design. It consists of 3 cycles of feedback and refinement in order to allow for maximum collaboration with increased efficiency.
PRD HLC Cycle
In this cycle the senior UX works with the senior product manager in their respective squad to come up with the best UX and requirements to execute the initiative. Initiatives can come from any part of the organization (Platform Experience, Product Initiative from C-Suite, Business Objective or UX Initiative).
HLCs In instances of high level concept work, cycle could be localized to the UX chapter or in a small group including CPO, Head of Product Design, Senior UX, and Squad Senior Product.
Stakeholder Cycle
UX or UI design is presented to Product, QA and Engineering for feedback to uncover any potential pitfalls, pain points or technical limitations. Designer refines and reviews with attendees as needed to solidify a working UX concept.
Development Cycle
Engineering and UX work together either asynchronously or synchronously to achieve a working version of the approved UX/UI. The design can change. Designer may choose to update designs based on any technical limitations to make sure engineering is not blocked by design as long as approved UX is maintained.
Large Project Finalization (Burn Down):
For larger projects bugs and requests should be itemized in a burn down sheet rather than separated into JIRA tickets. This allows for one source of truth for all aesthetical fixes. Design can itemize adjustments, make comments and hand off to QA to verify. Sample file here.
Formal Design Review
In most cases Engineering and UX can flush out any issues in the Development Cycle ad-hoc. If Senior UX feels another review is warranted then the Engineer should schedule a formal review with stakeholders.
Back to QA
If major issues are uncovered in this review items should be listed in the ticket or if more that 10 in a burn down sheet and handed off to QA.
Post release
UX should always have a plan for tracking new features in UX Analytics post release. Heatmaps, Click Stream Data, Journeys etc. If pain points and issues arise during this analysis Senior UX should create a new backlog ticket and prioritize enhancements with senior product.
Workflow Visual
If your visual learner like most designers, I took that into account and created this Figjam and is the source of the above explanation.
