[Sigia-l] is it just me, or is it really hard to find IAs right now?

[Listera]

> but are you there for 3.0?

Do I need to be? 
If asked, I could be. It's another contract for me.
In many of my contracts, either I ask or I am asked to provide "training"
for the in-house team during the project or post-delivery. By the time I'm
completely done with the project, there's a directional blueprint for v3.0.
Having said that, it's also clear that I'm not there to provide design
maintenance. This could be done at a much lower cost. Would Jobs ask Ive to
take care of nagging PowerBook design issues like monitor latches/hinges or
trackpad integration post-introduction? He could, but I bet he would ask him
to work on what is going to follow the iPod instead.

> Whether they start in 2.0 or n.0 it doesn't matter, but do they stay for
> n+x.0?

Why should they? That's what in-house design teams are for.

> What I have found from many consultants and I'm sure you are the
> exception Ziya, but they don't know about lifecycle management and so
> their designs aren't realistic.

I should clarify that my comments refer generally to senior/lead designers.
The latter don't grow on trees; they get seasoned after many years of
experience, including iterative design cycles.

For instance, I spent hours (many, many hours) taking the in-house team
through v2, v3 and even v4 of a product I designed recently. I visited
scenarios where specific market changes, client requests, technology
improvements, etc would impact the design and how it would evolve. They are
paying me to do that. And I'm happy to do it.

Once again, the issue is *not* the label. It's the quality of the
vision/process/culture and, indeed, the person.

Ziya
Nullius in Verba