• Paul Gates, over 1 year ago

    A few direct suggestions:

    1. Discuss this issue with your team. This is a team process, and they should have some input on how you work as a collective.

    2. For small changes, work out a process with your team that allows you to review a build before it goes out. You should have the ability to hold a release back if you don't think it's ready. Document anything you'd like fixed, prioritize it as a team, and focus on a few things at once. Be flexible.

    3. Larger changes should not come as a surprise to your developers. Get them engaged in the feedback and your rationale before you run off making decisions on your own. This way, you build trust and help to maintain focus on important UX issues for your team.

    Lastly: tools, frameworks, and process will never trump a good relationship with your team. Making collectively agreed upon design decisions via communication is your most important job. The little details that annoy you will be much easier to address if your team trusts you and your process is focused.

    11 points
    • Jan Vu Nam, over 1 year ago

      Great comment Paul! Thank you! Nothing beats a good and enthusiastic relationship with your dev team, agreed. Still the documenting part can be greatly automated. As designer, I tried to visualise the solution over this weekend.


      Do you think a tool like this could help in way or do you think it's not necessary?

      0 points
      • Paul Gates, over 1 year ago

        Very hard for me to say. As I suggested, it's up to you and your team to iterate on what works best.

        In theory, an automated process that spits out diffs in design files at the right level of granularity could help your workflow. An integration on top of that with task-tracking software would be the obvious next step. That said, for me, this issue is mostly solved by having a focused, iterative working style with my team.

        0 points