robertogreco + teamwork + design   7

The Pastry Box Project: Jason Santa Maria
"When I want to find out more about my own work, I ask a question. When someone asks me to look at their work, I ask a question. It’s a silly thing to say, but it took me years to do that. 

It’s silly because it’s probably obvious to you, or to anyone who’s thought about it for a moment: If you want to get a better understanding of something, asking a question is infinitely more useful than making a statement. 

It took me years to get there because I fell into the same trap many young designers do when in a critique—I tried to participate by offering answers. 

Answers are appealing, of course, as is the idea of a charismatic leader who has pockets full of them. But of all the work I’ve done, the projects I consider most successful were accomplished by teamwork. Answers shouldn’t come from one single person, no matter how skilled they may be. Instead, they come as a result of discussion among peers. 

Asking questions is at the heart of collaboration, more so than any project management software or process. And if you want to truly collaborate, I’ve found you need to allow yourself to be someone without the answers."
questions  listening  collaboration  2014  askingquestions  curiosity  answers  leadership  criticism  howwework  tcsnmy  design  teamwork  discussion  conversation  questionasking 
march 2014 by robertogreco
DrupalCon Portland 2013: DESIGN OPS: A UX WORKFLOW FOR 2013 - YouTube
"Hey, the dev team gets all these cool visual analytics, code metrics, version control, revision tagging, configuration management, continuous integration ... and the UX design team just passes around Photoshop files?

Taking clues from DevOps and Lean UX, "DesignOps" advocates more detailed and durable terminology about the cycle of user research, design and production. DesignOps seeks to first reduce the number of design artifacts, to eliminate the pain of prolonged design decisions. DesignOps assumes that the remaining design artifacts aren't actionable until they are reasonably archived and linked in a coherent way that serves the entire development team.

This talk will introduce the idea of DesignOps with the assumption that the audience has experience with a basic user research cycle — iterative development with any kind of user feedback.

DesignOps is a general approach, intended to help with a broad array of questions from usability testing issues, documentation archiving, production-time stress, and general confusion on your team:

What are the general strategies for managing the UX design process?
How do you incorporate feedback without huge cost?
What happened to that usability test result from last year?
How much space goes between form elements?
Why does the design cycle make me want to drink bleach?
WTF why does our website look like THIS?
* Features turnkey full-stack (Vagrant ) installation of ubuntu with drupal 7 install profile utilizing both php and ruby development tools, with all examples configured for live css compilation"
chrisblow  contradictions  just  simply  must  2013  drupal  drupalcon  designops  fear  ux  terminology  design  audience  experience  shame  usability  usabilitytesting  work  stress  archiving  confusion  relationships  cv  canon  collaboration  howwework  workflow  versioncontrol  versioning  failure  iteration  flickr  tracker  creativecommons  googledrive  tags  tagging  labels  labeling  navigation  urls  spreadsheets  links  permissions  googledocs  timelines  basecamp  cameras  sketching  universal  universality  teamwork  principles  bullshitdetection  users  clients  onlinetoolkit  offtheshelf  tools  readymadetools  readymade  crapdetection  maps  mapping  userexperience  research  designresearch  ethnography  meetup  consulting  consultants  templates  stencils  bootstrap  patterns  patternlibraries  buzzwords  css  sass  databases  compass  webdev  documentation  sharing  backups  maintenance  immediacy  process  decisionmaking  basics  words  filingsystems  systems  writing  facilitation  expression  operations  exoskeletons  clarification  creativity  bots  shellscripts  notes  notetaking  notebo 
may 2013 by robertogreco
The Auteur Myth | Wired Science | Wired.com
"…it’s also important to remember that nobody creates Vertigo or the iPad by themselves; even auteurs need the support of a vast system. When you look closely at auteurs, what you often find is that their real genius is for the the assembly of creative teams, trusting the right people with the right tasks at the right time. Sure, they make the final decisions, but they are choosing between alternatives created by others. When we frame auteurs as engaging in the opposite of collaboration, when we obsess over Hitchcock’s narrative flair but neglect Lehman’s script, or think about Jobs’ aesthetic but not Ive’s design (or the design of those working for Ives), we are indulging in a romantic vision of creativity that rarely exists. Even geniuses need a little help."
jonahlehrer  creativity  collaboration  alfredhitchcock  stevejobs  johngruber  design  film  decisionmaking  auteurs  howwework  constraints  support  making  business  teamwork  leadership  2011  from delicious
july 2011 by robertogreco
Tom Wujec: Build a tower, build a team | Video on TED.com
"Tom Wujec presents some surprisingly deep research into the "marshmallow problem" -- a simple team-building exercise that involves dry spaghetti, one yard of tape and a marshmallow. Who can build the tallest tower with these ingredients? And why does a surprising group always beat the average?"

