Skip to main content

Posts

Showing posts with the label design

Getting into product management: Designer to PM

  Good news first - a designer is already a PM, a bit. Designers are driven by very much the same forces as PMs - find and solve customers' problems. Unsurprising that many designs are interested in switching to product management to have a greater influence on the overall product lifecycle. This switch, easier than from most other roles , still comes with several challenges, especially when it comes to business aspects of product management. 

Why all products are similar?

Have you ever wonder why most of the products look quite similar? All mobile phones are just plastic/glass/metal rectangles with a screen on top. All keyboards, however shiny, are qwerty-based. Or even Windows and macOS, despite cosmetic differences, are similar in core design principals. How come everything is so similar?   

Conversational UI, chatbot, AI - simply explained

Conversational UI, chatbot, AI are the concepts often misunderstood. This presentation aims to provide clarity for these popular technologies.

"Don't make me think" is not always a good user experience design

Simplicity was the mantra most UX designers followed in the last 10 years. " Don't make me think ," the iconic book by Steve Krug, popularized the concept of simplicity in digital product design. This concept helped a lot. To make computer interfaces actually usable for the broad audience. It's so easy today to order a cab, buy tickets online, find an answer to any question, connect with people around the globe, spend money... Is there a limit to simplicity or we should carry on simplifying any product?

User Onboarding

What is it? Why is it so important? And what are the examples of a winning user onboarding?

Conversion != satisfaction

"Sales" is a king! If they buy, if they "convert" - we're doing a great job! We're satisfied coz they're buying. They're buying so they must be satisfied! No, not always .

Don't do Design Sprint when

A Design Sprint is a structured, 5-day process to learn about critical business problems. Companies of different sizes use the Design Sprint to innovate, move faster and be more confident in their product investments. Yet sometimes a Design Sprint is overused, misused and wasted. Reason being the lack of the process understanding and lack of application experience. When shouldn't you use a Design Sprint?

The Design Sprint

What is the Design Sprint?  The sprint is a five-day process for answering critical business questions through design, prototyping, and testing ideas with customers. Developed at Google Ventures, it’s a “greatest hits” of business strategy, innovation, behavior science, design thinking, and more — packaged into a battle-tested process that any team can use. The entire process is described on this page: The Design Sprint I encourage you to travel through the links on this page to learn or refresh things related to discovering market problems, working out possible solutions, rapid  prototypes design, and testing with the real people.