Hi Charlie,
On Thu, 14 Feb 2008 10:52:50, Charlie Kreitzberg [EMAIL PROTECTED] wrote:
I have always positioned myself with clients as the person
responsible for the conceptual design of the product. I take
input from both the business stakeholders and the technical team and
synthesize their
Pankaj,
I think you are over-generalizing a bit much. First off, an
interactions of any type (computer computer and human human
and computer human) all can be handled by an IxDA at some level.
Usually in the enterprise situation is a mix of all the above that
needs to be facilitated within
Pankaj:
I think your question about the role of solutions architects is a
good one. I am not certain where the term comes from but Microsoft
defines it here:
http://www.microsoft.com/learning/mcp/architect/specialties/default.mspx#solutions
As I read the definition, the solution architect is a
On Fri, 15 Feb 2008 06:37:43, dave malouf [EMAIL PROTECTED] wrote:
Pankaj,
I think you are over-generalizing a bit much. First off, an
interactions of any type (computer computer and human human
and computer human) all can be handled by an IxDA at some level.
I agree 110% with you but
In the context of Alan's keynote, I totally agree with Alan. ;)
In the context of a more complex conversation, I'm not sure I agree
with your assertions and assumptions.
In the building world an architect is often partnered with a civil
engineer and both are responsible for different aspects of
Dave/Pankaj,
I think you're both making valid points, and the answer is, as usual,
it depends.
I would normally tend to side with Pankaj's side of the argument. I
have yet to meet many IxD's who are interested or experienced in
designing a device driver communications protocol or a data
On Fri, 15 Feb 2008 11:11:16, dave malouf [EMAIL PROTECTED] wrote:
I also disagree with your assumption about computer | computer
interactions. To me a conversation is a conversation and the IxD is
best at creating conversations between any intelligent entities.
silicon or carbon.
What kind
Eco-system design is the great next area of IxDers to explore. The
iPodiTunes example is the tip of the iceberg.
I wish I could go into more detail, but I'm treading on where the
work I'm doing is right now. But how does my iPod talk to my PC/Mac
is an interaction design problem, not a system
Pankaj:
I think you have pointed out a critical issue for the IxD profession.
If, as you say, people involved in the whole process of software
creation consider interaction designers to be a small part of the
total process, we will not achieve our potential as a profession.
I have always
