I’ve been a designer long enough to see more than a few tools come and go. Without dating myself, I can remember designing UI with a little Fireworks followed by LOTS of Photoshop. I remember when Sketch felt like the future. Then Figma showed up and changed everything again. Now it’s Framer, Webflow, Penpot, and dozens of AI-assisted tools popping up weekly.

It’s easy to feel like you’re falling behind if you’re not constantly learning the next hot thing. But I’ll be honest ... I’m not chasing every new tool anymore.

This isn’t a post about which design tool will win. It’s about how I’m thinking through the changes, what I’ve decided to focus on, and the skills I believe will actually matter if the dust ever settles.

I’ve Stopped Caring About “The Best Tool”

If there’s one lesson that’s stuck over the years for me, it’s this ... there’s no “best” tool. There’s only the one that works best for the thing you’re trying to do.

Some teams need real-time collaboration. Some prioritize handoff to developers. Some need marketing sites that launch fast and look great. The tool you choose should fit the job ... not the trend. In a previous role I had a designer that lived by Figma for his vector work, icons, logos, etc. For me the best tool for those tasks is still Illustrator.

I’ve been guilty of chasing the latest features before, what designer isn't guilty of this? But these days, I care a lot more about mastering the tools I already use, and gaining efficiencies, than swapping them every six months.

When I've worked with younger designers I tend to tell them ... "I don’t think there’s a ‘best’ design tool. I think there’s the one that works for you."

Systems Over Screens

When I started, design was mostly about making beautiful screens, how can I make this notebook app feel like real paper and give the user the sense they are using a real notebook? Now it’s about building smart, reusable systems. Design systems, tokens, components ... these aren’t just buzzwords. They’re the new mental model for working at scale.

I’ve found myself thinking more like a product owner and less like a pixel-pusher, as I mentioned in Field Notes Vol 4. How do you build something once and use it everywhere? How do you design for change while still creating that visual impact?

Tools like Figma have made this easier, but honestly, the mindset is more important than the software. Thinking in systems is a skill that outlives the tools.

AI Is Here ... And That’s (Mostly) a Good Thing

Let’s talk about the elephant in the room ... AI.

There’s a lot of noise out there ... hype, fear, big promises. I’m not convinced AI will replace designers. But I am convinced it’s going to deeply impact how we start, learn, and overall become more efficient.

I’ve been experimenting with layout suggestions, copy generation, even asset creation. And here’s what I’ve noticed ... getting to a first draft is now the easy part. The real skill is in shaping it, editing with intention, knowing what not to keep and where to dig deeper.

If you’re resisting AI tools because they’re not perfect, you’re missing the point. AI is not here to finish the work, it's here to get you past the blank canvas faster with thoughtful exploration.

Collaboration > Execution

Here’s an underrated skill: being good at feedback! Giving it, receiving it, and navigating it without an ego.

I’ve seen incredible design evolve inside FigJam whiteboard sessions, Slack threads, comments on comments. It’s not always glamorous, it’s not what you show in your portfolio ... but it’s the real work.

More and more, our tools are built for teams, not solo flights. Figma is a multiplayer canvas, that’s not a coincidence.

The better you are at working with others, the better your design outcomes ... Period.

I’m Not a Developer, But I Think Like One (Sometimes)

I’ve never wanted to become a full-time front-end developer. But I’ve also never regretted learning how to do basic coding within web or native apps.

Knowing what devs care about ... layout systems, responsive constraints, performance. Honestly helps me design smarter. It’s not about writing code, it’s about understanding what your design decisions mean in production and how they impact the code.

Think of it this way: Designers who can think like devs ... not code like them, but think like them ... will always have an easier time collaborating and creating meaningful products.

If you’re a designer who doesn’t want to learn to code, I get it. But I’d still encourage you to sit in on dev meetings, don't be afraid to ask questions. Spend the time to build a shared language, teach them your tools and your approach, in the end it pays off. This approach doesn't care what design tools you use, it's a system of working together that will last.

What I’m Doubling Down On Instead

Here’s what I’m focused on getting better at right now:

• My overall UX strategy and approach
• Staying on top of standards (HIG / Material / Etc.)
• Accessibility and inclusive design
• Writing for clarity
• Facilitating better workshops and reviews
• System thinking

These things have outlasted every tool I’ve used. They’re not always glamorous and they’re not necessarily new. They build a structure, a foundation, something reliable. And they make every new tool more powerful when you do decide to use it.

The TL;DR: Zoom Out

If you’re feeling overwhelmed by tools, try zooming out and step back.

You don’t need to learn everything. You don’t need to jump on every new beta or hot new product showing off unrealistic designs on social media. You need to know what kind of designer you want to be ... and invest in the skills that get you there. After that find the tools that fit your needs, master them, and leverage your tool set to be an efficient and meaningful designer on your team.

Focus on what makes you a better designer, not just a better software user. And take it from someone that has seen seismic shifts from design tools over the years ... tools will keep changing and you can't control that, what you choose to learn and master you can control and is up to you!

I'd love to hear about your thoughts, connect with me on LinkedIn and let's chat.

Until the next volume, thanks for joining me. 
Andrew Preble