My book, Designing Usable Apps, is now available!
- How to conduct heuristic inspections for evaluating software usability
- Focus groups as a usability evaluation technique
- Analytics as a usability evaluation technique
- Quantifying cognitive load and task efficiency
- The impact of hardware devices on software ergonomics
- Software requirements in a nutshell
- Designing search systems
- Designing an interaction framework for your application’s tasks
- How to build a visual hierarchy to express relationships between page elements
- Interaction design and usability for data persistence and transactions
- Designing navigation and wayfinding in software applications and websites
- Designing your application’s interaction concept
- What characteristics contribute to a negative user experience?
- What characteristics contribute to a positive user experience?
- How to design software to encourage flow states, concentration, focus, and productivity
- Design techniques for reducing cognitive load
- “Don’t make me think!”: Eliminating excise and reducing cognitive load
- Communicating your mental model to the user: Design models and the system image
- Understanding the process of user interface design
- Donald Norman’s design principles for usability
- How do users perform tasks, do work, and learn how to use software applications?
- Understanding the technology framework for building your product’s user interface
- An introduction to data models and UML class diagrams for user interface designers
- Why understanding your application’s domain and data model is a prerequisite for good user interface design
- Requirements gathering techniques for understanding user characteristics
- How to write user personas
- User requirements: Understanding your users’ characteristics
- End users vs. buyers
- User segments and roles
- How to conduct user observation sessions
- How to recruit users for usability testing
- What user interface designers need to know about how human memory works
- How users’ skills and competence improve with practice
- Designing software for different user skill levels
- Security usability: Designing usable software security measures
- Designing error-handling for maximum usability in your application
- How to name things in your application
- Choosing an interaction style for your application
- Don’t make assumptions about your users’ existing skills!
- What is involved in designing user interfaces for an application?
- What is gamification?
- How do users learn and use software applications? An introduction to mental models
- How to use visual attributes to create contrast and attract interest
- Unity: A primary goal in visual design
- Software delivery mechanisms: Comparing desktop applications, web apps, and static websites
- What should you look for in a usability trainer?
- The Gestalt Laws of Perception and how to use them in UI design
- How do people look at and read pages? (Part 3 of 3)
- How do people look at and read pages? (Part 2 of 3)
- How do people look at and read pages? (Part 1 of 3)
- The impact of visual design on usability
- Preview of upcoming topics for this blog
- What is Information Architecture and why is it important in software application design?
- Overcoming objections to involving users in your software project
- What is User Experience (UX)?
- What is User-Centered Design?
- What does “easy-to-use” mean?
- Welcome to Architecting Usability
- About (2)
- Information Architecture (18)
- Interaction Design (10)
- Office Politics (3)
- Product Management (20)
- Product Marketing (2)
- Project Management (5)
- Psychology for UX Design (23)
- Requirements Engineering (12)
- Training (2)
- Uncategorized (4)
- Usability (38)
- Usability Testing (6)
- User Experience Design (37)
- User-Centered Design (15)
- Visual Design (16)
Category Archives: Requirements Engineering
Requirements are statements of things that your product must achieve for it to be considered successful. If you are building a customized solution for a client, requirements express the wants and needs of your client. If you are building a … Continue reading
Your application’s interaction concept is a basic summary or description of the fundamental way the user interface works. It describes the general way that users interact with the application to complete their tasks. Because usability problems tend to emerge when … Continue reading
Designing a user interface for a non-trivial product is a complex task. One traditional approach to designing and building software products was the waterfall model, where requirements are first gathered and written up in specifications documents. These are then handed … Continue reading
If you are designing the user interface for an application, you will likely begin with rough conceptual sketches, but at a certain point, in order to create detailed designs and high-fidelity prototypes, you will need to know what software framework … Continue reading
In the previous post, we argued that the ability to read and interpret data model diagrams is an important skill for user interface designers working on business information systems or other applications that involve a lot of structured data. In … Continue reading
All software manipulates information or data in some way, and to be able to design a user interface for a product, you need to understand the information that the product will present and manipulate, and how this information is structured. … Continue reading