Ben Perreau

21.5K posts

Ben Perreau banner
Ben Perreau

Ben Perreau

@perreau

Building @parafoilco | Before: Working with Fortune 100 CxOs on Leadership, Strategy & Culture | Former Prod Mgr & Journalist | LA via SF via LDN via someplace.

on the pale blue dot Katılım Eylül 2007
2.5K Takip Edilen4.8K Takipçiler
Ben Perreau
Ben Perreau@perreau·
When you've spent your life being a hammer and suddenly there's a whole new shed to build. Is this the era where "software builders" cease to be intermediaries/gatekeepers and the builders instead get sorted into people who understand the problem, and the rest, who don't? Probably.
Todd Saunders@toddsaunders

I know Silicon Valley startups don't want to hear this..... But the combination of someone in the trades with deep domain expertise and Claude Code will run circles around your generic software. I talked to Cory LaChance this morning, a mechanical engineer in industrial piping construction in Houston. He normally works with chemical plants and refineries, but now he also works with the terminal He reached out in a DM a few days ago and I was so fired up by his story, I asked him if we could record the conversation and share it. He built a full application that industrial contractors are using every day. It reads piping isometric drawings and automatically extracts every weld count, every material spec, every commodity code. Work that took 10 minutes per drawing now takes 60 seconds. It can do 100 drawings in five minutes, saving days of time. His co-workers are all mind blown, and when he talks to them, it's like they are speaking different languages. His fabrication shop uses it daily, and he built the entire thing in 8 weeks. During those 8 weeks he also had to learn everything about Claude Code, the terminal, VS Code, everything. My favorite quote from him was when he said, "I literally did this with zero outside help other than the AI. My favorite tools are screenshots, step by step instructions and asking Claude to explain things like I'm five." Every trades worker with deep expertise and a willingness to sit down with Claude Code for a few weekends is now a potential software founder. I can't wait to meet more people like Cory.

English
0
0
0
58
Ben Perreau
Ben Perreau@perreau·
@andrewchen Interesting. My take: the human element will be the differentiator once we all have access to the same commodity. Taste, Empathy, Judgement, Disernment, Influence—if you're a PM and need to develop those skills? Time to get cracking.
English
0
0
0
9
andrew chen
andrew chen@andrewchen·
in a world of agents, the product role is going to split into two jobs: - one that organizes humans (stakeholders, design, eng) - one that organizes agents (prompts, evals, workflows, etc) Both will be in pursuit of offering the right products to customers, but how you get there will dramatically change. What happens to the typical product rituals? Instead of PRDs, OKRs, standups, product reviews, we'll need the equivalent for agents. Couple wild ideas here... instead of standups: the equivalent is that agents will report back to us based on run logs and anomaly flags. no one needs to say what they did yesterday, the system already did thousands of things. the question is where it broke, where it surprised you, and where it got better. Show us the patterns, the trends, the edge cases - particularly the ones the agents didn't fix automatically. the daily ritual becomes reviewing deltas, scanning failures, and deciding which ones matter. less reporting, more triage instead of OKRs: we’ll need adversarial agents that continuously monitor/grade the system and detect patterns, scoring outcomes on an hourly or daily basis. Rather than setting a quarterly goal of "increase X by 5%" and revisiting slowly -- instead, management will be able to monitor success in real-time and detect trends/patterns towards overall goals instead of PRDs: we won't need waterfall. Prototyping will rule the day, and we’ll need a living agentic loop that mediates customer feedback/ratings and what's being prioritized and built. you don’t hand it to eng, you deploy it into the agent loop. if it’s wrong, it fails visibly and you can revert. if it’s right, it produces the right output instead of product reviews: we'll need simulation systems to examine agent behavior in different scenarios. In an agentic world where UI shifts from buttons/menus to agents automatically doing things, you'll want to examine their behavior before you deploy. You rewind decisions, fork alternate paths, and see how different prompts or constraints would have changed outcomes. the review becomes interactive. less storytelling, more counterfactuals. The PM sits in the middle of this split. On the human side, still aligning taste, risk tolerance, and strategy across people. On the agent side, shaping the actual behavior of the system through prompts, evals, and feedback loops. one side is persuasion. The other is instrumentation. the best ones will collapse the gap, translating intent directly into systems that act on it. the fascinating part is that the agentic loop will run 10000x faster than the human one, and of course, you can "hire" them faster. Thus the “organizing humans” half starts to feel slow and lower impact unless it directly improves the agent loop. Eventually the PM will shift towards agents and maybe ignore the human coordination altogether...
English
80
53
582
56.1K
Ben Perreau
Ben Perreau@perreau·
The great thing about leadership, if you get it right, is it that you barely need any rules at all. In fact, learning how to shape culture, goes a lot further than learning how to set rules. I can't tell what Travis has learned while he's been cooking (sic), but it certainly sounds like he's grokked the idea that the best leaders are masterful at setting the culture for their teams, and minimal at policing structure. In fact, this is often how people make the transition between management and leadership.
TBPN@tbpn

