WordPress.org

Humans testing WordPress flow. Our goal is to make the WordPress user experience better as a whole.

Be aware of users' perspectives and make a visual record of what our users see.

Flow Patrol

Flow Tickets

The next team meeting is on Thursday 18:30 UTC 2015 in #core-flow, but please drop in any time.

Flow is an experience vector. Flow is that unselfconscious feeling conjured by surfboards, skateboards, and kindred planks. Flow is what happens when difficulties are removed and you are freed to pursue an activity without forming intentions. You just do it.

Flow is the path of screens and interactions taken to accomplish a task. Visual records are storyboards of flow.

Flows are just as important to good interfaces as individual screens are. Customers don’t land on screens from out of nowhere. Specific sequences of actions lead customers through your app as they try to accomplish their tasks. RJS

One does not form an intention unless there is some difficulty associated with performing an activity. Without any difficulty one would simply go ahead and do it. Baumann

A visual record is a screencast or series of screenshots documenting a flow.

Visual records capture what someone is actually seeing. They capture what a flow looks like on a particular device with a particular browser and a particular set of plugins/extensions.

There are many flows, this one is mine. There are usually many flows for accomplishing a given task. Visual records of the real flows of real people enumerate which flows are being used and reveal the difficulties and workarounds that spawned and directed those flows.

Visual records highlight changes in flow as interfaces change.

Creating visual records engages developers and designers in their own product, especially when the visual records are then published using the product.

Visual records encourage thinking of interfaces as flow vectors rather than isolated scalars.

Visual records make sure you're paying attention to your interfaces and flows, on all platforms.