為什麼我建議 UX/產品設計師學習寫程式?

我一直想要寫這篇文章。

一方面因為我認為在設計的路上 coding 真的讓我受益匪淺,另一方面是學 coding 直接導致我架了自己的網站,然後跌跌撞撞踏上設計這條路。

這篇文章是一篇心得統整 — 以 UX/產品設計師的角度,分享寫程式為我帶來了哪些好處。我主要整理了三點:設計效率、更多接觸不同東西的機會以及溝通能力

先強調一下,我認為會寫程式不是產品 …

--

--

--

--

Great article. Valuable insights on the matter of design management and very practical.

I myself tried to build design system three times in 2 different teams and the results were all a mixture of success and failure.

A design system is difficult to build and nearly impossible to maintain properly especially when you are dealing with complex customer facing products in a company with multiple stakeholders.

The amount of time and energy it take is just not worth it and it at best can be treated as a hi-fi mockup tool.

However, the process of making the design system does bring about learnings and does synthesize design ideology and logics within the team.

Maybe thinking holistically about the design, having reoccurring retrospect, documenting the proper structure and UI state are where the value truly lies in Design System.

--

--

特別想討論一下「對設計師需求愈來愈高,甚至沒有產品經理」的這個趨勢。

我前幾週也看到一篇文章在討論這個問題,好像是個印度的產品設計師。他做了一個簡單的調查,發現自己身邊的很多設計師的職責範圍也跨到產品經理的部分了。

我現在的工作模式也是沒有產品經理,設計師負責全部的東西。

我自己感覺雖然這樣需要負責的事情多了,但似乎更合理一些,因為設計師才有最大的誘因與足夠的能力去產出一個好的產品。

我想如果公司的產品本身不需要太多對於市場的理解,也沒有太多資源分配的問題的話,也許真的不用產品經理帶領產品團隊,只需要設計經理統管設計師,然後顧更多設計師、研究員去負責更細的產品Feature就好。不知道這會不會變成一個趨勢呢。

--

--

Hi there, thanks for the nice article!

However I think group has its place to stay.

It allows more intuitive control over the elements, for example, you don't have to worry about dragging an element out of the frame it belongs to. Also it is a pain in the ass when there's frames in frames in frames.

Besides, personally I think the resizing issue you mentioned is over-rated because we would have dedicated frames/variations for different width to demonstrate the behavior.

I agree that when there's extra time or the elements are going to be massively reused, making everything in frame is best practice, I do that as well. But groups are more handy in the process and not using it altogether may create more problem than it solves.

--

--