May 26, 2015
4 min

Are small links more attractive to people as icons or text?

"Dear Optimal Workshop
How do you make a small link attractive to people (icon vs. text)?"
— Cassie

Dear Cassie,

I'm going to dive straight into this interesting question with a good old game of Pros and Cons, and then offer a resolution of sorts, with a meandering thought or two along the way. Let's kick things off with Team Icon.

The good side of icons: A picture is worth a 1000 words

When shopping online, the number above the little shopping trolley icon tells me how badly behaved I’ve been, and if I click on it, I know I’ll get to gleefully review all the shoes I've selected so far. There’s a whole heap of icons out there like this that people have absorbed and can use without thinking twice. Marli Mesibov wrote a fantastic article on the use of icons for UX Booth on the use of icons that is well worth a look. Marli discusses how they work well on small screens, which is a definite bonus when you’re on the go! Young children who aren’t yet literate can easily figure out how to open and play Angry Birds on their parent’s smartphones thanks to icons. And icons also have a great capacity for bridging language barriers.

The not so good side of icons: We’re too old for guessing games

On the flipside, there are some issues that may huff and puff and blow that cute little home icon down. Starting with there being no consistent standard for them. Sure, there are a handful that are universal like home and print, but beyond that it seems to be a free-for-all. Icons are very much in the hands of the designer and this leaves a lot of room for confusion to grow like bacteria in a badly maintained office refrigerator. Difficult to understand icons can also seriously hinder a user’s ability to learn how to use your website or application. When icons don't communicate what they intend, well, you can guess what happens. In a great piece advocating for text over icons, Joshua Porter writes about an experience he had:

"I have used this UI now for a week and I still have do a double-take each time I want to navigate. I’m not learning what the icons mean. The folder icon represents 'Projects', which I can usually remember (but I think I remember it because it’s simply the first and default option). The second icon, a factory, is actually a link to the 'Manage' screen, where you manage people and projects. This trips me up every time."

If people can't pick up the meaning of your icons quickly and intuitively, they may just stop trying altogether. And now, over to Team Label.

The good side of text: What you see is what you get

Sometimes language really is the fastest vehicle you've got for delivering a message. If you choose the right words to label your links, you'll leave the user with very little doubt as to what lies beneath. It’s that simple. Carefully-considered and well-written labels can cut through the noise and leave minimal ambiguity in their wake. Quoting Joshua Porter again: "Nothing says 'manage' like 'manage'. In other words, in the battle of clarity between icons and labels, labels always win."

The not so good side of text: Your flat shoe is my ballet pump

Text labels can get messy and be just as confusing as unfamiliar icons! Words and phrases sometimes don’t mean the same thing to different people. One person’s flat enclosed shoe may be another person’s ballet pump, and the next person may be left scratching their head because they thought pumps were heels and all they wanted was a ballet flat! Text only labels can also become problematic if there isn’t a clear hierarchy of information, and if you have multiple links on one page or screen.  Bombarding people with a page of short text links may make it difficult for them to find a starting point. And text may also hold back people who speak other languages.

The compromise: Pair icons up with text labels

Because things are always better when we work together! Capitalise on the combined force of text and icons to solve the dilemma. And I don’t mean you should rely on hovers — make both text and icon visible at all times. Two great examples are Google Apps (because nothing says storage like a weird geometric shape...) and the iPhone App store (because the compass and magnifying glass would pose an interesting challenge without text...):

When text and icons wins

