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...

Agile Entrepreneurs Manifesto

The  Agile Manifesto  defines the 4 core Values that define "Agile":  " Individuals and interactions",  " Working software",  " Customer collaboration", and  " Responding to change" As I applied Agile requirements (user stories), engineering (XP), and process & project management (Scrum & Kanban) to my startups  (RideStation, and Agile Entrepreneurs)  starting from 2005 to now in 2018, I learned numerous lessons and shared them with my fellow entrepreneurs for the next dozen years. These lessons I have incorporated by "extending" the Agile Manifesto with two additional values pertaining to  Product (5th) and Startup/Business (6th)  -  that the services consultants who wrote it in 2001 probably didn't have to contend with as most (all?) of them were not founders of product startups:  "User Validation, Customer Traction, and Business Milestones" Agile Entrepreneurs Manifesto Us...

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.