[via: http://scudmissile.tumblr.com/post/554987122]
building  business  challenge  collaboration  creativity  design  prototyping  ted  teamwork  teams  leadership  management  motivation  inspiration  innovation  process  tcsnmy  learning  problemsolving  iteration  failure  administration  tomwujec  psychology  extrinsicmotivation  intrinsicmotivation  success  incentives 
may 2010 by robertogreco
Rules for Brainstorming - d.school news
"Our bootcamp class got an introduction to the d.school's rules for productive team brainstorms today. These are a time-tested, road-worn recipe for successfully generating ideas with your team. 1. Defer Judgment. Don't block someone else's idea if you don't like it... 2. Go for volume. Getting to 100 ideas is better than 10... 3. One conversation at a time. When different conversations are going on within a team, no one can focus.
d.school  design  brainstorming  creativity  innovation  teamwork  productivity  management  ideas  tips  projects  leadership  administration  tcsnmy 
october 2009 by robertogreco

related tags

21stcenturyskills  abstraction  adaptability  administration  advice  agileux  alfredhitchcock  answers  archiving  arts  askingquestions  audience  auteurs  backups  basecamp  basics  bootstrap  bots  brainstorming  breadth  breakingrules  building  bullshitdetection  business  buzzwords  cameras  canon  careers  challenge  checklist  chrisblow  clarification  clientdriven  clients  collaboration  colleges  communication  compass  confusion  constraints  consultants  consulting  contradictions  conversation  crapdetection  creativecommons  creativity  criticalthinking  criticism  critique  css  curiosity  cv  d.school  databases  decisionmaking  denmark  depth  deschooling  design  designops  designresearch  designthinking  discovery  discussion  documentation  drupal  drupalcon  economics  education  edutopia  engineering  ethnography  exoskeletons  experience  experimentations  exploration  expression  externalization  extrinsicmotivation  facilitation  failure  failurerecovery  fear  filingsystems  film  flickr  getout  googledocs  googledrive  hiring  howto  howwework  human  ideas  immediacy  improvisation  incentives  influence  innovation  inspiration  instruction  interationdesign  interested  interestedness  interesting  internalization  intrinsicmotivation  invention  iteration  johngruber  jonahlehrer  just  knowledge  labeling  labels  lcproject  leadership  leanux  learning  links  listening  lookaround  maintenance  making  management  mapping  maps  meedan  meetup  memory  methods  motivation  must  navigation  notebooks  notes  notetaking  offtheshelf  onlinetoolkit  operations  patternlibraries  patterns  pbl  permissions  pixar  play  portfolio  principles  problemsolving  process  productivity  projectbasedlearning  projects  prototyping  psychology  questionasking  questions  random  randomness  readymade  readymadetools  relationships  research  resilience  revolution  rewards  rote  rotelearning  rules  sass  schools  shame  sharing  shellscripts  simply  sketching  spreadsheets  stencils  stevejobs  stress  sublimetext  success  support  systems  tagging  tags  tcsnmy  teaching  teams  teamwork  ted  templates  terminology  thisandthat  timelines  tips  tomwujec  tools  tracker  universal  universality  universities  unschooling  urls  usability  usabilitytesting  user-centered  userexperience  users  ux  values  versioncontrol  versioning  webdesign  webdev  words  work  workflow  writing 

Copy this bookmark:



description:


tags: