PowerDMS by NEOGOV is a software platform designed to recruit, train, equip, and protect employees across their careers, used for policy management, community engagement, and staff scheduling.
N/A
zeroheight
Score 8.6 out of 10
N/A
zeroheight helps teams create, manage and maintain their design systems. Using zeroheight, designers, engineers, and product teams can collaborate and build design systems that can be easily shared across teams.
Getting 100% signature compliance on policy updates used to take months but since automating out policy management updates in PowerDMS, we can get 100% compliance in as little as 2 weeks. Internal requests for things such as training, purchases, etc used to be pushed up the chain of command via a paper copy and would often get misplaced or lost in a full mailbox. Using PowerDMS to automate those requests put the power back in the requester's hands and increased transparency and accountability across the organization.
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.
The Workflow process in PowerDMS is not as easy to grasp as some of the other concepts and requires a little more explaination, especially for non-administrative background users.
Users are unable to view the steps in a Workflow template in order to determine which Workflow would work best for their needs when routing documents.
It would be great to have multiple message options for past due inbox notifications in addition to the options for past due tasks to encourage users to go to their inbox to review their messages.
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
I have had nothing but positive experiences with PowerDMS from day one. If we ever run into a situation we are unsure of, PowerDMS support has ALWAYS been able to answer us basically immediately. I really love that they are constantly seeking to improve and expand.
While not necessarily user-intuitive, with a small amount of dedication to training and learning how the system functions, it becomes very usable. I would say that the usability scale is quite user-dependent. For a standard user that just needs to review and sign documents, it is very easily used. On the other end, management does a bit more of a learning curve.
We use PowerDMS in the cloud so our performance might be different from other users who use on-premise. The program has always been up with very minimal downtime and always seems responsive and snappy when navigating the UI and searching documents. We don't currently have any integrations with other software.
I just wish we had some in-state support. The contacts I have had with customer support have been great. Awesome communication, problem-solving, and support. I have talked to and met Stephanie Williams (CSA for Power DMS) at the most recent Entrust conference. She was professional and devoted time to addressing our agency needs.
Implementation of PowerDMS was near seamless. The product was able to input existing policies and procedures within a few hours, which helped to lay the foundation for future use. Having PowerDMS on-boarding readily available was also a huge benefit.
Our previous document product was Image Silo. It was a stable-enough product, but was strictly an indexed filing system. PowerDMS goes well beyond indexing (which it does very well) and provides countless more features and functions as described above. I would describe the difference between our previous product and PowerDMS like the difference between the library and the Internet. Both contain information, but on is limited, while the other has it all.
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.
Created efficient processes for approving document revision
Migrated what originally was a paper system to electronic
Accessible for any employee by logging in, employees do not have to seek out policy and procedure binders, and updated documents can be automatically sent to inboxes when updated.
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.
