Agreed. There will -always- be compromise, even in the most ideal situations. Unless your project has a single stakeholder, then there will be compromise to please all parties. Compromise doesn't mean "bad" though, and sometimes compromises can actually lead to better solutions, ones that a single designer working in isolation wouldn't have thought of.
On Dec 24, 2007 3:40 AM, Desiree McCrorey <[EMAIL PROTECTED]> wrote: > Mark Schraad <[EMAIL PROTECTED]> wrote: > > What IS frustrating within the corporate environment is that so often > > compromise is the outcome. > > We may have different perspectives on compromise, Mark. The best I would > expect > from a product development effort would be a compromise; a delicate balance > between the needs of users, designers, architects, business, engineering, > marketing, QA, sales, etc. since all of those needs have to be represented in > the end commercial product for a business to stay afloat. > > However, if all most or all of those stakeholders don't work collaboratively, > the product ends up, at best, software functional - a level that most > software/web products seem to have achieved. > > desiree -- Matt Nish-Lapidus work: [EMAIL PROTECTED] / www.bibliocommons.com -- personal: [EMAIL PROTECTED] / www.nishlapidus.com ________________________________________________________________ *Come to IxDA Interaction08 | Savannah* February 8-10, 2008 in Savannah, GA, USA Register today: http://interaction08.ixda.org/ ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [EMAIL PROTECTED] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
