Technically, I'm a designer...
However, over the past decade (as titles have become more specific, roles more specialized and responsibilties more broad) the definition of what it means to be a designer has evolved and changed dramatically. I began my career focusing on visual and graphic design - spending my earliest years at a New York advertising agency. As companies began to prioritize 'digital transformation' my career did as well. Along with learning and applying user centered design principles and digital product development methodologies I eventually moved to the west coast. It was there I began to learn to code for personal projects and out of curiosity.
Companies across all industries have realized the business value of design. Consequently, whether industrial, digital, services or a combination, expectations have been set higher and skillset requirements have expanded. Processes and methodologies have been adapted from other industries - all in an effort of gaining a competitive edge. The goal: to deliver consistent high quality results that leverage new technology and engaging experiences.
A modern designer must be able to play contradictory roles at a moments notice. We're constantly adapting and questioning things, while at the same time refining our craft, learning new technologies and gaining a higher level understanding of what we're ultimately working towards.
I come from a diverse background (more on that here) and eventually my curiosity and continual learning of code opened doors to new opportunities as I expanded and refined my skillset. Ultimately, after a few years dedicated to technical roles, I decided to return to more design-centric ones.
Technical knowledge is a nice-to-have and allows me to design with consideration given to any technical limitations or opportunities. This has been indespensible when establishing a design system or working as one of the first design hires for a startup by ensuring there is no handoff gap but rather collaboration from the start.
The foundation of good design isn't technical or specialization of any kind - it's communication and empathy. Delivering a product whether digitally or physically requires things that aren't taught but learned, refined and acquired over time. At a high level, the modern designer needs to understand their role, how it relates to the development process, as well as the organization, company and products they're creating. Without context and an understanding of the underlying systems or development process that drive business goals - how can a designer hypothesize the best solution? 'Design' is no longer just the 'look and feel' of a product. It's even more than one of many dimensions of a product.
Consequently, it isn't the responsibility of one group or organization to be applied to the surface at a designated stage of development in a silo.
While it might sound overwhelming - having the ability and opportunity to ideate, create and learn new things as demands change each day is one of the most exciting parts of the job. With the paradigm shift away from command-based interfaces towards intent-based outcome-specific ones and the introduction of spacial and natural language interfaces, there's arguably never been a better time to be curious. We've already stepped into a new era and I'm excited to see what's next.