I am wondering if using buttons or navigational elements that look
like buttons(for e.g BACK link) are intuitive?

Let me give you guys some context here:

I am working on designing a knowledge base interface where a user can
look for articles and click on a particular link to read that article.
In the article page on the top I had a "BACk" link that would take
the user to previous page/results page.

Based on some feedback I changed the "BACK" to look like a button.
I am not sure if buttons should only be used to submit data and not
for navigation?

By watching their videos I got an impression that is too back-end
focussed. No much room for a 'rapid' UX mind-set. For that I tend to
stand for Axure. Light and fast prototypes with documentation. I have
no experience with iRise and depending on complexity it might bring
benefits to the requirements management and other parts of the
application development, e.g. back-end programming, test scripts and
so on. It looks overkilling to test UX, though.

Is someone, focused on UX, actually using it? For fast simulations in
an iterative design process?

Hi all,
We the UX team at Samsung India Software Operations is in the process
of conducting a survey to understand energy conservation practices, or
energy consumption patterns globally. It would be great help if you
could answer the survey (25 questions) and have some of your friends
or colleagues answer it as well.

Digitaria is looking for a User Experience Designer for our San Diego
location.
The User Experience Designer role mainly focuses on examining user's
needs and client's business challenges and translating them into
solutions to improve online processes and experiences.
A UX Designer is expected to have a good understanding of Human
Computer Interaction principles and usability best practices.

Wikipedia has had such wide-spread acceptance despite the fact the it
expects the user to learn a new syntax. Of course one needs to learn
that only if one wants to do some formatting, add images etc.. but
one would quickly need those tools when writing articles.

I am wondering if there is any material available on how this new
language was adopted. Was it that the early adopters were much more
tech savvy and quickly learnt? was the help content great? is the
syntax itself very natural? Something else?

There seems to be two major methods of faceted search
design- for the sake of my own vocabulary- I call them 'static' and 'dynamic'
(I suppose there would be some formal terminology, but I couldn't find
any).
The Static model (Eg: Search for laptops in Yahoo Shopping-http://shopping.yahoo.com/search;_ylt=AitSGJz_qz4V.Woy9WLIzSQbFt0A?p=laptop&did=)
typically involves clicking through one facet element at a time (multiple
select being present occasionally) causing the search results to filter

Meld has reached that point where I need help to get through the work that’s
building up. There’s work on social media strategy and planning to do; work
on communications strategy and design to do; work on the strategy, design &
implementation of a Website for a small not-for-profit; and some other bits
and pieces.

Rather than specify a bunch of skills, knowledge of & experience withs, let
me just say what I need you to be able to do:

This is a reminder that our next event, which is guaranteed to be even
more fun than the last, is a few days away. Please join us on Tuesday,
July 28th at 6pm at Gangplank in Chandler.

During this event, we will be merging product and interaction design
for a night of playing with boxes. If you have a pair of scissors you
can bring or some smaller boxes (shoe/mailing size), it would be very
helpful.