Work/ Case Study/ Tech Alliance of SWFL
Hero Image PC Website Home Frame
✶ UX / UI Redesign

Tech Alliance of Southwest Florida Redesign.

Impact
< 3s
Group discovery
100%
Event findability
1–2actions
Group page access
3–4s
Organizer info found
Overview

The existing platform made it difficult to find groups, predict navigation, or discover upcoming events without guessing. I reorganized the information structure, surfaced groups and events directly, and standardized interactions so users could complete core tasks with confidence.

  • Role
    UX / UI Designer
  • Timeline
    Aug — Nov 2025
  • Tools
    Figma, Discord, Docs, AI-assisted exploration
  • Team
    Tyler Martin + stakeholders + devs
  • Scope Research IA Wireframes High‑fidelity Testing Handoff


    Problem & Research Synthesis

    What broke, and what the research confirmed.

    Users couldn't find groups, predict navigation, or locate upcoming events without guessing.

    Confusing hierarchy Original Homepage
    Key Problems
    • Interactive elements appeared clickable but produced no response
    • Navigation behavior was inconsistent across page types
    • Homepage hierarchy gave equal weight to unequal actions
    • Events were buried behind a calendar with no visible overview
    Buried event discovery Calendar and events view
    Research Inputs
    • Nine recurring violations found A heuristic review identified nine interaction issues across consistency, click expectations, and information hierarchy, pointing to systemic problems rather than isolated bugs.
    • Competitors surfaced content immediately Peer platforms surfaced events and groups on landing. Tech Alliance required multiple clicks for either.
    • Stakeholder priorities were clear Stakeholders consistently prioritized dedicated group pages, a unified event feed, and visible member activity.
    • Users gave up before succeeding Feedback consistently flagged navigation confusion, missing events, and text-heavy pages as the primary barriers to engagement.
    Core Findings
    Discovery

    Interactive elements looked clickable but did nothing, so users lost confidence before exploring further.

    Hierarchy

    Navigation, cards, and the calendar competed equally for attention with no clear entry point.

    Events

    Events required clicking individual calendar dates, with no overview and no at-a-glance scanning.

    Trust

    The same elements behaved differently across pages, causing users to stop exploring early.

    ✶ Design Challenge

    How might we make it immediately clear where to find groups, events, and key actions without requiring users to search or guess?

    Next Research Synthesis Information Architecture Wireframes

    03 · Ideation & Low-Fidelity Design

    Ideation & Low‑Fidelity Design

    Those findings shaped three structural questions: where navigation should live, how groups should be weighted, and how events could surface without relying on a calendar.

    Core design principles
    Navigation Paths

    Icons, cards, and header nav all led to the same destination, so users could start from anywhere.

    Group Parity

    A balanced 3×2 layout ensured all groups received equal visibility above the fold.

    Scannable Content

    Long text blocks were broken up so users could identify groups without reading every word.

    Wireframe exploration
    Wireframe
    3 Navigation Paths 6 Groups Above Fold 1 Consistent Scroll Rhythm
    • 01Homepage hierarchy and entry points
    • 02Equal visual weight across all six groups
    • 03Group page content prioritization
    • 04Events moved above the calendar view
    • 05Text density reduced for faster scanning
    Responsive Thinking

    Layouts adapted across desktop, tablet, and mobile, with condensed navigation, hamburger access, and deeper scroll on smaller screens.

    Next High-Fidelity Testing 03 / 06 · Ideation

    04 · High-Fidelity Solution

    High-Fidelity Solution

    Early wireframe decisions evolved into a clearer system where navigation became predictable, events surfaced naturally, and interactions felt consistent across the experience.

    View Prototype:

    Mockups
    Desktop
    Tablet
    Mobile
    What changed
    Navigation
    • Consistent link behavior
    • Clickable icons, titles, cards
    • Mobile hamburger menu
    Homepage
    • Clear group discovery
    • Hierarchy organized around primary actions
    • Visible summaries and social links
    Group Pages
    • Organizer info surfaced
    • Events visible without opening a calendar
    • Responsive grid and carousel
    System
    • Reusable components
    • Consistent spacing
    • Predictable interaction states
    After testing
    01Added visible carousel arrows
    02Expanded clickable areas
    03Standardized hit zones
    04Fixed prototype interactions
    Next Testing Handoff 04 / 06 · High-Fidelity

    05 · Testing & Iteration

    Testing & Iteration

    The redesign created clearer pathways. Testing then validated whether those decisions actually reduced friction when real users engaged with them.

    Test Methodology
    5Participants
    6Tasks
    3Devices
    Desktop · Tablet · Mobile
    Identify a group
    Navigate to group page
    Find upcoming events
    Locate organizer info
    Find the calendar
    Identify clickable elements
    Validation
    <3s
    Group identification
    <2s
    Open group page
    100%
    Event discovery success
    3–4s
    Organizer discovery
    Behavior by device
    Desktop
    01

    Explored icons first, then used cards for context and the header for quick navigation.

    Tablet
    02

    Switched fluidly between icons and header nav depending on the task.

    Mobile
    03

    Tapped icons first, then used the hamburger menu. Scrolling was secondary.

    What changed

    Four small fixes that made the experience feel predictable.

    01

    Users hesitated on the carousel, expecting visible arrows.

    Added visible left & right arrows.

    02

    Users clicked card titles instead of the explicit button.

    Expanded clickable areas across the card.

    03

    Clickable behavior varied across icons, titles, and cards.

    Standardized hit zones for predictable interaction.

    04

    A tablet prototype link failed mid-task during testing.

    Resolved missing prototype interactions.

    Next Handoff 05 / 06 · Testing

    06 · Outcome & Reflection

    Outcome & Reflection

    Outcome

    Navigation became predictable, key actions became obvious, and users completed tasks with greater confidence. What began as a platform built around guessing became an experience users immediately understood.

    Reflection

    Testing reinforced that small inconsistencies rarely feel small to users. Defining interaction standards earlier would have prevented friction from compounding across the experience.

    Next Steps
    • Validate carousel controls with additional users
    • Explore event gallery expansion
    • Finalize stakeholder copy
    • Prepare developer handoff
    End of case study 06 / 06 · Tech Alliance of SWFL