No posts containing your search terms were found.
Your search did not match any documents.
Suggestions:
* Make sure all words are spelled correctly.
* Try different keywords.
* Try more general keywords.
The Role of Collaboration
March 19, 2010. wandereye
Wireframes should not be "interpreted" - they sould be collaborated upon with the "user experience architect" (as well as all the "stakeholders" and production people involved). Unless, of course, you prefer to the throw it over the wall approach. In other words, an example would be processes in the early stages of MML and with Iga and Rod on the DIG team and with a former creative named "[omitted]" and with some FEDs (talk to [omitted]). Whenever I am tasked with "wireframes" (we could speak about those and their relevancy to Web 2.0 and 3.0 and beyond over a drink or smoke if you want), I do my very best to work on them WITH FED and Design and other people with a "stake" in the "ground".
Why the separation? Contrary to some people's beliefs, I don't think the roles are as siloed or specialized as we tend to treat them. What helps is well-thought out strategy and a team that can develop tactics to meet this strategy. Without solid strategy, with only directives and a timeline, it makes sense that we "divide and conquer" to get the job done. However, working with FED, Design, IT all people involved with the implementation and production, should work together and support one another - especially when faced with a paucity of both strategy or objectives or resources or time.
And if you are finding design-change opportunities within a waterfall approach, I would suggest running them by the "author" of the "wires" and perhaps iterating the wires where value is clear. A "good" UX-er is concerned with the USER and will be open to ideas that promote giving users great experiences.
UX: there is so much we can continue to learn from Design, IT, FED. If you are not inquiring, IMHO, you are not doing UX. Your job is inquiry, asking questions, clarification, interpretation, understanding.
Design: one of the primary jobs of the UX professional is to understand the needs of the customer/user and the objectives of the business. If you are not getting solid input on this from your "UX" friend, something is amiss.
FED/IT: You know everything. Just answer us when we have questions. Help us understand. Lots of us do not.
Why the separation? Contrary to some people's beliefs, I don't think the roles are as siloed or specialized as we tend to treat them. What helps is well-thought out strategy and a team that can develop tactics to meet this strategy. Without solid strategy, with only directives and a timeline, it makes sense that we "divide and conquer" to get the job done. However, working with FED, Design, IT all people involved with the implementation and production, should work together and support one another - especially when faced with a paucity of both strategy or objectives or resources or time.
And if you are finding design-change opportunities within a waterfall approach, I would suggest running them by the "author" of the "wires" and perhaps iterating the wires where value is clear. A "good" UX-er is concerned with the USER and will be open to ideas that promote giving users great experiences.
UX: there is so much we can continue to learn from Design, IT, FED. If you are not inquiring, IMHO, you are not doing UX. Your job is inquiry, asking questions, clarification, interpretation, understanding.
Design: one of the primary jobs of the UX professional is to understand the needs of the customer/user and the objectives of the business. If you are not getting solid input on this from your "UX" friend, something is amiss.
FED/IT: You know everything. Just answer us when we have questions. Help us understand. Lots of us do not.
0 Comments:
Post a Comment
<< Home