tag:blogger.com,1999:blog-4667198366772137516.post6693164309858456314..comments2023-09-25T06:55:58.791+00:00Comments on The Casablanca Weblog: Open source experience designPhil Whitehousehttp://www.blogger.com/profile/00707058659116319394noreply@blogger.comBlogger6125tag:blogger.com,1999:blog-4667198366772137516.post-23251293346213171852007-09-25T13:35:00.000+00:002007-09-25T13:35:00.000+00:00Phil - This is an excellent topic that you've brou...Phil - This is an excellent topic that you've brought up. With my role as an application delivery manager the past couple of years, I've had ample opportunity to set development priorities. Unfortunately, I've never placed that high of priority on the actual experience design, versus core functionality that always seemed to have a moving target given the ambiguous nature of requirements that are the norm in my job of intranet web apps. With at least one example of an application failing its goal because of lack of user take-up, I have a much better appreciation of experience design now then ever. How to push the UE on deliveries managers like myself will not be easy, but we have to start somewhere, and the earlier the better!James Shihttps://www.blogger.com/profile/00434302852090126539noreply@blogger.comtag:blogger.com,1999:blog-4667198366772137516.post-13748044294268402722007-09-24T12:19:00.000+00:002007-09-24T12:19:00.000+00:00I think there's a lot of value in having your deve...I think there's a lot of value in having your developers understand the value of a design - why it has value as a product, why the experience is relevant to the user. Communication not only needs to happen early and often between design and build people, it also needs to happen in a way that can enhance the quality of the end product and the happiness of the team.Unknownhttps://www.blogger.com/profile/02075656338677724149noreply@blogger.comtag:blogger.com,1999:blog-4667198366772137516.post-26544577322361230142007-09-20T13:17:00.000+00:002007-09-20T13:17:00.000+00:00@FND: Perhaps the best person to gather and proces...@FND: Perhaps the best person to gather and process feedback in a transparent fashion would be the person responsible for designing the experience in the first place. <BR/><BR/>This person would be well placed to explain which suggestions make the cut and why, with specific reference to the impact on the experience.Phil Whitehousehttps://www.blogger.com/profile/00707058659116319394noreply@blogger.comtag:blogger.com,1999:blog-4667198366772137516.post-75623694768648234962007-09-20T12:05:00.000+00:002007-09-20T12:05:00.000+00:00One of the major issues with user/community feedba...One of the major issues with user/community feedback, especially in open-source projects, is to make sure that it's actually harnessed effectively.<BR/><BR/>There needs to be a transparent system of receiving, collecting, processing/evaluating and ultimately implementing these suggestions.<BR/><BR/>If that is not in place, valuable input will likely get buried and people are discouraged from contributing ideas.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-4667198366772137516.post-83592245241071627662007-09-19T17:18:00.000+00:002007-09-19T17:18:00.000+00:00Ok, so for me the best bit is that you really enco...Ok, so for me the best bit is that you really encourage the communication bit in as many channels as possible. That's something that in my experience people don't often get done very well. I've found people pick one or two channels and then stick with those, even if they don't provide sufficient coverage.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-4667198366772137516.post-90834063924745071802007-09-19T15:50:00.000+00:002007-09-19T15:50:00.000+00:00Well yeah... absolutely.I am currently trying to f...Well yeah... absolutely.<BR/><BR/>I am currently trying to figure out the best way to overlay the JJG abstract-to-concrete experience model onto a big telco's waterfall process.<BR/><BR/>One of the hardest things to explain to the armies of middle managers who ultimately make or break this type of process is that the IA (or EA if you work at LBi or heck, why not UEA while we're at it...) needs to be involved from the inception of the product right through to ultimate delivery and beyond.<BR/><BR/>The challenge I'm struggling with now it that in a large organisation you are often working with people who have little or no knowledge of what the IA does. Co-workers need to find a box to put you in and in the current thinking, none of the available boxes spans the whole product lifecycle (well, sort of)<BR/><BR/>Anyhow, I'm a big follower of the value co-creation teachings of CK Pralahad and V Ramaswami and find open source methodologies to be a good support for productive relationships based openness, dialogue and transparency.<BR/><BR/>Sounds a bit bollocksy but open source is the only culture I can think of where transparency is built in to the core (in that we all publish our work to a cvs for all to see)<BR/><BR/>Curious to see what responses you get:-)Anonymousnoreply@blogger.com