Three months ago,
I was given my first work opportunity at Information Architecture and User Experience at an exciting digital marketing agency. Having come equipped with over 5 years of experience as a Business Systems Analyst, and about a years worth of self development in the IA/UX field, nothing could have prepared me for the fast-paced and exciting world of agency life! I kind of knew what to expect in terms of the amount of work required, and that every minute was considered billable. However, what I didn't know or realize was how quickly things get done around here, and how quickly YOU are expected to get things done! Sink or swim baby!Prior to starting at the agency, I had been participating regularly in mentorship sessions conducted voluntarily by IA/UX guru Brad Einarsen. During each session, participants were expected to complete some "homework" to help apply Brad's teachings. The great part about this arrangement was that I could take as much time as I needed to complete the work!
I know how to create wireframes, sitemaps, user flows, prototypes, functional specifications, personas, and for the most part, how to conduct usability tests. However, one of the most unexpected challenges that I encountered during my first week at the agency was to provide an IA estimate. Seems pretty straight forward, right? Actually, no. For someone who's had the luxury of taking the time to just create wireframes during his spare time with no cost or timeline to worry about, it's not that straight forward.
I recall my first request was to provide an estimate on building wireframes, a
sitemap, and a prototype of a microsite that consisted of about 10 to 15 pages. Again, having only created deliverables at my own leisure and in the comfort of my own home, I had no idea what would be considered a "reasonable" estimate. So my approach was to break down the tasks into smaller logical parts, estimate how long each part would take, and add a little buffer for my learning curve. Needless to say, my formulated estimate raised a lot of eyebrows! Perhaps a bit too much buffer? =)The lesson here was simple. Although my IA estimation tool provided a (lot) higher estimate than what the Account Manager expected, it really helped me to understand a couple important things. Not only did I have to do my job correctly, for example, making sure to follow strong usability guidelines, but I also had to do my job quickly and efficiently! My IA estimation tool and thought process has evolved dramatically since then, but the key point here is that it provided me with an excellent starting point. It allowed me to quickly plug in some numbers based on the information provided, add a little complexity multipler, some buffer, and voila!
In my previous post, What is Information Architecture?, I had mentioned that the one thing I absolutely love about this job is the fact that there is a LOT of room for creativity. Three months ago, that side of my brain was locked inside a highly secured vault just screaming to get out! Thanks to all the helpful support and creative minds at my agency, this vault has been destroyed forever!