.@travisk explains his approach to management: "the fewest number of rules while staying out of chaos." "I basically have figured out management and leadership structures. The real thing is about empowerment. You must be able to empower teams." "Once you figure out the management piece, your imagination can go pretty damn far."

English
0
0
2
112
Sonia Baschez
Sonia Baschez@SoniaBaschez·
@perreau @pitdesi lol we Americans can’t tell too much unless it’s like Liverpool or something 😅
English
1
0
1
14
Sheel Mohnot
Sheel Mohnot@pitdesi·
Someone needs to do a study to quantify how many points of perceived IQ a posh British accent adds to American ears
English
62
6
331
30.8K
Ben Perreau
Ben Perreau@perreau·
I love that you are sharing this, and couldn’t agree more. Everyone should be more intentional, careful and precious with the time they spend in meetings. At their best they create explosive value, but at their worst they tire everyone out. That’s why we’re building the infra that creates more leadership value out of meetings as a primitive.
English
0
0
1
112
Behzod
Behzod@beh_zod·
A large part of my job at @vercel is meetings. While I’m still mastering the art of a good meeting, treating them like products has been helpful in identifying what’s broken and how to improve them. Like other products, they require intentional design and care.
Behzod@beh_zod

x.com/i/article/2031…

English
4
16
269
78.2K
Ben Perreau
Ben Perreau@perreau·
I love this. Look for the builders, the tinkerers, the ones who can’t help themselves, the ones with a chip on their shoulder to make something. I’ve never felt so invigorated to be building. It feels like the spirit of making is back again.
Aditya Agarwal@adityaag

x.com/i/article/2031…

English
0
0
2
99
Ben Perreau
Ben Perreau@perreau·
Product Managers like to talk about great PRDs, but builders just ship. Increasingly, articulating the product you want to build and focusing on taste, design, user experience and the data choices matter more than the finesse of the document to build it. Just build the thing.
English
0
0
1
47
Ben Perreau
Ben Perreau@perreau·
@vixsheikh You’re right, all this personalized tech. It’s an exciting time to be connected to it!
English
0
0
1
46
Waqas
Waqas@vixsheikh·
@perreau I was thinking, we’re living in the era of both the Flintstones and the Jetsons with these tools :)
English
1
0
1
19
Ben Perreau
Ben Perreau@perreau·
Happy weekend. Most people are just vibe coding the Homer Simpson car, but some people’s creativity and product sense is unleashed now.
English
1
0
2
81
Ben Perreau
Ben Perreau@perreau·
This new Gorillaz album is remarkable.
English
1
0
1
76
Ben Perreau
Ben Perreau@perreau·
@robinpembrooke I think it might be a little on the long side, and possibly even a bit “two white guys found themselves in India”, but it’s also expansive… vast even, genre-shifting and wonderful—going to be hard to beat this year, for me.
English
1
0
1
18
Ben Perreau
Ben Perreau@perreau·
Love to see this. Leadership skills are only gonna become more important in the future, and how we develop them and what we need is going to shift too. My prediction is that agents will handle a lot of the tactical workflow, and administrative side of our work. But what we previously called soft skills: including judgment, discernment, decision-making, these skills will come to the fore.
English
0
0
2
153
Quinten Farmer
Quinten Farmer@quintendf·
Agentic engineering is completely rewriting the role of a software engineer, but how we hire and evaluate talent hasn't caught up. We're fixing that, by defining a new engineering role at Tolan: Agent Engineering Manager.
Quinten Farmer tweet media
English
31
35
463
50.3K
Ben Perreau
Ben Perreau@perreau·
@nbaschez You do it with class. I am always down for a hang dude.
English
0
0
0
71
Nathan Baschez
Nathan Baschez@nbaschez·
Also there’s some bravado in my OP here but genuinely I don’t think it will crush me if Lex, Inc does end up shutting down or getting acqui-hired I feel so lucky to get to do what I do and although it’s often hard it is deeply meaningful to me And I know I will still feel that way and be ok no matter what comes next The beauty of Silicon Valley is no one cares about the ideas that didn’t work. They only care about how you conducted yourself. I write this because I imagine I’m not the only one “not killing it” and I hope if anyone is reading this it makes the stress of pre-PMF life a little easier
English
2
0
33
2K
Ben Perreau
Ben Perreau@perreau·
Respectful communication, severance. When you do it, this is how you do it. Cold and sad as the decision is. Less convinced on the causality. We are all tech folk and have significant belief in the value of AI, but I also think Block’s workforce was a little bloated. As always the reality is more nuanced than the narrative. Nothing but compassion for those affected.
jack@jack

