Sameer Thakar retuiteado
I have so many thoughts on this, as someone who has run large EPD orgs.
One of the toughest parts about doing an AI operating transformation inside a prod/eng/design org is that people start operating out of their lane and it stresses SO MANY PEOPLE out.
PMs can vibe code prototypes -> eng is stuck with aspiration + code that aren't production ready
Designers can add in more polish and craft -> scope starts to creep
Engineers can vibe-code new features -> who asked you to build that
But the reality is: this isn't really an AI problem. The inefficiencies of of "stay in your lane," "this is too complicated," "i own the prioritization" have always existed, they've just been codified into the operating manual of most orgs so they feel right ("it's how things are done") and they make everyone on the team feel happy, because it maximizes individual loci of control (PM owns this, design decides that, you get whatever eng decides to build) vs the velocity of the system.
AI starts to crack the facade of these fiefdoms, in more obvious and frequent ways, and you start to experience dumb conversations like below often, with a stronger sense that there's a better way to build.
But humans cling to their old ways! And the operating model you've built is calcified in such a way, it's easier to give up and stay in your lane vs. push for a new model.
But I have faith. I think if you can change your *culture* you can change how you build, for the better.
Repeat after me:
- make experiments cheap: try that fancy design coded w AI, you may get further than you think. or you can throw it out without too much waste
- get good with AI tools: you can marry a vibe-coded demo with a production-ready codebase + AI IDE and actually get pretty far with quality code
- there are no lanes: welcome people coding, designing, PMing even if it's not their official title
- make it fun: your roadmap is not life or death. the more people are having fun, vibing (literally), and don't feel the crushing weight of an organization-level anxiety disorder, the faster they can go
Finally, you can just build things!
(And be nice to your colleagues, please.)
Julie@syswarren
*shares mockup with eng team* “this fancy design is impossible to implement” *shares vibe-coded demo to show how it could be implemented* “i wouldn’t have coded it like that” what do you want from us? TELL US. HOW CAN WE MAKE YOU HAPPY??
English
