Alexander Byrne

Alexander Byrne

•

Builder

Craft led

AI native

Builder

Alexander Byrne

Alexander Byrne

Builder

Craft led

AI native

Builder

Alexander Byrne designs the logic beneath the interface. A craft-led Product Designer, he uses high-fidelity prototyping to shape strategy, architect complex systems, and turn ambiguity into shipped reality.

He specialises in:

Applying Original Thinking

Step-change through visionary product concepts and a culture of experimentation.

Driving Measurable Business Impact

Shaping product strategy and roadmaps through data-driven design decisions to achieve quantifiable results.

Cohesive end-to-end Experiences

Leveraging an ownership mindset to identify overlap/opportunities across organisations.

Aligning through Storytelling

Combining creativity with business-critical insights and strategic vision to unite teams and leadership.

Championing Design Excellence

Leading from on-tools execution through to mentorship, 1:1 training, and knowledge sharing.

Google. Defining Ambient AI for over 1 Billion Users.

B2C, Artificial Intelligence (AI), Operating System, Human-AI Interaction Design

Lead Product Designer

Lead Product Designer

B2B payment dashbaord highlighting the customisation and personalisation users can add to the Payments List

Decisions and impact.

How it shaped Android’s roadmap

Due to confidentiality, further specifics cannot be shared.

When should AI be allowed to appear?

Passive Tips notifications arrived at the wrong moment with no sense of priority, so users ignored them. I shifted from passive education to proactive, contextual engagement, so features are discovered at the moment of need. Three principles define when AI has permission to appear: Proximity-Based Discovery, Peripheral Interaction and Familiarity as UI. The result is a soft offer in the flow, built on recognition, not surveillance.

Prototypes, not strategy decks

I chose engineering-grade prototypes over strategy decks, because on a device is how 1B+ users would experience it. They set the direction and the design language to execute it, de-risking the roadmap before engineering committed. Gemini approved the vision, aligning roadmaps across Google, and the Android Onboarding team is now rolling it out across the OS as a new personalised storytelling pattern.

Decisions and impact.

How it shaped Android’s roadmap

Due to confidentiality, further specifics cannot be shared.

When should AI be allowed to appear?

Passive Tips notifications arrived at the wrong moment with no sense of priority, so users ignored them. I shifted from passive education to proactive, contextual engagement, so features are discovered at the moment of need. Three principles define when AI has permission to appear: Proximity-Based Discovery, Peripheral Interaction and Familiarity as UI. The result is a soft offer in the flow, built on recognition, not surveillance.

Prototypes, not strategy decks

I chose engineering-grade prototypes over strategy decks, because on a device is how 1B+ users would experience it. They set the direction and the design language to execute it, de-risking the roadmap before engineering committed. Gemini approved the vision, aligning roadmaps across Google, and the Android Onboarding team is now rolling it out across the OS as a new personalised storytelling pattern.

Decisions and impact.

How it shaped Android’s roadmap

Due to confidentiality, further specifics cannot be shared.

When should AI be allowed to appear?

I replaced ignored Tips notifications with three principles for when AI may appear: a soft offer in the flow, built on recognition, not surveillance.

Prototypes, not strategy decks

Engineering-grade prototypes won Gemini’s approval and aligned roadmaps across Google, and the Android Onboarding team is now rolling the vision out across the OS.

Decisions and impact.

How it shaped Android’s roadmap

Due to confidentiality, further specifics cannot be shared.

When should AI be allowed to appear?

I replaced ignored Tips notifications with three principles for when AI may appear: a soft offer in the flow, built on recognition, not surveillance.

Prototypes, not strategy decks

Engineering-grade prototypes won Gemini’s approval and aligned roadmaps across Google, and the Android Onboarding team is now rolling the vision out across the OS.

Checkout.com. Architecting the Intelligent Payment Workspace.

Enterprise Ecosystem, Fintech Infrastructure, System Architecture, Intelligent Interfaces

Staff Product Designer

Staff Product Designer

Decisions and impact.

How it won and kept merchants

What could only Checkout.com show?

