Andy Dunn

8.7K posts

Andy Dunn banner
Andy Dunn

Andy Dunn

@dunn

A founder of Bonobos, Pie, Monica + Andy, and Red Swan. Author of Burn Rate: Launching a Startup and Losing My Mind. 🎢 Posts on startup, leadership, culture.

Chicago Katılım Ekim 2010
14.3K Takip Edilen24K Takipçiler
Sabitlenmiş Tweet
Andy Dunn
Andy Dunn@dunn·
Let me tell you a ghost story. My Ghost first arrived in the year 2000 and would haunt me for the next sixteen years. It was a secret, known only to a handful of my closest loved ones.
English
51
53
734
0
Andy Dunn
Andy Dunn@dunn·
"it is the damn phones." new essay in comments. 👇
Andy Dunn tweet media
English
1
0
3
305
Andy Dunn
Andy Dunn@dunn·
does anyone know a highly recommended company that does podcast production, editing, booking for founders? recently met a firm that does this and looking to calibrate... happy to share who i'm talking to on dm to compare notes...
English
1
1
3
836
rvb
rvb@ryanvailbrown·
@dunn how long did it take ChatGPT to write this?
English
1
0
0
26
Andy Dunn retweetledi
Sergio Pereira
Sergio Pereira@SergioRocks·
The rise of the Product Engineer is not a fad. It is a structural shift in tech. For years, the split was clear: - Product Managers wrote specs. - Software Engineers implemented them. - PMs owned discovery, user interviews, roadmap, prioritization. - Engineers owned architecture, APIs, performance, deployment. AI tools are collapsing that boundary. With tools like ChatGPT, Notion AI and Perplexity, engineers can synthesize user research, draft PRDs and decide priorities themselves. With Cursor, Claude Code and Copilot, they can turn those product decisions into working software in hours. The bottleneck is no longer typing code to build something. It is actually deciding what deserves to be built, how and when. The Product Engineer combines both tracks: - Frames the problem - Talks to users - Defines the MVP - Designs the system - Ships the code - Measures the outcome Fewer handoffs. Fewer translation errors. Faster learning loops. And for Startup Founders, this changes hiring. Instead of asking “Should we hire a PM or another Engineer?” the better question is: - "Who can own this product end to end?" For Senior SW Engineers, this changes careers. - If you only execute tickets, AI will compress your role. - If you define value and ship it, your leverage expands. The Product Engineer is not a new title. It is a new career and a new set of expectations.
English
37
53
426
46.4K
Andy Dunn
Andy Dunn@dunn·
Two entrepreneurs. One marriage. What could go wrong? 👇
Andy Dunn tweet media
English
4
0
22
2.6K
Andy Dunn retweetledi
jack
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
8.8K
6.7K
51.3K
64M
Andy Dunn retweetledi
Deirdre Bosa
Deirdre Bosa@dee_bosa·
ok WOW. Woke up this morning and said, for fun, lets try to recreate monday. com w Claude cowork. it wont work or anything, but we can just show our audience that its plausible. 1 hour later... I literally have my own monday. com that's plugged into my calendar & gmail and surfaced a kids bday that was not anywhere on my radar and I need to get a gift for. Can imagine next step being: order gift and have it delivered by Sunday. 2026 is WILD.
Deirdre Bosa tweet media
English
153
103
1.9K
474.6K
Andy Dunn
Andy Dunn@dunn·
🍿
Aakash Gupta@aakashgupta

The CPO role is here to stay. I respectfully disagree with Gokul. Here’s why. The CPO exists because product needs a neck to wring in the C-suite. When revenue misses, the CEO calls the CRO. When systems break, they call the CTO. When the product fails to convert, retain, or differentiate? Someone has to own that answer at the executive table. That accountability doesn’t disappear because ICs can now ship faster. The “product builder” thesis confuses execution speed with strategic clarity. Yes, AI-native companies have engineers who design and designers who code. Great. Who decides which market to enter? Who kills the feature that engineering loves but customers ignore? Who tells the CEO that the board’s pet initiative will cannibalize the core business? That’s not an IC job. That’s a CPO job. Look at what happens when companies try to eliminate this role. Google famously ran without PMs in the early days. Larry and Sergey believed engineers should own product decisions. By 2002, they’d hired a VP of Product Management. The complexity forced it. The AI-native startups cited as evidence are sub-100 employees with single products. Perplexity has one core surface. Cursor serves one user type. When they’re managing enterprise vs consumer, platform vs application, and core vs adjacent bets simultaneously, a dedicated product executive will emerge. The pattern has repeated for 30 years. Nothing about AI changes the coordination math at scale. Here’s what the CPO of 2030 actually looks like: They own product, design, growth, AND data. Not because they can do all four jobs, but because these functions have become inseparable when AI makes distribution the only moat. The companies winning will have CPOs with broader scope, not narrower. The title might evolve. The power concentrates. Career advice to “stop aspiring to CPO” is advice to cap your own leverage. Founders don’t need career ladders. The 99% working at scaled companies still need executives who translate board priorities into product bets and protect teams from strategic whiplash. AI compresses execution. It doesn’t compress the judgment calls about what to build, what to kill, and what to defend when the CEO wants to pivot. The CPO who owns those calls is more valuable than ever.

ART
0
0
1
2.1K
Andy Dunn retweetledi
Tansu Yegen
Tansu Yegen@TansuYegen·
When you apply physics to your job
English
293
1.9K
29.1K
3.6M
Andy Dunn retweetledi
Robert Mays
Robert Mays@robertmays·
Winning six Super Bowls isn't that impressive when you really think about it. There have been like 60 of them. x.com/AdamSchefter/s…
Adam Schefter@AdamSchefter

Bill Belichick, the 8-time Super Bowl-winning HC, is not a first-ballot Hall of Famer, per @SethWickersham and @DVNJr. Belichick fell short of the 40 out of 50 votes needed for induction to the Pro Football Hall of Fame in his first year of eligibility. espn.com/nfl/story/_/id…

English
34
48
1.4K
77.3K
Andy Dunn
Andy Dunn@dunn·
Founder vision is bullshit. 🔗 👇
Andy Dunn tweet media
English
2
0
2
434