Publications

When developing a banking application, teams must comply with countless regulations, directives, and technical requirements.

Amid product managers, architects, developers, testers, and legal advisors, two roles are especially critical: the IT security professional and the UX designer.

But what does real collaboration between UX and IT security actually mean?

Design: the first line of defense

“If the secure solution is not also the easy, convenient, or practical one, users will find a way to bypass controls for their own comfort or efficiency.” — Miklós Zakar, Senior IT Security Expert, BinX Zrt.

Good UX design creates intuitive, seamless interactions that reduce user errors and lower security risks.

However, UX alone cannot prevent fraud if the underlying system is not secure by design.

Security and usability must reinforce each other.

Mitigate risks

Secure usability ensures that security measures are both effective and user-friendly. Overly complex mechanisms, such as unclear password rules or confusing 2FA flows, encourage users to bypass safeguards.

UX designers play a key role in making security features intuitive and accessible. A well-designed interface communicates risks, such as phishing warnings, without causing security fatigue. Clear guidance prevents accidental actions like exposing sensitive data or misconfiguring privacy settings.

Poorly designed interfaces overwhelm users with security options, leading to mistakes or indifference. A strong UX mitigates these risks through clear visual cues, structured workflows, and non-intrusive prompts. Consistency is crucial — familiar patterns help users spot anomalies and suspicious behaviour.

Joint effort is necessary

Security measures must be easy to follow to be effective. If controls are cumbersome, users will find ways around them. At the same time, security elements that do not require user interaction must be fully embedded and unavoidable — beyond UX influence.

User involvement is necessary in specific cases:

1. Passwords — strong setup requirements and secure reset flows.

2. Multi-Factor Authentication (2FA) — combining knowledge, possession, and inherence factors.

3. 3D Secure (3DS) — additional authentication for card payments under PSD2 and SCA requirements.

4. Biometric authentication [/strong] — fingerprints or facial recognition for secure and effortless access.

“PSD2 introduced Strong Customer Authentication (SCA), making multi-factor authentication mandatory for certain transactions. Over time, 3DS evolved to support richer, more frictionless authentication flows.” — Kristóf Belucz, Head of Payment Cards Department, BinX Zrt.

Good UX embeds security into workflows without disrupting efficiency. Clear guidance, intuitive alerts, and secure defaults help users comply naturally. For this to work, IT security and UX must collaborate from the very beginning as core contributors.

IT security: invisible, but effective

Banks manage vast amounts of sensitive data, making them prime targets for fraud and cyberattacks. Strong authentication, encryption, and layered defenses protect data in transit and at rest.

Secure design principles

Security relies on layered protection — defense in depth. UX plays a role where user interaction is required, while other safeguards remain invisible. Key principles include:

- Fail safe defaults — deny access when errors occur.

- Least privilege — users and employees access only what they need.

- Separation of duties — critical actions require multiple approvals.

- Economy of mechanism — simple, understandable security settings.

- Complete mediation — verify every action, not just initial login.

- Open design — security relies on credentials, not obscurity.

- Least common mechanism — minimise shared access paths.

- Psychological acceptability — security must not frustrate users.

- Weakest link awareness — audits and testing remain essential.

- Leverage existing components — use proven security frameworks.

Strong security isn’t about rigid controls alone. It’s about resilience, usability, and real-world effectiveness.

Teamwork for the win

Without IT security involvement, UX designers may overlook critical threats. Collaboration from the start helps designers understand risks and implement effective safeguards.

For example, a quick-transfer feature designed for speed may introduce fraud risk. By collaborating, teams can require biometrics for high-value transfers while keeping small transfers frictionless. This balance protects users without sacrificing usability.

Good UX also reduces support costs. Intuitive security flows lower the need for password resets and account recovery calls. Secure, well-designed aftercare benefits both users and the business.

Enhance collaboration

Effective collaboration between UX and IT security can be fostered through:

- Workshops — sharing knowledge about threats and usability.

- Testing — combining penetration testing with usability testing.

- Design thinking — creating secure solutions that respect human behaviour.

Conclusion

UX design and IT security must work together to create safe digital experiences. Poor UX can encourage risky behaviour, while thoughtful design supports security adherence. However, UX addresses only a subset of security risks — architecture and OS vulnerabilities remain critical.

In banking applications, UX plays a supporting role. Designers advocate for clarity and usability but do not make security-critical decisions. By integrating UX into secure development and fostering strong collaboration, organisations can achieve both robust protection and excellent user experiences. In the end, security is only as strong as its usability.

Why does neuro-UX matter?

Ever found yourself endlessly scrolling through social media or compulsively checking notifications? That’s not a coincidence — it’s design at work, using our brain’s natural shortcuts to keep us engaged. Our brains are wired to make fast decisions, often subconsciously, and this strongly shapes how we interact with digital products.

Designers who understand these shortcuts — known as cognitive biases — can create experiences that feel effortless and even addictive. This is where neuro-UX comes into play.

The term “neuro-UX” refers to user experience design inspired by neuroscience and psychology. It focuses on how our brains process information, make decisions, and form habits. By aligning with instinctive patterns, neuro-UX reduces cognitive load and triggers emotional responses that keep users coming back. For transparency: neuro-UX is not an official scientific term, but a practical umbrella for these ideas.

