[Sigia-l] UI for the $150 Laptop (OLPC)

[Ziya Oz]

Bill Killam:

> And no one should give this type of authority to a team member - interaction
> designer, developer, business manager, HFE, trainer, etc. for the same reason
> we don't allow one of the lawyers in a case serve as judge.

I won't bother with this nonsensical analogy, familiarize yourself with the
notion of first-chair, second-chair lawyers, etc.

> The role you are talking about is that of Systems Engineer

No kiddin'. You haven't followed a word I'm saying.

> "Designer who want more power" still need to know their place.

In any case, you have finally arrived at the shrine of "design by
committee." Congratulations. Enjoy your interminable stay. While you're
languishing there, you might want to read the articles I posted a few days
ago about why the largest software company with the most teams and team
members on the planet keeps churning out one insipid product after another
for lack of strong, strategic design leadership.

You see, jumping up and down with the team mantra *alone* doesn't get you
good design; strategic leadership does. Now, the question before all of us
is, do we let others (CIOs, CFOs, BAs, PMs, IT heads, developers,
accountants, really anybody else) to fill that vacuum or do we begin to
equip ourselves with what it takes to provide the strategic leadership.

My contention is that the 21st century designer is the best candidate (for
reasons I cited previously on this list) as we can uniquely balance the
needs of the business and the user.

And *you* can keep on *implementing* what the leadership (whoever they may
be) hands down to you.

Ziya
Nullius in Verba