"I love the challenge of working on systems that rely so much on communicating a lot while still making pathfinding clear. For complex, data-heavy apps, like internal tools, platforms, and games, information architecture and creative problem-solving are the best tools."
This is sparse, my work tends to be under NDA.
These are some examples of some of the projects that I've worked on. They are all based on Salesforce (SF), most on Lightning.
*For those that don't know very much about SF and SF Lightning, it's a very complex cloud-based CRM that many companies implement internally to better track their sales processes, but because of how useful the tracking is it is also being utilized for many other quite different things to CRM. As well, especially in Lightning, there is a decent amount of restriction on what you can do out of the box, and doing things custom typically takes a lot of work and requires even more upkeep as they (SF) have new releases. In other words, a lot of planning and problem solving is needed to design an intuitive system that isn't overly customized.
Call Center Console
Product Designer
Call Center Console
Salesforce with 6+ integrations
Custom & Lightning Design
My Role: Study user, current process, needs; entire design functionality, usability, and UI. Parts to be reused/treated as templates. Only designer on project.
User: 20-28 yrs, predominantly male, gamer-type, respond well to visual queues.
Attack: Use of iconography, color for visual queues. Step-by-step flows, clarity. Information most-used to be up front and easy to access quickly. Most processes became automated instead of manual. Troubleshooting section helped by system information to find correct info.
Insurance - Mobile
UX/UI Designer
Union Insurance Site
Salesforce
Custom Design
My Role: Create a mobile experience based off of the current desktop site. Had to keep the look and feel while making it as optimized as possible where necessary to avoid extra development.
User: 35-50 yrs, low tech-savvy, want clarity on process on each step.
Attack: Large buttons and text (where applicable), large calls to action, clear path. Optimized and accessible.