Hi.

Flow Diagram for how users would pass through a process connecting their self-hosted WordPress site to WordPress.com through the Jetpack plugin. The data visualization surrounding the screens shows potential user loss at each step of the way, with users having to go through WP-Admin at particular risk for being lost along the way.

A proposed design process flow, taking into account various design roles, including growth optimization.

Audit and recommendations for standardizing patterns across the app that had diverged over time.

User mental model of how people interact with their site (or a nerdy Flux Capacitor).

Wireframe outlining possible ways of getting users' attention to the state of their site, without using the already-overworked notifications system.

Before/After of Sharing Settings, a page outlined in my team's heuristics review of Calypso. The after image shows how much cleaner the UI became when using standard components in a more user-friendly way.

Connected Applications screen, before and after atomic design review.

This is currently the screen on WordPress.com to manage Pages on your blog. It doesn't seem to follow many of the UX principles in the rest of Calypso, so I re-composed it using standard components.

A simple nag screen to get users to turn on a feature of Jetpack.

A tightly-composed screen made up entirely of core Calypso components.

Since Calypso's look and feel is taking over all of Automattic's products, these are some screens I designed to make the VaultPress and Akismet plugins look more like Calypso while inside of WP-Admin.

Atomic design principles applied to the Stats page of WordPress.com.

Multi-Step Indicator component I designed for the two-factor auth workflow.

Two-factor auth workflow on WordPress.com