5 ms·

I don’t understand. Would it be sensible to require people using Figma to instead use Jira? Two tools with completely orthogonal use cases. It sounds like you’r

• OJFord 3y ago
  GP said 'things are documented in' - while neither's an ideal tool for long-term product-oriented 'how its supposed to work' docs, both are definitely used like that. (You probably wouldn't choose either for that from the beginning, but you start using Jira for issue tracking/feature planning, of Figma for feature design, and end up with them holding a lasting record of how the feature is intended to be.)
  • tobr 3y ago
    “You must use this tool for this specific collaborative process” is not the same thing as “You must not use this tool at all”.
    • TeMPOraL 3y ago
      As 'zokier pointed out[0], we live in the age of apps. If you're not allowed to use this tool for collaborative process, often enough you may just as well not use it at all - as moving data between apps is usually a manual process that's boring, time-consuming, and lossy. Modern apps are tools of control, not cooperation. -- [0] - https://news.ycombinator.com/item?id=36402497 https://news.ycombinator.com/item?id=36402497
• gumby 3y ago
  It seems that at her company, some people do use Figma for internal documentation. SHM.