Design is what keeps me curious and finding ways to make it count toward the human experience. I am a Senior UX Strategy and Design leader with over 20 years of expertise in creating impactful experiences that bring value to the customer and help organizations realize their digital transformation. I have 10+ years of experience in building diverse, highly collaborative cross-functional teams that understand and embrace the craft in creating a cohesive customer experience. Together we shape the design practice and culture to build autonomy and trust.
Read moreI work with organizations to implement a Design Operations plan which allows processeses to scale and create a shared understanding by encouraging open discovery, design, and collaboration across disciplines. This creates a model where work centers around the problem a customer is trying to solve or the job to be done (JTBD), rather than the platforms on which users are interacting with your organization. Disciplines are able to work in parallel (not waterfall) towards the same goal.
Present and discuss the customer needs and the business/market value. The depth of the discussion during the kick-off meeting is not exhaustive. A kick-off can happen ad hoc or during a regular refinement meeting. A feature or opportunity canvas provides the team with strong indicators on what research is needed, user interactions and goals, and system architecture.
Who's there:
Design, Content, Research, A11y, Product Manager, Architecture/Tech Lead, SME's, Taxonomy/SEO
After the scope and high-level requirements are analyzed from the kick-off, the Design team jumps into focused design discovery work (solo or small groups). Activities may include:
Who's there:
Design (UX), Content, Research, A11y, Architecture/Tech Lead (as needed), PM/SME's (as needed)
The process may start with high level page flows that evolve into black/white wireframes which represent the details of the entire flow including empty states, error scenarios, transitions, content, CTA's, etc. It's important that there is collaboration between design and front-end development so that service and UI/Design system components can be identified.
Who's there:
Design (UX), Content, A11y, PM/SME's (as needed), Front-end dev (as needed)
Present wireframes along with any prepared design and A11y documentation. Architecture/Dev use this phase to respond to the design, ask questions, etc. Stakeholders are tagged as Reviewers (Content, Design Lead, A11y, Dev). User research sessions are executed and designs are refined based upon user feedback. Development should be able to begin early services/API work at this phase.
Who's there:
Design, Content, A11y, Research, Architecture/Dev, PM, SME's, Taxonomy/SEO
Once the wireframes are approved, UI visual comps can be created. Content may be refined and A11y executes their final review of the designs (color, interactions, etc.). The Design team is available to Dev beyond hand-off to answer questions as implementation of the design may represent micro-interactions and states that need to be fully understood.
Who's there:
Design, Content, A11y, Architecture/Dev, PM, QA, Analytics
Digital experiences are never "set it and forget it". Establishing success metrics during the discovery phase will allow the team to track analytics so they can hypothesize, experiment, and iterate on a solution to achieve the desired results. Experimentation leads to innovation.
Teams should be able to establish backlogs that contain a prioritized mix of new experiences as well as refinement or growth hacking initiatives.
Who's there:
Design, Content, Research, Architecture/Dev, PM, SEO
I fundamentally believe that as a design leader I am more authentic when I am able to guide teams and create great customer experiences by keeping my own design skills honed and sharp.