Bringing clarity to Edge Settings

Bringing clarity to Edge Settings

An improvement initiative to reduce abandonment and improve task completion across Edge Settings.

An improvement initiative to reduce abandonment and improve task completion across Edge Settings.

ROLE

ROLE

Initiated and owned Settings improvement efforts from audit to framework to delivery.

TEAM

TEAM

Designer (Myself), Product Manager and Developer

Designer (Myself), Product Manager and Developer

Designer (Myself), Product Manager and Developer

STATUS

STATUS

Ongoing

Ongoing

Ongoing

The challenge

The challenge

The challenge

Users arrived at Edge Settings with a clear intent to change, fix or understand something. But they were leaving without resolution. Not because the setting didn't exist, but because UI obscured what the product could actually do, which was eroding trust and confidence at the moments that mattered most.

The solution

The solution

The solution

Initiated the Settings Improvement Initiative — a planned, multi-cycle effort to audit inconsistencies across Edge Settings at scale, define key areas of improvement cycle by cycle, and roadmap a pipeline to automatically raise PRs with implementation fixes directly to the codebase.

My role

My role

My role

Conducted a parity audit of Edge Settings against Chrome, mapping where Edge leads, where it follows, and where clarity gaps were creating friction and defined opportunity.

Defined six key improvement areas sequenced for cycle-by-cycle delivery, vibecoded the audit findings and improvement framework into an interactive website for broader team visibility.

Owned the Settings Headers improvement workstream end-to-end by publishing guidelines for partner teams via the Edge design system, with a planned PR pipeline to scale fixes directly to the codebase in future cycle.

Initiated the Tone of Voice improvement workstream in collaboration with a content designer, setting the brief, a quick copy audit and establishing the Chrome vs Edge comparative baseline.

Conducted a parity audit of Edge Settings against Chrome, mapping where Edge leads, where it follows, and where clarity gaps were creating friction and defined opportunity.

Defined six key improvement areas sequenced for cycle-by-cycle delivery, vibecoded the audit findings and improvement framework into an interactive website for broader team visibility.

Owned the Settings Headers improvement workstream end-to-end by publishing guidelines for partner teams via the Edge design system, with a planned PR pipeline to scale fixes directly to the codebase in future cycle.

Initiated the Tone of Voice improvement workstream in collaboration with a content designer, setting the brief, a quick copy audit and establishing the Chrome vs Edge comparative baseline.

Proposed outcome

Proposed outcome

Proposed outcome

Targeted +2% improvement in task completion with a framework to scale Settings improvements independent of dev bandwith.

This is a redacted version of the project . Interested in knowing more? Reach out for more details.