FigJam vs. Stack Overflow for Teams

It is well suited when people use it to sketch the first wireframes of the UX, like the Breadboarding technique from Basecamp. I used to work like that when modifying some UX. Our designers used to sketch over our current experience wireframe, and then we could discuss it by using the comments in Figjam or the Call feature at FigJam. That made it easy to discuss it. When building up group boards to discuss ideas, I use Miro, once it has more native pre-sets that help conducts the discussion.

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

• One file, auto updated, no need to get latest
• Easy to preview
• Lack of client is benefit to some (not me)

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

• Less Rigidity
• Ability to work with Different Documents
• A light version of Figma

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

Positive: FigJam is cheaper than Miro and allows connecting with FigJam, where we design our user interfaces. FigJam is more complete and visually appealing than draw.io, although draw.io is free. FigJam allows calls, which both competitors do not. Negative: Miro has more pre-set diagrams than FigJam and they are native and easy to use FigJam is paid, while draw.io is not.

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

• I believe that creating professional projects inside a web app feels amateurish.

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