Whether we want to admit it or not, our industry is going through one of the most dramatic shifts we've seen in decades. Web design has always evolved alongside technology. In the late '90s, we moved from table-based layouts and transparent GIF spacers to semantic HTML and CSS. In the late 2000s, responsive design fundamentally changed how we thought about interfaces as screens expanded from tiny smartphones to ultrawide monitors. Each of those moments forced designers to rethink their craft.
Today we're experiencing another transformation. AI-powered design tools can generate layouts, write code, create illustrations, and prototype applications in minutes. Work that once took days - or even weeks - can now happen before you've finished your first cup of coffee. It's exciting, a little intimidating, and impossible to ignore. But while the tools have changed dramatically, the need for thoughtful design hasn't disappeared. Instead, the role of the designer is changing.
The roles, they are a changin'
Lately I've found myself asking a simple question: "What does it actually mean to be a web designer today?" It's a fair question. If a stakeholder can generate a landing page with AI, or a developer can spin up a polished interface with a few prompts, it's easy to wonder where designers fit in. For much of my career, projects followed a familiar rhythm: understand the problem, estimate the work, create wireframes, refine the design, then build it. AI is compressing many of those middle steps from weeks to hours.
That doesn't make designers obsolete. It simply shifts where we provide the most value. Design has never really been about drawing boxes on a screen. The real job has always been understanding people, solving problems, making trade-offs, and helping teams build the right thing - not just build something quickly. AI makes execution faster. It doesn't replace judgment.
Where Designers Create Value
If I had to give one piece of advice to someone entering design today, it would be this: don't focus on becoming better at pushing pixels. Focus on becoming better at solving problems.
That means learning how to identify the right problems before anyone starts designing. It means advocating for the people who will actually use the product. It means understanding accessibility from the beginning instead of treating it as an afterthought. And it means expanding your technical knowledge so you can collaborate effectively with engineers and make the most of modern tools - including AI itself.
The designers who thrive over the next decade won't necessarily be the ones who make the prettiest mockups. They'll be the ones who help teams make better decisions.
Don't be just another designer - Become a consultant
One of the biggest opportunities AI creates is pushing designers further upstream in the product process.
Instead of waiting for someone to hand you requirements, help define them. Ask why a feature exists before discussing how it should look. Dig into user research. Interview customers. Look at analytics. Challenge assumptions. Help stakeholders understand what problem they're actually trying to solve.
One phrase that keeps coming up whenever people talk about AI is "garbage in, garbage out." It's become a cliché, but it's true. AI can produce impressive work - but only if it's solving the right problem with the right context.
Think of it like building a house. If the foundation is crooked, it doesn't matter how beautiful the walls are. The entire structure will have problems. Design works the same way. A designer's ability to frame the problem is becoming more valuable than their ability to draw the solution.
Put Humans First
No matter how sophisticated our tools become, we're still building software for people. That sounds obvious, but it's surprisingly easy to forget. We spend our days looking at screens, design systems, and component libraries, while our users are simply trying to accomplish a task. They don't care how elegant our Figma file is. They care whether they can complete their work without confusion or frustration.
That's why human-centered design matters now more than ever. Talk to users. Watch how they use your product. Ask questions instead of making assumptions. Test your ideas early. Listen to feedback, even when it's uncomfortable. In my experience over the years uncomfortable feedback is 10x more valuable than a simple "I like it, it works and looks great".
AI can generate interfaces, but it can't build empathy. Understanding the frustrations, motivations, and behaviors of real people is still one of the most valuable skills a designer can have.
Put ALL Humans First - Accessibility Is Design
Accessibility isn't a feature you add at the end of a project. It's part of good design.
For years, many teams have treated accessibility as technical debt - a checklist to run through before launch or a compliance issue to fix after the fact. Too often it's viewed as a pass-or-fail exercise instead of a fundamental design principle. We have to change that mindset.
Accessible design creates better experiences for everyone. Clear language, sufficient contrast, logical navigation, keyboard support, descriptive labels, and thoughtful interaction patterns help people with disabilities - but they also improve usability for every user. Accessibility should influence every design decision from the first sketch to the final release.
As designers we should be advocating for it from day one and treating it as a standard, not asking whether there's enough time to fit it in.
Learn Enough Code to Have Better Conversations
Throughout my career I've worked with designers who refused to touch code. Some couldn't write a basic HTML page. Others only knew how to work inside a single platform like WordPress. Years ago that specialization was often enough. Today the expectations need to be different.
You don't need to become a full-stack engineer, but you should understand how the web works. Learn semantic HTML. Understand modern CSS. Know what responsive layouts actually do under the hood. Get familiar with component-based frameworks like React or Angular - not because you'll necessarily write production code every day, but because you'll collaborate more effectively with the people who do. Being able to communicate with developers is an extremely underrated skill. If you come up with a feature you should know if its something that could be done in an afternoon or two weeks. Trust me, your developers will thank you.
The good news is that it's never been easier to learn. Between AI assistants, open-source projects, online documentation, and countless free tutorials, the barrier to entry is incredibly low. A laptop, curiosity, and consistency are enough to get started. The more you understand the medium you're designing for, the better your designs will become.
Build Something You Actually Care About
One of the hardest parts of learning isn't the technology - it's deciding what to build. Here's my advice: find a problem you genuinely want to solve.
I'm a genealogy nerd, so I wanted a private family tree application. I built the first version with Jekyll and stored everything in YAML files. Later I rebuilt it in Ruby on Rails with a proper database. Eventually I rewrote it again in React. There were no stakeholders. No deadlines. No sprint planning. No creative director giving feedback. Just curiosity and the freedom to experiment.
I think that's a much better way to learn than endlessly following tutorials that teach everyone to build the same travel website or shopping cart. Those projects teach syntax, but they rarely teach problem solving.
When you solve a problem you actually care about, you'll naturally stick with it longer. You'll make real design decisions, encounter real technical challenges, and end up with something meaningful in your portfolio that you'll care about. Heck, you may even have a product on your hands.
The Future Belongs to Designers Who Keep Learning
The designers who will succeed aren't the ones competing with AI to make screens faster. They'll be the ones asking better questions, understanding people more deeply, collaborating across disciplines, and using AI as a tool instead of seeing it as a competitor. Technology will continue to change. It always has.
AI isn't the end of design. It's the end of treating design as the production of static mockups.
The skills that matter most, though - curiosity, empathy, critical thinking, communication, and the ability to solve meaningful problems - have never been more valuable.
If you're just starting your career, don't be discouraged by the pace of change. Embrace it. Learn broadly. Build things. Talk to users. Keep asking why.
The tools will evolve, but great designers have never been defined by their tools. They've always been defined by the problems they're able to solve.