I was designer leading the vision for new products and features for Paychex Flex while working for ITX The following is an overview of my design process and team Interaction.
There is a lot left out of this, including project specifics and the products I helped create. While presented linearly, stages were often revisited while designing and building in an agile process.
During my time working with Paychex, I had the chance to design and impact various lines of businesses. Here is an overview of a few of the projects I was apart of and my responsibilities:
Projects would stem from a few different avenues. These could arise from user feedback and requests, building feature parity with classic software, building and innovating on industry features, solving around inherited complexities for a better user experience, and more.
Projects would stem from a few different avenues. These could arise from user feedback and requests, building feature parity with classic software, building and innovating on industry features, solving around inherited complexities for a better user experience, and more.
When kicking off a new project we would in some cases start with a design sprint loosely built around Google’s design sprint model. In these sessions we would involve stakeholders, designers, and architecture to identify problems and rapidly iterate. As the designer on the projects I would be wire framing on paper and whiteboards in the sprint, which would lead to an interactive, clickable prototype that would be placed in front of users for usability testing. From there we would iterate on what worked and continue the vision forward.
At this stage I would take the data from UX research and the results from design sprints to design out many possible variations of a possible solution.
In this stage, there is a lot of collaboration as I refine the design through regular design reviews to get fresh outside perspectives from other designers, input from product managers and stakeholders to make sure we are on track and addressing all the needs, and development to make sure what is being designed is buildable in scope and if there are any possible efficiencies.
As designs start to take shape and solidify, the goal is to test assumptions and judgment calls made along the way tp make sure we are delivering a worth-while vision.
I used prototypes to gain feedback from users, fellow designers, developers, managers, and other stakeholders. These were high fidelity prototypes built to mimic the real life Paychex Flex environment as much as possible.
The benefit of using high fidelity prototypes allowed:
I would often build the prototypes in Sketch and InVision to handoff for in-browser viewing and testing.
Using various tools such as Zeplin and Jira, designs are handed off to developers. As the project would be built out and tested I would sit in on developer meetings to address any questions, iterate on edge-cases and errors, performing UX reviews to ensure the project is built to spec, and to iterate design when a pivot is needed.
I'd love to chat about potential partnerships, design, artificial intelligence, chicken wings, or a dog pic exchange. You can contact and connect with me through email, on Dribbble, or LinkedIn as well.