So what comes next? (You can probably guess what I'm going to say)

Whatever you decide to run with, test it. Use whatever techniques you have on hand to test all three possibilities — icons only, text only, and icons and text — on real people. No Pros and Cons list, however wonderful, can beat that. And you know, the results will probably surprise you. I ran a quick study recently using Chalkmark to find out where people on the ASOS women's shoes page would click to get to the homepage (and yes, I can alway find ways to make shoe shopping an integral part of my job). 28 people responded, and...

Chalkmark first click text

...a whopping 89% of them clicked the logo, just 7% clicked the home icon, and just one person (the remaining 4%) clicked the label 'Home'. Enough said. Thanks for your question Cassie. To finish, here's some on-topic (and well-earned) comic relief (via @TechnicallyRon)

When icons go wrong
Share this article
Author
Optimal
Workshop

Related articles

View all blog articles
Learn more
1 min read

The importance of roles in making meaningful project experiences

In this post, Daniel Szuc describes why it’s important to go beyond how we may see our roles traditionally when only focusing on job titles. By exploring other roles, as outlined in the post that follows, we can all play a part in helping to glue a team together, making project work easier for all and creating a more positive environment to help in making meaningful project experiences.

Collaboration is hard and needs practice 🙂↔️

“Collaboration” is a term that gets thrown around in workplaces to encourage people to work together better. Sometimes, though, the people using the term may not understand the range of skills required to make collaboration work well, including (but not limited to) listening, expression, empathy, and curiosity.

Each of these skills requires practice.

So asking people to simply collaborate, without understanding the skills required nor the necessary spaces to practice these skills, may well frustrate people more than it helps.

Misalignment 😤

As work hums along in a team, it’s easy for misalignment to creep in. Misalignments are caused by a lack of communication, limited time, poor project management, and micro/macro issues that are addressed too late, causing friction between people. If specific roles are not put in place, these frictions can create difficult work environments, making coming to work unpleasant.

Teams may lack common artifacts to help them communicate with a shared language, which in turn helps connect a project and business narrative together. Importantly, this helps aggregate what a team learns together from customer interviews to help improve a product or service.In effect, there is no light leading the way, so people can get lost in details that have nothing to do with a common and well understood purpose.

Roles beyond a job title 👔

When we speak about roles, we are not referring to traditional job titles such as project manager, developer, and designer, for example. Rather, we mean roles that everyone can play at various points in a project, helping others do their job well and the team deliver on making meaningful experiences.Roles, beyond job titles or the tasks inherent in those titles, help people think in integrated and holistic ways beyond their official job title.

At times, our work requires that we delve deeply into design details; in other situations, we are required to step back and see how all the elements of our work connect in delivering solutions that are part of a broader narrative.As members of teams, we can work more effectively – whether it’s by advancing ideas or in recognizing when it’s time to consider alternative approaches.

Four roles for making meaningful experiences 🎢

We have identified four roles to encourage making meaningful experiences for the team and customers, as well as to encourage integrated ways of working:

  1. Facilitators can define approaches that guide the process of informing, sense-making, and evaluating. They can craft agendas for working sessions and identify what problems need attention. Facilitators can also manage interactions between functions, aggregate a team’s learnings, and map these learnings to shared artifacts. They identify themes that require further study and set goals for the team’s next sessions.
  1. Mentors need to be aware of approaches and skills that require ongoing development and practice, and organize safe spaces in which people can practice, using them over and over during working sessions and across projects. Mentors should work closely with facilitators and custodians to identify the knowledge that the team has captured and map it to a learning program for team members, with a focus on informing, sense-making, and evaluating.
  1. Connectors create artifacts that help bridge gaps and make interactions between people feel more fluid, connecting people’s skills and roles.
  1. Custodians maintain the knowledge base that forms over time and leverage it in creating approaches and courses that help our project teammates to improve at what they do.

Practicing shared skills within roles ⚙️

Independent of whether a person works in management, engineering, product management, design, user research, or some other function, there is a common set of skills of which people need to remain aware: skills that help make our project teams’ collective efforts better.Because there is an intention to integrate ways of working, collective learning makes teamwork effective and results in more meaningful experiences. Working sessions, in which people from different teams or functions come together to solve a problem, provide a common space to focus on that problem, define approaches to help solve the problem, and work through issues together.

A team can identify the skills they practice, reflect on any gaps that may require them to expand their practice, and aggregate their learnings in common artifacts. These then help form and guide a project narrative with which the team resonates or can critique.In understanding the ways in which we work together – in essence, developing empathy for each other – we may see other benefits in addition to the work we produce.One benefit could be to move away from a blind focus on just tools and processes towards a primary focus on how we approach our work together or how we think about problems within the context of a project.

The ways in which we interact with each other suggest that we should look at the following roles, again independent of function or job title:

  1. Informing a problem - What evidence or learnings have we gained to date? What outstanding questions do we need to answer? How would the answers inform the solution to a problem we’re solving now or over time?
  2. Making sense of the data we have - How can we make sense of our learnings as they pertain to specific questions or larger themes that we need to understand and for which we need to design solutions over time?
  3. Evaluating designs - How can we evaluate designs and iteratively improve a product or service and its positioning over time?

Questions for future consideration 💭

  • What roles resonate with you more?
  • What roles do you think are missing?
  • What skills do you need to practice in order to help your team make more meaningful experiences?
  • What skills do you think are missing?
  • What gaps, if any, do you recognize between roles on project teams?
  • What frictions exist on a team and why do you think they occur?
  • How can customer interviews – as one approach to understanding customer stories – encourage constant cycles of informing, sense-making and learning in the spirit of the learning organisation, so to help glue team practices together and create integrated ways of work?

Acknowledgements

Thanks to Josephine Wong for contributing to this piece. For more, see Integrated Approaches to Constant Personal Learning, Improvement, and Maturity.

Learn more
1 min read

CRUX #6: Information architecture in unexpected places

According to Abby Covert, author, teacher and community leader in the field of information architecture (IA) : ‘IA is the way we arrange pieces of content to make sense when experienced as a whole. By this definition: there is information architecture in everything. Mindblown?’

😮 (That’s a resounding yes from an IA rookie like me.)

In this issue of CRUX we go in search of information architecture and have some surprising encounters in the worlds of emoji, elevators, walking tracks, games and more. We meet UX designers, developers, researchers and even a Senior Park Ranger. It seems you can have your ‘IA hat’ on without even realising it. That’s the power of information architecture.

Some highlights from this issue:

  • UX research and strategy specialist, Q Walker explores the world of emoji from an information architecture perspective and sparks curiosity along the way. Have you ever wondered why clock emojis are organized under travel and places? 🤔
  • We talk to Senior Park Ranger David Rogers about the thinking behind creating and building New Zealand’s national walking track network and reveal how information architecture can also live ‘in the wild’.
  • UX developer Ben Chapman delves into the classification systems of libraries over time and ponders the pros and cons for users of moving information online.
  • We talk to Sam Cope, Lead UX Designer at Wētā Workshop’s Interactive division about what it takes to drive design decisions with the end user in mind - something crucial for any video game’s success, whether it’s a blockbuster or something more niche.
  • And much more about information architecture in unexpected places….

The stories and people in this issue of CRUX certainly captured our imagination and attention - we hope they inspire and even surprise you too.

Get comfortable and settle in for a great read. Welcome to CRUX #6.

A plug for the next issue

Do you have a burning idea to share or a conversation you’re dying to kickstart that’s of interest to the world of UX?  Now’s your chance.  We’re already on the lookout for contributors for our next edition of CRUX for 2022.  To find out more please drop us a line.

Learn more
1 min read

Navigating the Complexities of Information Architecture vs Data Architecture

Thanks to an ever-growing digital world, businesses are spoiled for information and data. The more complex the business, the more information there is and the more complicated the business requirements are. But where there are challenges, there is opportunity. That’s where information architecture and data architecture come in.

Information and data architecture both seek to make sense of the plethora of information a business handles. However, the two have different roles to play in the way businesses use, move, maintain, and present data - both to internal and external stakeholders. So what are they and why should businesses take note?

Defining Information Architecture 🗺️

Information architecture is the structure used to organize and label content on websites, mobile applications and other digital environments. Its primary purpose is to enhance user experience by ensuring information is structured in an accessible, usable and relevant way.

Information architecture seeks to understand user needs and goals by analyzing both existing and required information, then building an information framework in a logical and user-friendly way. It deals with three main components:

  • Labels: How information is represented
  • Navigation: How users make their way through the information
  • Search: How users look for information

Whilst this information sits in the background, it’s the layer upon which you build the design of your digital products.

Information architects bring data from file systems and databases to life by building meaningful narratives and stories. Outputs can include site-mapping, information architecture diagrams and content inventories. These outputs are supported by user research techniques such as card sorting, tree testing, user surveys and first-click testing.

Defining Data Architecture 💻

Data architecture bridges the gap between business needs, goals, and system requirements related to data handling. It sets out a framework for managing data assets, the flow of data and the maintenance of data systems. As such, it has a slightly more macro view than information architecture and concerns itself with emerging technologies such as artificial intelligence, machine learning, and blockchain.

Where information architecture centers around the end-user interaction, data architecture centers around practical handling and operation of data processes i.e. collection through to transformation, distribution, and consumption. Because of this, data architecture must take into account the businesses ability to scale operations, integrate with third party systems, support real-time data processes and the reduction of operating costs. Modern data architecture may point to artificial intelligence to tackle some of these challenges.

The Importance of Enterprise Architects in Information and Data Architecture 🏗

Enterprise architects are big-picture people. Data architecture and information architecture both fall within their remit, and they often oversee other data management job specialities within an IT department.

As a leader (and often, visionary) within a business, enterprise architects shoulder the responsibility of ‘mission critical’ projects. As a result, they tend to have several years experience with IT systems, backed by a bachelor’s degree in computer science, IT management, data science or similar. Many will hold a master’s degree and specialty certifications.

The role involves collaborating with senior business leaders, solution-delivery teams and external stakeholders, and requires creative problem solving and excellent communication skills. Therefore, enterprise architects very much steer the ship when it comes to information and data architecture. Combining high-level business strategy with knowledge of ‘the nuts and bolts’ of IT data systems and processes, they command an annual salary in New Zealand between $150,000 and $200,000 per annum..

Continuous improvement within any business that has substantial IT infrastructure calls for serious investment in enterprise architecture.

Designing and Implementing an Effective Information and Data Architecture 𝞹📈🧠📚

Once overarching business goals are aligned with the scope of data and system requirements, information and data architecture design (or redesign) can begin.

Crucial to the design and implementation process is developing an architecture framework. This is a set of guidelines that lays out principles, practices, tools and approaches required to complete the design. It supports system design decisions, assigns key tasks and provides project guidance throughout the design process. The framework essentially aims to unite disparate teams and maintain business and IT alignment.

The choice of architecture design is also critical. It should consider scalability, performance, maintainability and adaptability to emerging technology. Which is why cloud platforms feature so heavily in modern data architecture. Cloud architects will navigate the architecture design and technical requirements of cloud-based delivery models, which offer the solution to those scalability and adaptability challenges. They are responsible for bridging the gaps between complex business problems and solutions in the cloud. Modern data architecture tends to involve some form of cloud delivery component.

Throughout implementation, data and information architects will work closely with designers and engineers until testable architecture is ready. User research and testing will be carried out, and a feedback loop will commence until requirements are met. Users, as always, should be at the center of your digital product.

Summing Up the Complexities of Information and Data Architecture 🧮

Whilst the difference between information and data architecture can appear nuanced on the surface, they hold unique roles when delivering a cohesive, user-friendly digital product.

Think of a sliding scale where business operations sit at one end, and users sit at the other. Data architecture addresses challenges closer to the business: aligning business requirements and goals with how data flows through the system. On the other hand, information architecture addresses the challenges related to how this data is organized and interpreted for the end user.

At the end of the day, both information and data architecture need to work in harmony to satisfy the user and the business.

Seeing is believing

Explore our tools and see how Optimal makes gathering insights simple, powerful, and impactful.