1. Notes: 10 / 1 month ago  from hiten (originally from 52weeksofux)

   Deliverables vs. Delivery

   hiten:

   52weeksofux:

   

   Wireframes, flow diagrams, personas, card sorts, content strategy documents, etc. All of these things are important to design, and designers need some combination of them to synthesize their user research and communicate what they’re doing with the other members of the team.

   But too often these deliverables are the last line of contact for designers. Too often these deliverables are what designers prepare and then hand off to implementors. Then they shuffle off to create more deliverables and the cycle is repeated.

   In the end deliverables are merely artifacts of the design process. They are not the final design, they are not the artifact of experience. The end user never interacts with them…they interact with the product or service that is actually delivered.

   That’s the difference: deliverables are divorced from delivery.

   Thus, the task of a UX designer, in order to stay true to our calling, doesn’t stop at any deliverable. Even if our “job” is to create wireframes, we cannot be satisfied with passing off wireframes to other team members. If we are truly concerned with the experience of the people who use our product/service, we will infiltrate their world…we will demand to know the quality of their experience.

   Many UX designers are judged on the quality of their deliverables. This is necessary to a point, we must make sure each step is faithfully executed. But to truly be a user experience designer, we must have a longer scope. We can’t stop at deliverables. We must extend through delivery.

   Deliverables are diminishing in importance. Sketches, super important to early design synthesis, have fleeting value. They are valuable for a very short period of time. Design, implement, iterate, move on. Record the learning, but don’t judge the sketch, judge the resulting experience.

   So, if you’re not involved in the day to day feedback loop of your user’s experience, make sure you get involved. Ask about your feedback channels: support emails, call-center requests, twitter mentions, all of it. Do regular surveys and user testing. Investigate. Demand data. If you don’t, you’re just creating deliverables and missing the forest for the trees.

   Experience, in the end, cannot be captured in a deliverable.

2. Notes

   1. interfaceaddiction liked this
   2. bulszit liked this
   3. hyv reblogged this from 52weeksofux
   4. techbytes reblogged this from hiten
   5. hiten reblogged this from 52weeksofux
   6. 2105 reblogged this from 52weeksofux
   7. tiffehr liked this
   8. cesarhcjr liked this
   9. zebrapoo liked this
   10. subcreation liked this
   11. 52weeksofux posted this


Comments (View)

blog comments powered by Disqus

In computer science a byte (pronounced "bite", IPA: /baɪt/) is a unit of measurement of information storage, most often consisting of eight bits.

techbytes.biz is a unit of measurement of information about all things digitized from the perspective of Douglas Craver.

Doug is a tech marketing and operations action strategist and startup craftsman, entrepreneur, writer, huge Hammond B3 Organ fan - and any musician who can master one - and a great cook (I’m told I can, “throw it down”) based in Northeast Ohio.

I like to think of techbytes.biz as a utilitarian tumblelog and virtual workspace. I hope you enjoy your visit, comment and come back soon.

::my_links::
::email_me::
::twitter::
::facebook::
::the_mobilized_life::
::knotice::
::the_lunch_pail::
::realeflow::
::for-screen::
::skitam::
::extreme_ edge::
::challenge_ aspen::
::brewed_fresh_daily::
::meet_ the_bloggers::
::gamesnake::
::mike’s_barn::
::jack/zen::
::optimistic_rebel::
::intentional_model::
::guy_kawasaki::
::mobile_defense::

View my page on Social Media Club - Cleveland

Following

Tumblr