I am deisnger and I will provide design information.
디자인의 여러가지 이야기
A design retrospective is the first thing to get cut when a team is already racing into the next project the day after wrap. But a project that ends without one tends to repeat the same mistakes a few months later, followed by the familiar line: “didn’t we run into this exact thing last time … 더 읽기
Long before anyone agrees on the problem, a meeting has usually already produced three solutions. “What if we made the button bigger?” “Let’s just add one more onboarding screen.” Proposals like these get thrown out before anyone has settled what the actual problem is. Naming the problem is harder than finding an answer to it, … 더 읽기
The design sprint comes with a built-in burden: the name itself implies you need to clear your calendar for five straight days. Dedicating an entire team, Monday through Friday, to a single question is ideal in theory and, for teams juggling several projects at once, close to impossible in practice. But that doesn’t mean the … 더 읽기
Benchmarking is not the same as screenshotting a competitor’s onboarding flow and dropping it into a slide. Done properly, it’s less a survey of what other products did and more an inquiry into why they did it, and whether that reasoning holds up in your own context. Skip that question and benchmarking quietly becomes copying. … 더 읽기
No time for usability testing is one of the most common complaints on design teams. Booking a formal test lab, recruiting a dozen participants, and running the whole thing over several weeks understandably feels overwhelming. But usability testing doesn’t need to be that heavy. It’s a well-established finding in the field that just five people … 더 읽기
