
Sign up to save your podcasts
Or


There are many prioritization strategies available for choosing the next features/experiments for our product… but how do you decide which one to use?
Is there a moment in time for doing product discovery?
Best product teams are cross-disciplinary, small, and autonomous. Their composition varies from company to company and from project to project and yet they have a set of essential characteristics in common.In this episode, we discuss what is a product team, what makes it different from “classic” teams, and which are the main skills needed for a successful product team. These abilities translates into different roles depending on the company or the product:
Last but not least, we talk about Product Trios: a model for collaborative product leadership that represents the intersection between the 3 key disciplines in product:
_____________
How do you frame the first iteration/s of a product or feature? How do you decide where to start building it? We like to use the ICE scoring framework to help us prioritize our ideas based on Impact, Confidence, and Effort.
Lean is all about learning 🧠
Instead of committing to our ideas, first, we want to learn if the assumptions we are making about them are actually true!
Will the users really want it? Will it generate the impact we expect? Setting up rapid and continuous experiments lets us move forward faster and reduce risk!👩🏽🔬 🧑🔬
In this episode we explain how to design and plan experiments: from defining the hypothesis, to setting up both success and failure metrics and finally, measuring the outcome.
We also explain the most popular Lean Experiments:
In this episode, we have our special guest Natasha that explains to us how the world can be interpreted as linear and organized, or volatile and ambiguos. Also, together with her we discuss how the triple diamond model helps us navigate the complexity and ambiguity of this world when finding solutions to complex problems.
Is our world as linear, causal, and based on rational decision-making as we might deem it to be? The traditional understanding of the world perceives humans to be rational and logical 24/7, as well as reality to be a “clock world”-- easy to figure out and simple. But, our world is not like that: we live in a VUCA world… Volatile, Uncertain, Complex and Ambiguous… a “cloud world”: highly irregular, disorderly, and more or less unpredictable.
Our new understanding of the world needs new principles, and these are ours:
In more practical terms, we work with the TRIPLE DIAMOND: understanding latent user problems and needs (“doing the right thing”); building the right solutions to solve these problems (“doing the thing right”); and, this way, reducing waste and maximizing value delivered using techniques like Lean startup or Scrum.
Our biggest learnings come from failures, right? To see our work in practice, we are going to present and analyze a real DocPlanner project that did not go so well mainly because it underestimated our new principles, as well as skipped triple diamond steps. In addition, we will look back and discuss best practices: practices we would apply if we faced this project again!
“If we would only spend a bit more time on this feature before release, we could make it just perfect”... does this sound familiar?
And yet when building digital products, we work with MVPs and small improvements. Why is this better than working on more finalized features?
As startups, we are trying to figure out what’s the best thing to build as quickly as possible. That’s why early products are not meant to be perfect… we are in constant experimentation!
In this episode we talk about Lean Startup, the scientific approach proposed by Eric Ries in his book: “The Lean Startup: How Today's Entrepreneurs Use Continuous Innovation to Create Radically Successful Businesses”
We explain why Startups need a specific approach to creating products. We give an introduction to the Lean Canvas and we cover in detail the Build - Measure - Learn loop:
Agile is not easy for UX design. It was created to address developers' pains without considering the designers.
There are different ways to inject the design process into Scrum, as the Dual Track, but in the end, this creates a small waterfall that stops us from being really Agile.
In this episode, we talk about Lean UX, the framework that has helped us to really be Lean and Agile taking into consideration the UX Design process.
Lean UX is a combination of Lean Startup, Agile, Design Thinking, and UX Design. It transforms the UX Design process into a fully collaborative one where the whole multi-disciplinary team takes part in the UX Research and defines and co-creates the solutions together.
The deliverables and documentation are replaced by communication, common understanding, and collaboration; and instead of focusing on outputs, now the team works based on outcomes.
The UX research is embedded inside the team, with the participation of all the team members, building increasing knowledge, understanding, and empathizing our customers. We talk about tools like Proto-personas and weekly interviews.
We explain how the UX designer takes the role of a design facilitator, making the design process more collaborative with whiteboards, workshops, Design Studio sessions, or Design Sprints.
This process, together with a UI Kit or Design System, allows designers and developers to work simultaneously and in parallel to be really Agile.
Metrics help us make better product decisions and evaluate how good our choices are. They guide us to our goals and show us how we are moving towards them. Metrics reflect the health of our business as well as the behavior of our users.
In this episode, we get into the detail of how should metrics be: user-centered and actionable, so they don’t become vanity metrics.
Tune in to discover the list of the most popular ones explained with examples. As promised, here’s the list of the ones mentioned in the episode:
We invite you to continue the conversation and give us feedback!
From having an idea to executing it, there is always a process: ideas are vague, full of questions to be answered and decisions to be taken. We also have limited resources to carry them out so, how do we move from ideas to action?
We invite you to continue the conversation and give us feedback!
From the publisher's feed