UX: The One-Stop Guidance Principle
Join the DZone community and get the full member experience.
Join For Freeearlier this year i posted a blog about our move to the new office . then, after a while, i wrote about the unexpected harmony of the circular walls . our new office never stops to inspire me. today i’ll explain one basic ux design principle, relevant both for the navigation in user interfaces, and for the real world.
if you’ve been following our blog this year, you might recall that the office occupies the entire level in a 3-tower office building. here’s the sketch of our office space:
the three towers have been named by the colors: the orange, the blue and the green tower (you can check the colored plans for each of the towers here ).
now, imagine how we felt as we just moved in here. a huge office space of ~10,800 sq ft, the orange, the green and the blue towers, not yet painted back then… and the entryways that went into some unknown directions, as you were trying to get to any of the towers. we were lost at first, and the quick-fix solution for a faster navigation was this:
the stickers posted on the doors of the elevator hall. it’s simple. when you’re exiting one of the towers, you face these doors, and you can’t see the walls of the other towers. you are supposed to figure out that if the blue-colored sticker is on the left, then you should take the entryway on the left. the green-colored sticker is on the right, so head to the entryway on the right if you want to get to the green tower (a very popular route by the way, as our sports-room and dining space are located in the green tower :)
then, as we settled in, we implemented a one-spot guidance framework to get to any tower: a certain pattern for painting the walls. wherever someone exits one of the towers, if they are visitors, or some new people, they have these two questions on their minds:
- where i am? in which tower?
- how do i get to where i need? to my destination tower?
all right, what happens if you want to go from the orange tower to the green tower now? take a look:
the orange-green route
remember, that you can’t see this entryway when you’re just about to exit any of the towers. the semiotics is simple: the orange on the right means that you’re now in the orange tower. the green stripe next to this piece of orange means that this route will take you to the green tower, and you do see this green stripe with your peripheral vision as you’re facing the elevator doors when exiting the orange tower. then, once you make a couple steps to the right, you can see the green wall ahead of you, and that’s where you are certain that now you’re on your way from the orange tower to the green tower.
the other routes are marked in the same fashion. if you refer to the image on the top, you’ll see that the entryways between the towers form a triangle, the sequential counter-clockwise flow. the orange-green route makes the first side of this triangle (as i’m residing in the orange tower :).
keep in mind that the orange-green route and the other two images do not include the elevator doors (if honest, it’d be too hard to take such a picture for me), only the pieces of the “departure” tower and the “destination” tower:
the green-blue route
.. and the blue-orange route completes the counter-clockwise motion along the entryway triangle:
the blue-orange route
you get the idea now. if we go clockwise, the sequence will be orange-blue, blue-green and green-orange, with the same painting patterns on the walls used.
i can easily draw an analogy between this simple gps semiotics in our office space, and the navigation in user interfaces. users feel very comfortable and in the flow if they can answer those 2 questions:
- where i am now?
- how do i get to where i need to get?
once your software app makes them feel confident in their answers, this can account for as much as 90% of success.
Published at DZone with permission of Olga Kouzina, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.
Trending
-
Competing Consumers With Spring Boot and Hazelcast
-
Implementing RBAC in Quarkus
-
Does the OCP Exam Still Make Sense?
-
Implementing a Serverless DevOps Pipeline With AWS Lambda and CodePipeline
Comments