Doing It Right--Iterative Design Based on User Feedback 19 on the next project during implementation of the first. He could also have this person work on related infrastructure projects, like style guides, between projects. "Developing infrastructure would ultimately make us more efficient on new projects," said Jim. Mark asked, "Would this new hire contribute to writing the GUI code?" "Not directly," said Jim, "but given the new appli- cations would be web-based, the UI prototypes could be done in HTML. This could save the developers a lot of time. During the implementation phase, the developers could copy and paste the HTML from the prototypes into the product code. And, at least the UI code would be stable before integrating it with the server logic code. That way, the back-end code would have fewer changes late in the project to accommodate changes in the UI design. Since the UI and the associated logic often accounts for a large pro- portion of the overall implementation effort, having the design locked down before committing to the schedule will improve the accuracy of the project plans." (Jim knew that Jack based part of every engineering manager's bonus on meeting deadlines.) Mark was convinced and approved Jim's hiring budget. Shortly thereafter, Jim hired Rick to work on prototypes and design specifi-