REactor UX Team Mission Vision Strategy
I worked with my UX team and leadership across our products to create
strategy cascade to use internally with UX team to discuss our plan for impact on our organization
mission, vision, and values for UX team to define for ourselves and share with the organization (shown below)
strategy through roadmap, timeline and process for UX interaction with products and the organization
Our UX team worked together to create the discussion of our evolving design system and component library
Mission, Vision and Values, and Strategy
Outlined below is the Mission, Vision and Strategy that I developed. I’ve included what each component means and how they are built to strengthen our focus on improving the design of our products.
PURPOSE
(Guides us, Why we do what we do)
Deliver a superior experience of Comcast products and services
This works for all of our segments, stakeholders and products. MISSION
(Drives us, How we accomplish our purpose)
We empower problem solvers. We simplify complex information to improve the speed and ease with which our users accomplish their goals.
It’s a direct path to purpose and vision; unlocks strategy that delivers results and impact.
VISION
(What we want to be)
We deliver the go-to tools for Comcast and partner’s top tier support.
VALUES
(What we believe in and how we will behave)
Real Value is Discovered
By understanding our user’s troubleshooting process and goals, Comcast’s products and services, and common customer problems and questions, we can make optimal improvements and uncover innovative possibilities.
Meet users early and often
We meet users regularly throughout design and development. Everyone in the team meets users, not only designers.
Test and Iterate
Achieving true simplicity is a lot like solving a riddle — the answer is obvious only after you’ve worked it out. We challenge ourselves to look at problems from all angles in order to find the simplest solution.
We are aware that our design solutions are assumptions until they are tested with real users.
We experiment, test assumptions, learn and improve our ideas. We iterate our ideas in small steps to reduce the risks of failure. Experimentation is key to innovation. We value testing with users, learning, and iterating not only the systems we are building but also our design process.
Focus on Adding Value
Design decisions must be rooted in solving real problems suffered by true users. We spend time and effort on features that people need. We do this by understanding the root of the problem we are trying to solve and by fully understanding user needs and business needs.
Think lean and be efficient
We are efficient in our process and focus on the effectiveness of the outcome. We spend effort in the most valuable areas of the product and reuse elements whenever possible
Design for Context, Not Device
We consider every part of the user’s experience when we make design decisions. The physical conditions beyond the edges of a screen have every bit as much to do with how we design as the size of the screen.
Be consistent
Being consistent helps with usability, efficiency, and how users perceive our software (trust and professionalism). We should be consistent with our designs, the language we use on interfaces, our code, and the data.
Make it attractive and usable
A usable interface allows user to achieve their goals without friction. We also care about how our applications look and feel because attractive interfaces have an impact on perceived usability and users’ trust.
Collaborate
We enjoy solving complex technical and design challenges – that’s what we are best at. To really understand problems and to solve them effectively, we work in our multidisciplinary product teams that tackle problems together.
We build relationships and mutual trust with our UX team, product teams, SME’s and users. We listen, we understand, we encourage everyone to discuss problems. Our team members learn from each other and are empowered to make decisions on functionality and design and understand the value of what we’re building.
We support each other. We’re all in it together — and we all matter.
Innovation = Aspiration ÷ Feasibility
We ship because we design things that can be built. Feasibility comes from collaborating, and our developers’ input is just as important as that of our designers. We focus our effort on the innovative differentiators rather than reinventing the wheel.
.