Subscribe
Sign in
  1. Discussions
  2. Post-launch of your very first product, how did you guys...

Post-launch of your very first product, how did you guys iterate?

Evan Christopher
6 replies
Hi PH Community! After launching, (1). how do you iterate on your very first product? Do you follow a regular process like getting feedback, compiling it, prioritizing the most urgent issues, ideating the best solutions, then moving on to design, testing, and development? Or do you have a different approach? (Esp for a SaaS tool) Also, (2). do you have a set timeframe for each phase, like "okay, this is enough of a problem cause it's alr X days", or like "okay, it's time for designing cause it's alr X days of prioritizing & ideating solution", etc.? Let’s discuss your experiences about this matter!

Replies

Allan
Aiswers.com
Aiswers.com
I guess it depends on the nature of the product. For our website, we have a long list of requirements need to be done, so we set a fixed weekly iterate inverval. But for other products, I think it needs on the complexity, I see a lot of products don't iterate after launch and a lot of products doesn't have fixed iterate period.
Share
Evan Christopher
@allan_ryl cool! Before you got those reqs, how are your approach to that? Is it the same like the nature of ‘design thinking’ method as I mentioned above? Do you always do design test everything you release a new feature (except maybe bugfix)? Anyway, thanks for sharing Allan.
Share
Ksenia Meshkova
Love your discussions! Read everything, it really suits my current interests , thanks!!
Share
Christopher Anderson
1. We iterate based on user feedback and analytics. Identifying the top pain points or requests, then designing and testing solutions. Repeat. 2. No strict schedule, it's fluid based on urgency and impact. Fix critical issues ASAP. Give enough time to design good UX. Ship quality over arbitrary deadlines. Worked well for our SaaS so far!
Share
Evan Christopher
@christopher_andersona nice insight! Thanks for sharing Christopher. Curious about your testing approach, how do you test Christopher? Are you inviting users to 1o1 UT or just implement Beta Test at your app, and inviting user e-mails into it, and wait for them to try, and leading them to give feedbacks?
Share