Comments on: Pair Design – Less Wireframes, More Collaboration http://www.andersramsay.com/2009/05/01/less-wireframes-more-collaboration-with-pair-design designing user experiences Mon, 06 Feb 2012 17:34:23 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Reflections on four years of integrating design and development | Atomic Spin http://www.andersramsay.com/2009/05/01/less-wireframes-more-collaboration-with-pair-design/comment-page-1#comment-68528 Reflections on four years of integrating design and development | Atomic Spin Wed, 16 Nov 2011 18:12:49 +0000 http://www.andersramsay.com/?p=644#comment-68528 [...] Anders Ramsay, a friend of Atomic’s from the Agile UX community, identifies advantages of pairing across design specialities. We achieve some of these with our poly-skilled team approach. Leisa Reichelt concluded that pair [...] [...] Anders Ramsay, a friend of Atomic’s from the Agile UX community, identifies advantages of pairing across design specialities. We achieve some of these with our poly-skilled team approach. Leisa Reichelt concluded that pair [...]

]]> By: Jonathan http://www.andersramsay.com/2009/05/01/less-wireframes-more-collaboration-with-pair-design/comment-page-1#comment-53971 Jonathan Mon, 08 Nov 2010 00:10:54 +0000 http://www.andersramsay.com/?p=644#comment-53971 "... standard UI libraries, such as ui.jquery.com, that a front-end developer probably can prototype faster than the interaction designer can spec it." I rather think that's the exception that proves the rule. 99% of the time, a UI designer will be able to design far faster than anyone can create a functional prototype - even using rubbish like Visio. This leads to a rather glaring obstacle in the way of pair design: the fact that at anyone one time, the developer will usually be working hard on the stuff that the designer produced a couple of weeks ago. As one of my team once said to me as I approached him with paper and sharpies in hand: "Dude. Not again. When, exactly, I am supposed to ship deployable code?" Just sayin' :-) “… standard UI libraries, such as ui.jquery.com, that a front-end developer probably can prototype faster than the interaction designer can spec it.”

I rather think that’s the exception that proves the rule. 99% of the time, a UI designer will be able to design far faster than anyone can create a functional prototype – even using rubbish like Visio.

This leads to a rather glaring obstacle in the way of pair design: the fact that at anyone one time, the developer will usually be working hard on the stuff that the designer produced a couple of weeks ago. As one of my team once said to me as I approached him with paper and sharpies in hand: “Dude. Not again. When, exactly, I am supposed to ship deployable code?”

Just sayin’ :-)

]]> By: Casper http://www.andersramsay.com/2009/05/01/less-wireframes-more-collaboration-with-pair-design/comment-page-1#comment-49673 Casper Thu, 22 Jul 2010 09:07:25 +0000 http://www.andersramsay.com/?p=644#comment-49673 Really interesting thoughts, thanks for sharing. Esp. the idea of designer/front-end developer working simultaneously, entices me a lot. I'll definitely have to pitch this idea to my team. Really interesting thoughts, thanks for sharing.
Esp. the idea of designer/front-end developer working simultaneously, entices me a lot.

I’ll definitely have to pitch this idea to my team.

]]> By: Agile UX and The One Change That Changes Everything - Anders Ramsay.com http://www.andersramsay.com/2009/05/01/less-wireframes-more-collaboration-with-pair-design/comment-page-1#comment-49260 Agile UX and The One Change That Changes Everything - Anders Ramsay.com Fri, 09 Jul 2010 18:45:15 +0000 http://www.andersramsay.com/?p=644#comment-49260 [...] designs something and then has to meet with another person to review it and so forth.  This is why pairing is so powerful, because you are in a continaul state of both exchanging and vetting one another’s [...] [...] designs something and then has to meet with another person to review it and so forth.  This is why pairing is so powerful, because you are in a continaul state of both exchanging and vetting one another’s [...]

]]> By: Why Agile UX is Meaningless without an Agile Attitude - Anders Ramsay.com http://www.andersramsay.com/2009/05/01/less-wireframes-more-collaboration-with-pair-design/comment-page-1#comment-48782 Why Agile UX is Meaningless without an Agile Attitude - Anders Ramsay.com Tue, 29 Jun 2010 22:14:56 +0000 http://www.andersramsay.com/?p=644#comment-48782 [...] start designing together?  Two inter-related patterns are Cross-Functional Pairing, which I’ve talked about before (and others have as well), and Active [...] [...] start designing together?  Two inter-related patterns are Cross-Functional Pairing, which I’ve talked about before (and others have as well), and Active [...]

]]> By: Eli http://www.andersramsay.com/2009/05/01/less-wireframes-more-collaboration-with-pair-design/comment-page-1#comment-16275 Eli Mon, 08 Jun 2009 18:36:11 +0000 http://www.andersramsay.com/?p=644#comment-16275 Yes, I do think that pair design is a good idea. I'm an interaction designer and have tried out pair design both with developers and with other designers. However we do create quite a few PowerPoint sketches and find this a valuable way to communicate design toughts and get clarifications from the product owners. Yes, I do think that pair design is a good idea. I’m an interaction designer and have tried out pair design both with developers and with other designers. However we do create quite a few PowerPoint sketches and find this a valuable way to communicate design toughts and get clarifications from the product owners.

]]>