Laurent Leca

openai just released a 𝗽𝗿𝗼𝗱𝘂𝗰𝘁 𝗽𝗿𝗼𝗺𝗽𝘁 𝗽𝗮𝗰𝗸 25 prompts for product managers. they’re not meant to be copy-pasted. the real value is using them as a starting point and adding • your product + company context • your tone of voice • an example of the output you expect otherwise it’s just another generic prompt. link in comments.

331

19 commentaires

With the advent of AI tech challenged PMs will soon become history. However, most intro to tech for product managers ends at (REST) APIs over HTTP/HTTPs, let's now talk about so many other ways in which client and server can interact. What is an API - well the most simplistic but clear explanation is it is a URL/endpoint that gives you raw data that you can munge as per your requirement. This is the classic request, response model. The client requests, the server responds. There are more options here in the request, response model eg. there is the newer GraphQL rather than REST and then there are Remote Procedure Calls in the new avatar gRPC. However, I digress. Let’s switch gears. If you follow the simple Socratic way of reasoning you can easily think of scenarios where the request-response model doesn't work. All you have to do is look around. Example there are very common scenarios where a server would like to push updates without waiting for client to seek anything. Still unsure? ***Think Chat Apps, collaborative editing such as Google docs, multiplayer games***. In fact in all these cases you want the client and server to push updates to each other at any point of time in a bi-directional manner. ****For this the classic rest APIs don't work, what you need are Websockets.**** Never heard of websockets, well time to upgrade. The above example is bidirectional communication. What are the other possibilities - well think of scenarios where it is the server pushing updates to client in one direction. You ask what are these scenarios. ***Well here are some - Live News, Sports scores, Stock tickers*** In these scenarios all you want is client establishing a connection and server pushes information whenever it has a new update. The client doesn't request data every single time. ***This paradigm is called Server Sent Events/SSE**** If you think more there are lots of other scenarios such as 1:1 video streaming, broadcast streaming etc which have other paradigms which we can cover in a subsequent post. My Playbook - https://lnkd.in/gHzyN-Xc Follow me https://lnkd.in/gHweK_q7 AND https://lnkd.in/ggUKftFq To learn more about tech holistically - https://lnkd.in/gkrJ8MZu

57

4 commentaires

PROTOTYPES ACCELERATE DISCOVERY, NOT DELIVERY Prototypes are powerful tools for the discovery phase — helping teams quickly explore product directions, validate concepts with customers through high-fidelity experiences, and align executives around tangible visions. The leverage they provide in answering "what's the right experience to build?" is remarkable. However, I frequently see PMs expecting to hand prototypes directly to engineering teams for production implementation. This approach consistently leads to disappointment. Here's why: prototype code isn't built to meet the security, reliability, robustness, and maintainability standards that production systems require. Your engineering team rightfully prioritizes these critical attributes. And that's perfectly fine. The value of prototypes lies entirely in discovery. Even when engineering teams ultimately rebuild from scratch, prototypes have already delivered tremendous ROI by: - Accelerating team alignment on product direction - Validating customer demand with realistic experiences - Securing executive buy-in through tangible demonstrations The code was never meant to ship — the insights were.

54

8 commentaires

If you do this, you’re the worst kind of Product Manager. A customer starts explaining a need, and before they finish, you cut them off: “We already have that! Let me show you…” They describe a problem, and you jump straight to: “Here’s how you can fix it…” They share negative feedback, and you rush to defend: “We did plenty of research…” Here’s the problem: When you respond too quickly, you trap yourself in your own interpretation of what they meant. Great Product Managers slow down. They ask: • “Tell me more about when this happens” • “What impact does this have on your workflow?” Because once you understand the context, everything changes: Customers feel heard. They open up to your ideas. They trust your judgment. They see you as a partner, not a vendor. This isn’t just Product Management. It’s basic professional etiquette. Listen first. Probe for clarity. Then respond. Better outcomes follow always. #productmanagement #customerservice

64

12 commentaires

After 10 years of building Productboard, we're shipping something that feels like magic: an AI agent built specifically for product management. Here's the thing—product teams are drowning in context. Customer feedback lives in 12 different tools. That brilliant insight from last quarter? Gone when someone leaves. And you're still making calls based on vibes instead of the full picture. Generic AI tools? They're helpful until the conversation ends and they forget everything. Spark is different. It lives in Productboard. It remembers. It knows your customers, your product, your strategy, and it gets smarter as your team does. What you can do right now: → Generate PRDs that pull from your actual customer data → Turn messy feedback into clear, lasting insights → Keep competitive battle cards fresh without the manual grind This is organizational memory that actually sticks. Context that doesn't disappear. Clarity without the chaos. #ProductManagement is about to get a whole lot more fun. Ready to try Spark? Join the beta: https://lnkd.in/grDPp_xQ #ProductManagement #AI #ProductDevelopment

217

4 commentaires

People often describe the Product Manager as the “GM of the product.” I’m not sure that’s quite right! You’re not the CEO. You don’t have direct authority. Instead, you sit at the center of a complex web of stakeholders: - Engineering - Design - Go-to-market - Customer success - And, most importantly, your customers Your job? Be the hub of clarity. That clarity comes in three phases: 1. Clarity on What to solve: Cut through the noise. Find the highest-leverage pain point or opportunity for the business. 2. Clarity on How to solve it: Push for depth. Explore multiple paths before settling on the best one. 3. Clarity on Execution: Make sure the build team knows exactly what success looks like—and ensure the GTM team can position it effectively. You don’t need to “own” everything. But you do need to make sure everyone is aligned and moving toward the same outcome. At the end of the day, your job is: Do whatever it takes to make the product successful by bringing clarity at every step. But clarity doesn’t come easy. Most PMs don’t lack ideas, they lack signal. Overwhelmed by the fragmented feedback from customers, stakeholders, and competitors, and no systematic way to cut through it. That’s where Enterpret comes in. We help you identify the right problems to solve by analyzing customer feedback at scale. And we help you align on how to solve them by surfacing the insights and opportunities that matter most. So you can spend less time debating what’s real, and more time driving impact.

82

1 commentaire

For product managers, engineers, and designers who feel ready for the next step - but aren’t sure what it takes to get there, sharing this in case it helps 😊 My friend, Nicolas Liatti just launched a new group coaching program designed to help ambitious product leaders make the leap into management and director roles. He’s no stranger to growth: - At Adobe, he helped scale 3D products from $8M to $100M ARR - earning both a Technical Oscar and an Engineering Emmy along the way. - At Allegorithmic, he turned a niche product into the industry standard for 3D texturing, leading to its acquisition by Adobe. - At Playsoft, he scaled the studio to 150+ people, making it the largest video game company in its category. - He personally grew from Group PM to Senior Director in just 4 years - and has helped many others do the same. Now, he’s sharing the same playbook he’s used to help countless professionals step confidently into leadership. If this sounds like something you’re interested in, give him a follow! I’ve learned so much from his daily posts and insights on leadership.

28

15 commentaires