A one-size-fits-all dashboard treated every payment state the same, a problem I named Contextual Blindness. I architected a polymorphic interface that reconfigures by payment state, from reconciliation tools for clean transactions to customer intelligence for disputes. Existing merchants stopped hunting for what mattered, and new visualisations surfaced hidden failure patterns, moving them from reactive firefighting to proactive oversight. This became the centrepiece of enterprise sales demos and contributed to 26 new enterprise merchants and hundreds of millions in processed volume.

Bespoke, not fast-follow

Dashboard limitations were the #1 merchant change request raised through Customer Success, and a primary churn risk. I resisted pressure to fast-follow competitor dashboards and argued for a bespoke architecture built on transaction intelligence only Checkout.com could surface, delivered while only the front end could change. I aligned teams that had competed for pixels around it, and it contributed to improved retention.

Complexity that scales to the user

Enterprise merchants demand data density, but overload can kill usability. I used progressive disclosure and widgets that scale complexity to the user, giving SMBs a simple default view of the same product with no separate build. That opened a segment complexity had excluded and contributed to 76 new SMB merchants. The widget system and refreshed design direction were adopted by every team.

Risk signals where the work happens

For flagged accounts, I put risk signals beside the actions that resolve them, removing the searching and context-switching the current experience forced. Merchants act on threats before they escalate: time-to-resolution for critical tasks, including fraud detection, fell from minutes to seconds (measured in production analytics).

Decisions and impact.

How it won and kept merchants

What could only Checkout.com show?

A one-size-fits-all dashboard treated every payment state the same, a problem I named Contextual Blindness. I architected a polymorphic interface that reconfigures by payment state, from reconciliation tools for clean transactions to customer intelligence for disputes. Existing merchants stopped hunting for what mattered, and new visualisations surfaced hidden failure patterns, moving them from reactive firefighting to proactive oversight. This became the centrepiece of enterprise sales demos and contributed to 26 new enterprise merchants and hundreds of millions in processed volume.

Bespoke, not fast-follow

Dashboard limitations were the #1 merchant change request raised through Customer Success, and a primary churn risk. I resisted pressure to fast-follow competitor dashboards and argued for a bespoke architecture built on transaction intelligence only Checkout.com could surface, delivered while only the front end could change. I aligned teams that had competed for pixels around it, and it contributed to improved retention.

Complexity that scales to the user

Enterprise merchants demand data density, but overload can kill usability. I used progressive disclosure and widgets that scale complexity to the user, giving SMBs a simple default view of the same product with no separate build. That opened a segment complexity had excluded and contributed to 76 new SMB merchants. The widget system and refreshed design direction were adopted by every team.

Risk signals where the work happens

For flagged accounts, I put risk signals beside the actions that resolve them, removing the searching and context-switching the current experience forced. Merchants act on threats before they escalate: time-to-resolution for critical tasks, including fraud detection, fell from minutes to seconds (measured in production analytics).

Decisions and impact.

How it won and kept merchants

What could only Checkout.com show?

I architected a polymorphic interface that reconfigures by payment state, moving existing merchants to proactive oversight and helping win 26 new enterprise merchants.

Bespoke, not fast-follow

Answering the #1 merchant change request, I chose a bespoke architecture over a fast-follow copy, delivered within front-end-only constraints, and it contributed to improved retention.

Complexity that scales to the user

Widgets that scale complexity to the user gave SMBs a simple default view, contributing to 76 new SMB merchants, and every team adopted the system.

Risk signals where the work happens

Putting risk signals beside the actions that resolve them cut time-to-resolution for critical tasks, including fraud detection, from minutes to seconds.

Decisions and impact.

How it won and kept merchants

What could only Checkout.com show?

I architected a polymorphic interface that reconfigures by payment state, moving existing merchants to proactive oversight and helping win 26 new enterprise merchants.

Bespoke, not fast-follow

Answering the #1 merchant change request, I chose a bespoke architecture over a fast-follow copy, delivered within front-end-only constraints, and it contributed to improved retention.

Complexity that scales to the user

Widgets that scale complexity to the user gave SMBs a simple default view, contributing to 76 new SMB merchants, and every team adopted the system.

Risk signals where the work happens

Putting risk signals beside the actions that resolve them cut time-to-resolution for critical tasks, including fraud detection, from minutes to seconds.

National Australia Bank. Elevating mobile banking for 10 Million Aussie customers.

B2C, Banking Infrastructure, iOS & Android App, A11Y & Inclusive Design

