FigJam vs. Filestage

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.

Filestage is perfect for staging a review with multiple stakeholders from different organizations. You can control who sees your project and when they can see it. Controlling this aspect of the review process is so important because some stakeholders might not understand a work in process and really only need to see something that's close to finished, while other collaborators might need to get in earlier to make art changes, copy changes, etc.

Incentivized

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

Incentivized

• Compares past and present versions.
• Makes commenting easy.
• Easy navigation.

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

Incentivized

• Notifications can be buggy
• Google Docs implementation - currently if you use a static Google Doc it doesnt allow you to strike or highlight text like it does with PDFs
• Perhaps not allowing the person who submits a document to also be the reviewer of it

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.

Filestage is by far the easiest and most affordable option for our team.

Incentivized

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

Incentivized

• Saves time when proofing and editing work.
• Creates a unified place for feedback from team members.
• Allows all editing and review to happen in one place.
• Allows for versioning and version comparison.

Incentivized