PolicyManager vs. zeroheight

The part I like the most is our staff not having to log in to view policies. We have so many passwords to remember having this convenience is a big satisfier.

For creating and maintaining a component library, it is a fantastic tool that creates an interface between Developers, UX Engineers and Designers. It is easy to get both general information about a component, but also incredibly detailed information when looking at the component on a pixel-level, where information on paddings, margins, colors, fonts etc. can be easily accessed.

Incentivized

• If I ever have any technical issues or questions the support team is great at getting back to me very quickly. I also like all the resources available to help as well.
• Policy reports, there are so many to choose from. These reports help me track several different things in the system. Compliance, attestations, past due, and so much more.
• Another plus for me is being able to add linkages to outside programs like TJC and Elsevier. Linking these to policies saves a lot of time.

• showcasing components and other topics
• ease of seeing detailed information on components (colors, paddings, sizes etc.)
• ease of finding information
• possibility of going to previous versions of the design guideline

Incentivized

• The program doesn't work well with Chrome, would like to see that fixed. We have several staff members that use Chrome.

• when opening a component image (which opens a new page where the detailed information like paddings and colors are shown), the zoom can only be done by buttons, I'd prefer to be able to use my mouse scroll and for vertical / horizontal scrolling to do ctrl+scroll or ctrl+shift+scroll or something like that

Incentivized

Overall this program is great. I am continuously in the program and find it very simple to use. I do have some staff that struggle, only because they are not in the program as often as I am

I have used and still use Sketch and Zeplin too, but they serve other purposes for us. Sketch is used to design the components themselves and they are then exported to Zeroheight where they are showcased and enriched with textual information. Zeplin is used to design application pages, and again the components are exported to Zeplin from Sketch. But Zeroheight is mainly used for the development of the components themselves as well as a documentation for our design guideline in general. It is also used by us for design tokens and patterns, as well as other information on the design guideline, so if someone wants to understand the "why" of a design decision, the explanation can be usually found in Zeroheight too.

Incentivized

• The program has kept us compliant on reviewing and updating all of our policies.

• increased quality, as less misunderstandings or communication problems occur
• increased speed of development, as it is a single source of truth for us. The developer can rely on the information in Zeroheight being correct so that he doesn't have to iterate his code again and again.

Incentivized