👋 Oi, mga repapips, Brian Dys here! I love music, photography, and creative stuff like UX design and art. This is a place where I collect my thoughts and works. Apart all these, I’m Jaycelle’s better half and Bryce’s dad. 🥰
But I know every rock and tree and creature
Has a life, has a spirit, has a name
Colors of the Wind
The Name—Description—Purpose Information Structure or NDP becomes a tool in identifying any UI element within a system. The Designer would have a glimpse of what it is called (Name), what it does (Description), and why it exists (Purpose).
Be a jack of all trades and a master of none or a master of one (and more)? It is an age-old question.
It depends on the environment where you want to focus on:
- in a one-man band freelancing: jack of all trades
- in a company with team members with specializations: specialize
- in a company with “all-around” team members: jack of all trades
In general, be the best at one thing and not so best or at least familiar with other things.
There are many default usability styles designed by the browser.
Sometimes it is best to leave it alone because it covers a lot of area that you might not be able to cover if you nitpick it.
Now if the color of the outline clashes with your branding like “blue is really banned from your UI” then change it.
Or if the outline color is the same as the background color, it won’t be seen, of course, so change it.
It’s important to note that styles whose main purpose is usability must be left alone especially if your purpose is to simply comply with color schemes.
There are initial points to take into consideration in order to make sense of the connection between HTML elements (
<div>, etc.) and CSS properties (display, font-size, background-color, etc.).
- The nature of the HTML element
- The purpose of the HTML element
You might notice that it is all about HTML elements. This is because HTML elements already have implicit CSS rules in them thru the browser. It is called the User Agent Styles or browser default styles.
Now your question borders around creating your own styles, thus, overriding the default styles.
- Roles & Capabilities
- Skills & Personalities
- Reliable & Resilient
- Flexibility in the Roles
- Learning other areas
- Do not design in an assembly line — always have a view of the bigger picture
- Passion. What motivates them?
- Curiosity. Are they willing and prone to ask important questions, especially before they start creating?
- Communication. How do they articulate the problems they’re working on? How do they help others understand the solutions they’re considering?
- Engagement. What’s their view of the design process? What steps do they take to approach it?
- Autonomy. Are they able to understand the big vision and work toward it? Are they pushing the team forward with new insightful ideas, or are they dragging it behind by needing to be told what to do next?
- Reveal themselves — strengths and weaknesses
- Problem-solving Capabilities
- Take–home Tests regarding a real-life problem they have
- Design concept
- Problem solving
Let’s frame your question in the following:
- You’re applying for a web development company
- Your portfolio currently would not demonstrate your superpowers
- But a Test Project will
- You are applying for a User Interface Designer position
- In the company, they have a UX Researcher and a UX Designer in the team
- You would like to foresee the Test Project that they will give you to be able to prepare for it