DocuSign supports transactions with document sharing and electronic signature, as well as automated and guided data collection and entry, record updating across disparate systems and payment collection upon agreement, as well as analytics and reporting.
$15
per month
zeroheight
Score 8.0 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.
This product is well suited in the use case that I provided before: when it comes to onboarding employees and providing a clear channel for decision making for human resources, this is an excellent tool to accomplish that. I would say the weak points is when you have back and forth communication with users that it might seem a little redundant to have that back and forth communication in that scenario.
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.
Tracking, particularly when collecting signatures through connected applications, such as an ATS, is not always clean or easily traceable.
Formatting documents to handle electronic signature types (signatures, initials, etc.) is not always easy, and highly dependent on the partner's technology.
It is not convenient to have to use DocuSign as a stand alone product if the signatures are required for 3rd party applications. It definitely excels on its own, but the scope of that usage, at least for us, is slim.
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 can't imagine doing business without DocuSign now. I would never want to go back to the way we used to do things. The "new way" is "the way" is "the right way." We can honestly be proud of a "one right way" process and not have to suffer through "5 ways for 5 days."
Generally user-friendly once you have command of the basics, but also has a lot of nuances that can make it difficult to train others on. DocuSign University is a helpful tool, but understandably a lot of content to get through to become a well-versed user. A lot of different functionalities but only a few I use on a weekly basis.
I'd give them a 10, but there has been 1 or 2 small cases that seemed to fall to the wayside, but I was able to call them up and get them resolved. We were having a bad implementation night (after midnight) and we needed assistance from Docusign. They were able to get an engineer to help us in the early morning hours
Docusign is super easy to use, and apart from a few administration details, there was really nothing to train on. Post implementation, there were issues with configuration of auto-filled documents with the integrating 3rd party. That training required some time, because the DocuSign expert took the time to walk me through the 3rd party's configuration (how often does that happen?) so I could see how DocuSign should be best used to overcome weaknesses in the 3rd party platform. 10/10 expert care.
Until you get the hang of it, I recommend doing several internal tests before sending a document to a client. As I mentioned earlier, you have to go through a bit of trial and error at first to verify that the workflow works as expected.
There has never been anything that we could really compare to Docusign. We have tried sending documents in a PDF version, but that was not nearly as efficient. DocuSign saves your signature in the system and uses that as it goes through your documents.
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.
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.
