How do you guys track designs, components, and requirements changes and make sure all parts of the application gets updated?

11 months ago from , UX Consultant

i know there's some tool trying to cover version control in design but idk if i've heard anyone talk about just like tracking... component changes, requirement changes, layout changes and knowing:

1) the items affected by this change, e.g. where this component is being used at, which dependencies are affected, etc, 2) all the relevant assets and screens in invision, zeplin etc being updated fully, and 3) making sure it gets communicated to everyone on the team properly and

i'm still pretty green but so far the process i've seen and confirmed with others in the industry is god-awful. you just try to "documen it as well as possible" through jira (which is also god-awful) and review all the past screens to see if any of them will be affected.

things are constantly dropped and missed in the process ofc, as it's a terrible, error-prone way to deal with something that will inevitably happen innumerable of times in a project. Yet i haven't heard of any better ways to do it, or anyone really discussing how we can improve this process.... im curious to see what others are doing to deal with this.

1 comment

  • Christopher Chae, 10 months ago

    Hey Angel. Thanks for some good thoughts. I think what it comes down to is, whether you have a good, sustainable system when developing design projects. A system that pre-defined its processes to the granular level, so that people exactly know what to do.

    Too much freedom lets people rename files using whatever convention they feel like using. Too much freedom allows people to skip making updates to others. Too much freedom lets people update a file without writing a single sentence describing what they changed.

    Too many times we've seen this with the teams we were part of, and we'd like to change that. We believe that well-defined workflow and subtle constraints make a good combination when it comes to managing creative projects.

    An example of how a software tool can help out with this is specifically requiring a user to write detailed descriptions of what they changed on an update. Another one is the ability to view a project in a logic-tree view. See exactly where you started, who branched out and merged with the master file. See how the progress is being made.

    We are currently building a product that exactly solves this pain point. http://pixelic.io. I'd love to chat if you have 15 minutes? Want to know more about what makes you actively seek solutions on this. Let me know!

    0 points