Design Process

At Heritage, our team has developed a detailed design process. Not all of these steps are required for each project. I think of our design process as "tools in a toolbelt" that I can pull from as needed. To design the most effective software, I need to learn about the users' processes and their unique needs. The best solutions result when I combine objective observations, empathy for the users, and my sharp design instincts.

Quick Overview:

• Kickoff - Set stakeholder expectations and define scope
• Research - Talk to users, conduct field observation, analyze data
• Ideation - Whiteboard, sketch, diagram, and create wireframes
• Reviews - Review with Designers, Developers, Users, and Stakeholders
• Alpha Testing - Run code tests and use cases with Developers
• Beta Testing - Run through use cases with Users and Stakeholders
• Roll Out - Announce the new tools, launch, and train users
• Follow Up - Field Observation, analyze data, conduct follow ups with users and stakeholders

Design Process

Design Process

For a more detailed look at our process, keep reading.



Kickoff
Show more


Research
Show more



Ideation
Show more


Reviews
Show more



Alpha Testing
Show more


Beta Testing
Show more



Roll Out
Show more


Follow Up
Show more


← Heritage Auctions Work





Go Top