Designers ship code, developers ship interfaces, and AI is dissolving the wall between two crafts that spent decades apart.
It all started a few years ago with no-code editors like Webflow and Elementor. Now it's accelerating through vibe-coding tools like Lovable, Claude Code, and even Figma Make, which sits directly inside most designers' workspace. Designers can often build functional prototypes or products today without waiting for developers.
But it's also going the other way. Coders are starting to design more: Google recently released Stitch, a "vibe design" tool that lets developers produce polished interfaces without traditional design training. No matter how one judges the individual output, the convergence is happening from both sides.
AI seems to achieve something the industry failed at for years: making these two disciplines grow together. And I think that's a good thing.
A design silo is the organizational and cultural separation between disciplines, typically design and engineering, where each side works in isolation, with limited shared vocabulary, no joint decision-making, and no shared accountability for the outcome. Its opposite, a cross-functional team, shares goals, language, and ownership from start to finish. AI is finally making the second pattern easier to operate than the first.
At SCHUMACHER, a core value has always been that clients work with an agency that can advise from a single source on user-centered strategy, excellent design, and technical implementation. No friction losses, no meaning lost in translation between disciplines.
Personally, I've been passionate about design and technology for 20 years now, ever since I (as a teenager) started my own business as a web developer before studying design. That dual perspective still shapes how I see our work today: not as separate crafts, but as one integrated task. It's a big part of why the role of design in the AI era is shifting so fast, and why the democratization of production hits the design industry so directly.
In the end, it's about creating results that work on every level: purpose, emotion, function, and business. The less we work in silos, the better we get there. And the more joy we find in the process.
Welcome to this beautiful new era. Are you seeing this development in your field too?
Read next:
- Designer archetypes that get hired – which roles thrive as designers start coding
- Vibe Coding for Designers: The Real Risk Nobody Talks About – what the new tools actually change (and don't)
- Event management tool, vibe-coded – a practical example of shipping without waiting for a developer
- Flip-dot display – where code, electronics, and design meet physically
FAQ
What is a design silo?
A design silo is the organizational and cultural separation between disciplines, typically design and engineering, where each side works in isolation, with limited shared vocabulary, no joint decision-making, and no shared accountability for the outcome. Silos slow product work because context and trade-offs get lost in translation between teams. The opposite pattern, a cross-functional team, shares goals, vocabulary, and ownership from start to finish.
What is cross-functional collaboration in design and engineering?
Cross-functional collaboration is the practice of teams from different disciplines working together throughout a project rather than handing off work in sequence. In design and engineering, it means designers and developers share goals, language, and accountability from the first sketch to the final release. The point is not just communication, but shared ownership of the outcome.
How do vibe coding tools like Lovable and Claude Code help designers ship code?
Vibe coding tools let designers describe what they want in natural language and get working code back, without hand-writing JavaScript or setting up a build pipeline. Designers can now prototype, test ideas, and even ship small products directly, without waiting for developer availability. The tools do not replace design judgment, but they remove the build bottleneck that used to sit between a designer and a running prototype.
Why are designers and developers converging in 2026?
Two shifts are driving the convergence. On the design side, AI coding tools have made implementation cheap and conversational, so designers can build directly. On the engineering side, "vibe design" tools like Google's Stitch have made interface generation accessible to developers without formal design training. Both sides are reaching into the other discipline, and AI is the enabler of that reach.
How can an agency break down the design–engineering silo?
The most effective move is structural: staff teams as cross-functional units from the start, not as handoff chains. That means designers who can read code and developers who participate in user research, with shared rituals, shared definitions of done, and shared accountability for the outcome. At SCHUMACHER we have built the whole agency around this principle, and the AI tools now make it dramatically easier to execute on it at scale.