On 25 Aug 2009, at 21:48, Amy Jones wrote:
I'll just add that nothing I've done has ever been more persuasive
to a
dev team than producing a highlight reel. Watching one person
struggle
with an interaction is one thing, watching 5 users have the same
problem
in 5 1 minute clips is quite
I don't actually like finishing reports very much - but having to
write them does force one to actually think long and hard about
what's going on.
Any many is the time about three quarters of the way through writing
the report I've suddenly thought 'Aha, so that's how its supposed
to work !'...
"Isn't a better way to just sit with the client's development team
and/or management, and get things done together?"
When I worked as a Usability Logger during my studies, my task was to
ensure that the usability Reports were correct. I also asked for the
development team to be present, but at ti
I agree that it largely depends on the client personality and their
expectations. I work with non-profits and the report is often
something they need to justify the costs. That being said, I realize
that all relevant stakeholders won't read a long, drawn-out report.
My preference is to do the repor
rk and the recommendations are perceived is
really amazing.
--Amy
-Original Message-
From: discuss-boun...@lists.interactiondesigners.com
[mailto:discuss-boun...@lists.interactiondesigners.com] On Behalf Of
paul bryan
Sent: Tuesday, August 25, 2009 8:03 AM
To: disc...@ixda.org
Subject: Re: [Ix
The scope and contents of a usability report should be tailored to
reflect the organizational context in which it is sponsored and
produced.
If you are internal to the organization, and the organization is
small, then I think a bullet list of recommended changes that can be
discussed in person wi
Mashoor, I'm guessing that you make a report and then mail/ hand it out.
*If* that's the case, then there's a simple solution. The issue with
preparing a report and mailing it out to stakeholders is that there is a
slim chance that it will be read by all. Taking print outs and personally
handing th
In my experience, usability reports go largely unread. The business
wants to know the quick wins as well as the longer term issues, but
they need to be easy to digest, engaging and prioritised: filter out
the stuff people dont need to know right now. As a UX designer
working in an agile environment
On Sun, Aug 23, 2009 at 8:44 AM, Mashhoor Aldubayan wrote:
> I'm wondering: how many of you think that writing a big report on
> the findings/recommendations for a project is inefficient?
Absolutely! But sometimes, it's the right way to approach the problem.
Let me explain...
> >From my experienc
On 22 Aug 2009, at 22:44, Mashhoor Aldubayan wrote:
I'm wondering: how many of you think that writing a big report on
the findings/recommendations for a project is inefficient?
From my experience, it seems that I end up discussing (and often
justifying) almost every single thing I write on t
r analysis.
Julie
-Original Message-
From: discuss-boun...@lists.interactiondesigners.com
[mailto:discuss-boun...@lists.interactiondesigners.com] On Behalf Of
Mashhoor Aldubayan
Sent: Saturday, August 22, 2009 10:44 PM
To: disc...@ixda.org
Subject: [IxDA Discuss] Usability Reports: A was
Hi,
I'm wondering: how many of you think that writing a big report on
the findings/recommendations for a project is inefficient?
>From my experience, it seems that I end up discussing (and often
justifying) almost every single thing I write on the report, no
matter how logical it is.
Isn't a bet
The type of report can vary, but there is an issue of tracking
usability problems. When you do a study or review, the product team
will likely only fix a minority of problems and some problems may be
deeply rooted in the Web or GUI architecture and you will have to
decide whether to patch (tempora
Rolling back 5-7 years ago we used to write lengthier reports for
clients. This was partly because Usability was new in our market and
the clients we were working with required more extensive reports.
Today, we definitely lean towards presenting results in a PPT using
screen shots, call outs
On 16 Nov 2007, at 11:59, Marianne Jensen wrote:
> I'm curious to know what other usability specialists are including/
> excluding
> in their usability reports. I'm finding that it largely depends on the
> client, as well as budget of course.
[snip]
It depends :-)
Actually, when I can, I prefe
When doing a written report, we use a modification based on the CIF.
We've made adjustments based on feedback from our clients in regards
to what works/doesn't work for them. But most of our "reporting" is
done with a Keynote presentation. We discuss what works and what
doesn't work, provid
Amen! This is exactly what my team is doing right now. Instead of a
huge report that no one digests, we meet face to face and go through
the problems we found and the proposed solutions. Screen recordings
are also a huge help.
Jeff
On Nov 16, 2007 7:25 AM, Adrian Howard <[EMAIL PROTECTED]> wrote:
I'm curious to know what other usability specialists are including/excluding
in their usability reports. I'm finding that it largely depends on the
client, as well as budget of course. The more liberal the budget, the more
likely it is that we have time to go through and design suggested
alternativ
18 matches
Mail list logo
