While Google may be getting better at indexing Javascript content, it turns out that it still takes quite a while in some cases. In this article on SEJournal, Tomek Rudzki presents eye-opening data on the average time Googlebot needs to …
A Product Manager at a startup has to typically deal with 3 main phases – formation, validation and growth. And each of these phases has their distinct requirements. In this enlightening article by Vivek Lakshman, VP Innovation @ Pramati Technologies, …
One of the most fundamental reasons as to the requirement of a Product Management function is helping build product that customers need. And to do that Product Managers themselves need to be attuned to making that happen by understanding users …
As a founder / product leader / marketer – the biggest thing you can do to yourself and your business is to understand that you are biased.
Biased based on your life history, based on where you are, the context, your version of future etc.
This master list of cognitive biases is something you gotta keep visiting very frequently to really gauge where you are and what your biases are.
Cognitive biases are systematic patterns of deviation from norm or rationality in judgment, and are often studied in psychology and behavioral economics
Kevin Systrom and Mike Krieger, the co-founders of Instagram share a few great insights on how to build great products and how Instagram evaluated / prioriotized features.
Reading is a habit that every Product Manager should inculcate – considering how multi-disciplinary the field is, and not to mention how quickly things change and move in today’s world. If you’re worried about what to read – fear not! …
As Product Manager / Founder, one is expected to understand the journey of taking a product from an idea to market and all that it encompasses: hypothesis, prototype, validation, testing and importantly, dealing with organization-wide coordination. Having a clear understanding …
Ever since Product Management has gone from relative obscurity to greater spotlight over the past decade – owing to the rise of tech companies – there has been confusion about the typical Product Manager’s career path. From experienced Product Managers …
Movie trailer expert, Jessica Fox, deep dives into five movie trailer styles and explains what makes a trailer successful. Using movies like ‘Us,’ ‘Inception,’ ‘Little Women,’ ‘Sex and the City,’ and more, Jessica explains how narration, an established landscape, repetitive …
Great talk by Rajiv Bajaj, Managing Director of Bajaj Auto. This is pretty much 2-year MBA compressed in this 55 minutes talk. Watch the keynote if you still believe that building a great product = guaranteed successful business (hint: it …
How should one go about doing product management for AI – based products? As AI continues to grow in acceptance and use, more companies will require fine tuning of product strategy and the importance of AI product managers will become …
In this video, Brian Lawley, author of Product Management for Dummies, provides a simple framework with which you can prioritize features clogging up your product backlog with 3 easy steps. It consists of a four quadrant matrix that stacks up …
In this video by Henrik Kniberg, an agile coach at Crisp, he explains what Product Ownership truly means in an engaging animated video. Going over the aspects of vision, communication within the team, risks involved (business, social, tech, cost & …
When Steve Jobs was brought back to Apple, he applied 30% rule to create a flywheel. —- We examined the future product roadmap … and what we found was that 30 percent of them were incredibly good. And about 70 …
Adopting dark mode is all about setting a new set of colors.
For most apps, adopting dark mode is a process of replacing your static color to a dynamic one.
Let’s say your app has a white background, and you want to adopt dark mode. You open up Asset Catalog, create a new color set, and put white and black colors for each appearance. You might end up with something like this.
There are four core sections of a PRD — defining purpose, describing features, setting release criteria, sketching rough timing.
According to Marty Cagan, the PRD’s goal is to explain the “What”, not the “How”. In each section, remember to be clear on the problem being solved versus the solution otherwise you may lead the team to make incorrect assumptions.
The engineers, designers, and UX folks are the ones designing solutions for the product — don’t piss them off by making the PRD a recipe rather than a guideline.