The ease of use. I generally tell people making a standard with GembaDocs is only anywhere from 1 to 10 minutes longer than it takes to actually execute the process (depending on how many process steps there are of course). The biggest hindrance, in my opinion, to you building the team you want is both you and your team's lack of understanding and discipline around standards and their importance. There's no better tool for reaching that required level of discipline and understanding of standards than GembaDocs. Review collected by and hosted on G2.com.

Speaking candidly, 1 minor feedback item I have is that when a standard is already made, every new step I add (after saving) prompts an option to increment the rev and document the reason for the change. Although both of those items are important, I think having to acknowledge them that often can be improved. Possibly, there could be 2 options for update down on the bottom of the screen where "UPDATE" usually is. Option 1: Update without incrementing rev or documenting a change log entry. Option 2: Update WITH incrementing rev or documenting a change log entry. The best thing about GembaDocs, however, might be that this type of feedback is sought after and executed upon frequently by the founder and development team. Can't say enough great things about this product. Review collected by and hosted on G2.com.