I specialize in making user experiences and user interfaces. That includes everything from competitive analysis and wireframe design to aesthetic mockups and swell HTML and CSS. I recently joined ThoughtWorks and will be working to build out amazing experiences for our clients while helping guide the integration of experience design and Agile.
Workflows may sound boring, but I find them fascinating - truly. Since I care about the holistic experience, one of the first things I need to understand is an existing process. Why are things done this way? Is there efficiency there, or is it just a workaround? Once in design mode, I'm constantly refining my wireframes and designs, looking to make things not just functional but enjoyable too.
I'm working on UX, but I have lots of experience with front-end tech (HTML5, CSS3, JavaScript w/Prototype and jQuery)... PHP and mySQL are still on speaking terms with me, too. I'm a solid communicator who can take very technical and snooze- inducing subjects and make them exciting and accessible for non-techies: C-level executives, newbies, you name it. I've managed a team of developers, and I've been in roles where I've done it all as "the web guy." I play well with others.
I've written essays and posts on user experience and user interface, often in Twitterform too. Interested in something a little more formal? See my career on LinkedIn. And as always, I welcome your comments and thoughts via email.