Hey everyone! 
I’ve recently been tasked with auditing and exploring the intersection of Design and AI at my workplace. I’m looking at this holistic landscape through the lenses of our User-Centred Design (UCD) team, Product Owners, and Developers.
The goal? Find smart, modern ways to design and build using cutting-edge tech stacks. We’re deep-diving into everything from the handoff process and documentation to accessibility (WCAG compliance), reusable components, and strict, scalable design systems. 
I wanted to drop my current thesis here to spark some conversation and gather your insights.
My Hot Take: The De-centering of the Design Tool
I’m starting to lean into a realm of thinking where the specific design tool we use is slowly becoming less important. (No disrespect to Figma, Sketch, or the amazing Penpot team - hear me out! 
)
Think about how modern software development works:
-
You have a team of developers all contributing to the exact same codebase.
-
The text editor they use is completely interchangeable. One dev might swear by VS Code, another is testing out Zed, and a third is a purist running Vim.
-
It doesn’t matter. At the end of the day, they are all editing the same source files and committing to the same repository and also pulling the latest updates.
The Proposal: A Two-Way Unified Design System
Why can’t design follow the exact same paradigm?
Right now, there’s an artificial wall between design files and code. But what if the Design System itself is the single source of truth, and the design tool is just a themed skin to view and manipulate it?
Imagine a workflow where:
-
The Design System rules the kingdom. It dictates the design tokens, layout logic, and component behaviours.
-
The tools are agnostic. Whether you prefer Figma, Penpot, or Sketch, the tool simply reads from a standardised ruleset (like a universal JSON schema for design tokens).
-
True two-way synchronisation. An update made to a component in Penpot is submitted to the central Design System, which then compiles cleanly into HTML/CSS/JS and simultaneously syncs back to update the component libraries in Figma or Sketch for the rest of the team.
Pipedream or the Next Logical Step?
Instead of being locked into a monolithic ecosystem, this would create a beautifully relaxed, versatile, and interoperable design process. The tool becomes a matter of personal preference, just like a developer’s IDE.
With AI rapidly accelerating how we translate intent into code and UI, this feels like where the puck is heading.
What are your thoughts? Are we moving toward a tool-agnostic future?
- Has anyone successfully bridged the two-way sync gap between code repositories and canvas-based design tools without a massive headache?
Thoughts??? 
