This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
Being a Product Manager at an Early Stage Startup In my previous article , I reflected on a few things that I would tell myself if I could travel back in time and the concept of “three waves of changes.” In this post, I want to talk about the three most important lessons I have learned so far as a Product Manager at a startup.
This is a guest post from Dillon Forest, cofounder, CTO & product manager at RankScience. One litmus test for this: if you’re working on your product and you hit a roadblock, and you can’t find a satisfactory answer to your question on Stack Overflow. Do some user research. Make some mockups.
One of those niches that’s become more valuable in recent years: product analytics. As data-driven product development continues to balloon in popularity, so does the need for accurate and sophisticated implementation of analytics tracking in softwareproducts. Spearhead a slick analytics implementation.
Product analytics is an ongoing effort. As new features are added to your products, so should new analytics events be added to your codebases. When engineers implement features, they write code. When engineers add analytics events to new features, they add additional analytics code to their new feature code.
FUN FACT: It is actually thanks to the coaching service for innovative and technological SMBs (PMEit) administered by MAIN that we’ve been able to work with some of our incredible clients, Wastack , LiveScale , Blaise Transit and Enkidoo , and provide them with product management, consultancy and coaching support. Are you a product manager?
I’d be interested in other products that tap into the trends around AirPods, Alexa, voice assistants, etc., It could create a strong advantage around paid marketing if a product has high subscription retention or ARPU, allowing them to make higher bids in the various ad networks. but may not directly sound like podcasting. Podcasting?
I’d be interested in other products that tap into the trends around AirPods, Alexa, voice assistants, etc., It could create a strong advantage around paid marketing if a product has high subscription retention or ARPU, allowing them to make higher bids in the various ad networks. but may not directly sound like podcasting. Podcasting?
We organize all of the trending information in your field so you don't have to. Join 96,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content