GoProof vs. Stack Overflow for Teams

In our small membership-based organization, we have many stakeholders both internally and externally. GoProof doesn't require accounts and is extremely user friendly. I find even the most technology-hesitant person is comfortable using GoProof. Many within my company take advantage of a flexible schedule, but that means reviewing marketing projects under deadlines can be tricky. GoProof can be easily accessed and proofs quickly reviewed. The system then notifies all stakeholders of updates so fewer emails need to be sent. It's much more efficient and I find work is completed much faster.

Incentivized

In my opinion, Stack Overflow for Teams is well suited for an organization that is on a hiring spree for the engineering teams. The reason for it is because instead of catering to doubts of new joinees individually, they can be asked to refer to the Stack Overflow and hence will save a lot of time for both new joiners as well as the existing employees.

Incentivized

• Reviewing design proofs
• Easy for new users to understand
• Commenting history
• Integration with Adobe CC

Incentivized

• Sharing technical solutions to problems we encounter in our internal development environment.
• Sharing best practices we find in external resources.
• Discussions on design patterns and conventions we can use in our projects.

Incentivized

• Reviewing design and function of email and web pages
• Adobe CC extension occasionally won't load
• More agile foldering/organizing system

Incentivized

• I would recommend an increased engineering focus on the Microsoft Teams integration.
• It would be nice to make more medals.
• Easier ways to earn points.

Incentivized

I prefer GoProof over PageProof. GoProof has a more user-friendly layout and workflow. PageProof has many functions hidden on the screen so it's not as simple to understand. One of the features, in particular, adding other reviewers, is too complicated with PageProof and I am never sure if I am doing it correctly. GoProof allows proofs to be removed by an administrator no matter the status of the creator. With PageProof, I have proofs sitting in my inbox for months that were unfinished for a reason but I can't remove them. PageProof does allow emails and webpage to be sent through the system to review function and design. It's a really great feature that I wish GoProof had.

Incentivized

It's easier to use Stack Overflow for Teams Q&A to maintain our knowledge base over time, over the Confluence wikis that we also maintain. You don't need to bother about folders, filenames, templates - just ask a question and answer it or get it answered. It feels less formal, so developers feel more free to add content.

Incentivized

• Went completely paperless and sold two large printers
• Flexible employee schedules no longer hinders project flow
• Work from home is possible and very easy

Incentivized

• It makes the search for answers more efficient, so devs can focus in more important things.
• Knowledge is not lost, even if people leave the company.

Incentivized