I recently shared content about Product Thinking during an event and this mindset is changing the way I’m looking at Projects and Products.

There are great articles out there about Product Thinking, like this one, but no canvas that brings together all the main questions Product Thinking focuses on.

With that being said, I took a stab at it and created one (there is a tiny possibility others are looking for something like this but never found it).

The result you can check below:

The Product Thinking canvas tackles user first (problem + target audience) followed by job to be done (vision + what you can do with our product + strategy) and finally the goals to be achieved and which features will ensure the product meets them.

The heart of the canvas is: what you can do with our product because this sentence impacted me profoundly:

“Here’s what our product can do” and “Here’s what you can do with our product” sound similar, but they are completely different approaches.

— Jason Fried (@jasonfried) November 13, 2013

As an example to materialize this sentence, we can state that Uber is not providing an app; it’s providing the possibility of connecting riders and drivers, anywhere, anytime.

Along with the fact that Product Thinking focuses on resolving real problems, it also opens up the opportunity to build products that can help us faster, that have the ability to know us more and surprise us whenever possible.

I hope this post inspires you to research further about Product Thinking and empower you to build more human-centered, product-oriented and business-relevant products.

One of my favorite parts of the PM job is to search and try new and fun ways of conducting Sprint Retrospectives. =]

Sprint Retrospective is an opportunity for the team to inspect itself and create a plan for improvements to be enacted during the next Sprint.

Continue Reading

Django built-in migrations were designed as a way of propagating the changes you make on the models to the database. Migrations exist mostly to keep your code in sync with your schema and to provide a good way of versioning it. We just need a couple of commands to get our apps up and running with an updated version of our database, or not.

Continue Reading

Picture this: 5 people talking about the same subject in different languages. What are the chances of misunderstanding? As you can imagine: a lot. Well, this is a common scenario in software development teams up to some point. One of the most common reasons that lead to failure when building a product is the lack of well defined goals and requirements amongst developers and stakeholders. This can be caused by a wide variety of reasons. But it is safe to agree that most of them are due to lack of communication.

Continue Reading

This post was originally written as an internal article on Cheesecake Labs’ wiki. It merges (no pun intended) pull request practices from many different cultures and backgrounds into a definitive workflow. We will discuss why you should have a guide for managing your PR lifecycle, as well as tips on how to accomplish that.

Continue Reading