The science behind irresistible UX: key principles

Neuro-UX leverages psychology to make design smarter and more engaging. Cognitive biases such as fear of missing out (FOMO) or confirmation bias strongly influence online behaviour. To understand frictionless user journeys, let’s pair two powerful concepts: Gestalt principles and Hick’s Law.

The Law of Similarity (Gestalt principles)

“Gestalt principles describe how humans group similar elements, recognize patterns, and simplify complex visuals when perceiving objects. Designers use these principles to organize content so interfaces are aesthetically pleasing and easy to understand.” — Interactive Design Foundation

Gestalt principles help users naturally group elements through proximity, similarity, and structure.

Hick’s Law

“Hick’s Law states that the more choices users are presented with, the longer it takes them to make a decision. Designers use this principle to evaluate how many options should be offered at any given moment.” — Interactive Design Foundation

Hick’s Law reminds us that fewer choices often lead to faster, more confident decisions.

When combined, Gestalt principles and Hick’s Law create experiences that are visually intuitive and decision-efficient. Patterns help users understand structure, while limited options reduce mental effort. Together, they guide users smoothly through complex interfaces.

Habit-forming design

Why do we keep opening our favourite apps? The answer lies in the habit loop: cue, routine, reward. Fitness apps use notifications as cues, actions as routines, and progress or badges as rewards. Social media apps rely on likes and comments to reinforce this loop. Designing with habit formation in mind increases long-term engagement. It turns occasional users into loyal ones.

KISS: the power of reducing cognitive load

In UX design, less is often more. Too many options or too much information overwhelms users and leads to decision paralysis. Designers counter this with progressive disclosure, clear navigation, and strong visual hierarchy.

Netflix is a great example. Instead of showing everything at once, it breaks content into digestible categories. Browsing becomes easy, familiar, and low-effort.

Emotional triggers: designing for feelings

Great design doesn’t just function — it feels. Colours, micro-interactions, and feedback trigger emotional responses. A small animation, like a heart bursting on Instagram, can create joy and satisfaction.

Urgency is another powerful trigger, often used in e-commerce. Messages like “Only 2 items left!” push users toward action. However, this approach can backfire. Pressure can cause frustration, especially when urgency cues feel manipulative or untrue.

Irresistible UX in practice

Spotify’s Discover Weekly is a strong example of neuro-UX in action. Every Monday, users receive a single personalised playlist.

Gestalt principles group similar songs, while Hick’s Law limits choice to one clear option. The result is a simple, enjoyable, and repeatable experience.

Duolingo’s learning path offers another example. Lessons are grouped logically and presented in small chunks. Limited choices keep users focused and reduce overwhelm. This structure supports habit formation and sustained engagement. Side note: some argue that Duolingo’s emotionally charged notifications can be counterproductive. While this debate deserves its own article, research shows these methods work for most users. Those who dislike them usually find alternative learning methods.

Wrap-up: the future of neuro-UX

The future of neuro-UX looks even more promising with AI-driven personalization. As we learn more about the brain, designers gain new tools to craft intuitive experiences.

But with great power comes responsibility. Designers must balance engagement with ethics. Creating addictive products without regard for user wellbeing can cross a dangerous line.

Neuro-UX is not just a trend.

By understanding how the brain works, designers can create experiences that feel natural, intuitive, and genuinely engaging. The future of UX lies in designing products that resonate with users on a deeper, instinctual level.

Inclusive design sounds fancy, but it’s much more than accessibility for people with disabilities. True inclusive design creates experiences that work for everyone — whether someone is on a shaky bus, speaks a different language, or faces cognitive challenges. It’s about adaptability across contexts, devices, and situations.

Addressing accessibility debt means prioritising critical issues while setting long-term goals. Preventing it requires integrating accessibility from the very beginning. Inclusive design ensures products are intuitive, usable, and effective for all users.

From accessibility to true inclusivity

Accessibility is the foundation of inclusive design. Alt text, keyboard navigation, and screen reader support are essential — but stopping there misses the bigger picture. Inclusive design considers cognitive differences, cultural backgrounds, internet speeds, devices, and real-life usage scenarios. A truly inclusive product is like a Swiss Army knife — useful in every situation.

Cognitive differences

Designing for cognitive differences is essential for inclusive experiences. A cluttered interface increases cognitive load and harms accessibility. For example, excessive emojis can overwhelm screen readers, disrupting comprehension and usability. Clean, clear content significantly improves the experience.

Consistency helps users know what to expect. Consistent navigation and design patterns reduce cognitive strain. Information architecture principles help structure content and control how much information is revealed. Progressive disclosure is key — too much information at once overwhelms users.

Visual perception also matters. Some users need larger text or higher contrast. Simple layouts, consistent patterns, and customization options like text size or contrast improve satisfaction. Empowered users are more likely to stay.

Culture matters

What feels obvious in one culture may be confusing or offensive in another. Designing for a global audience requires more than translation — it requires cultural understanding.

Gestures, symbols, and colours can carry very different meanings across regions. For example, a thumbs-up gesture may be offensive in parts of the Middle East and Africa.

Colours can also mislead — red signals danger in Western cultures, but prosperity in China.

Cultural research and localization are essential. Without them, organisations risk alienating users and damaging their brand.

Inclusive design must be culturally aware as well as technically accessible.

Data-driven design

Inclusive design starts with research and data. Test products with diverse users across abilities, backgrounds, and cognitive styles. Use analytics to identify friction points for specific groups. Gather feedback through surveys and validate solutions with A/B testing.

The accessibility debt

Accessibility debt is similar to technical debt, but focused on accessibility issues. It builds up when accessibility is neglected during development. Missing alt text, poor contrast, or inadequate navigation accumulate over time. Fixing accessibility debt later is more complex and costly.

Ignoring accessibility excludes over a billion potential users. It increases legal risk, raises costs, and damages brand reputation.

How accessibility debt grows

1. Initial oversights — small omissions seem harmless but accumulate quickly.

2. Compounding issues — each inaccessible feature adds complexity and cost.

3. Integration challenges — fixing issues later often requires redesigning existing systems.

[strong]The impact of accessibility debt

On the product — inaccessible features prevent users with disabilities from using it at all. Retroactive fixes require additional development time and rework.

On user satisfaction — frustration and exclusion damage trust and perception. Users increasingly expect inclusive experiences.

On the company — accessibility is legally required in many regions. Failing to comply can lead to lawsuits and financial penalties. Accessibility is also a market opportunity — excluding users means lost growth.

Avoid the accessibility debt

1. Integrate accessibility from the very start of design and development.

2. Follow established standards such as WCAG.

3. Use automated tools for early detection of issues.

4. Conduct testing with diverse users to uncover real-world problems.

5. Educate teams so accessibility becomes a shared responsibility.

6. Perform regular audits to prevent debt from accumulating.

Designing for everyone, everywhere

Inclusive design goes beyond disability. It accounts for cognitive differences, cultural contexts, and real-life usage. By grounding decisions in research and data, products become intuitive, flexible, and enjoyable. In today’s world, inclusivity is not optional — it’s essential. The more inclusive a product is, the more people can use it — and love it.

Many companies, especially those founded by engineers, initially focus on building a great product. As they grow, however, maintaining organised and scalable information architecture (IA) becomes increasingly challenging. A well-structured IA ensures sustainable growth, user-friendly products, and aligned teams, ultimately enhancing the product, the user experience, and the organisation as a whole.

The scenario

A company founded by engineers created a popular mobile app with innovative features. As the product grew, new functionalities were added organically, resulting in a complex and highly interconnected system. Despite strong user loyalty, frustration emerged due to navigation difficulties, scattered data storage, and organisational misalignment between teams.

But how can this happen?

The application is an IoT management tool that allows users to automate their environment and manually adjust device settings. Initially built for early adopters, it later attracted mainstream users seeking comfort and convenience. As the app evolved organically, little emphasis was placed on logical flows, information architecture, or overall user experience.

The ripple effect

As growth accelerated, leadership introduced UX researchers, data analysts, and product designers. While these experts identified usability issues, management prioritised new features to remain competitive instead of addressing core structural problems. An information architecture audit was initiated only after a prolonged crisis, by which point user dissatisfaction had already grown significantly.

One designer took initiative and mapped the entire application. The audit revealed that many features were accessible from multiple locations, both top-level menus and deep submenus. When questioned, the rationale was flexibility — allowing access from anywhere. What once seemed logical evolved into overwhelming complexity.

The result was an application with intricate cross-connections and dependencies. Developers became hesitant to modify the codebase due to fear of unintended side effects, resembling a butterfly effect. Users, overwhelmed by complexity, began abandoning the product in favour of simpler alternatives.

The problem with poor information architecture

Poor information architecture directly undermines operational efficiency.

- Time wasted — teams spend excessive time searching for information and duplicating work.

- Resource drain — repeated tasks consume capacity that could be spent on strategic initiatives.

- Higher error rates — disorganised IA leads to reporting issues, misinformed decisions, and revenue loss.

- Delayed response — slow reactions to market changes reduce competitiveness.

Poor IA also disrupts strategic alignment across organisations.

- Conflicting priorities — teams interpret and manage information differently.

- Inconsistent objectives — lack of shared structure leads to diverging goals.

- Information silos — critical insights remain inaccessible.

- Hindered collaboration/B] — unclear documentation and inaccessible data slow progress.

Detangling the chaos: a step-by-step guide to improving information architecture

Once IA was identified as the root problem, the team faced the challenge of simplifying a complex, multi-layered ecosystem.

1. Conduct an IA audit — catalogue all features, data, and user flows; identify pain points; document the current state.

2. Define clear IA goals — prioritise user-centric design, consistency, and scalability.

3. Create a unified IA plan — develop content models, sitemaps, and intuitive navigation paths.

4. Implement structured data management — centralise data, apply metadata and taxonomy, and establish data governance.

5. Establish governance and maintenance — assign ownership, perform regular audits, and maintain documentation.

6. Enable cross-functional collaboration — host workshops, align shared goals, and maintain continuous communication.

Raising IA to the next level: future steps

Once stability is achieved, organisations can further mature their IA.

- Scalable design systems — reusable components aligned with IA and branding.

- Advanced data analytics — deeper insight into user behaviour and predictive capabilities.

- Cross-department collaboration — clarity, consistency, and alignment across teams.

Information architecture applied: simplifying product design

The design team introduced a structured design system to accelerate delivery. Design engineering bridged the gap between design and development, aligning component logic with code logic. Clear documentation and component readiness states significantly reduced development time.

Template screens were introduced for common layouts. Once defined, developers could reuse these templates with minimal changes, resulting in dramatic delivery speed improvements.

Benefits for all

Data analytics teams benefited from consistent data structures and improved reporting. Product teams gained clearer insights to guide prioritisation and decision-making. Sales teams accessed accurate, real-time data, improving lead management and customer relationships.

At the organisational level, streamlined workflows, reduced redundancy, and informed strategies boosted productivity. These improvements resulted in more engaged users who chose to stay with and invest in the product.

Conclusion

A small shift in perspective can create a powerful ripple effect. Simplifying and clarifying information architecture transforms not only user experience but also internal collaboration and organisational effectiveness. Information architecture is the backbone of both the product and the organisation behind it. By addressing IA deliberately and continuously, companies can detangle complexity, improve maturity, and pave the way for sustained growth and long-term success.

“Maybe it seems like a painful investment in the beginning, but it’ll turn out to be an incredibly huge win later on.”

[strong]Introduction

Picture this: engineers are building the software kingdom, and suddenly someone shouts, ‘Wait, where are the design wizards? We need them too!’ Bringing design into the mix later can feel like trying to fit a square peg into a round hole — it rarely works smoothly. What is essential for harmonious collaboration? How does early design involvement benefit engineering, product development, management, and customers?

[strong]The dynamics of software development companies

Many software companies are founded by individuals with deep engineering expertise. These visionaries excel at turning ideas into functional products through hands-on problem solving and technical proficiency. However, as companies grow, relying solely on engineering perspectives can limit long-term success.

A real-world example is Reddit. Founded by Steve Huffman and Alexis Ohanian, Reddit initially focused on technical execution and community growth. While functional, the platform’s early interface was difficult to navigate and lacked visual appeal. As Reddit gained popularity, the team recognised that improving user experience through design was essential. By investing in design, Reddit transformed its platform into a more intuitive and engaging experience, contributing to sustained growth and success.

[strong]Design as a complementary function

Designers and engineers form powerful partnerships when building products. Designers contribute insights into user needs, visual clarity, and usability, while engineers ensure technical feasibility. Together, they create products that function well, stand out in the market, and delight users.

Apple’s iPhone is a prime example of this synergy. Led by Jony Ive, Apple’s design team prioritised simplicity, elegance, and user experience. Engineers, under Dan Riccio, translated this vision into a technically advanced yet refined product.

The result was a revolutionary device whose success demonstrated the impact of close collaboration between design and engineering.

[strong]The pitfalls of delayed design integration

As companies grow, management perspective becomes increasingly important. Delaying design integration often leads to usability issues, disengaged users, and costly redesigns. Even products built on brilliant ideas can fail if the user experience is poor. Simply put: bad user experience leads to low Net Promoter Score, customer loss, and reduced revenue. Design should never be viewed as a frivolous cost — it is an investment in retention and satisfaction.

Twitter (pre-X era) illustrates this risk. Initially focused on functionality, Twitter neglected cohesive design. As competition grew, users criticised its cluttered interface and inconsistent experience. A later redesign improved usability, but delayed design integration had already impacted retention and growth.

[strong]Integrating design into the organization

Engineers play a critical role in aligning design with technical feasibility. Their insights help ensure that design decisions support performance and scalability. Involving designers brings benefits such as improved usability, smoother development, enhanced problem-solving, and better developer experience. Clear design documentation and robust design systems accelerate delivery and reduce friction. By collaborating closely, engineers and designers bridge gaps between vision and implementation. Designers gain insight into technical constraints, while engineers benefit from clearer intent and user-centred thinking.

Airbnb exemplifies successful early design integration. By embedding designers into cross-functional teams and fostering a strong design culture, Airbnb created cohesive, user-friendly experiences. This commitment to design excellence helped differentiate Airbnb and fuel its global growth.

[strong]Conclusion

Design is a fundamental component of successful software development. Integrating design early alongside engineering and product is a strategic investment, not a cost-cutting exercise. Early design involvement enhances user satisfaction, strengthens competitiveness, and drives long-term success.

Conversely, neglecting design risks eroding trust, losing customers, and missing growth opportunities. Design influences not only visual appeal but usability, developer experience, teamwork, customer engagement, and overall market performance.

Evolution: how it works in organizations

Evolution occurs as living organisms adapt to changes, with those unable to do so becoming extinct. Diversity, adaptability, and an iterative approach are crucial not only for survival, but for achieving higher levels of success. Various team structures, organizational formats, and hierarchies exist, each with its own dynamics.

In my experience, software development firms often operate under strong engineer-led influence. Many such companies were founded by engineers who bring a highly practical mindset. Nonetheless, for a company to progress, change must be welcomed at every level.

Supportive and understanding management is just as vital as an innovative development team. Management must understand the long-term advantages of integrating design into development. Initially slowing down to include design is an investment that ultimately reduces overall delivery time.

Those who recognize this understand the importance of integrating designers into teams — a shift that inevitably alters team dynamics. To adapt successfully, engineers must recognize the value of incorporating different perspectives. My aim is to help engineers engage with designers and help designers understand what supports smoother development processes.

It’s important to note that the following only works if the organization genuinely wants to evolve and embraces change. There may be cases where some individuals struggle to adapt. With patience, transparent communication, and involvement, teams can support them through this transition.

Recognize similarities: get to know your partner in crime

When designers and developers collaborate, it’s like blending strawberries and chocolate — a combination that enhances almost everything. Designers bring creativity, fresh viewpoints, and ideas that transform ordinary projects into digital experiences. Developers contribute technical expertise that brings these ideas to life. Both designers and developers share curiosity, intelligence, and a desire to understand. They are both problem-solvers, but with different focal points. Developers approach challenges through technical feasibility, while designers focus on user pain points.

When these perspectives converge, real magic happens. The result is satisfied users, resolved challenges, and an overall sense of accomplishment. That said, collaboration can be challenging and requires empathy and alignment to build efficient workflows.

Unlocking the power of design collaboration: why does this matter?

Working with designers ensures that problems are solved from the user’s perspective. Designers apply diverse methodologies, leading to a broader range of potential solutions. This diversity often results in more thorough and successful outcomes.

Even the most user-focused developer may overlook certain scenarios or stakeholders. Designers analyse data, conduct research, and interview real users, while developers focus on technical implementation. This division of labour is beneficial and complementary. Through collaboration, developers gain a holistic understanding of projects, while contributing their unique technical insights.

The design adventure begins: from brainstorm to brilliance

The design process is a dynamic journey combining creativity, data analysis, and stakeholder collaboration.

Initiation — designers begin by understanding business requirements and analysing data.

Data analysis — collaboration with researchers to understand markets, competitors, user pain points, and opportunities.

Prioritization and validation — designers prioritise elements that meet business and user needs, sometimes redefining the core problem.

Logical flow and user journey — creation of flowcharts, journey maps, or similar tools to streamline experiences.

Low-fidelity wireframing — iterative sketching and early validation with stakeholders.

High-fidelity mockups — consistent designs built using a documented design system, leading to prototype creation.

Prototyping and testing — interactive prototypes support validation, testing, and clearer documentation.

Documentation and handover — final documentation and close collaboration with developers for smooth implementation.

Throughout development, designers and developers collaborate to identify issues early and streamline releases. Post-release, designers continue iterating with stakeholders, reinforcing the iterative nature of design.

Maximizing efficiency: crafting connections and crushing challenges

You might wonder where you can jump in and initiate change — here’s an example from my experience.

A few years ago, we introduced regular design critique sessions. These sessions were open to all stakeholders and anyone interested in participating. The goal was simple: more perspectives lead to better solutions. Initially attended by designers, researchers, and product managers, the sessions gradually attracted developers, sales leaders, support teams, and eventually the CEO. As our ecosystem expanded across mobile, desktop, and hardware products, shared understanding increased across the organization. People became more aware of current work, future plans, and could align their own roadmaps more effectively.

While these sessions may appear resource-intensive, they helped prevent dissatisfaction and future roadblocks. Designers also gained a better understanding of technical and hardware limitations.

One challenge to address is ego. Successful collaboration requires setting aside superiority and treating all contributors as equals. True partnership thrives on respect for different expertise domains. Transparent, honest, and respectful communication fosters curiosity and shared understanding. When teams understand the reasoning behind decisions, collaboration becomes enjoyable and effective.

The importance of customer experience (CX): who counts as a customer?

Designers aim to deliver not only visually appealing interfaces but exceptional experiences. Users include not only end users, but also developers who work with the designs.

Designers should consider developer experience during handover. Effective UX goes beyond aesthetics — it relies on data, research, feasibility, and real user needs.

Thorough documentation and designer availability are critical. Even if assistance initially seems unnecessary, consistent collaboration builds long-term trust and appreciation.

Developers can contribute insights into structure, feasibility, and design organisation. Designers presenting clear, well-structured, and comprehensible designs benefit everyone.

Developers can guide designers toward logical approaches where needed. When design files are self-explanatory, developers can focus on assessing practicality and consistency.

Benefits of patience: what comes with good collaboration?

Active engagement and shared workflows lead to smoother transitions and clearer communication over time. Mutual understanding develops even from incomplete expressions. This collaboration accelerates delivery and establishes strong organizational foundations.

Encouraging management strengthens cooperation, while rushing development without refinement undermines it. The partnership between designers and developers is like a well-coordinated dance — each step enhancing the rhythm of the project.

By embracing structure, open communication, and collaboration, teams can create digital experiences that truly drive success.

Imagine a startup consisting of a salesperson, a leader, and a developer. They undertake the development of their application relying exclusively on their own experiences. However, due to budget constraints, they lack the resources for additional research, let alone conducting user testing.

In the rapidly evolving world of software development, the creation and deployment of applications have become an integral part of modern business strategies. Developers often work under tight deadlines and resource constraints, resulting in applications that lack a coherent structure. These unstructured applications can be difficult to navigate and comprehend, leading to user frustration and operational inefficiencies. The solution lies in revamping these applications to enhance usability and coherence.

In this article, we will explore the crucial role of information architecture in transforming unstructured applications.

Understanding unstructured applications and their challenges

Unstructured applications, often referred to as legacy applications, are characterised by a lack of organised design, inconsistent codebases, and limited user-centred approaches. They are typically developed by small teams, individual developers, or startups with constrained resources. While they may fulfil immediate functional requirements, they often suffer from significant usability and coherence issues:

Disjointed user experience — inconsistent design elements, varying interaction patterns, and fragmented workflows make applications difficult to navigate.

Maintenance nightmares — the absence of a coherent structure leads to spaghetti code, tangled dependencies, and poor modularisation, increasing the risk of bugs.

Inefficient collaboration — lack of standardised practices and documentation hampers teamwork, onboarding, and productivity.

Unclear user journey — without clear information architecture, users struggle to find features, leading to frustration and reduced satisfaction.

The role of information architecture in revamping

At the core of transforming unstructured applications lies a comprehensive overhaul of the information architecture. Information architecture defines the organisation, labelling, and navigation of content within an application. It serves as the blueprint for user interaction, shaping how users access and engage with features. By reimagining this structure, developers can significantly improve usability and coherence.

Defining a clear hierarchy and navigation

The first step in revamping information architecture is defining a clear hierarchy and navigation structure. Categorise functionalities into logical groups, identify primary and secondary features, and prioritise them based on user needs. This hierarchy acts as a roadmap, guiding users intuitively through the application.

User-centred design principles

A user-centred approach is essential in the revamping process. Develop personas and user journeys to understand behaviours and expectations. Use these insights to ensure frequently used features are easy to access and aligned with real user workflows.

Consistent design patterns

Coherence in design is critical to success. Implement consistent design patterns across the application, standardising elements such as buttons, forms, typography, and colour schemes. Consistency reduces cognitive load, improves usability, and enhances visual clarity.

Simplify and streamline navigation

Unstructured applications often suffer from overly complex navigation. Streamline navigation by reducing the number of steps required to reach key features. Use breadcrumbs, dropdowns, and clear calls to action to guide users efficiently.

Intuitive labelling and information placement

Clear labelling and thoughtful information placement help users quickly understand interface elements. Use descriptive labels for menus, buttons, and links. Place information where users naturally expect to find it, following established design conventions.

Approaches to information architecture revamping

Revamping information architecture requires a multifaceted approach spanning research, design, and development.

[strong]User research and analysis — conduct research to understand behaviours, pain points, and expectations through feedback, surveys, and usability testing.

Content audit and prioritisation — identify redundancies, outdated features, and prioritise elements aligned with user needs and business goals.

Card sorting and wireframing — use card sorting to understand mental models and wireframes to visualise the new structure.

Iterative prototyping — build interactive prototypes, gather feedback, and refine the architecture incrementally.

Responsive design considerations — ensure the architecture adapts seamlessly across devices, prioritising mobile usability.

Expected positive outcomes

After implementing a revamped information architecture, users typically report significant usability improvements. Navigation becomes more intuitive, tasks are completed more efficiently, and user satisfaction increases. Applications often see growth in their user base, supported by positive word-of-mouth.

Vonclusion

Revamping unstructured applications is a transformative process centred on rethinking information architecture. By prioritising user experience and embracing coherent design principles, teams can overcome usability challenges. A well-executed information architecture enhances usability, supports collaboration, simplifies maintenance, and ensures long-term user satisfaction. As software continues to evolve, information architecture plays an increasingly vital role in sustainable application development.

Hey there, design enthusiasts! Let's dive into the exciting world of Design Operations (DesignOps) and discover how it's changing the game in driving growth and unlocking the full potential of creativity within organisations.

So, what exactly is DesignOps?

Well, it's like the conductor of an orchestra, orchestrating and optimising the people, processes, and craft to amplify the value and impact of design at scale. Imagine a well-oiled machine where the design team operates with high efficiency, low friction, and generates jaw-dropping design outputs.

What is NOT DesignOps?

Hold on a sec — DesignOps is not about adding more frameworks and drowning everyone in bureaucracy. It's about suggesting, proposing, and getting everyone on board with fantastic ideas. It's not about micromanaging either; it's more like being the go-to superhero who listens to feedback, addresses concerns, and brings better systems to the table. And no, DesignOps doesn't take charge of individual projects. Instead, it provides a bird's-eye view, making sure there's consistency and harmony across the design universe.

What are the responsibilities?

It's all about coordinating processes and tools, developing a design-oriented culture, and integrating design into the heart of the organisational strategy. It's like equipping designers with superpowers, enabling them to deliver mind-blowing designs. DesignOps also fosters relationships between teams, raising awareness of design team goals and methods, and bringing everyone together in a design extravaganza.

What skills are required?

First of all, you need strong self-esteem fueled by extensive research. Knowledge is your weapon, and you'll use it to find the right tools and empower your team members. Once you've armed yourself with knowledge, you'll unleash a wave of benefits for everyone involved. You'll simplify processes, slash task durations, and make everyone's lives easier — a true win-win situation for the design team and all stakeholders.

