snape
Hardcoding is a bad word and it will kill your product.
Rally Health Enterprise Tools

I worked and lead my team to design a tooling system that would allow for a wide range of tasks, across a variety of administrative users, that focused on creating a seamless experience that would vary from tool to tool but use foundational workflows. We created a style guide and work it into a living sketch styleguide to help speed up the design and implementation of any new tools projects.
My Role - Designer, Collaborator, Director
_ Primary designer and helped craft the global concept for the tools
_ Worked closely with product and development teams to implement tooling strategy
_ Built and Directwed the design team working on the Enterprise Tools
Multi Prong Impact
The Rally Tooling initiative contributed to multiple efficiency improvements:
snape
The Approach
_ Modular approach to the tools, to create reusable patterns and components
_ Develop a workflow that could flex based on the needs of any individual tool
_ Atom Design Methodology
Tools Dashboard
Allows an admin to view all the tools they work with and see any tasks that need their attention and notifications. It also focuses the admins work based on common workflows.
snape
Component Library + Style Guide
Developed to maintain a high level of consistency across all the tools. This would allow any admin to be able to work in any of the tools and be able to understand the steps needed for any configuration. The style guide was also adapted both as a shareable sketch library, and a development driven living style guide. This greatly increase the speed and accuracy of the designers work.
snape
Common Patterns + Workflow
Wizard Configuration
The importance of creating a process for the admins is is critical across the whole tools suite This allowed for a modular approach to configuration needs, but has the flexiblity to custom any given step in the wizard.
snape
Partner + Client content association
The relationships between the insurance company the employer is a common pattern this was always the initial step in every tool, as that configuration determined other parameters or data that would be available during the configuration process.
snape
Publish + Promote
The ability to publish/launch your content was crutial allowing the administrators to determine when, and where to publish a user experience configuration, moving something from development to production, created a smoother workflow without needing the help of development teams. The process also allowed for time and date specific promotions, which was key for our implementation teams large 1/1 deliverables.
snape
Content Version Control
We developed a process for draft vs. published content. When would the content still remain editable vs. being locked post client sign off. Also the ability to copy a configuration, either as a new version or a unassociated version that could then be tweaked or customized further while using the base configuration as a starting point. This also allowed for zero downtime of any content in the experience.
snape