> On 10/18/07, Wesley Hall <[EMAIL PROTECTED]> wrote: > For example, I keep seeing junior designers on my team apply patterns > without understanding the intention/context behind the pattern. Then, when > I suggest changes to the design, they will debate me citing my own pattern > as evidence "But you did it here!" without understanding the context of the > problem...Sigh... >
This is exactly why I'm so excited Christian Crumlish from Yahoo! has heeded the call to reflect on (and share with us publicly, thank you!) the impact of using an internal pattern library over a substantial amount of time. I *believe* their internal library had a rating system associated with each pattern, where team members across the organization could rate...something about the pattern. Its utility? Its appropriateness? Its effectiveness in addressing the problem? I want to learn if the patterns were applied inappropriately early on, but after time/education/usage, did the error rate decrease? And are there any checks and balances to make sure the pattern is being applied appropriately? I feel like that's just simple management or peer review of work, but how does that impact the pattern itself? After applying a pattern in a project, is there any reflection on how well it worked within the pattern documentation? Wesley, I think there is always risk of a pattern being misappropriated (that happens even without a formal library to pull from). I wonder, though, within your organization, if the patterns you document tend to cover newer, less-familiar territory as opposed to tried-and-true, everyone-knows-what-THAT-is problem/solution set? That's definitely been my experience. janna > > ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [EMAIL PROTECTED] Unsubscribe ................ http://gamma.ixda.org/unsubscribe List Guidelines ............ http://gamma.ixda.org/guidelines List Help .................. http://gamma.ixda.org/help
