Hi devs, I get some anxiety about two facts I noticed. I'm wondering if I should. Maybe you can give me advices ?
Points are : - UX design can be faster than dev. Especially when UX design is made upon rapid expertise according to the UX designer experience. - Open source devs sometime dev for them own fun. People want UX advice, which can also easily transform in a list of a bunch of things to do. Well, even when UX goes faster than dev, a brainstorming period let ideas mature, fork, merge, jump to new ones... So it is not important if the UX specifications is not implemented immediatly as it mature among analysis & dev iterations. UX designers may have to explore various dimensions too detect the major points. This process can reveal also bunches of minor points that could be capitalised for later. What amaze me is when a UX analysis create to too many potential dev work, I'm always afraid of the risk of stressing and discouraging devs that code on them free time. This is quite the same as making user tests, or a vote, so this already exists. The result is a list of points to work on, with intrinsic relative importance evaluation. This could be a good point for classifing things, yet I'm amways affraid that some devs can feel less fun if this look like a pile of things to do (beacause I may feel it, that's why). Also when this is user advices, the dev is making is own classification by analysing the comments. So it is his classification. I know that, for my part, this sort of thing can be key in my motication. The fact may be that when asking an expert advice this is a bit different. The advice come directly from one person so if the dev consider the UX designer as an authority advice this may not be anymore his own classification. An approach that may be interesting could be that if the UX designer act as a consultant. I mean he transfert his knowledge to the dev by giving the details on how he makes his analysis and detect UX implications. So that the dev can take himself the decision of classifing the by mixing UX and Dev priorities according to the importance he gives to each single point. This means the dev has a will in entering the UX process details and gaining skills. Also this could be interesting for the UX designer because it let him share the brainstorming with devs and other UX designers before the decision is taken by project manager, community or the main dev. Iterations is always good in the UX design process. So this an approach. There may be others ones better, or adaptated among each cases. I would love to have feedbacks on this points, to be able to understand how people are felling about this. Thanks ! Thibaut. _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
