Process

Every project has unique needs, but here’s a basic outline of our typical process for designing software.

Design Process

Here is a basic outline of my typical process for designing digital products and services.
Please note that this process adjusts to each project’s unique needs, and stages are more iterative than the list below may convey.

 

Scoping
• Vision and goal definition across stakeholders
• Assess current capabilities, limitations, positioning in the market, etc
• Define project budget, resources, key deliverables, etc
• Draft a tactical timeline within the context of a future focused roadmap

Working with the c-suite, strategy and business ops, product, engineering, and other stakeholders

 
image shows the top of four articles about design for users with low literacy

Research
• Dissect and review the current experience
• User/stakeholder research and interviews to identify pain points and needs
• Literature review to better understand the clinical context
• Landscape review to better understand the market

Working with UXR, SMEs, analysts, customer service, business development, etc

 
image shows a visual user journey map

Synthesize Learnings
• System diagrams
• User research report
• User experience journey map
• Competitive analysis

Often presenting to the c-suite, product owners and managers, dev leads, and other stakeholders

 
image shows sharon writing on a whiteboard and a hand drawn sketch

Generate Concepts
• Group and individual brainstorming sessions
• Whiteboard
• Hand sketch

At times, running collaborative brainstorming sessions with stakeholders

 
image shows user interface designs with annotations around them

Design and Discuss
• Mockup screens (Figma)
• Organize designs into “comps”
• Establish or align with the design system
• Team feedback to focus direction and iterate ideas

Working with product with insight from engineering on feasibility

 
image shows designs on a desktop and mobile phone with a photo of group feedback in the background

Prototype and Test
• Define testing goals
• Coordinate with users/stakeholders
• Assemble a simple clickable prototype (Figma or code)
• Finalize testing protocol
• Run qualitative interview sessions with users or stakeholders, cart sorting session, and/or surveys for quantitative feedback

Working with any user research resources, analysts, etc

 
image shows designs with quotes from user interviews around them

Process Feedback and Iterate
• Review feedback and synthesize insights
• Present results to stakeholders
• Use data driven and evidenced based decision making to iterate designs

Working with product with insight from engineering on feasibility, often presenting user research findings to c-suite, product, dev leads, and other stakeholders

 
image shows designs with detailed annotations around them as well as icons organized for engineers

Production-ize
• Cover all necessary use cases and edge cases
• Revisit and finalize the Design System for designers and developers to reference
• Create prototypes and annotate key screens to demonstrate user workflows and interaction design
• Gather all visual assets and organizes files for effective collaboration

Collaborating closely with engineering and product

 
image shows designs with annotations for engineers around them

Ongoing Support during Development and Release
• Answer engineering questions about design decisions
• Provide design feedback on engineering outcomes
• Monitor and address any design challenges that emerge after release

Collaborating closely with engineering (agile teams to handle evolving needs), product, customer service, etc