#76: Working ( as a designer ) in an open space office #designerproblems #startups #reactions

Below is the first version of this project, I worked with Claude code and Pencil app which created actual pixel designs, now mostly working with figma's mcp build prototypes. but i have these 2 tools available to use any time. will continue to update!

My takeaway: this might be the future of product design workflows. Not one universal tool — but custom IDE-like environments each designer builds for their own problem space.

Each agent shares the same core “DNA” for how work is done — but their knowledge and patterns evolve per context. Two designers may share methodology, yet operate differently depending on product surface, history, and constraints.

To make this possible, I built a 3D workspace in Three.js where agents (researcher, designer, developer) collaborate inside feature-based rooms, share context, and present outputs live on walls and screens. The environment is the product.

For the past week and a half I’ve been running an experiment: executing a full end-to-end product design workflow — research, design, and development definition — using only Claude Code. 🧵

#141: When you didn't considered that feature on mobile view #designerproblems

#138: When there's no time and you deliver the design with no specs #developerproblems

#137: When dev team criticise your design and you were gentle with your QA until that point #designerproblems

#136: Trying to be useful while they’re implementing your design #designerproblems

#133: When developers try to convince you to stay with default style settings #startups #designerproblems

#129: When you find out people get more equity than you #startups #designerproblems

#126: When you're watching #SilliconValley with your family #startups #designerproblems

#125: When the dev team decided to take that design decision by themselves #startups #designerproblems

#124: When user testing brings nothing but confusing #startups #designerproblems

#123: When 3 Linkedin recruiters sending you in-mails at the same time #startups #designers #reactions

#122: When they ask you to visually demonstrate how backend systems works #startups #designerproblems

#121: When you propose too many options #designerproblems

#120: When users gain access without registering #startups #users #reactions

#119: When you expecting a short and quick feedback from stakeholders #startups #designerproblems

#118: When you're new in the company and someone talking bullshit next to you #startups #designerproblems