Suggestions
David Pereira
Product Coach, Book Author, Keynote Speaker
David Pereira is a dedicated Product Leader with a wealth of experience in product management, specializing in driving teams towards delivering high value and impactful solutions. With over a decade of experience, David has successfully led multiple product teams through significant growth and innovation projects.
Throughout his career, David has achieved remarkable milestones such as exponentially growing marketplaces, innovating markets like the secondhand car industry in Brazil, and revamping route planning systems to generate substantial cost savings. His mantra revolves around the idea that the quicker we learn, the faster we succeed.
Apart from his professional endeavors, David enjoys writing articles and sharing his insights on platforms like Substack, Untrapping Product Teams, and LinkedIn. He finds joy in continuous learning and engaging with a diverse community.
David's educational background is extensive, including studies in Master of Business Administration with a focus on Entrepreneurship and Information Technology. He holds a Bachelor's degree in Computer Science and has complemented his formal education with specialized courses in software engineering and industrial information technology.
Throughout his career, David has held various key positions in organizations such as Miro, omoqo GmbH, Virtual Identity, limango GmbH, Universidade Anhembi Morumbi, FIAP, evino, Instacarro.com, Ability Trade Marketing, and more. He has also leveraged his expertise in roles ranging from product management to software development and teaching.
In summary, David Pereira is a seasoned Product Leader with a proven track record of driving successful product initiatives, coaching teams for optimal performance, and contributing thought leadership through his writing and community engagements.
Highlights
Good product teams look reckless.
How they act is counterintuitive. They:
- Don’t know everything upfront
- Skip more meetings than most people
- Reject creating a detailed plan
- Write high-level backlog items
How can they ever succeed with such a crazy attitude? Let’s break it down
1 - Don’t know everything upfront
. Instead of discussing the work, they aim to get hands-on fast . Understanding the context is more important than knowing every step . Knowing where to start is what unlocks progress . Doing the work over discussing it is the ultimate principle
2 - Skip more meetings than most people
. Focus on solving issues instead of scheduling meetings . Mindful about each other’s time . Micro-interactions over meetings with passive participants . Don’t accept meetings unrelated to what they aim to achieve now
3 - Reject creating a detailed plan
. Once they know the big picture, they only want to clarify the starting point . Recognize that unknowns will emerge on the way . Bias toward action instead of speculation of what they don’t know . Understand that no plan will be correct; execution is what matters
4 - Write high-level backlog items
. Context is what matters most, not details . Backlog items are reminders of conversations, not requirements . When refining the items, they add relevant information, not solutions . The items relate to the problem space, objective, and learnings
— If you like this content, my book Untrapping Product Teams will speak to you. It's available now at Amazon and your favorite bookstore. Get it to level up your product game.
Shall we rock it together?
Dealing with complexity can be troublesome. Yet, small steps can help you out. Here's how pilots can help you gain support to progress.
Read this episode of Untrapping Product Teams to gain more insights: https://lnkd.in/dShQigSm
Here's the summary of 8 Steps for implementing a pilot project:
-
Find a problem worth solving Identify something valuable enough to drive change. We identified the inaccurate inventory.
-
Define a compelling objective Commit to a goal that matters. We challenged ourselves to reduce inventory errors from 10% to 1%.
-
Agree on the investment Pilots come with a cost, and you need to clarify whether you can get approval.
-
Set the pilot timeframe Pilots run for a limited period. Define how long you need to prove whether progress is worth making.
-
Run the pilot Observe how the pilot project operates in production. Be as close as possible to it.
-
Measure results Continuously evaluate the results. Strive to understand where the pilot is going and be open-minded to uncover potential improvements, even if that requires a pivot.
-
Iterate Your first pilot version probably won’t cut, so you have to adapt to what works as you envisioned.
-
Decide As you reach the end of your pilot, you need to decide whether it was a success or failure. Be objective and make the call.
Subscribe to Untrapping Product Teams to gain weekly insights for free. Shall we rock it together?
