JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for PHD-DESIGN Archives


PHD-DESIGN Archives

PHD-DESIGN Archives


PHD-DESIGN@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

PHD-DESIGN Home

PHD-DESIGN Home

PHD-DESIGN  2004

PHD-DESIGN 2004

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: vain design researchers?

From:

John Feland <[log in to unmask]>

Reply-To:

John Feland <[log in to unmask]>

Date:

Thu, 7 Oct 2004 09:45:59 -0700

Content-Type:

TEXT/PLAIN

Parts/Attachments:

Parts/Attachments

TEXT/PLAIN (124 lines)

My goodness, things get so personal so fast around here.

Regardless...

Design does not have a monopoly on research not being widely cited or
ucsed by practitioners or researchers not always being away of the most
pertinent issues of practice.  Researchers in the engineering and business
space have been struggling with this issue for eons. (Okay, maybe not that
long but a long time)  We beg people from industry to come to our
conferences, offering plenary speaker positions and complimentary tote
bags.  On one instance I recal a senior mechanical engineering professor
openly ranting to Siemens (the largest funder of his research) regarding
their lack of adoption of his brilliant insights.  He continued the rant
by pointing out that Siemens was relying on technology that was almost a
century old, denying themselves the performance gain enabled by the
efforts of the denizens of the ivory tower.  The professor was correct,
they could improve their performance by adopting his reseach
findings.  The point the professor missed was the cost of adoption for
Siemens.  For Siemens to adopt these new methods and technology, the
installation technicians would require PhD's, the economics of which are
not solvent.

You hear similar stories from boths sides of the fence, research and
practice. The challenge is that as researcher, it is easy for us to
perceive the usefulness of our efforts and see applications everywhere.  
(The proverbial "everything looks like a nail.")  The good and bad thing
about this is that many times our audience (practitioners and other
researchers) do not appreciate our advice or cannot afford the costs of
time, or money, or performance impact the make the changes we might be
advocating.  I've heard so many people engaged in conversations, "If you
would only.... then all...."  

There seems to be two significant issues inhibiting the cross pollenation
between research and practice.
1) Cost of Adoption
2) Awareness of research, both within design and other fields

I've already given examples regarding the cost of adoption and the lack of
awareness by some researchers the overall implications of what they are
proposing.  What if we were to DESIGN our research to lower the cost of
adoption?  Imagine using our findings on OURSELVES to understand the
practitioner as a user and exploring the implications of intentionally
designing the dissemination of results in such a fashion to minimize the
cost of adoption of whatever tools and methods we may be advocating. I
feel that going through this process will also help the researcher
understand where their results might have the most impact.  I think it
would surprise Anne-Marie more to see her journal cited in the Journal of
Mechanical Design in an article regarding optimizing the design of the
profile of gear teeth than maybe the lack of adoption in the arenas she
considers her home turf.  This notion of designing research results may be
an old idea in your particular subfield, but it seems pertinent in the
engineering design domain.  We have relied for so long on the channel of
journal articles and research conferences.  These channels have become the
main metrics of academic promotion, assuming that publication directly
leads to broad dissemination and adoption.  We should challenge these
assumptions if the end goal is really adoption.

I believe the awareness piece is more challenging.  Each researcher can
take responsibility for examinging the cost of adoption of their research
results, while the issue of awareness takes the efforts of the entire
community and/or communities.  I recall the title of Hilary Clinton's book
on children, "It Takes a Village."  The same is true with the
awareness.  Rosan's work on ICT may or may not have application to my
daily work of designing MEMS sensors.  My immediate assumption is that her
results could impact the design of a user interface for one of the
products we are contemplating but may have little to do with what method I
design to mechanically couple the sensor to the target system.  We can
help each other out by understanding the bounds of what our research
focuses on within the subfields of design rather than, in the interest of
trying to find commonality in all things, discussing design always at the
abstract.  Moving from the depth of our research application area to
high level discussion of Design with a capital D without couching our
discussion with the perspective or subfield we are coming from creates
confusion on language and misunderstandings surrounding overapplication of
particular viewpoints.  The abstract insight from one field may be
entirely correct within that application area but may not transfer
effectively into another context.  During these discussions some list
members become dogmatic about their positions, knowing in their heart and
soul they are correct.  And they are for their context.  Those opposing
these positions may be equally dogmatic regarding their view of the design
truth.  And they are correct for their context as well.  It is rare that
the "truths" we discover or craft during our research are true for all
cases.  That does not make them any less true or less valuable.

So, if we can begin to address the awareness and cost of adoption issues
within this group, I believe this will better equip us in our design
evangelism with practitioners and researchers alike.

Back to (engineering) design practice...

John

On Thu, 7 Oct 2004, Gunnar Swanson wrote:

> On Oct 7, 2004, at 12:15 AM, Rosan Chow wrote:
> > when i read your previous post, i doubted if the design researchers 
> > you know
> > and criticize are the same as the ones i know. for one thing, i 
> > ignorantly have
> > not heard of 'wallpaper' and 'metroplis'. and the design researchers 
> > whom i am
> 
> Rosan,
> 
> I have no idea what sort of research you do and what it has to do with 
> what sort of design. Maybe there's no professional reason you would 
> have heard Wallpaper or Metropolis (or Eye or Emigre or. . .) but 
> there's a fair amount of consternation expressed on this list that 
> working designers don't go way out of their way to sort through a large 
> amount of uninteresting and widely-dispersed material to find the small 
> percentage of useful-to-them research. I wonder how many design 
> researchers have no connection with designers, the design fields, or 
> the culture(s) of design.
> 
> Gunnar
> ----------
> Gunnar Swanson Design Office
> 536 South Catalina Street
> Ventura California 93001-3625 USA
> 
> +1 805 667-2200
> [log in to unmask]
> 

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

May 2024
April 2024
March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
2006
2005
2004
2003
2002
2001
2000
1999
1998


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager