Guy Peled (@peledg) profile picture

Product Manager. I tweet and blog about discovery and company culture

Joined June 2011
Photo by Guy Peled (@peledg)Photo by Guy Peled (@peledg)Photo by Guy Peled (@peledg)Photo by Guy Peled (@peledg)Photo by Guy Peled (@peledg)Photo by Guy Peled (@peledg)Photo by Guy Peled (@peledg)Photo by Guy Peled (@peledg)Photo by Guy Peled (@peledg)Photo by Guy Peled (@peledg)
Product management is such a misunderstood role. Mainly because it’s unique per company. But a lot of the "it's unique per company" is actually "it's unique per founder". A thread about resentment and empathy towards leadership 🧵
1
1
285
Love Ryan's replies about this being for his personal use. So personal preference > best practice UI. The double click to change duration as an alternative to an on-screen "are you sure?" is not intuitive, but it is to Ryan and he likes the interface as clean as possible so..
Its funny how many tiny little judgements it takes to make something the way you want it to be. Even for something as simple as a pomodoro timer. First swing at an Omarchy plugin.
21
Spot on. Both for designers and product managers.
we’re not really “designing” right now, we’re just constantly switching contexts trying to not get left behind every week there’s a new tool claiming to be the future → paper, pencil, magicpatterns, magicpath… now noon shows up with $44M and changes the narrative again so instead of going deep, everyone’s just sampling everything trying prompts here, generating screens there, tweaking in figma, jumping to code, back to AI again half the industry is already inside code editors the other half is still figuring out which tool is even worth committing to fomo is doing more damage than we realise because depth needs stability and right now the stack itself is unstable so no one is mastering anything everyone is just trying to be early eventually this will settle and a default will emerge till then, we’re all just beta testers pretending to have a workflow 👀
1
72
Guy Peled retweeted
I've teamed up with the team at @MavenHQ to put together a series of LIVE workshops centered around the theme of "The AI-Native PM," featuring a stacked lineup of product leaders: @cohentomer @wes_kao @HamelHusain @petergyang @marilynika @talraviv @amankhan @HilaQu @ViableBen @EthanEvansVP The workshops are across 3 themes and all totally free: 1. AI workflows 2. Becoming more technical 3. Product sense & influence A few years from now, these skills will be table stakes for PMs. If you want to learn where things are heading in a hands-on way, this is the perfect way: bit.ly/ai-native-pm
27
54
9
417
243,008
Replying to @steipete
@steipete on @lexfridman Great bit about AI content slop. Mainly because of who’s saying it. Has a great human-in-the-loop orientation (apparent throughout the whole interview). Refreshing. Comforting. Especially now that he’s joining OpenAI.
Peter Steinberger is joining OpenAI to drive the next generation of personal agents. He is a genius with a lot of amazing ideas about the future of very smart agents interacting with each other to do very useful things for people. We expect this will quickly become core to our product offerings. OpenClaw will live in a foundation as an open source project that OpenAI will continue to support. The future is going to be extremely multi-agent and it's important to us to support open source as part of that.
1
61
Recommend listening to all of it and mainly to the last two bits which are around 20 minutes: 2:52:20 - AI agents will replace 80% of apps 3:00:57 - Will AI replace programmers? teapaw.org/lexfridman/status/2021…
Here's my conversation with Peter Steinberger (@steipete), creator of OpenClaw, an open-source AI agent that has taken the Internet by storm, with now over 180,000 stars on GitHub. This was a truly mind-blowing, inspiring, and fun conversation! It's here on X in full and is up everywhere else (see comment). Timestamps: 0:00 - Episode highlight 1:30 - Introduction 5:36 - OpenClaw origin story 8:55 - Mind-blowing moment 18:22 - Why OpenClaw went viral 22:19 - Self-modifying AI agent 27:04 - Name-change drama 44:15 - Moltbook saga 52:34 - OpenClaw security concerns 1:01:14 - How to code with AI agents 1:32:09 - Programming setup 1:38:52 - GPT Codex 5.3 vs Claude Opus 4.6 1:47:59 - Best AI agent for programming 2:09:59 - Life story and career advice 2:13:56 - Money and happiness 2:17:49 - Acquisition offers from OpenAI and Meta 2:34:58 - How OpenClaw works 2:46:17 - AI slop 2:52:20 - AI agents will replace 80% of apps 3:00:57 - Will AI replace programmers? 3:12:57 - Future of OpenClaw community
25
Such a great read. Thoughtful. Well written. An engaging marketing lesson. More content like this please.
1
66
Move fast and rename things
🦞 BIG NEWS: We've molted! Clawdbot → Moltbot Clawd → Molty Same lobster soul, new shell. Anthropic asked us to change our name (trademark stuff), and honestly? "Molt" fits perfectly - it's what lobsters do to grow. New handle: @openclaw Same mission: AI that actually does things.
42
Curated AI output > AI Output Good take by Ryan. Good example.
I'm seeing a key difference in the results friends get using AI for real work. It's whether they create trusted ground truth for the agent or not. Example. If you ask AI to summarize a meeting and then you save that, your ground truth is suspect. Instead, save the full transcript, iterate with the agent on what is important and true to highlight (with adjustments), then save that. This is why we see Claude Code pulling ahead like crazy. Because it's grounded in specific knowledge (the files). Not just fuzzy memory. But this depends on how you hold it too. Eg if you put a lot of mixed content into a request (try to one-shot something too big), you don't have grounding for what is happening. That's why planning works. Planning gives you ground when the chasm is far. It's not just about "think ahead." "Think ahead and lay some stones down that we can agree are true" is very different from "think ahead and see what happens."
29
1/ I’ve seen colleagues, friends, and my past self burn mental bandwidth "managing" imposter syndrome. Self-help podcasts. Books. Pep talks. Threads like this one 😉 They feel helpful in the quiet moments, but vanish the second we are triggered. The problem has two parts 🧵
1
28
6/ Evidence looks like: - PM: Crafting a high-quality decision & moving quickly. Bringing the team along for the ride - CSM: A champion using your deck to get buy-in internally - Colleague: Solving a peer's obstacle - Fun: Creating an AI side project to fix a personal/work gripe
1
17
7/ When you have enough data, you stop explaining your worth to yourself. Stop trying to feel ready. Build the case that you are. Nike wasn't wrong. And there's the below which is my favorite @JamesClear quote teapaw.org/JamesClear/status/1300…
Working on a problem reduces the fear of it. It’s hard to fear a problem when you are making progress on it—even if progress is imperfect and slow. Action relieves anxiety.
17
Guy Peled retweeted
In 2025, a lot of teams treated AI like a feature multiplier. Bolt it on, ship a demo, call it progress. The hard work of designing systems that learn, degrade gracefully, and hold up under real usage was quietly discounted. Those teams looked slow because the visible output lagged the hype. That gap shows itself in 2026. AI-powered products only scale when teams treat data feedback loops, model failure modes, and human-in-the-loop tradeoffs as first-class constraints. Teams that internalize this early compound their progress. Everyone else keeps shipping polished surfaces that fail as soon as usage grows or the stakes get real.
12
3
31
3,257
Interesting AI auto complete UI solution
I’m very excited to announce AI Autocomplete AI Autocomplete is a breakthrough patented technology that supercharges natural language input = Unlocking 10x faster search and commerce, advertising, and powerful augmented reality. Available for use as an SDK. This solves a fundamental problem of today’s chat interfaces – They are good at single step request, but any multi-step action (like booking a flight or purchasing goods) quickly becomes a back and forth 'game of 10 questions'. While working on our own assistant, we realized the core driver of this problem is a human one: People don’t know everything they need to say upfront, for every action you could do on the internet. And to solve it, we would need to think about how to marry design and technology in a new way. AI Autocomplete solves this, and can now plug into chat interfaces to guide you in real-time, with everything you would need to say, upfront. So you can do anything you can do on the internet in one shot. No more back and forth. As a result, this unlocks multiple AI breakthroughs: 1. 10x faster search and commerce 2. Smarter (and far lower cost) media generation 3. Natural language advertising 4. Powerful, lightweight Augmented Reality From here, we’ll be using this for Hero, but we also want others to use it too since this is an industry-wide problem. So if you have a product that could benefit from AI Autocomplete and want to work with us, reach out below! Shoutout to @seunglee1b who helped think of and patent this nearly 3 years ago! And shoutout to the entire @hero_assistant team that keeps innovating on the next generation of AI products
22
Great post by @yourgirlhils The mindset shift for trying out AI tools over time as their quality improves "𝘛𝘩𝘦 𝘮𝘰𝘴𝘵 𝘦𝘹𝘱𝘦𝘯𝘴𝘪𝘷𝘦 𝘰𝘱𝘪𝘯𝘪𝘰𝘯 𝘪𝘯 𝘵𝘦𝘤𝘩 𝘳𝘪𝘨𝘩𝘵 𝘯𝘰𝘸 𝘮𝘪𝘨𝘩𝘵 𝘣𝘦 𝘰𝘯𝘦 𝘺𝘰𝘶 𝘧𝘰𝘳𝘮𝘦𝘥 𝘢 𝘮𝘰𝘯𝘵𝘩 𝘢𝘨𝘰" substack.com/home/post/p-182…
23
How many users to talk to as part of discovery? It's not about the number. Minimum is the amount willing to talk to you in the ballpark timespan that you have. Depends on your assessment and your manager's appetite for discovery (could come out to be 1-3 interviews). 1/3
1
14
The maximum isn’t a number either. it’s about knowing when to stop. You stop when the main insightful patterns are repeated, and you’re no longer learning anything new that passes your meaningful/useful threshold. 2/3
1
12
So stop when you feel you learned about 70-80% of what can be learned. The other 20 or so percent would demand exponential amount of interviews, so not worth the effort/time. 3/3
9