Nothing stands without structure.
Objects made by nature and those that humans make have structure. The same is true for application user interfaces. In this post, we describe UI Structural engineering and review its importance in creating digital user interfaces.
Why is structure important?
The structure of an object provides a function of support. For example, bones, joints, and muscles provide structure for the human body. Consider how your performance would diminish if your bones, muscles, and joints were moved around, compromised, or even removed. Likewise, application user interfaces have a structure that should be carefully considered and maintained. If not, the intended performance of a user interface design can be compromised.
What is UI structural engineering?
In Project Accountability Model for UI Teams, I describe engineering activity as an effort to rationalize a structure supporting a design solution. Hence, UI structural engineering is concerned with defining the structure of application user interfaces.
To illustrate the value of UI structural engineering, it helps to understand how it relates to other key activities. My research in project accountability proposes four project-level activities: UI architecture, UI Design, UI engineering, and UI production.
For instance, architecture activity frames the underlying intentions of a project. Individuals who create a solution that satisfies the architectural constraints participate in design activity [1].
Architecture and design artifacts are but aspirations until their underlying structure can be rationalized. The effort to define the structure is an act of engineering. And together, architecture, design, and engineering provide the plan to enable production.
Lastly, production activities translate architecture, design, and structural documentation into artifacts that are consumed by technology infrastructure and delivered as an interface on a computing device.
Overall, UI structural engineering is an essential function in creating digital user interfaces. Acknowledging this fact helps organizations better address the growing complexity of their digital interfaces.
How is UI structure created?
The conceptual reasoning of humans influences the creation of any application user interface. Hence, a user interface inevitably reflects the human concepts that shape it.
If the conceptual assertions used to define the behavior of an interface are sound, the interface has a higher probability of performing as intended. If the underlying concepts are flawed, the performance of the user interface will likely follow suit. In every case, the aggregate of all underpinning conceptual relationships of a user interface defines its structure. [2]
…a user interface inevitably reflects the human concepts that shape it.
There are two classes of UI structures: static structure and dynamic structure. UI structures that are documented using static (unstructured) methods and don’t support systematic intervention have a static UI structure. Dynamic UI structures offer traceability and methods for systematic intervention and management.
Most organizations still rely on static UI structures. They are unsustainable at scale, can create considerable waste, and lower structural performance in complex UI environments.
Can the structure of a user interface fail?
Yes, similar to physical buildings, the structure of user interfaces can fail. When a UI team does not properly account for UI structural integrity, the user interface can impede users from achieving their business-aligned objectives. In other cases, an interface will become completely unusable for some users. These are clear indicators of compromised or failed UI structure.
Conversely, a sound UI structure avoids the possible “collapse” of usability. Overall, structural integrity helps to improve UI design outcomes and reduces unnecessary iteration on failed features. It also lowers business risk and saves teams time and money.
What makes for good UI structural engineering?
Context, human behavior, and language directly impact the nature of a website’s UI structure. The analysis of each reveals human-centered concepts and content that are essential for digital engagement. UI structure is created when the aggregate of these concepts and content is systematically related to serving as the blueprint for the desired UI behavior.
Conceptual modeling is the primary method for planning UI structure. The resulting models should express more than the constructs for navigation, labeling, and content organization; UI structure documentation should include models for who, what, where, when, why, and how content is displayed.
As an interactive environment scales in scope and complexity, defining and maintaining UI structure requires operational maturity. Meaning, the UI structure must be 1) manageable, 2) measurable, and 3) allow for documentation that promotes referencing and traceability. For example, Methodbrain uses specialized software to design UI structure and evaluate UI structural integrity by tracking and diagnosing more than 16 structural definitions and using a battery of novel evaluative methods.
Do standards exist for UI structural engineering?
As of this post, there are no official industry standards for assessing UI structure.
Despite industry consensus, Methodbrain has amassed a decade of research in UI structure through the lens of information architecture science. My investigation of information behavior has resulted in internal standards that Methodbrain uses to deliver reliable UI engineering services.
What professional practices help to address UI structure?
UI structural engineering originates from applying UI-based information architecture practices and information architecture science. Information architects have earned a reputation for their ability to design UI structures. [3]
Without a specialist on the team, it is common for practitioners of UX design, interaction design, content strategy, and product management to rationalize the structure. However, their use of basic techniques provides much less traceability and manageability of the UI structure.
Can we refer to UI Engineering as Information Architecture?
There are varying schools of thought concerning information architecture, making a professional stance on information architecture debatable. In general, information architecture can be described as an area of study that’s used as a lens to promote conceptual clarity while facilitating alignment and understanding. However, in practice, this can manifest itself in different ways.
The most popular idea of information architecture that relates to UI design is centered on how content is organized, labeled, and navigated. There are many tactical methods and approaches to achieving these goals, which have become common for UI and UX practitioners. However, this popular view of information architecture as a practice has unfortunately diluted the necessity of IA specialization for more complex circumstances. This is where UI structural engineering comes into the picture.
UI structural engineering is focused on managing the systemic and operational activities that promote sustainable UI structure for digital applications. This includes managing conceptual (relational) systems of context, language, behavior, content, interaction, and more. Information architecture theory and science have become most relevant to improving human-digital interaction at this level of complexity. I’ve posited in my own research that IA science improves the structure of application user interfaces [4].
UI structural engineering reaches broader than current forms of information architecture practices because it addresses more in-depth structural and operational activities that must support conceptual coherence beyond navigation, labeling, and search systems. While UI engineering is technically an expression of information architecture study, its value is best realized through its specific scope.
Can we call it UI Engineering?
Yes, UI structural engineering can be called UI engineering. However, this may confuse someone who uses UI Engineering as an alternate term for UI design and development. Over the years, this has become less common. At Methodbrain, we add the word “structural” to reinforce the fundamental value proposition and limit confusion. However, the long-term goal is to promote “UI Engineering” as the preferred term over “UI Structural Engineering.”
Notes
[1] This is similar to Jared Spool’s design definition as “the rendering of intent.”
[2] This perspective is based on the DSIA definition for information architecture as a work product.
[3] Many IA practitioners are also highly proficient in UI architecture. Learn more about information architects.
[4] Davis, N. (2013). Transforming our conversation of information architecture with structure. Journal of the American Society for Information Science and Technology. https://asistdl.onlinelibrary.wiley.com/doi/full/10.1002/bult.2013.1720390510
Comments are closed