Ask DN: Design handoff within your team

over 7 years ago from , Design at TrendyMinds and Official

We are always looking for ways to make our process more efficient. One topic which came up was how to best prepare for handing off projects to other designers. Being part of a relatively small design team, we occasionally share projects or pick up where another has left off, etc.

What documentation do you use? Do you maintain libraries of assets? How do you account for the knowledge outside of assets on a page, like design philosophies, strategy, and even the client's likes/dislikes?

Thank you!


  • Jeff HeatonJeff Heaton, over 7 years ago (edited over 7 years ago )

    I use the same file structure for every project I work on: - assets - libs - refs - src README.md

    • Assets are ready for dev consumption
    • Libs are libraries that i've used (wireframing sketch library, icon sets)
    • Refs are where all documentation lives. I share this with whoever is on the project so they get a sense of what's going on. It's where the design brief goes. Marketing drops their images of choice in here, etc.
    • Src is where all the PSDs, AIs, and Sketch files live. I keep one sketch file for every section of the app. New versions get documented in separate 'pages'
    • Readme works as an overview of the project/changelog.

    I've been wanting to implement some kind of Git for each iteration, but I haven't found a solution I like yet. If I move the team toward designing in the browser it may be more feasible, but I don't think we'll ever do away with Sketch files and the like. No reason to throw away good tools.

    For the library of assets across the app there's a /styleguide.sketch/. I'm toying with the idea of using (Lingo)[www.lingoapp.com].

    1 point
    • Bilal MohammedBilal Mohammed, almost 7 years ago

      Does this sit on the cloud? (I'm guessing you do user some sort of a cloud service)

      How to you manage its folder structure?

      0 points
  • brad wrage, over 7 years ago

    Jordan, over here at Udacity we currently use a combo of both invision for flows and zeplin spec. I do know invision is introducing the spec and asset exporting soon which will be great to be purely using one tool. We also have a sketch ui kit that is imported into zeplin for the larger or to reference. Obviously, I glossed over the details here, but hopefully gives you an idea of one of the stages.

    0 points