Lead Product Designer

Lead Product Designer

Decisions and impact.

How NAB went from 2.8 to 4.7

Why was NAB the lowest-rated banking app?

Years without meaningful investment had left inconsistent patterns, an outdated visual language and accessibility failures that didn’t represent the brand. I replaced them with simpler hierarchies, clearer discoverability, intuitive interaction and personalised onboarding at key brand moments. As it rolled out, review themes shifted from usability complaints to praise for clarity and ease, and the rating rose from 2.8 to 4.7, alongside engineering’s stability work.

A prototype, not a roadmap deck

Worse than the technical debt was the cultural debt: a “good enough” mindset that treated incremental improvement as the ceiling. I bypassed it with a high-fidelity Vision Prototype the C-suite could experience directly, collapsing months of debate into alignment. Codified into the design system, it set the direction the website and other digital products now follow, and it reached over 100 designers.

Design as a trust signal

Design quality had been a visible gap against market-leading bank apps. A modernised visual language that signals security, competence and market leadership helped restore customer confidence and took design off the list of reasons customers gave for switching.

Accessibility built in, not bolted on

The industry assumed beautiful design compromises accessibility. I challenged that: building accessibility in from the start, rather than retrofitting it for compliance, removed barriers for customers with accessibility needs and showed the two reinforce each other when craft comes first. The app met WCAG 2.1 AA without compromising the new visual language.

Decisions and impact.

How NAB went from 2.8 to 4.7

Why was NAB the lowest-rated banking app?

Years without meaningful investment had left inconsistent patterns, an outdated visual language and accessibility failures that didn’t represent the brand. I replaced them with simpler hierarchies, clearer discoverability, intuitive interaction and personalised onboarding at key brand moments. As it rolled out, review themes shifted from usability complaints to praise for clarity and ease, and the rating rose from 2.8 to 4.7, alongside engineering’s stability work.

A prototype, not a roadmap deck

Worse than the technical debt was the cultural debt: a “good enough” mindset that treated incremental improvement as the ceiling. I bypassed it with a high-fidelity Vision Prototype the C-suite could experience directly, collapsing months of debate into alignment. Codified into the design system, it set the direction the website and other digital products now follow, and it reached over 100 designers.

Design as a trust signal

Design quality had been a visible gap against market-leading bank apps. A modernised visual language that signals security, competence and market leadership helped restore customer confidence and took design off the list of reasons customers gave for switching.

Accessibility built in, not bolted on

The industry assumed beautiful design compromises accessibility. I challenged that: building accessibility in from the start, rather than retrofitting it for compliance, removed barriers for customers with accessibility needs and showed the two reinforce each other when craft comes first. The app met WCAG 2.1 AA without compromising the new visual language.

Decisions and impact.

How NAB went from 2.8 to 4.7

Why was NAB the lowest-rated banking app?

Years of underinvestment left the app inconsistent and inaccessible; my redesign turned reviews towards praise for clarity, and the rating rose from 2.8 to 4.7, alongside engineering’s stability work.

A prototype, not a roadmap deck

A Vision Prototype the C-suite could experience broke a “good enough” culture, and its direction now guides NAB’s digital products and over 100 designers.

Design as a trust signal

A modernised visual language that signals security and competence took design off the list of reasons customers gave for switching.

Accessibility built in, not bolted on

Building accessibility in from the start met WCAG 2.1 AA and showed that craft and accessibility reinforce each other.

Decisions and impact.

How NAB went from 2.8 to 4.7

Why was NAB the lowest-rated banking app?

Years of underinvestment left the app inconsistent and inaccessible; my redesign turned reviews towards praise for clarity, and the rating rose from 2.8 to 4.7, alongside engineering’s stability work.

A prototype, not a roadmap deck

A Vision Prototype the C-suite could experience broke a “good enough” culture, and its direction now guides NAB’s digital products and over 100 designers.

Design as a trust signal

A modernised visual language that signals security and competence took design off the list of reasons customers gave for switching.

Accessibility built in, not bolted on

Building accessibility in from the start met WCAG 2.1 AA and showed that craft and accessibility reinforce each other.

Nebula Insurance. Designing the future of Insurtech from 0 → 1.

