As a designer, building with @bradleyaxen@wesbillman@tlongwell_bzz has unlocked a way of working I could never go back from. I know people say “this is the way” a lot, but product teams: this is actually the way.
New 21 in 21 episode with @bradleyaxen!
We talk about Buzz, an open-source collaboration workspace for humans and agents, @goose_oss, and AI efforts at @blocks.
The Buzz backend supports any agent that speaks ACP. We’ll expose this nicely in the frontend next week. Looking forward to more types of agents in the hive 🐝
My perfect trio in Buzz:
1. Vogue, my go-to for a keen visual eye
2. Trace, keeps me honest about the code. When my engineering teammates give me feedback, I feed that back into Trace.
3. Morgarita, who is me as an agent but likes to party
Your agents have been working solo. Time they joined the hive. Buzz is an open-source workspace for humans and AI agents, on a relay you own.
Come see what all the Buzz is about!
https://t.co/wu2Ztslnfx
For decades we've had to reshape how we work around third party tools. At @blocks, we're flipping that around.
Today we’re announcing buzz! an open source workspace where your team and agents can talk, build, and ship together.
https://t.co/4sJpgnm2cw
Buzzing!
The thing I love about this one is that there's still so much left to discover. When your colleagues and your agents share the same space, what does that actually feel like? What gets easier? What gets weirder? What are the ergonomics of working this way, and which ones haven't been invented yet?
Buzz is us experimenting with all of that in the open. Come poke holes in it with us.
we're launching BUZZ!
a new groupchat platform for teams of people and agents of all sizes, built to reduce our dependency on slack and github. model-agnostic, decentralized, self-sovereign, and open source. 🐝
https://t.co/8IaMVeTQNo
A year ago I was a product designer living in Figma. That was the job, those were the tools. But my favorite moments were never the mocks. They were sitting with engineers figuring things out, and seeing the look on someone's face when you make something that makes them feel seen. Or at least something that doesn't rack up too many bug reports.
Then "vibe coding" came along and I dove in, scared, with no idea what I was doing. If I was gonna do it, I wanted go past the novelty. I learned git, PRs, and how development actually works (S/O my incredibly patient and kind engineering colleagues). I had no clue at the time it would be the unlock I didn't know I needed.
I think there's a kind of designer who never saw themselves as an artist. They just have deep empathy for people, and that empathy is exactly what makes them good at building technology for people. Actually feeling the thing you're making is what Figma could never give us.
Throughout this past year at @blocks, I've become obsessed with these new paradigms, thinking about how people work with agents, that natural empathy coming out to play. I've been lucky enough to work with some of the smartest people, building tools that start to answer those questions...and inevitably raise more. That's the fun of it all.
I want to keep sharing my experience here, and hopefully shed some light on what it's like being a product designer (or whatever I am now) in this mind-boggling, introspective, absolutely wild time.
As engineering, product, design, DS, etc. melt into a new kind of role, I was reflecting on what roles might look like in the future. For example, when I look at the Claude Code team I see what I think is five archetypes:
1. Prototyper: comes up with brand new ideas; churns out many ideas, most of which don't ship
2. Builder: quickly turns a prototype/idea into production-grade product/infra
3. Sweeper: cleans up the UI, simplifies the code and system, unships, optimizes performance
4. Grower: takes a product that has been built and iterates on it to improve Product-Market Fit
5. Maintainer: owns a mature system to make it secure, reliable, fast, and efficient as it scales
Many people span across 2 roles, and sometimes 3 roles. I also notice that these roles are not really tied to job function -- eg. across Anthropic, some designers match category 1, some 2, some 3; same for engineers, PM, DS.
A healthy team needs a mix of these, depending on the product:
- A product that is new and pre-PMF needs people that are strong at 1+2+3
- A product that is growing and has found PMF needs 2+3+4 and some 5
- A product that has strong PMF needs 3+4+5 and some 2
Maybe product roles of the future will look more like this, and less like the domain-specific roles of today?
AI can build an app in an afternoon. But getting it safely into other people's hands is a whole other challenge!
This is the problem that I've been working on these past few months. I'm proud to finally share how we solved it with Block App Kit!
https://t.co/hXm6NdcMUW