I'm working to make this project look better. I'm reviewing the content
Matter of fact, if this new tools keep on being asked by customers like the one I present you Lumsa University, well it might be possibile to experience a new era of world wide web where users will be interacting with virtual assistant first, then navigating to pages. With this being said, Nielsen says that all the heuristics know until today might not be so effective the same way we, as Designers, have studied and applied across the past decades
As already mentioned in Nexa web app product, Lumìa is targeting professors, personal technical administrator and students. We as team covered the user analysis with stakeholders from Lumsa University to make sure we could meet the desired business requirements and satisfy users needs that evolve with technology advancement
Planning a backlog is the secret sauce to keeping a development & design team aligned, efficient, and focused on delivering actual value. Without it, a backlog quickly turns into a "black hole" of forgotten ideas and outdated feature requests. As IXD Designer I had the chance to structure a dedicate backlog for design User Stories and Tasks to provide Developers with info details about User Centered Design framework of processes
Here I wrap Nexa Design Library components to create UI templates. In fact, templates are pre-designed layouts, components, and wireframes that allow developers and designers to build the app without starting from scratch. Not to mention, that this method helps myself as well, as I don't have to update every single screen everywhere across the design files. Also, they ensure visual consistency, accelerate production speed, and incorporate UI best practices.
Starting off with Student Profiles experience either on Desktop, laptop and mobile:
Next I designed Interfaces for Professors:
Not to mention the Personal Technical Admin, a staff that would setup and manage the Virtual Assistant with their new brand back office
I offer refer to this design beat as design Breakdown, as I put down all the interaction necessary to understand what happens under a prototype and or a visual architecture. In fact, here I place Ui Clusters which contains an amount of standalone screens and components to explain the design engine. A Ui Cluster works best, if they are connected with arrows and sidenotes (a design library i created out of the file) that helps the readers (stakeholders and develoeprs, even other designers) to understand the interaction playground
Starting off with Student Profiles Ui Cluster breakdown:
I designed Interfaces for Professors interactions as well
And above all the Personal Technical Admin, the most complex storyboard as these type of user need more interactions and sections to setup and manage the Virtual Assistant with their new brand back office
OK now, Let’s strip away the implementation details. I'm talking about a formal, written PDF document (often called a Product Manual or Functional Specifications Document) that describes the web application's interface. When you are writing and designing this kind of long PDF guide, it serves as the ultimate reference manual for designers, developers, or clients. It is a comprehensive document that deconstructs a web application into its fundamental visual parts. It acts like an architectural blueprint of the user interface. Instead of just showing screenshots, it maps out the purpose, behavior, and content rules of every single section (block) on a page.
Because this could have been a long PDF, readers would have got lost, if the text is too dense. So I split the web app content according to the subject. here I created the Virtual Assistant Manual where I explain everything about the it with the help of images and related text
When the client Lumsa handed over us their Google Analytics, they were giving us the keys to their digital kingdom. For an Interaction Designer like me (even a content strategist, or copywriter) this data is gold. It tells me exactly what is working, what is broken, and where users are getting lost. And most of all it tells me about browser and its versions, devices, viewports & breakpoint being used by Lumsa Student. Since this data is usually given raw, so I have to analyze it, meaning I often have to deduct the given infos and make final heuristic assumptions according to tech hardware and software progress at that time. Next, I translate the raw data with simple words, so that stakeholders and my peers can better understand it
Speaking of user interface, I wrote a dedicated manual about the Visual Architetcture that help Ui Templates stay together. Often referred to a Design System Manual or Information Architecture Blueprint, this document is a comprehensive technical document. It defines the structural, hierarchical, and visual rules of a product’s interface. Think of it as the blueprint of a building. While a standard UI kit gives you the materials (the bricks and windows), the Visual Architecture Manual explains how the entire building connects, floors are mapped, and spaces are utilized!
Finally, all the work has paid off! Now student can interact with Lumìa to explore, search, question, study and do much more to increase their experience at Lumsa University. This project has received numerous likes frome veryone, specially the user themeselves, as Lumìa is providing them with awesome features on daily basis
