Tomorrow I fly out to attend this years IA Summit in San Diego. Last time I attended I found I got so much out of it, met some very cool people, and was full ideas on how to take everything up a notch. And I’m not the only one who get’s excited IAS.
As I mentioned in my last post about attending, I’ve created a Tumblr to post my notes, etc. Now this isn’t in keeping with the IndieWeb outlook, but I was at a bit of a loss. Step in IFTTT. I set up a “recipe” that any time I post something here with the ‘IAS14′ tag it should get posted over at my IAS14 Tumblr. We’ll see if it works with this post. This also means if I syndicate to Twitter from here, I shouldn’t get double tweets when it hits Tumblr.
We’ll see how this, and posting from a phone & tablet, goes when I’m out there.
Once again I’m lucky enough to be attending the IA Summit, which this year takes place in San Diego. As usual I’ll be publishing my notes, photos etc. over on a dedicated Tumblr – http://ias14-davidmead.tumblr.com/.
Yes it’s in a silo, but until I can get the right tools in place it’ll do.
As with IAS12 I’m expecting great workshops, presentations, and conversations about where we’re going in the world of IA and UX. Hopefully catch up with a few online friends IRL too, but not to have a repeat of my phone dying.
If you’re attending, and want to chat, let me know. Always happy to geek out over drink.
Had a great time at June’s NEOUPA meeting. It was a free event and they partnered with Cleveland Give Camp to help with the upcoming Give Camp weekend.
After some pizza we got to meet one of the charities being helped – P.A.W.S. After a brief intro we broke into groups and started going through the information packets. We had an hour to pick one aspect to help with. Number 2 group (Nicole, Mindy, Jackie, and myself) had a wide range of skills from technical writing to information architecture. We decided to look at the content, re-do the navigation and present the home and internal page.
That hour goes quick.
We decided to cut and combine a lot of the content, which it turns out most in the room did too, and then come up with a main navigation that could hold this. Testimonials were distributed through the site as opposed to being on their own page. We added a donate widget on every page, as well as a widget for events.
I did some sketching and when we agreed on the approach, I drew it up on the large paper for Jackie to present. It was a fun challenge to see how much you could get done and see all the different approaches people took.
Our work will be part of the information packets for P.A.W.S. used during the weekend. It’ll be interesting to see if any of our ideas get used in the final site.
One thing I’ve been thinking about recently is when do I, as a user, expect to have a piece of information presented to me.
Take, as an example, driving along the freeway. I see signs for the different gas stations that I could use. What would be nice (my expectancy) is seeing how much they are selling their gas for on those signs. For me this is making my decision to leave the freeway now or wait until the next exit easier.
Now technically this is possible, but is it in the best interests of the gas station? No, obviously. They want you off the freeway because you are more likely to fill up, regardless of price, than get back on and try again.
It’s a balancing act that we online folks have to go through all the time when creating sites and experiences.
When paying bills online you generally receive an email reminder. Do I expect the amount to be shown in the email or when I log in? And if it is when I log in, should it be the first thing I am presented with?
For me, the expectancy is showing the amount in the email. For the company it could be after logging in. They may want to show/sell me something else or maybe they are not allowed to show that information in something as unsecure as email.
Instead of leaving it there though, I find I’m thinking about the next level of expectancy for the user – If you cannot show the amount due, are they expecting to be presented with a reason why?
Next time you’re designing something, think about your users “expectancy of information” one or two steps further along than normal.