Flag

We stand with Ukraine and our team members from Ukraine. Here are ways you can help

Get exclusive access to thought-provoking articles, bonus podcast content, and cutting-edge whitepapers. Become a member of the UX Magazine community today!

Home ›› Design ›› You’re (just) a designer

You’re (just) a designer

by Nick Groeneveld
6 min read
Share this post on
Tweet
Share
Post
Share
Email
Print

Save

justadesigner_Slider

Are you a designer? It might be the case that you are not sure what to call yourself, or that you have difficulty explaining to others just what you do.

Are you a designer? Maybe you’re a visual designer, a user experience designer, or a product designer. Or something else. It might be the case that you are not sure what to call yourself, or that you have difficulty explaining to others just what you do (which is even more difficult). I know I have a hard time explaining my design role(s) to others.

Back in the day we all were (just) designers. There was a time where an agency had a creative director, his team of art directors, designers and maybe an intern or two. If you take a quick look around the office today you see an ever increasing number of design roles. Next to the (visual) designers you have user experience designers, service designers and sometimes even something called unicorn designers. Not to mention cool new design roles like design ninja’s and magicians you see at startups.

Anyway. Let’s focus on designers, user experience designers and service designers.

Where did user experience and service design come from?

As stated on Nielsen Norman Group’s website; “User experience” encompasses all aspects of the end-user’s interaction with the company, its services, and its products.”

If you believe design is about more than just pixels on a screen, I can imagine that you create your own view on design and how it should be, just like Don Norman did. It makes perfect sense. There’s a problem, however. If you skip a few years since he came up with the term user experience, you now see that we’re back where we came from. Many job openings still ask for “UI/UX designers”. The actual job openings that ask for UX designers do not always ask for UX the way Don Norman intended. In many of the UX designer job openings, designers are expected to deliver pixel perfect design, prototypes and maybe facilitate a workshop or two. There hasn’t been a lot of change in the role, except for a new name. Companies still consider UX designers to be a combination of a visual designer and what a UX designer should be. Don’t get me wrong. I understand why that’s the case. One employee who can do multiple things is cheaper than having an employee for every detail you’re working on. It is just not what Don Norman envisioned when he came up with user experience. That’s why we’re seeing a new kind of design emerging; service design.

Yet another split. (Web) design was too much about pixels, so we moved to a new kind of design; user experience design. In practice, user experience design is still believed to be too much about pixels, so now service design takes the center stage. They use the same arguments; user experience is too much about visuals. It should be about more than what you can see on your screen. Service design is about working together with your users and stakeholders. It is about the customer journey, user research and touch points. Visual design has a lower priority for service design than it has for user experience or web design. Maybe service design is the way Don Norman wanted user experience to be?

Finding the designer’s balance

It brings us to a question. Should design be about what you see on a screen? Or should we focus on everything else? Well… Design is about pixels on a screen. Just not only about pixels. It is a subtle balance between the screen and everything evolving around the screen. Great design is where business goals meet the user’s needs. That does include the screen. It doesn’t matter what you call the design role.

Designers come in different shapes and sizes. Some are called ’T shaped’, others are called ‘I shaped’ or ‘unicorns’. Maybe we should say designers are M shaped, or stop judging designers based on letter shapes all together. Sure, every designer has his specialty. You just can’t assume everybody has just one specialty (T shaped) or that his other skills are all on the same expert level (unicorn designer).

There shouldn’t be a different label for every individual designer. You’re a designer. You (should) possess basic skills to make your design stick. Those skills are the same, whether you call yourself a user experience designer, a product designer or something else entirely. You should be able to develop and facilitate design sprints and workshops, be able to do your research, validate your assumptions and be able to communicate and sell your design to your stakeholders. Don’t forget; you also have to be able to make an awesome looking visual design, whether it is a presentation, a user interface prototype or a research study. It’s part of your designer’s tool box.

Why are user experience and service design two different terms? Both consider themselves to be a holistic approach to design where they focus on the entire experience, not just the pixels on screen. In theory, user experience and service design are very similar. People just expect them to be something different because they have different names.

Design thinking

At Idean, we work using a double diamond visualisation of design thinking.

 

We work using three steps; discover, define, refine. It means that we start with collecting data and doing our research. We continue with prototyping during the define phase where we design different solutions and verify them. Once we have our core concept in place we continue during the refine phase. It’s a process of detailed design where we work in agile sprints to further refine and improve our concept into a full product.

Everyone at Idean can do the work using our design thinking framework. Even though we have visual designers, user experience designers and service designers in our ranks. We’re all designers, whatever kind of designer you call yourself. The designer’s tool box I mentioned before should be able to do the trick for the entire process.

Looking to the future

 
post authorNick Groeneveld

Nick Groeneveld

Nick is a designer with experience in UX, interaction and user research. He has worked as a design consultant in finance, healthcare and retail. As a designer, he believes design to be a holistic solution where the business’ goals meet the user’s needs. Nick currently works with Idean, Capgemini’s creative agency.

Tweet
Share
Post
Share
Email
Print

Related Articles

What if you could build software just by talking to your computer? Welcome to vibe coding, where code takes a back seat and the vibe leads.

Article by Jacquelyn Halpern
Vibe Coding: Is This How We’ll Build Software in the Future?
  • The article introduces vibe coding, using AI to turn natural language into working code, and shows how this approach lets non-coders build software quickly and independently.
  • The piece lists key tools enabling vibe coding, like Cursor, Claude, and Perplexity, and notes risks like security, overreliance on AI, and the need for human oversight.
Share:Vibe Coding: Is This How We’ll Build Software in the Future?
7 min read

Voice and immersive interfaces are no longer futuristic extras — they’re redefining how we shop, learn, and live. Is your product ready for this shift?

Article by Katre Pilvinski
Voice and Immersive Interfaces: Preparing Your Product for the Future of UX
  • The article shows that voice and immersive interfaces are becoming mainstream, not experimental.
  • It argues these technologies shine where traditional interfaces fail — in multitasking, accessibility, and spatial understanding.
  • The piece urges a voice-first mindset and a shift toward more natural, human-centered interactions.
Share:Voice and Immersive Interfaces: Preparing Your Product for the Future of UX
3 min read

The “3-in-a-box” era is dead. In an AI-first world, hand-offs kill products — only Snowball teams that build, test, and code together will survive.

Article by Greg Nudelman
Snowball Killed the Dev-Star: Stop Handing Off, Start Succeeding in the AI-First World
  • The article calls for the “Snowball model”: cross-functional teams building, coding, and testing with real users together from day one.
  • It argues that in AI-first UX, “design is how it works” — requiring designers, PMs, and devs to collapse silos, share ownership, and even code collaboratively.
Share:Snowball Killed the Dev-Star: Stop Handing Off, Start Succeeding in the AI-First World
11 min read

Join the UX Magazine community!

Stay informed with exclusive content on the intersection of UX, AI agents, and agentic automation—essential reading for future-focused professionals.

Hello!

You're officially a member of the UX Magazine Community.
We're excited to have you with us!

Thank you!

To begin viewing member content, please verify your email.

Tell us about you. Enroll in the course.

    This website uses cookies to ensure you get the best experience on our website. Check our privacy policy and