A few things I’ve learned that can help you with Digital Products

Over the past years…

Over the past years, I’ve learned a lot about building beautiful international products that hopefully people love. Some products have taken off. Some have failed terribly. However, more often than not, my learning came from mistakes as I worked on a bunch of web and mobile products. Most of my expertise comes from working with a small team rather than large companies but these learnings apply to both.

Focus on simple and hide the complex

Try to keep things simple. This doesn’t just mean the simplicity of a feature, but also the product itself. Every feature has a learning curve to it. Features that extend beyond core functionality shouldn’t be key parts of the experience. They could be hidden in the settings or deprioritized in the UI.

Prioritize the features

Sometimes we get caught trying to make an extra amazing feature and we spend a lot of time. The reality is that way often this feature will not drive mass engagement. Is more a scenario where just a few people will impact.

I’ve learned to prioritize features that contribute to primary business goals. These features are actions that take place during or shortly after the user is onboard. Features that are more focused towards experienced users have their place, but they won’t be something that everyone uses.

If you are sinking, get feedback. Feedback is oxygen

Until you don’t show something, you don’t know how people will react to it. Iterating with a black box in front of real users or investor can be dangerous. Launch what you’re building and get test users engaged. Yeah, will require time to make this offline interviews and interactions but is time you will save later. Don’t worry if your product doesn’t look that pretty, for startups, done and functionally is better than perfect. A perfect example is saying that an iOS team can work and ship independently of their Android team.

Divide and conquer.

Is easier to do 10 small tasks (and feel rewarded for finishing all) rather than finish one huge task (and get stressed). I like to break big features down into smaller components and then prioritize those components to get us from zero to a completed feature. I’ve found it helpful as a way to release things faster and provide more


By Carlos Lastres

Tagged with: