How User Testing Revealed Hidden Workflow Barriers

Committees in UI V2

As part of the BoardPro UI V2 redesign, the information architecture was restructured to simplify navigation across the platform. One important change moved Committee Management under Organisation Settings.

The team needed to understand whether board secretaries could still locate and manage committees easily, especially since committee creation was tied directly to customer expansion and revenue.

The Challenge

On paper, the revised navigation structure was logical. But committee management was a high frequency administrative task, and even small navigation barriers could disrupt workflows or reduce feature adoption.

The goal was not only to test findability, but to understand how board secretaries naturally expected committee related tasks to work within the broader platform experience.

My Contribution

I led the research and testing process from planning through to synthesis and recommendations. This included:

  • Defining research objectives and testing scenarios

  • Recruiting participants using LaunchDarkly and Intercom data

  • Creating and iterating prototype concepts

  • Conducting usability testing and behavioural observation

  • Synthesising findings for the product team

The work focused on uncovering workflow friction that may not have been visible through analytics alone.

What We Learned

Testing showed that placing Committees solely under Organisation Settings created hesitation and slowed task completion for some users.

Board secretaries tended to think about committees as part of their active board workflow rather than as an administrative setting.

The research highlighted the gap between a logically structured IA and users’ mental models during real tasks.

Outcome

The findings helped shape a navigation approach that made committee management easier to discover and access within everyday workflows.

Reducing friction around committee setup also supported business goals by making it easier for organisations to create and manage additional committees within the platform.

I conducted this research in the post-production phase by having participants interact with the live product using controlled scenarios. I then had them perform the same tasks using the prototypes I designed, allowing for direct comparison and validation of design improvements.

    1. Analyse users' navigation habits and preferences regarding the Committees page in the new UI.

    2. Use prototypes to test new IA ideas for the "Add Committee" function and evaluate their effectiveness for users.

    • Usability Testing

    • Prototype Validation

  • Participant Criteria

    • Roles: Administrators, Board Secretaries

    • Number of Participants: 5

    • Based in: New Zealand, Australia

    Recruitment Process
    We cross-referenced data from LaunchDarkly to identify users who have engaged with the new UI (up to January 16, 2025) and have recently added committees by using the newly released function (between September 24, 2024, to January 15, 2025). Selecting users from this group ensures that the participants have relevant experience with both the new UI and the committee feature.

Key Insights

Recommendations

Other Observations & Feedback

Previous
Previous

Web App: from discovery to launch

Next
Next

SaaS App: define MVP scope through user research