A 20-year journey from Adobe to AI, and the three tools that now run my world
My design stack, 2010 to now

A 20-year journey from Adobe to AI, and the three tools that now run my world
I still have Adobe Creative Suite installed. I probably always will. But I haven't opened Illustrator out of habit in a long time. And I'm not sorry about it.
What I am is excited about design in a way I haven't felt since the first time components clicked in my brain and I thought, wait, you mean I never have to update that button a hundred times again?
The Adobe years (and why they were good)
For most of my career, I lived in Adobe Creative Suite. Illustrator for vectors, logo design, storyboards, and social. InDesign for long-form thought leadership and print. Photoshop for image manipulation, compositing, and yes, animated GIFs before that was even cool.
I knew those tools the way a chef knows their knives. Deeply, intuitively, without thinking. And for a long time, that fluency was the craft.
Then Sketch happened
Around 2010, someone introduced me to Sketch. And something shifted.
The canvas felt natural in a way Illustrator never quite did for screen design. The ability to create components (reusable, updatable) blew my mind. Sketch is still my sentimental favorite. There was something pure about it: clean, fast, focused. It did what it did and it did it beautifully.
I didn't want to give it up. But then Figma arrived, and I didn't have a choice.
Figma changed everything (again)
By early 2020, I had fully made the switch. And I haven't looked back.
Figma did everything Sketch did, and then kept going. Auto layout (which I have a love-hate relationship with that is entirely ongoing). Real-time collaboration with teams. Grids, frames, design systems, FigJam for working sessions, components that could actually talk to each other. It became the center of gravity for almost everything I do. Today I spend more time in Figma than in any other tool, and that's saying something given where I started.
But even Figma didn't prepare me for what was coming next.
Enter AI. Enter Claude.
I did what most creatives did. I tried ChatGPT, poked around Perplexity, figured out where AI fit into my workflow. But Claude became my real go-to. It thinks the way I think. It's my co-pilot for strategy, copy, ideation, and increasingly for things I couldn't have imagined doing without a developer beside me.
Claude Code, Claude Cowork, the API integrations: the ecosystem keeps expanding. If I can't figure something out, Claude is the first place I go. That's not a small thing after 20 years of figuring things out myself.
And then Stitch.
Google launched Stitch at Google I/O in 2025 as a Google Labs experiment, a tool that generates UIs for mobile and web applications.
In March 2026, Google rebuilt Stitch. It now has an AI-native, infinite canvas that gives ideas room to grow from early sketches to working prototypes. You can bring anything to the canvas (images, text, code) and a built-in design agent works across the whole project.
The best part: you can upload a screenshot of a UI you like, a whiteboard sketch, or a rough wireframe, and Stitch turns it into a digital UI you can paste directly into Figma for refinement. I took a static PNG of a website and had a working web layout in minutes. Not perfect, but a real starting point.
It goes further than that. A Voice Canvas lets you talk to the canvas: the agent listens, asks clarifying questions, gives design critiques, and makes live updates. You can save interface design details in a plain-language file called DESIGN.md to keep a consistent look across tools and projects. And for anyone working across tools, a new SDK and MCP server connect Stitch to coding assistants like Claude Code, Gemini CLI, and Cursor.
For most teams right now, the workflow is: explore in Stitch, refine in Figma, build in your deployment tool of choice. For me, that means Stitch → Figma → Claude → Webflow or Framer. And I'm doing things that used to require a full team.
What this actually means
I'm not worried about it.
I have a smaller team and a bigger output. I can go from brief to a designed first draft in a fraction of the time it used to take. And I have more creative control, because I spend less time on production and more time on thinking.
The complex stuff (sophisticated CMS architecture, advanced GSAP animations, custom interactions) still needs a developer. That's not going away. But a landing page? A brand system? A responsive web layout? I can move fast and move alone in a way I couldn't before.
The stack, right now
For anyone curious what my current workflow looks like:
- Ideation and UI generation → Stitch
- Design, systems, and refinement → Figma
- Strategy, copy, and code co-piloting → Claude
- Deployment → Webflow or Framer
Adobe still lives on my machine. Photoshop for image work, Illustrator when vectors need to be vectors. But the center of gravity has shifted, and I think anyone who's been in this industry long enough to remember when Sketch felt revolutionary can feel it too.
This is the most exciting time to be a creative I've experienced in 20 years. And I've had a lot of exciting years.
Elisa Ivany is a Creative Director & Brand Strategist based in Chicago, with 20+ years building brands in healthcare and fintech. She builds in Figma, thinks in Claude and ships in Webflow.



