April Martin’s Post

When launching a new product, you always want to optimize for the problems you want to have, like your customers succeeding quickly and always wanting more. This is a commmon mental model I provide product teams I lead or work with when it comes to prioritizing features and whittling down an MVP. Whatever you launch with will have more gravity than you think and needs to be “enough” - but you can delay the enhancements happy customers will want over time. I liked this graphic I came across a few times that adequately visualizes what I’m trying to say:

When launching a new product, you always want to optimize for the problems you want to have, like your customers succeeding quickly and always wanting more. This is a commmon mental model I provide product teams I lead or work with when it comes to prioritizing features and whittling down an MVP. Whatever you launch with will have more gravity than you think and needs to be “enough” - but you can delay the enhancements happy customers will want over time. I liked this graphic I came across a few times that adequately visualizes what I’m trying to say:

When launching a new product, you always want to optimize for the problems you want to have, like your customers succeeding quickly and always wanting more. This is a commmon mental model I provide product teams I lead or work with when it comes to prioritizing features and whittling down an MVP. Whatever you launch with will have more gravity than you think and needs to be “enough” - but you can delay the enhancements happy customers will want over time. I liked this graphic I came across a few times that adequately visualizes what I’m trying to say:

When launching a new product, you always want to optimize for the problems you want to have, like your customers succeeding quickly and always wanting more. This is a commmon mental model I provide product teams I lead or work with when it comes to prioritizing features and whittling down an MVP. Whatever you launch with will have more gravity than you think and needs to be “enough” - but you can delay the enhancements happy customers will want over time. I liked this graphic I came across a few times that adequately visualizes what I’m trying to say:

When launching a new product, you always want to optimize for the problems you want to have, like your customers succeeding quickly and always wanting more. This is a commmon mental model I provide product teams I lead or work with when it comes to prioritizing features and whittling down an MVP. Whatever you launch with will have more gravity than you think and needs to be “enough” - but you can delay the enhancements happy customers will want over time. I liked this graphic I came across a few times that adequately visualizes what I’m trying to say:

When launching a new product, you always want to optimize for the problems you want to have, like your customers succeeding quickly and always wanting more. This is a commmon mental model I provide product teams I lead or work with when it comes to prioritizing features and whittling down an MVP. Whatever you launch with will have more gravity than you think and needs to be “enough” - but you can delay the enhancements happy customers will want over time. I liked this graphic I came across a few times that adequately visualizes what I’m trying to say: