[IxDA Discuss] Apparently, IxD is not obscure enough

[Robert Hoekman, Jr.]

> My advice, if you don't mind me stepping in... Stop making
> "recommendations" and start designing.


>From the harsh reaction, I'm guessing you have someone on your team who's
not doing his job and you've assumed I'm suffering from the same issue. I
assure you, this is not the case here. It's also interesting that you'd
assume such a thing based on the tiny amount of information I provided in my
first post. It's simply not enough to go on to make such a leap.

These debates so far have been about the structure of an app I'm designing.
Specifically, the client argued that they didn't want a product page to be
part of their catalog system. They wanted to send users straight from a
search result set to a reader type app for reading the digital resources
offered by the system. My argument was that, by excluding a product details
page, they were missing a core opportunity to A) reveal more info about the
product, B) suggest other, related products, thereby encouraging further
usage of the system, and C) scale their offering to include the ability to
rate and review the products. They were also breaking a user expectation
that clicking a search result would take them to a new page about that
result.

In other words, they were arguing in favor of breaking a *very standard*
commerce system model, despite all the very positive points for following
it.

I designed the page in question. I showed it to them. They got it. They're
sold on the idea. Rest assured, I'm doing my job.

What I was trying to communicate was that the accessibility expert didn't
have to do any of this. She simply states a few facts and calls it a day. No
arguments there. Just thought it was humorous, hence the ";)" at the end of
my post.

Incidentally, all an interaction designer can do most of the time, really,
is make recommendations (whether in words or in prototypes or something
else). IxDs rarely have authoritative power. In the end, the inmates are
still running most asylums. This is especially true when you are a vendor
rather than part of an in-house software or ENG team.

Also, anyone can argue about anything they want, and people argue about
functioning prototypes *all the time*. Without debate like this, what drives
us to become better designers?

If I worked where you work, I'd quit. It's easy to be right all the time if
no one makes you justify and validate your ideas, and I don't want to be
right all the time. Being wrong makes me better.

-r-