Jason Spidle

Minneapolis, MN Full Stack Designer Joined about 8 years ago

  • 2 stories
  • 21 comments
  • 20 upvotes
  • Posted to Agency Juice issue 06; The ramblings of a Creative Director, Feb 19, 2020

    Just wanted to say that I always enjoy these missives and I really dig the format, coming from an agency myself. Indeed, once I figure out a good name for our version of Agency Juice, you can look forward to reading it on a Foundry blog near you.

    1 point
  • Posted to Site Design: The New Poolside.FM, Jul 26, 2019

    Definitely made me happy.

    2 points
  • Posted to Pseudo Design Titles, Mar 26, 2019

    I pressed the refresh button at least 50 times, laughed 14 times, and took 15 screenshots. Well done.

    1 point
  • Posted to How do you document the design environment?, Mar 19, 2019

    Tacking onto this, one thing we've just started to do is use Wake throughout the day to share in progress design. The thinking is that by sharing design, everyone on the team will be more grounded in how the design is evolving and if they end up needing to work on that project, they'll come in with some knowledge. Before, each person on our team was kind of in a silo, unfortunately.

    In any case, anyone else have experience with Wake? It seems dormant so I worry that it isn't a long term solution. Are there better tools for design teams to easily share in progress design directly from Sketch. That workflow is crucial to adoption...

    0 points
  • Posted to How do you document the design environment?, in reply to Sylvain Maretto , Mar 19, 2019

    Definitely a good point. I guess I wasn't super clear about my primary goal in my post. The biggest issue I've been running into is that our design team has went from just myself to me + two other designers that I manage. When switching between projects, we're all having difficulty knowing which plugins were used, if there is some kind of standardization in file naming and grouping practices, if there is a grid and when is it okay to deviate, etc.

    0 points
  • Posted to How do you document the design environment?, in reply to Sylvain Maretto , Mar 19, 2019

    This wiki is excellent! Thanks for pointing it out to me.

    And yeah, the Deliveroo article isn't really covering the same topic. It was more trying to show that I did do some research and this is about as close as I found...

    0 points
  • Posted to How do you document the design environment?, in reply to Nelson Taruc , Mar 19, 2019

    Thanks for sharing. Definitely understand that without a killer tool that nails this problem, it'll vary a lot from team to team. Do you match developer preferences on files to expedite dev?

    0 points
  • Posted to How do you document the design environment?, in reply to Artur Eldib , Mar 19, 2019

    One can dream

    0 points
  • Posted to How do you document the design environment?, in reply to Andrew Ciobanasiu , Mar 17, 2019

    No worries, that was definitely a useful post with some overlap. That Nathan Curtis post seems super useful and I definitely have been eyeing Abstract. The more people encourage it, the easier it might be to convince everyone else. I just wonder how easy or effective it will be trying to convince other designers on my team to make commits and pushes, etc.

    1 point
  • Posted to Simplifying Client Communication - How?, Dec 06, 2018

    I haven't yet had an opportunity to use it but Tapwater looks really nice and it seems to meet most of your needs.

    0 points
Load more comments