I found Figma docs thrown over the wall from designers pretty hard to consume.
Perhaps it was just how that particular design team used it but
- they put a huge amount of information in a single document.
- lots of sticky note style additions that were not clearly associated with what they referred to.
- hard to search.
- hard to determine what a single unit of work could be. Again, maybe this was the team but they didn't have a concept of discrete tasking. It was just "here's the giant figma doc with everything from p0s to stuff we might not even want"
Interesting, we have a similar situation. A lot of information all at once, hard to navigate, search etc. Usually developers are so confused a figma doc is often used more like a prototype to show during a demo than a spec to share. Instead our designers make screenshots of it and put them in a well-organized Confluence document. I don't know what's the right way.
Perhaps it was just how that particular design team used it but
- they put a huge amount of information in a single document.
- lots of sticky note style additions that were not clearly associated with what they referred to.
- hard to search.
- hard to determine what a single unit of work could be. Again, maybe this was the team but they didn't have a concept of discrete tasking. It was just "here's the giant figma doc with everything from p0s to stuff we might not even want"
What are the upsides?