I suspect the ideal solution will be: * Dedicated UX resources under platform headcount * UX Engineer make-up, equally comfortable with development and interaction design * Co-located with as many key platform people as possible (Mountain View or Toronto) * Experience with successfully advancing design objectives in pure engineer cultures
I speak from some experience here. On Firefox OS I struggled to make meaningful high level proposals until I’d had the time to soak in the tech stack and build relationships with key people like Jonas and Vivienne. Once I’d done that, the impact I was able to have went from tactical (eg this flow violates this IXD heuristic) to strategic (let’s leverage these three APIs to rethink the OS completely), and my ability to execute went through the roof because I knew the process. A consultant model can have limited success (eg bringing on IXD expertise to massage a new security workflow), but for that sort of deep impact in an extremely technical area, I believe you’re going to need a full-timer. To cite a few examples, Gordon Brander is probably the best example I know of from the current Mozilla UX roster. He’s currently leading the Browser.html team. He has a very rare combo of deep knowledgeable in the trifecta of interaction design, product development and engineering. Frank Yan—formerly of mobile team and now at Facebook—is also a very good example. — Josh Carpenter Product Designer, MozVR Mozilla > On Jan 4, 2016, at 6:05 AM, Marcio Galli <mga...@telasocial.com> wrote: > > Not sure how this [1] relates to, but the tone of your note reminded > me of this discussion. > > ## Making User Stories Obvious in Bugzilla > [1] https://groups.google.com/forum/#!topic/mozilla.dev.gaia/jjtzHnck4XQ > > m > > On Mon, Jan 4, 2016 at 11:40 AM, Anne van Kesteren <ann...@annevk.nl> wrote: >> At Mozlando we discussed how we could better coordinate between >> platform and UX. Put simply, platform's problem is the lack of UX >> input on API design, and UX' problem is not hearing about new platform >> features soon enough to influence the API design to better suit the >> needs of users. >> >> As a small step towards improving this Ehsan created >> >> https://lists.mozilla.org/listinfo/dev-platform-ux >> https://groups.google.com/forum/#!forum/mozilla.dev.platform.ux >> >> where ideally we discuss newly considered platform features early >> enough that UX input still has value. Please subscribe if this aligns >> with your interests. >> >> >> -- >> https://annevankesteren.nl/ >> _______________________________________________ >> dev-platform mailing list >> dev-platform@lists.mozilla.org >> https://lists.mozilla.org/listinfo/dev-platform > > > > -- > www.telasocial.com > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
