Suggestions
Hsu Ken Ooi
Co-Founder and Managing Partner at Iterative
Hsu Ken Ooi is the Co-Founder and Managing Partner at Iterative, a startup accelerator focused exclusively on Southeast Asia.13 He has a diverse background in entrepreneurship and product management:
Career Highlights
- Founded Iterative in December 2018, which invests between $150,000 and $500,000 in early-stage startups56
- Previously served as Chief Product Officer at Workmate, an on-demand blue-collar staffing platform in Southeast Asia (2018-2020)36
- VP of Product at Weave (YCS14), a networking app for professionals (2014-2016)36
- Co-founded Decide.com in 2009, an early machine learning company predicting consumer goods prices, which was acquired by eBay in 201323
Education and Background
- Holds a Bachelor of Science in Mathematics and Statistics from the University of Washington3
- Originally from Penang, Malaysia13
Expertise
Hsu Ken Ooi specializes in startups, product management, and accelerator programs. He leverages his experience to mentor and support early-stage founders in Southeast Asia through Iterative's YCombinator-style program.45
Highlights
🤘 Join Iterative's Team – Marketing or Growth Lead
You will be part of the Recruiting Team at Iterative. The Recruiting Team is responsible for getting people to apply to Iterative. Unlike most investors, we accomplish this by (1) getting them to believe they can be successful starting a startup and (2) teaching them how to be successful starting a startup. We do this through a mix of content, events, programs, products and services.
You will report to directly to me.
🙋 Your Responsibilities
Customer Lifecycle Strategy – Create, execute, analyze and iterate on Iterative’s customer lifecycle strategy. We currently think about this in 3 stages: acquisition, nurture and conversion. Figure out how to attract people interested in startups, nurture them in their startup journey and when they start a startup, get them to apply to Iterative.
E-Mail Marketing– To execute on your customer lifecycle strategy, you will be responsible for creating, executing, analyzing and iterating on our e-mail marketing strategy. We currently have roughly 6,000 e-mail subscribers.
Social Media – To execute on your customer lifecycle strategy, you will be responsible for creating, executing, analyzing and iterating on our social media channels. We’re open to expanding into other platforms (Instagram, TikTok, etc.) but ultimately that will be your decision.
Support for Internal Team – Since you’re the first marketing hire, and are responsible for our primary distribution channels (e-mail and social media), you will also be responsible for supporting team members who need to market their initiatives.
Support for Iterative Startups – Occasionally, you might be asked to support a startup that Iterative has invested in. Typically, these are one off phone calls where the founder needs to talk to someone with specialized knowledge and experience to solve a problem they have.
🥹 Who You Are
Comfortable with Ambiguity – Just like at a startup, you will be asked to do something without clear instructions on how to do it because no one knows. It will be your job to figure out whether we should do it and how to do it. We’re looking for people who don’t need a step by step guide. They are the ones that make the guides.
Product Development Process – Since our experience is building companies and products, we run Iterative in a similar way. It will be beneficial to have exposure to the product development process (requirements, sprints, etc.).
Metric Driven – Comfortable measuring the efficacy of all their initiatives. Iterative is a rigorous organization that is constantly evaluating whether we’re working on the right things and demands that we learn from everything we do.
Experience as a Manager – You will be responsible for managing and developing a team of people with diverse experiences and expertise.
If that sounds interesting, find the 📌 in the comments to apply. If you know someone that might be a good fit, tag them in the comments.
🧠 What Users to Focus on When Building Early Stage Products
An Iterative Founder asked me the following questions via e-mail this morning. After writing my response, I thought they might be interesting to others so posting I’m posting it here.
What should inform future product development, insights from: 1) Power users, who engaging deeply with the product, but make up a minority, or 2) Core users, who don't engage as often as power users, but make up the majority?
You’re optimizing for usefulness which is # of people who used the product multiplied by the usefulness each person receives from using it. The strategy for optimizing it is to figure out who finds it’s very useful and why then find as many of them as possible. Once you exhaust that group, you find the next group who maybe doesn’t find it as useful but still pretty useful and get all of them. Rinse and repeat.
Should our goal be to cultivate more power users, thereby increasing engagement per user, or to expand the overall user base? Considering our objectives of 1) encouraging more people to become founders, and 2) helping founders be more effective, one argument for power users, due to their engagement, is they are both more encouraged to become founders and more effective as founders.
Related to the above. If you’re optimizing for usefulness, you should do whatever has the highest ROI. If your product isn’t very useful to people, you should probably work on usefulness per person (engagement, NPS, etc.). If your product is useful but not very many people use it, you should probably work on getting more people to use it. It takes increasingly more work per unit of usefulness if your product is already quite useful.
How do you build a product without full visibility into data? More and more, I'm feeling the urgency to take the first month of next cycle to work on systems, processes and maintenance.
Vibes. Just kidding.. but less than you think. This is where understanding your users (motivations, pain points, etc.) is so important to people working on very early stage products. Understanding your users builds your mental model of what they want, you build lightweight versions of those things, use the data they generate to verify the mental model.
Don’t spend the first month on systems, processes and maintenance. That isn’t going to help you and there’s a hint of fear in it. Instead, build a mental framework based on what you know about your users and spend the month experimenting to verify your framework. Build systems and processes after you know your mental framework is reasonably correct. If you build it before then, there’s a chance you’ll have to throw it all away anyway.
If you have other product questions, leave them in the comments. I’ll share what I think but maybe other people have better answers too.
