Microsoft .Net 3.0 projects provide opportunities to build awesome UI, right? And surely you've got a developer who can construct WPF controls necessary to support the UI. So you've got a visual designer providing xaml assets to support his cool new UI concept, and your developer is quickly at work providing prototypes for the controls, and perhaps a test harness for the designers...but how does the visual designer's xaml get fully realized in the WPF app? First off, it's clear that the implementation of the UI is rarely done to the designer's full intentions. Enter the Integrator role. The Integrator understands the needs of the developer while also supporting the needs of the designer to assure that the app's UI is as compelling as it was designed, while also validating that the concepts can be realized in code from the developer. The integrator also needs to be able to implement animations and interactivity provided by the interactive designer. He speaks the language of both parties and should be a good negotiator, in my opinion. It also seems clearer these days that some face time with your visual designer and your integrator will assure that the hotness of the UI is realized - it seems less clostly to get the two of them on a box, and tweak the UI as needed. There is quite a lot of diversity in what this integrator role does, and I must say, I don't have all of the answers yet.