Close
Glad You're Ready. Let's Get Started!

Let us know how we can contact you.

Thank you!

We'll respond shortly.

LABS
Pair design Rule #2: "Yes, and…"

 We shared 40 hours a week, a screen, a product, client relations and a problem space. We raved about the joy and productivity of pairing is this post, and now we’re on a quest to codify the tenets of pair design.

Read more »

LABS
Doing it right

A famous American man called Theodore Roosevelt once wrote:

“Nothing in the world is worth having or worth doing unless it means effort, pain, difficulty… I have never in my life envied a human being who led an easy life. I have envied a great many people who led difficult lives and led them well.”

I am somehow drawn to this, while at the same time, believe that with most things worth doing, there is a hard, and an easy way to approach them.

Read more »

LABS
Balanced Team Sunday Salon at Pivotal Labs

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.

Read more »

LABS
How To Maintain Separate Design and Development Backlogs

In How To Manage A Design Backlog, I talked about some of the general ideas behind managing design work on teams where developers use an agile, XP-based backlog. In How To Integrate Design in an Agile Backlog, I talked about the specifics of integrating design stories into that development backlog.

Read more »

LABS
How To Integrate Design in an Agile Backlog

In How To Manage A Design Backlog, I talked about some of the general ideas behind managing design work on teams where developers use an agile, XP-based backlog—i.e., a Pivotal Tracker-based workflow. In this post, I’ll talk about the specifics of integrating design stories into that development backlog.

Read more »

LABS
How To Manage A Design Backlog

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.

Read more »

LABS
They Pair Too???

As part of NYC Comedy Fest, I went to see the writers of Colbert Report speak. It turns out that every day after the topics that they’re going to work on are chosen, they split up into pairs to work through the jokes.

Read more »

LABS
Why pair design?

This post has been pair-authored by Kim Dowd and Pam Dineva, designers at Pivotal Labs.

Consultancies and embedded design teams are owning more of the product creation process, expanding into early stage research and validation at one end and engineering to create prototypes and products at the other end.

Read more »

LABS
Laptops Not Invited

At Pivotal Labs we have a few basic rules for meetings. Number one: No Laptops Allowed.

At first this may seem counterintuitive and inefficient, especially for a software development firm. However, client and team members alike are pretty quick to convert once they experience the benefits of this simple rule, which has an immediate and profound effect on productivity and engagement.

Read more »

LABS
Software engineering team objective: minimize dark time

Like most engineers, I do a lot of optimizing, often just for fun. When walking to work I seek the shortest route. When folding my laundry I minimize the number of moves. And at work, of course, I optimize all day long alongside all my engineering colleagues.

Read more »