Types of Design

I just blogged about Types of Design over at the Pivotal Labs blog.

“Design” is a messy word, and describing which type of design you mean can be tricky. Sometimes it’s more helpful to describe types of design not as crisp definitions—”Visual Design looks pretty, and UX has boxes and arrows”—but instead in the spirit of Family Resemblance, i.e.:

things which may be thought to be connected by one things which may be thought to be connected by one essential common feature may in fact be connected by a series of overlapping similarities, where no one feature is common to all.

Check it out, and let me know what you think in the comments!

The Benefits of Pair Design

I just blogged about The Benefits of Pair Design over at the Pivotal Labs blog:

design-pair-4

How is design different for Agile product development?

“Design” can mean many things, but designing products for Agile software development methodologies present distinctive challenges. Engineers build software more quickly (and change it more rapidly) than most…

Check it out, and let me know what you think in the comments!

InVision takes a look Inside the Design Team at Pivotal Labs

invision-inside-labs-design

The fine folks at InVision did a nice interview and write-up of our design practice. Check it out!

Balanced Team Sunday Salon at Pivotal Labs

I just blogged about the Balanced Team Sunday Salon at Pivotal Labs over at the Pivotal Labs blog.

This Sunday Pivotal Labs hosted a Balanced Team Sunday Salon following the three-day LeanUX NYC conference. LeanUX was chock-full of amazing talks and workshops, and the ensuing sentiment was my brain hurts! The Balanced Team Sunday Salon was a chance to recover, process, and reflect. We started off with brunch: bagels and bellinis…

Check it out, and let me know what you think in the comments!

How To Maintain Separate Design and Development Backlogs

I just blogged about How To Maintain Separate Design and Development Backlogs over at the Pivotal Labs blog.

Previously, we discussed when to use different types of backlogs, categorized various types of stories, and described a general flow for agile design. In this post we won’t rehash that material, but instead will describe some of the practices specific to separate Design and Development backlogs.

Check it out, and let me know what you think in the comments!

How To Integrate Design in an Agile Backlog

I just blogged about the How To Integrate Design in an Agile Backlog over at the Pivotal Labs blog.

WHEN SHOULD I USE AN INTEGRATED BACKLOG?

An integrated design backlog is appropriate for small- to medium-sized projects (i.e. teams which can be fed with two or fewer pizzas), focused on a single platform. It can accommodate teams which have designers that code, as well as designers who don’t.

Check it out, and let me know what you think in the comments!

How To Manage A Design Backlog

I just blogged about the How To Manage A Design Backlog over at the Pivotal Labs blog.

Every project is different, but Agile and XP have taught developers a stable and robust set of tools for managing (development) work. What about managing design work? (With apologies to Tolstoy :)

[DEVELOPMENT BACKLOGS] ARE ALL HAPPY; EVERY [DESIGN BACKLOG] IS UNHAPPY IN ITS OWN WAY.

A designer colleague asks:

I’d love some insight into how other people use [Pivotal Tracker] / attach mocks and keep things updated as stories split and get added. I’d love to learn how to spend more time working on design rather than managing it.

There are many approaches to managing design and integrating design work with development work…

Check it out, and let me know what you think in the comments!