we're making @blocks smaller today. here's my note to the company. #### today we're making one of the hardest decisions in the history of our company: we're reducing our organization by nearly half, from over 10,000 people to just under 6,000. that means over 4,000 of you are being asked to leave or entering into consultation. i'll be straight about what's happening, why, and what it means for everyone. first off, if you're one of the people affected, you'll receive your salary for 20 weeks + 1 week per year of tenure, equity vested through the end of may, 6 months of health care, your corporate devices, and $5,000 to put toward whatever you need to help you in this transition (if you’re outside the U.S. you’ll receive similar support but exact details are going to vary based on local requirements). i want you to know that before anything else. everyone will be notified today, whether you're being asked to leave, entering consultation, or asked to stay. we're not making this decision because we're in trouble. our business is strong. gross profit continues to grow, we continue to serve more and more customers, and profitability is improving. but something has changed. we're already seeing that the intelligence tools we’re creating and using, paired with smaller and flatter teams, are enabling a new way of working which fundamentally changes what it means to build and run a company. and that's accelerating rapidly. i had two options: cut gradually over months or years as this shift plays out, or be honest about where we are and act on it now. i chose the latter. repeated rounds of cuts are destructive to morale, to focus, and to the trust that customers and shareholders place in our ability to lead. i'd rather take a hard, clear action now and build from a position we believe in than manage a slow reduction of people toward the same outcome. a smaller company also gives us the space to grow our business the right way, on our own terms, instead of constantly reacting to market pressures. a decision at this scale carries risk. but so does standing still. we've done a full review to determine the roles and people we require to reliably grow the business from here, and we've pressure-tested those decisions from multiple angles. i accept that we may have gotten some of them wrong, and we've built in flexibility to account for that, and do the right thing for our customers. we're not going to just disappear people from slack and email and pretend they were never here. communication channels will stay open through thursday evening (pacific) so everyone can say goodbye properly, and share whatever you wish. i'll also be hosting a live video session to thank everyone at 3:35pm pacific. i know doing it this way might feel awkward. i'd rather it feel awkward and human than efficient and cold. to those of you leaving…i’m grateful for you, and i’m sorry to put you through this. you built what this company is today. that's a fact that i'll honor forever. this decision is not a reflection of what you contributed. you will be a great contributor to any organization going forward. to those staying…i made this decision, and i'll own it. what i'm asking of you is to build with me. we're going to build this company with intelligence at the core of everything we do. how we work, how we create, how we serve our customers. our customers will feel this shift too, and we're going to help them navigate it: towards a future where they can build their own features directly, composed of our capabilities and served through our interfaces. that's what i'm focused on now. expect a note from me tomorrow. jack

English
0
0
1
167
joher khan
joher khan@joherkhan·
First company just got Citrini’d
jack@jack

we're making @blocks smaller today. here's my note to the company. #### today we're making one of the hardest decisions in the history of our company: we're reducing our organization by nearly half, from over 10,000 people to just under 6,000. that means over 4,000 of you are being asked to leave or entering into consultation. i'll be straight about what's happening, why, and what it means for everyone. first off, if you're one of the people affected, you'll receive your salary for 20 weeks + 1 week per year of tenure, equity vested through the end of may, 6 months of health care, your corporate devices, and $5,000 to put toward whatever you need to help you in this transition (if you’re outside the U.S. you’ll receive similar support but exact details are going to vary based on local requirements). i want you to know that before anything else. everyone will be notified today, whether you're being asked to leave, entering consultation, or asked to stay. we're not making this decision because we're in trouble. our business is strong. gross profit continues to grow, we continue to serve more and more customers, and profitability is improving. but something has changed. we're already seeing that the intelligence tools we’re creating and using, paired with smaller and flatter teams, are enabling a new way of working which fundamentally changes what it means to build and run a company. and that's accelerating rapidly. i had two options: cut gradually over months or years as this shift plays out, or be honest about where we are and act on it now. i chose the latter. repeated rounds of cuts are destructive to morale, to focus, and to the trust that customers and shareholders place in our ability to lead. i'd rather take a hard, clear action now and build from a position we believe in than manage a slow reduction of people toward the same outcome. a smaller company also gives us the space to grow our business the right way, on our own terms, instead of constantly reacting to market pressures. a decision at this scale carries risk. but so does standing still. we've done a full review to determine the roles and people we require to reliably grow the business from here, and we've pressure-tested those decisions from multiple angles. i accept that we may have gotten some of them wrong, and we've built in flexibility to account for that, and do the right thing for our customers. we're not going to just disappear people from slack and email and pretend they were never here. communication channels will stay open through thursday evening (pacific) so everyone can say goodbye properly, and share whatever you wish. i'll also be hosting a live video session to thank everyone at 3:35pm pacific. i know doing it this way might feel awkward. i'd rather it feel awkward and human than efficient and cold. to those of you leaving…i’m grateful for you, and i’m sorry to put you through this. you built what this company is today. that's a fact that i'll honor forever. this decision is not a reflection of what you contributed. you will be a great contributor to any organization going forward. to those staying…i made this decision, and i'll own it. what i'm asking of you is to build with me. we're going to build this company with intelligence at the core of everything we do. how we work, how we create, how we serve our customers. our customers will feel this shift too, and we're going to help them navigate it: towards a future where they can build their own features directly, composed of our capabilities and served through our interfaces. that's what i'm focused on now. expect a note from me tomorrow. jack

English
1
0
4
956