What about the long term?

DesignOps isn't just about short-term success; it's about long-term strategic vision. You'll define problems and goals before jumping into solutions, like a mastermind detective. As a true superhero, you'll balance continuous evolution with the human need for stability. It's like having one foot in the future and the other in the present — keeping your organisation ahead of the curve while maintaining stability.

“DesignOps is like glue: you notice it's not there when things start falling apart.” — Inayaili León, Design Program Manager @ GitHub, Config Conf 2022

Benefits of having DesignOps on board

DesignOps strengthens collaboration by acting as a bridge between teams and departments. Say goodbye to silos and hello to seamless communication, improved efficiency, and a shared sense of purpose. DesignOps eliminates the obstacles that slow down product designers, freeing them to focus on creativity and exceptional user experiences. Inefficient workflows and inconsistent design systems are left behind.

DesignOps is also a powerful growth driver. It aligns design and business goals, ensuring that every design decision contributes directly to strategic objectives. By infusing design thinking into the organisation's DNA, DesignOps enables faster market entry, delighted customers, and sustainable growth.

A healthy example

At our company, we assembled a global team of design superheroes. We transitioned from a lone-designer model to a collaborative powerhouse where each design role has clear responsibilities. Our product design team is self-motivated, confident, and doesn't require constant guidance.

DesignOps steps in to provide support, encouragement, and a steady flow of potential improvements. It's a creative environment where boundaries are constantly pushed and awe-inspiring designs are delivered.

Conclusion

DesignOps is the ultimate secret weapon for organisations aiming to unlock the full potential of creativity and achieve outstanding growth. By enhancing collaboration, eliminating obstacles, and embedding design into strategic thinking, DesignOps elevates organisations to new heights.

Embrace DesignOps, become a design superhero, and let the world witness the magic of creativity and growth like never before.

You are invited to a meeting. There's no agenda, no subject, just an invite. It's not optional, you're required to be there. You can see the participants: a product manager, someone from business and a designer. You can't prepare. You feel lost and hope for the best. You enter the video-conferencing channel. The host starts the meeting. After 29.5 minutes of listening, you are sure that this is about a new project. The product manager and the business representative are having a debate about the requirement and the initial idea. You and the designer are listening muted. You have a gut feeling that the designer didn't receive details earlier either. The meeting ends without action points. You feel that your time was wasted. How could all this be done well? What can the developer do to ensure that if the organisers are not properly prepared, you don't waste time? How can you help each other to get the best out of it?

Avoid assumptions

Continue with the above situation. Let's face the truth: the meeting was a failure. Why is that?

- Every participant assumed that others will have an exact topic to talk about.

- The participants hoped that the others will save the day by thinking during the meeting.

- Some hoped that they can get away with the whole meeting if they remain passively silent.

So what can you do?

You are a respected member of the team – take advantage!

Developers are in high demand. Take advantage of your privileged position. Point out that you can't be effective if other actors don't get the attention they deserve – in time.

- Without a well-defined business requirement, a UX researcher can't conduct interviews with the right interviewees.

- Without proper data and analysis, a designer can't create a logical operating flow with the best UI design possible.

- Without clarification of acceptance criteria, quality controllers can't come up with the right test cases and will miss potential edge cases.

- Without the above, you won't be able to provide the proper solution (for example, knowing only that a data table is needed doesn't guarantee scalability).

Clarify and force async collaboration

Every time you feel that expectations are not set, be the one who points it out. You'll save time not just for yourself, but for the team as well.

- Ask for a clear agenda when it's missing from the invitation.

- Check the documentation and comment if possible when something is missing or wrongly stated.

- Push async communication. Everyone has a different biorhythm, and not every meeting needs to be synchronous.

Respect others' time. A meeting that could have been an email often should have been one.

Avoid toxicity

Company culture is a critical factor when accepting or rejecting an offer. Once you feel respected, accepted and valued, you're more likely to stay long-term. You'll invest more energy into making the product successful, which benefits both you and your employer. Choose a communication style where your opinion is listened to and sought again. Instead of purely negative comments, make constructive suggestions when you disagree. Point out how a problem could be solved more effectively and more kindly.

Learn how to say no

Respectful, supported and well-reasoned opinions are more likely to be listened to. Even if you say 'no', strong reasoning and real examples help others accept your position. Saying 'no' at the right moment can save teams and projects from costly mistakes. If you combine your own professional suggestions with the interests and guidelines of others, cooperation can reach a much higher level.

Push out of balance

Let me share two stories about stakeholders being pushed out of a status quo for the sake of the project. A while ago, I was involved in a project that seemed like a simple redesign. I finished the mockups and handed them over, and the developers were happy. Later, I was invited to a review meeting where a business stakeholder appeared unexpectedly. This meeting turned into a debate about requirements that were never clarified before. After listening for half an hour, I suggested that the PM and business stakeholder align offline and provide a clarified specification asynchronously. They accepted this approach, and we're now waiting for proper input.

