It may sound like a simple question, but it’s a little more complicated than that, as it always is in the software world. Where should your breadcrumb start?Īn important part of the breadcrumbs conversation, when you’re depicting a hierarchy, is zeroing in on where to start. We suggest reviewing documentation, reading up on databases and drawing or mapping out your data. You’ll have to collaborate with a data architect, back-end developer, or even a data analyst/scientist type of person to fully understand how things are put together in your product. Understanding data is a key enterprise UX skill, and is essential for designing other interactions in your software like data tables and data dashboards, so face the music and get your hands dirty. We can say with confidence that you cannot design a halfway decent breadcrumb experience without deeply understanding your data. This is the scrappy, collaborative and downright nerdy part of the equation. This is the part they don’t mention very often on double diamond design frameworks□. To make good design decisions about breadcrumbs, regardless of the type of breadcrumb you have, requires a robust understanding of your data. So, if breadcrumbs aren’t simply depictions of the data architecture of your product, then how can breadcrumbs be structured? What are the types of breadcrumbs overall?īreadcrumbs and data structure Get to know the data ( Sorry, we’ve got this edgy take Norman, but we think you’ll understand. In brief, digital experiences are wildly varied and complex, so losing context or ‘history’ may block us from delivering a great experience. Sustaining context in various ways gets super important because users are expending a lot of brainpower already and the stakes may be very high– any opportunities to keep this context can be very beneficial to users. When the user experience is tailored towards efficiency and productivity like it is in enterprise UX, preserving the user’s sense of place and understanding of the current state is paramount. However, use cases within our enterprise software are typically more complex and optimized for performance and task completion which means that some of the strict guidelines suggested by NN Group may need to be expanded upon. If we were talking strictly about casual website browsing, maintaining context about the user’s exact path would rightly be banned – as it is in NN Group’s article. may involve contextual representations of path and/or state
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |