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 accept

Entrepreneur Committee - Advisory Board of SVASE

For whatever it is worth, I would like to announce to my millions of would-be readers that I have been invited to join the Entrepreneur Committee on the Board of Advisors to the Silicon Valley Association of Startup Entrepreneurs . And I have accepted. If you're a hi-tech entrepreneur, I would love to hear your suggestions on what I can do in my "official" capacity to make SVASE a better organization for startups.

Test Trimming: A Fable about Testing

While browsing the web randomly, I found this very cool article on the value of testing. Says the author, Gerald M. Weinberg: "Throughout my career, I've watched in dismay as one software manager after another falls into the trap of achieving delivery schedules by trimming tests. Some managers shortcut test work by skipping reviewing and unit testing in the middle of their project. Others pressure the testers to "test faster" at the end. And, most frequently, they just drop planned tests altogether, hoping they "get lucky." I've written several essays about the dangers of test trimming, but nobody seems to understand, so I asked myself, "What am I doing wrong?" Perhaps I wasn't practicing what I was preaching. Perhaps I was trimming tests myself. Perhaps my writing needed more testing! So, I wrote a story about taking shortcuts and read it to my granddaughter, Camille."