Scale, and what's next Để bắt đầu bài viết, mình muốn chia sẻ 1 dữ liệu dễ hiểu thể hiện sự tăng trưởng của Tiki trong vài năm vừa qua. Đó là hiện tại, doanh số mỗi ngày của Tiki còn cao hơn doanh số ... cả tháng tại thời điểm mình mới tham gia
The hard thing 1. Truly understand the "why" Why should we adopt this new shiny language/framework/database other than that being ... well new & shiny ? Why should we adopt Scrum other than that being recommended by ... so many gurus ? 2. Care to ask "what else ?" Is this the
Làm sản phẩm 1 team nói chung (không chỉ team làm sản phẩm) sẽ bao gồm đối ngoại và đối nội * Đối ngoại là làm sao cho những team khác, những phòng ban khác hiểu được giá trị công việc của team mình, thấy team mình ngon (looks good), từ đó hỗ trợ
What does a product guy do I like to look at and structure things from different angle. In term of the product life cycle, a product guy needs to involve * before the product is made: he needs to evaluate thing such as * is this product/feature actually needed ? * how it will work ? * when it will be
Keep getting better People recently ask me about the product roadmap and while this is not a complete list, they're what I see as must-have in an e-commerce company Product/Tech must enable the company to do the following stuffs 1. Business as usual This means customer can use our website
Managing Product in a company-that-grew-up If it's just your personal project, your team, your startup then product management might be figuring out what customers love and iterate your product accordingly. However, in a company that grew up, these are the questions that I have to answer daily * How should I get people to
Feature versus requirement > One of the most common mistakes made on a project is to seize on a feature and call it a requirement without first understanding the problem and the expectations around a solution source [http://www.amazon.com/Project-Guide-Design-experience-designers/dp/0321815386/ref=dp_ob_title_bk]