B2B, Insurtech, 0 to 1 Start-up, End-to-end Experience Design

Principal Product & Brand Designer

Principal Product & Brand Designer

A collection of brand mocups showing the logo consistently in the centre

Decisions and impact.

How it got Nebula funded and built

How do you fund a product that doesn’t exist yet?

Traditional insurance demands data before offering any value, so users expect extraction, not exchange. I originated Reciprocal Data Flow: enter a business address and get risk insights, like location-specific hazard maps, before a single form, so trust is earned by giving. Prototypes let investors use the product rather than imagine it, and were the main evidence behind seed funding from QBE Ventures.

A visible score, not long forms

Commercial eligibility is opaque: businesses don’t know why they’re rejected or how to improve. I designed the Insurance Health Score, a visible, gamified metric that shows where they stand and what to do next, and replaced long, dense forms with small, clear steps that capture what underwriters need upfront. That made automated quoting possible, replacing weeks of manual underwriting with tailored quotes in moments.

Designed for handover

As the only designer, I authored the design system alongside the product and brand experience. Developer-ready libraries meant engineers built the MVP directly from them, without design becoming an ongoing dependency or carrying debt into launch.

Warm and human, not safe and corporate

I steered the brand towards warmth, carried through a conversational tone. It gave Nebula a distinct position in a commoditised, low-trust market and made commercial cover less intimidating to buy.

Decisions and impact.

How it got Nebula funded and built

How do you fund a product that doesn’t exist yet?

Traditional insurance demands data before offering any value, so users expect extraction, not exchange. I originated Reciprocal Data Flow: enter a business address and get risk insights, like location-specific hazard maps, before a single form, so trust is earned by giving. Prototypes let investors use the product rather than imagine it, and were the main evidence behind seed funding from QBE Ventures.

A visible score, not long forms

Commercial eligibility is opaque: businesses don’t know why they’re rejected or how to improve. I designed the Insurance Health Score, a visible, gamified metric that shows where they stand and what to do next, and replaced long, dense forms with small, clear steps that capture what underwriters need upfront. That made automated quoting possible, replacing weeks of manual underwriting with tailored quotes in moments.

Designed for handover

As the only designer, I authored the design system alongside the product and brand experience. Developer-ready libraries meant engineers built the MVP directly from them, without design becoming an ongoing dependency or carrying debt into launch.

Warm and human, not safe and corporate

I steered the brand towards warmth, carried through a conversational tone. It gave Nebula a distinct position in a commoditised, low-trust market and made commercial cover less intimidating to buy.

Decisions and impact.

How it got Nebula funded and built

How do you fund a product that doesn’t exist yet?

Prototypes of Reciprocal Data Flow, with risk insights before a single form, let investors use the product rather than imagine it, and were the main evidence behind seed funding from QBE Ventures.

A visible score, not long forms

The Insurance Health Score and small, clear steps made automated quoting possible, replacing weeks of manual underwriting with tailored quotes in moments.

Designed for handover

As the only designer, I authored the design system engineers built the MVP directly from, with no ongoing dependency or design debt.

Warm and human, not safe and corporate

A warmer brand and conversational tone gave Nebula a distinct position in a low-trust market and made commercial cover less intimidating to buy.

Decisions and impact.

How it got Nebula funded and built

How do you fund a product that doesn’t exist yet?

Prototypes of Reciprocal Data Flow, with risk insights before a single form, let investors use the product rather than imagine it, and were the main evidence behind seed funding from QBE Ventures.

A visible score, not long forms

The Insurance Health Score and small, clear steps made automated quoting possible, replacing weeks of manual underwriting with tailored quotes in moments.

Designed for handover

As the only designer, I authored the design system engineers built the MVP directly from, with no ongoing dependency or design debt.

Warm and human, not safe and corporate

A warmer brand and conversational tone gave Nebula a distinct position in a low-trust market and made commercial cover less intimidating to buy.

Checkout.com. Productising the Service Layer to Unlock $200M in Recurring Revenue.

Enterprise Ecosystem, Fintech Infrastructure, Self-Serve Architecture

Staff Product Designer

Staff Product Designer

Decisions and impact.

How it unlocked $200M+

Why was growth waiting on review?

