Skip to main content

Why is it so hard to find a good "User Information Architect"?

As the bootstrapping founder of a web 2.0 startup, the single most important - and difficult to find - skill for me is the web User Information Architect. Not quite UI design, and definitely not graphic design, a UI architect is a human-computer-browser interaction expert and highly experienced and skilled at both layout and transitions.

Many of my fellow entrepreneurs seem to share my predicament. They tell me how they hire 3 different people:
- the first one to do the UI storyboards (in Visio or some graphic tool, or even paper);
- a second person who converts it to HTML, changing where needed to see what's really possible in HTML, finding appropriate tools/controls for combos, etc., but adding hard-coded links to show page transitions; and
- the third, to convert remove the hard-coded links from HTML before implementing JSP.

In the last 8 years, I have personally found only one person really skilled and able to do it all in HTML/JSP, with phenomenal productivity (about 3 times more productive than all the three combined). Yet, he seems to be charging the same as the first one who only does storyboarding. In sum, he's a huge bargain, given how talented and productive he is. But ... he's also very busy.

So, I'm always in a dilemma- should I find someone else to do my UI? And then the harder question- can I find someone I can afford who is equally good? So far, the answer has been a resounding 'No'.

Why are good UI architects so rare?

Comments

Popular posts from this blog

Splitting User Stories vs. Rally's "split" feature (that has nothing to do with it!)

Agile tool Rally has a "split" feature it recommends to handle "unfinished work" in a Scrum Sprint:

Manage Unfinished Work - Split user stories (new link)

Below are my observations on the "Split" feature in Rally (followed by a few excellent articles on Splitting User Stories):
This "split" feature in Rally has numerous problems: 1. Nothing to do with Splitting User Stories It has nothing to do with "Splitting a User Story" which is an advanced but fairly well-understood field in Agile, and a tool for Product Managers to use in one of the two scenarios: The Product Manager does it before an Iteration commences (i.e. during backlog creation or release planning) to create User Stories by business value that are right-sized, i.e. they can be comfortably implemented inside an iteration; The Product Manager does it in Iteration Planning or in the middle of an Iteration to reduce scope by removing/simplifying acceptance criteria, in response to t…

User Stories: you're not Agile without them

Failure to effectively transition to Agile development is often based on a fundamental failure to understand what a User Story is.

Allow me to explain.

The most important aspect of a User Story is that it's an independently *schedulable* unit of requirement (feature). The key to achieving the "independently schedulable" characteristic of a user story is that you express it in terms of how a "user" would use it. This leads you to a unit of functionality that's implemented end-to-end (UI to backend) that a user can actually interact with.

Not surprisingly, because of the focus on how a user would think about a feature, a user stories are highly readable - and could very well be written by the users themselves. However, the other important and less obvious aspect of a User Story is the emphasis on communication with the end-user and getting confirmation on the acceptance criteria.

Describing all the requirements as User Stories for a decent sized product is rigoro…

To dream or not to dream? How about keeping your mouth shut?

Here's a really nice quote from one of my dear friends in response to one of my dreams.
Between the bigger things you cannot do,and the smaller things you don't want to do,you may end up doing nothing The problem with quotes and analogies is that they are almost always approximately appropriate, but rarely if ever exactly applicable . A quote is by definition a generalization. Also, we are by nature biased with our prejudices, biased by our own very personal and unique experiences, and biased, by nature, against those who are near and dear to us. While we want them to succeed and would eventually be happy if they succeed big, our natural instinct is to "help" them "stay grounded".

I disagree with this helping nature, of course. I can - and will- expound on the virtue of dreaming big and having a big mouth. But that will be another day.

Today I'm going to present a few quotes on the flip-side of my friend's quote. Feel free to add yours to the list…