The art of the client meeting starts with not taking a request at face value. If you write down “make the button bigger” exactly as spoken, you’ve only done half the job. Most requests that surface in a client meeting are symptoms dressed up as solutions. 1. Telling a Request Apart from a Problem The … 더 읽기

클라이언트 미팅에서 나오는 요청은 대부분 해결책으로 위장한 증상이다. 진짜 문제를 찾는 질문법과 회의록 정리법을 정리했다.

In design pricing, the problem is rarely the number itself — it’s that there’s no logic explaining how you got there. Price a project by the hour and the client is buying your time, not the result, so an hourly rate gives them no real way to compare one quote against another. 1. Price the … 더 읽기

디자인 견적을 시간이 아니라 산출물 범위로 설명하는 법. 수정 횟수, 리스크 반영, 견적서 체크리스트까지 정리했다.

In a product designer portfolio, the page people notice first is usually the one with nothing but polished final renders. A beautiful outcome only tells you the shape of the ending — it says nothing about how the designer got there, and that “how” is what hiring teams actually care about. Skip the in-between sketches … 더 읽기

채용 담당자가 진짜 보고 싶은 건 결과가 아니라 과정이다. 제품 디자이너 포트폴리오를 과정 중심으로 재구성하는 법.

Data visualization design lives in a permanent tug-of-war between two complaints: “this chart is so flat nobody’s eye lands on it” and “it looks great, but I can’t tell what the numbers actually mean.” Good data visualization is the discipline of carrying a number without distorting it while still making someone want to keep looking. … 더 읽기

The first time you see a brand pour a serious budget into a pop-up store that runs for three weeks, the math looks wrong. There’s no way to recoup that spend through on-site sales alone, and rent plus build-out never comes cheap. But the calculation changes the moment you stop treating the space as a … 더 읽기