menu

SpecFM

A network of designers and developers making the best podcasts, blogs, and resources for designers and developers.

Channels
Team

74: I Have a Beef With Entrées

October 12, 2017 at 5:59pm

74: I Have a Beef With Entrées

October 12, 2017 at 5:59pm (Edited 2 years ago)

Our main topic this week is: How to make sure what you ship is not a crappier version of what you envisioned. We also talk a bit about the #MadeByGoogle event and Libraries in Sketch 47.

🎧 http://layout.fm/episodes/74

Topic

  • What you ship doesn’t match your vision
Side dishesRecommendations

October 12, 2017 at 6:55pm

I really enjoyed this episode!! The new format with the main entree followed up by the side dishes and the dessert is great.

  • reply
  • like

October 13, 2017 at 6:36pm

Thanks Kevin! 🙌

  • reply
  • like

What do you think of the naming though? haha

  • reply
  • like

October 14, 2017 at 1:42am

The naming is great! :D also I definitely connected with the main topic. What gets shipped never looks like what I envisioned - there is always some technical constraint or a use case that I didn‘t consider which changes things up. Then there‘s the desin -> dev handoff which is never a lossy transformation.

  • reply
  • like

also, you guys breifly touched on “timeless design” which I haven‘t really thought too much about but I think I tend to not strive for that very much. Most of the time I’m just trying to solve a problem that currently exists and not think too much about a hypothetical one that might exist in the future.

like-fill
1
  • reply
  • like

oops i meant to say that design -> dev handoff always results in some information loss, that it IS a lossy transformation

  • reply
  • like
I agree with you Kevin information loss in that hand off process is usually pretty rough. The only time I have ever seen a handoff where it doesn't happen that way is when Design and Dev are working really closes on the solution through out the whole process. (Research, Design, Implementation) So both parties have full ownership over the original idea. The problem is that it rarely happens where I work. But when it does it's magical.
  • reply
  • like

Very interesting stuff folks.

  • reply
  • like

I personally like to try and think of a solution in the most abstract way that I can, so that it can live as an independent component in my UI, and not being too closely tied with the current context.

like-fill
2
  • reply
  • like

(timeless design is something on our topic list, spoilers)

  • reply
  • like

October 16, 2017 at 3:14pm

Just saw this! (Still struggling with Spectrum notifications 😅) I think you're right Alex. The only way to not loose stuff in the handoff is to avoid it alltogether. Working together from beginning to end has always produced better results in my experience

like-fill
2
  • reply
  • like

October 19, 2017 at 9:21pm

Hey guys, loving the show and new systematic structure of it!! Adding to the discussion of not feeling like a design is ever 'perfect', I relate to this very heavily. I feel more comfortable knowing that a seemlingly 'last' iteration doesn't really exist. Depending on the setting, especially in agencies, it feels as if your latest iteration has to align with the some ambigious 'perfect non-existent last iteration' that needs to be shipped. Extending on IDEO's Circular Design (https://www.circulardesignguide.com)—if you think of product design in a circular and iterable sense, it starts to feel more logical that there will always be room to expand. Your mind can constantly think one step ahead and plan for the next iteration of a product, but there will always be room to iterate further!

  • reply
  • like

Also for website feedback, it'd be cool if there was some way to navigate back to SpecFM to check out related podcasts in your network.

  • reply
  • like