Designers “should”

Boundaries and limitations

Every so often you stumble across a wave of posts about “Designers should…” where authors go into great detail about the rules, limitations and approaches you ought to follow. I’m a big fan of “to each their own” and letting people decide what works best for their own situation. Take other people’s unsolicited advice, mine included, with a grain of salt and figure out what works for you.

Designers “should” code?

Having a basic understanding of HTML and CSS will help you make the most of Figma’s Auto Layout features and give you a better sense of how responsive websites and mobile apps are built.s are built.

It also helps when collaborating with developers and testers. It goes both ways too — a developer with a basic understanding of design fundamentals can improve the collaboration process significantly. There’s also a strong case for playing to your strengths and having genuine respect for what other people bring to the table.

Should designers have a degree?

In my experience, universities can be behind the curve, with more focus on theory than real-world practical application.

If you learn by doing, you can teach yourself industry-recognised tools like Figma and Webflow for a fraction of the cost. The fundamentals of design can be picked up through books and online courses. That said, a degree might still be the right path for some people and how they learn best. It’s up for grabs.

Consider what makes the most sense for your learning style. A few good places to start:

• Figma – https://www.figma.com/resource-library/
• Webflow – https://university.webflow.com/
• Interaction Design Foundation (IxDF) – https://www.interaction-design.org/?r=rich-mcnabb

Should designers have a portfolio?

Every recruiter I’ve spoken with ends the conversation with “Send me your resume and a link to your portfolio.” With that in mind, consider structuring your portfolio around case studies rather than just finished screens. Explain your thinking, your approach and how you solved the problem. If you can, include real customer quotes and metrics to show the impact of your work.

I’ve suggested doing case study walkthroughs over design challenges during interviews. In my experience, design challenges don’t accurately reflect real-world problem-solving or give you the chance to explain your approach properly. A solid case study lets you speak with confidence about something tangible you’ve delivered, including the wins and the challenges.

You get to decide

Take on board what resonates and leave the rest. Stay rad ✌️