Vin

[JSpitz]

---

Members do not see this ad.

Is it just me their message boards are nothing like the ones that we are used to (i.e. this one)? I know how to get to where I want, but I feel that the interface is quite cumbersome.

 

[twelvetigers]

It is. You get used to it, though... sorta.

 

[EllieGirl89]

I actually kind of like the VIN setup. Once you get used to it it's pretty efficient.

 

[goldnretrivrgrl]

I'm having so much fun just surfing vin. The format is a little odd but just playing around with it helps. 🙂

 

[twelvetigers]

Search for "VIN photo collection" in the message boards. Awesome thread.

 

[HopefulAg]

I hate the VIN setup and they've no desire to change it to a more user-friendly format.

 

[SilverSpyderGT]

I'll agree - the setup is proprietary and therefore less familiar to most than the typical vBulletin (like SDN) format, but if we (VIN) were to buy the vBulletin software and switch over, I guarantee there would be an outcry among the VINners accusing the admins of "selling out".

I like how the VIN format allows all of the users to see posters' names or to post anonymously. That is something you can't do with vBulletin.

There are some good pages in VIN's "Help" files if you are having trouble navigating the message boards or the site in general - if anyone needs help, PM me, and I would definitely be willing to lend a hand.

 

[twelvetigers]

I don't expect them to run out and get vBulletin or PhP. I know Paul built the site from the ground up back in the 90s. But, there are a few major shortfalls that should be fixed. The most painful thing, for me, is the way it works when you quote a previous post. It's annoying, hard to follow, and ugly.

But, VIN is a great resource. I'll never badmouth the content, just the design (and maybe a member or two, but I keep that to myself - lol).

How about the ability to edit a post? Definitely something we take for granted here.

 

[JSpitz]

.

 

[twelvetigers]

Maybe you should email Paul, as I have done (without response). If enough people do, perhaps it would help encourage an eventual change.

I do feel guilty - it's kinda like insulting chocolate chip cookies for being ugly. But they're still tasty! And euphemisms are still not my strong point!

 

[JSpitz]

Maybe you should email Paul, as I have done (without response). If enough people do, perhaps it would help encourage an eventual change.

I do feel guilty - it's kinda like insulting chocolate chip cookies for being ugly. But they're still tasty! And euphemisms are still not my strong point!

That would be like calling someone's baby ugly. I ain't going there, dawg.

Seriously though, even if Paul wanted a redesign, the whole thing might be cost prohibitive. I think a proper and complete interface/front-end redesign (message board, CE, others) will also require recoding the back-end.

Also, transferring the data out of the (current) legacy system. Actually, that is probably the reason why he's not doing it. SilverSpyder says that the "setup is proprietary". Transferring data from a proprietary setup implemented during the 90's onto a modern platform?? I do not envy the company taking on this task (if it ever happens).

 

[twelvetigers]

This is true.

Well, it's kinda ugly, and unlike the baby, it won't grow out of it anytime soon. So... I dunno. SOL?

'Spose I'll just deal, huh?

 

[quantized]

I don't mind the format. It takes a little practice to learn to use, but you have three years to play with it until you really need it. I think a change as drastic as you are discussing would be really hard for a lot of the less computer adept (and paying) generation to adapt to after learning the current format. They do make changes though so if you're curious about some of the changes that they've been working on, you can play with http://beta.vin.com

Paul is pretty good about responding to email but he gets a ton, so he doesn't always reply immediately.

 

[SilverSpyderGT]

There are some improvements in the works.

We are updating the search tools; I am not going to reveal any specifics now, but they will be very useful and I am excited for the changes to be unveiled.

Also the VIN beta site (http://beta.vin.com) is being designed to be more compatible with mobile browsers (better drop down menus, etc.).

Be assured, Paul is very aware of people's concerns and is continually trying to make VIN better for everyone! 🙂

 

[JSpitz]

.

 

[nyanko]

what

It would not be hard at all. I will crudely explain some parts of User Centered Design (UCD) in the context of a VIN redesign. I will be skipping a lot of steps and information.

Normally we start with user research. It will entail studying how the users use the site, what they use it for, where they use it, and the like. In a typical study, we would analyze the user population and form user profiles to represent different types of users. One of them would be the older population. Normally these profiles would be broken down with other factors such as profession, specialty, geographical location, but this is just a crude explanation.

After identifying these profiles, users that typify their groups would be asked to complete specific tasks such as finding papers or asking another VIN member a clinical question with the current VIN interface. These studies would be video taped along with eye tracking and mouse movement. The goal is to understand the thought process, behaviors, and motivations of this "type" of user.

After the initial study, it is up to the interactive designer to come up with a prototype that fits the needs and work flow of different user profiles. Then, user testing of the prototypes will commence to gain feedback. Prototypes typically go through two to four major reiterations (depending on the company and budget) before some form of alpha release occurs.

By the time the general population sees the interface, the product will have gone through exhaustive testing by almost all types of users. There will still be more feedback and further minor changes will occur, but the end product should be intuitive and simple to use. No one should have to be trained in the new system.

That is the whole point of User Centered Design. The user is king. If the user needs to read a manual or watch a video, then that is the designer's responsibility. If a user makes an error or can't find something, then that is the designer's responsibility.

For the record, there is no such thing as "not tech-savvy" users. There are only "not user friendly" interfaces. For anecdotal evidence, see how the older population rate Mac's ease of use versus PC's ease of use.