after the jump > type code: don't go chasing waterfalls: design and development as one fluid...

47
Design and development as one fluid process Don’t go chasing waterfalls

Upload: sullivan

Post on 01-Jul-2015

345 views

Category:

Business


0 download

DESCRIPTION

For many projects in the digital domain, it no longer makes sense to approach a problem as a linear process where polished mockups leave the designer’s hand and land on the developer’s desk. The growing possibilities—and the notable limitations—of the web and the devices used to interact with it require designers and developers to work together from the earliest stages of a project, getting their hands dirty in order to prototype, test, and revise a concept. On the web, nothing is ever “finished.” Rather, something that makes it into the launched project is a point in the evolution from this initial concept. This holds especially true for typography; no longer is type a static object, but rather, a living, dynamic, and adaptable element on the rapidly changing digital frontier. Type/Code, founded by Ian Lord, Andrew Mahon, Lev Kanter, Zeke Shore, is a studio of designers and developers who invent, communicate, build and refine. “We collaborate with ambitious clients who want to bring powerful ideas to life. We find clever solutions to hard problems. We love to immerse ourselves in new domains. We strive to make complicated things beautifully intuitive and powerfully functional.” http://www.typecode.com

TRANSCRIPT

Page 1: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process

Design and development as one fluid process

Don’t go chasing waterfalls

Page 2: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process
Page 3: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process
Page 4: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process

type influence

Page 5: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process
Page 6: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process
Page 7: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process
Page 8: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process

Designers who can code

Page 9: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process
Page 10: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process
Page 11: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process

http://screensiz.es

Page 12: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process

Some things we’ve observed

Page 13: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process
Page 14: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process
Page 15: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process
Page 16: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process

Some things that are working(for us... so far)

Page 17: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process

Iterations

Page 18: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process
Page 19: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process
Page 20: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process

Minimum Viable Product

Page 21: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process
Page 22: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process
Page 23: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process
Page 24: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process

Stories rather than artifacts

Page 25: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process
Page 26: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process

Rapid Prototyping

Page 27: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process
Page 28: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process
Page 29: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process

Integration

Page 30: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process
Page 31: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process
Page 32: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process
Page 33: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process
Page 34: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process
Page 35: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process
Page 36: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process
Page 37: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process
Page 38: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process
Page 39: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process
Page 40: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process
Page 41: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process
Page 42: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process

Individuals and interactions over process and tools.Working software over comprehensive documentation.Collaboration over contract negotiation.Responding to change over following a plan.

Page 43: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process
Page 44: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process
Page 45: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process

Pragmatism

Page 46: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process
Page 47: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process

thanks.

@typecode