Earlier, a top-level manager asked our team to create a dashboard. Business stakeholders listed buzzwords, but no clear needs. I asked to involve a UX researcher and suggested creating an interactive prototype. The goal wasn't perfection, but to force thinking and discussion. We ran two short meetings: one for insight sharing, one for feedback on mockups. This allowed the UX researcher to conduct meaningful interviews with real user feedback.

My point is simple: don't just put problems on the table. Bring ideas for solutions. Even imperfect ideas are powerful catalysts for better thinking.

A few words about psychology

The word 'psychology' comes from the Greek words 'psyche' (soul) and 'logia' (observing). What you do when reacting to others at work reflects how you understand the resonance of their thinking. It doesn't matter what role you hold in a team. What matters is how you collaborate. This affects not only your current position, but how you grow professionally. If you think of yourself as an expert, act like one. Support your teammates and the process, and your behaviour will help everything run smoothly.

Do you have a coaching mindset? Do you feel the urge to help rookies? Do you think of yourself as a (wannabe) mentor? Well, here's a unique story for you, which might help broaden your perspective. After reading this post, you might be able to see things from a different angle. You will understand what it feels like to be a noob. You will be able to provide the help that your mentees need.

Let me share my story. Currently, I'm working as a project manager. I'm working together with developers, QA engineers and designers. I felt that I wanted to understand them more.

"I want to learn to code!" – Wow, that's a great idea! I'll learn to code, and I'll understand what they're talking about! Simple as that. …Well, it's not that simple. It became more complex when I realised that online coding seminars do not work for me. But I wanted to create something exact. My learning path finally had a goal! This is the first point.

Really know your mentee!

People are different. I, for one, need to have an exact thing to achieve, so I can get from A to B. But what if your mentees do not know what they want to do? If you know me (your mentee), you have your first step towards success. You can give some hints, and ask the right questions. I'll start thinking of what joy I'll find in that process. What can I benefit from learning? If you understand my deepest professional desires, you'll be able to guide me. With your help, I'll have my definite goal which will inspire me towards success.

As I was saying, I had two specific goals. First, as a professional, I wanted to understand what happens during development. Second, I wanted to achieve the first goal by learning something and having fun. My hobby is sewing, and I always need to know how much material to order. A simple mobile web application would help in calculating it. "Well, that sounds great", I thought, "but where to start?" That's the second point.

Think with noob-head!

"Total beginners. They can't find Terminal. They do not know what 'npm' is. Do they even know what programming languages are there? What type are they – visual or thinking?" You might wonder. It's good luck if I know something about coding. Or is it? What if I have some knowledge, but from the wrong sources?

- I could not ask during online courses.

- There was no option for differing from the original structure during boot camps.

- Developers turned out to be juniors or mediors in their fields, so even they couldn't help me as I needed.

I was stuck. A mentor's task is to start from the beginning: to see where I'm now. If my knowledge is stable or is something to clarify. You need to show me the right tools to use. What command lines to use? Why those? Can I push enter, or will it be the end of the world? These are relevant questions. I asked them from my mentors. There is no such static page on the internet that shows the first steps for noobs like me. For people who are dealing with different things in their daily lives. For those who do not have a mindset that is similar to yours. This is why online coding academies won't work for everyone. You should be able to fit your approach to my needs. This way you'll be able to advise me the way I'll understand. (Remember: your principal task is not to create goals – but to show direction. This is not about your solution – this is about my learning.)

OK, the setup is ready, and the environment is running. Now what? Create a plan. How will I achieve their goal? How to even begin? Show me the first steps, based on my level that you already know. For me, it started with opening a blank .js document. I didn't have the courage to do so.

Encourage your rookie!

Mentoring means that you talk about stuff that is evident to you. It seems clear to you, but it's a hell of a frustration for me. Show me that I can try everything, there's undo. I need to learn how to fail. I also need to learn how to avoid failure. You're there to support me, you can show alternatives. But I need to start thinking ahead. I'll learn what to take into consideration. How to plan a function. How to validate it. How important tests are.

By creating more and more modules, I will be more confident. You'll talk less – perhaps just hints, or thinking together – I'll ask more. I'll find mistakes before tests are running. Finally, you'll be there only to smile at me and say: "You did it!" Do you remember what it felt like to see your first project in production? Nostalgic, huh? Well, now I have my application in production and even a British seamstress notified me that she uses it.

Celebrating success is just a key to opening a new door

I felt what success is like. I definitely want more. You'll be there, as you will also feel that this cooperation works for everyone. Either we continue the original project or start a new one. You, as a mentor, will also enjoy this symbiotic relationship. You'll face professional challenges besides building new soft skills. You'll be able to broaden your perspective. You'll understand different types of thinking. That there are more approaches and more logical explanations to the very same thing.

Closing thoughts

I definitely benefited from trying something new. Thanks to this coding experience, I started to understand my teammates more. Besides respecting them more than ever, I'm a bit closer to seeing their work as it is. Mentors might benefit from considering my story. Mentoring is not about teaching or knowing something better. Mentoring is about building trust. Trust needs to be made in the mentees – towards themselves. They can do it. This happens by guiding them towards the right approach and searching for new solutions or using the existing ones right. Highlighting alternatives and showing different perspectives. Mentoring is about understanding the needs of someone who trusts and respects you. This is huge. Take it seriously.