FigJam is an online interactive whiteboard from Figma headquartered in San Francisco, presently in beta (2021) but available to the public in a free trial. The vendor states that in 2022, FigJam will have plans for $0, $8, and $15 per editor, per month.
$5
per month per editor
Stack Overflow for Teams
Score 8.2 out of 10
N/A
Stack Overflow for Teams is a team knowledge management and Q & A platform for development billed per teammate, featuring roles and permissions, and integrations with popularly used collaboration tools.
If you're working in small product teams, like triads, and already using Figma, this is a no brainer for white boarding, quick/fast sketches, wireframing, collaborative doodling ... it gets less appropriate with large teams, infrequent. IMO, due to the way in which they price, it's better to keep the inner circle small-ish.
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.
It misses easy-to-use pre sets of diagrams. The ones presented seem to be not native and hard to use. Miro is a good benchmark.
Navegating throught projects in the main page is confusing, specially when people are not admin users.
It should suggest ways of organizing the pages designers do, specially when the project is big and have many pages and sections.
It could have, for example, a draft version for every page, so that one can hide it when they finish the work, but can open it whenever something needs to be modified, versioning the job.
I don't use it often, because the organization I work in uses a different environment on a commo basis. This is rather used between the designers, who prototype the solutions in Figma - they just have it as a workbook/notebook for their ideas. However, if those need to be shared with stakeholders or other organization members, the designers are expected to use a different environment.
FigJam works best in pair with Figma, as it allows you to keep track of your project in one place, supporting all phases of the process. The functionality is more intuitive, quick, and efficient. Visually, I also prefer it more —it’s more enjoyable and playful, making the experience much more engaging.
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.
FigJam saves a lot of time ... it's nice to have all my visual notes/sketches within Figma itself where a lot of design work lives
The project organization and other features contribute to the ease of answering that age old question ... "where can I find that mockup?"
Dev Mode is pretty cool. Not many use it, so some designers may spend unnecessary time spec'ing out things that no one will appreciate, let alone look at.