This wasn’t assigned work. My audit of service logs showed manual processes blocking about 50% of revenue opportunities, and research found merchants saw Checkout.com’s sales approach as aggressive. I built the case before leadership knew they needed it: productise eligibility checks so merchants can activate and scale their payment stack on their own, backed by the Customer Success Managers they already trusted. It unlocked $200M+ ARR that had been delayed or lost in the queue.

Time-to-Revenue as the north star

I rejected vanity metrics like Time-to-Onboarding, because fast sign-ups could still mean weeks of revenue delay, and defined Time-to-Revenue, from merchant decision to first processed dollar, as our north star. I led the design of the Visual Eligibility Engine, which turned fragile manual checks across thousands of spreadsheet rows into algorithmic decisions. Time-to-Revenue fell from about 3 weeks (often 6 months) to under 24 hours.

End the email tag

Automating eligibility logic ended the email tag between merchants and internal teams, so merchants could focus on strategy rather than paperwork. It saved thousands of admin hours a year and enabled Checkout.com to grow without hiring to match.

Self-serve, not white-glove

Self-serve onboarding replaced uncertainty with transparency and expert guidance, and removed the white-glove cost from every new merchant, bringing cost to serve below the point where SMBs became profitable. Its rebranded design direction, with more personalised context in the dashboard, was adopted by all teams.

Decisions and impact.

How it unlocked $200M+

Why was growth waiting on review?

This wasn’t assigned work. My audit of service logs showed manual processes blocking about 50% of revenue opportunities, and research found merchants saw Checkout.com’s sales approach as aggressive. I built the case before leadership knew they needed it: productise eligibility checks so merchants can activate and scale their payment stack on their own, backed by the Customer Success Managers they already trusted. It unlocked $200M+ ARR that had been delayed or lost in the queue.

Time-to-Revenue as the north star

I rejected vanity metrics like Time-to-Onboarding, because fast sign-ups could still mean weeks of revenue delay, and defined Time-to-Revenue, from merchant decision to first processed dollar, as our north star. I led the design of the Visual Eligibility Engine, which turned fragile manual checks across thousands of spreadsheet rows into algorithmic decisions. Time-to-Revenue fell from about 3 weeks (often 6 months) to under 24 hours.

End the email tag

Automating eligibility logic ended the email tag between merchants and internal teams, so merchants could focus on strategy rather than paperwork. It saved thousands of admin hours a year and enabled Checkout.com to grow without hiring to match.

Self-serve, not white-glove

Self-serve onboarding replaced uncertainty with transparency and expert guidance, and removed the white-glove cost from every new merchant, bringing cost to serve below the point where SMBs became profitable. Its rebranded design direction, with more personalised context in the dashboard, was adopted by all teams.

Decisions and impact.

How it unlocked $200M+

Why was growth waiting on review?

Unassigned, I found manual processes blocking about 50% of revenue opportunities and made the case for self-serve eligibility, which unlocked $200M+ ARR.

Time-to-Revenue as the north star

I chose Time-to-Revenue over vanity onboarding metrics, and the Visual Eligibility Engine I designed cut it from about 3 weeks to under 24 hours.

End the email tag

Automating eligibility logic ended the email tag between merchants and internal teams, saving thousands of admin hours a year and letting Checkout.com grow without hiring to match.

Self-serve, not white-glove

Self-serve onboarding removed the white-glove cost from every new merchant, making SMBs profitable to serve, and its design direction was adopted by all teams.

Decisions and impact.

How it unlocked $200M+

Why was growth waiting on review?

Unassigned, I found manual processes blocking about 50% of revenue opportunities and made the case for self-serve eligibility, which unlocked $200M+ ARR.

Time-to-Revenue as the north star

I chose Time-to-Revenue over vanity onboarding metrics, and the Visual Eligibility Engine I designed cut it from about 3 weeks to under 24 hours.

End the email tag

Automating eligibility logic ended the email tag between merchants and internal teams, saving thousands of admin hours a year and letting Checkout.com grow without hiring to match.

Self-serve, not white-glove

Self-serve onboarding removed the white-glove cost from every new merchant, making SMBs profitable to serve, and its design direction was adopted by all teams.

Let's craft a better

internet

experience

brand

app

product

product

.

Lets craft a better internet.

Resume

LinkedIn

hello@alexanderbyrne.com