FigJam vs. Lytho Workflow

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.

Incentivized

It's a flexible program that can be molded to fit most businesses. It's geared towards agencies but we've been able to use it successfully as an in-house solution. It's pretty intuitive for the most part and is easy for new hires or clients to get up and running pretty quickly.

Incentivized

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

Incentivized

• Requests - Request forms are set up so that certain fields are required and there's a minimum turnaround time. This prevents others from submitting an incomplete request or requesting things last minute.
• Proofing - Chasing after people to approve a proof is always a pain, but the simplicity of Lytho Workflow makes it less of a pain. I can quickly remind people in the route to review the proof by clicking a button.
• Templates - I use templates so that a list of tasks is created for me when I accept a job. It also creates a timeline for when each task needs to be done.

Incentivized

• 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.

• Not being able to permanently delete inactive/old users (i.e. employees that are no longer with the company).
• Search filtering features are lacking.
• Not being notified when someone replies to my comment without @ mentioning me.

Incentivized

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.

Incentivized

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.

Incentivized

By consolidating the requests, project management, and proofing without features we didn't need like invoicing it was an easy fit for us. We were able to quickly develop a comprehensive workflow and the gains to efficiency were immediate. Pricing was competitive (at least at the time) and the implementation was very good as well.

Incentivized

• 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.

Incentivized

• I wasn't working for the company when they first started using Lytho Workflow workflow, so I can't say what impact it has had. However, I do see the product as a necessity in the fast-paced environment that is retail marketing. The introduction of the new "change request" feature has saved countless hours of miscommunication and confusion when project objectives change.

Incentivized