Second day of the week two of lectures at Aalto University School of Economics’ ITP summer programme’s Strategy and Experience. https://itp.hse.fi/
Contents: Interaction design, designing for flow, prototyping
My keynote talk at the 2007 IA Konferenz in Stuttgart, Germany, I argued we need to create fewer final designed artifacts and more tools to help everyone design. The audio can be downloaded from here: http://www.iavoice.com/2007/11/27/ia-konferenz-2007-keynote-english/
Presentation by Erik Lennert of the successful collaboration between the Communications department of the Rocky Mountain College of Art+Design and Markit on Demand (ex WallStreet on Demand), made during the Cumulus Digital Culture session in Denver, October 29th 2011.
Software Architects traditionally have been expected to be well versed in the technologies and software platforms on which their organization run, as well as the businessses they serve. Software Architect's need to balance both sides of this coin: business and technology.
Today traditional ways in which architects engage with development groups often conflict with Agile methods. This presentation explores best practices for architects working in an Agile world and ways in which Agile methods might benefit architects. Additionally it attempts to address some of the concerns that many architects express about Agile, and attempts to provide practical ideas as to how architects and agile development teams can become allies.
May 25, 2011
In 2010 Panasonic made the decision to replace their legacy enterprise search tool and switched the search for all their European websites to a Apache Solr based solution.
Now their customers benefit from an incredibly fast and feature rich solution that is much more than just a search and has become a valuable sales-driving tool for Panasonic. Features like relevancy manipulation, autosuggest, contextual filtering for properties like color or product category were implemented under not the most ideal circumstances mainly that there was no access to structured data. The search was rolled out in close to 30 countries so far also putting Solr multi-lingual handling to a test.
DealerTrack is the nation’s first and largest credit application network for the automotive industry, connecting 17,000 dealers and over 1000 lenders. Senior Director of Technology Architecture, and one of the founding members, Chris DeMeo detailed DealerTrack’s complex environment, spanning multiple geos and data centers and with the diverse architecture that comes with multiple acquisitions over the course of several years. As is common with our customers, they brought Splunk in for a unified view of their data.
“Our developers had full visibility into the anatomy of a problem to rectify quickly and avoid similar errors in the future. We’ve had so many ‘a-ha’ moments with Splunk, it’s become second nature to expect them,” Chris said.
DealerTrack has moved from reactive to proactive, and they have a much better understanding of their transaction volume, transaction mix, and watch dashboards for bunching or other challenges during load tests.
Searching for the next watershed moment for the Drupal project. This is the version of this talk I gave at the Cologne Drupal user group and Kölner WebTreff meeting on September 22nd, 2011.
Second day of the week two of lectures at Aalto University School of Economics’ ITP summer programme’s Strategy and Experience. https://itp.hse.fi/
Contents: Interaction design, designing for flow, prototyping
My keynote talk at the 2007 IA Konferenz in Stuttgart, Germany, I argued we need to create fewer final designed artifacts and more tools to help everyone design. The audio can be downloaded from here: http://www.iavoice.com/2007/11/27/ia-konferenz-2007-keynote-english/
Presentation by Erik Lennert of the successful collaboration between the Communications department of the Rocky Mountain College of Art+Design and Markit on Demand (ex WallStreet on Demand), made during the Cumulus Digital Culture session in Denver, October 29th 2011.
Software Architects traditionally have been expected to be well versed in the technologies and software platforms on which their organization run, as well as the businessses they serve. Software Architect's need to balance both sides of this coin: business and technology.
Today traditional ways in which architects engage with development groups often conflict with Agile methods. This presentation explores best practices for architects working in an Agile world and ways in which Agile methods might benefit architects. Additionally it attempts to address some of the concerns that many architects express about Agile, and attempts to provide practical ideas as to how architects and agile development teams can become allies.
May 25, 2011
In 2010 Panasonic made the decision to replace their legacy enterprise search tool and switched the search for all their European websites to a Apache Solr based solution.
Now their customers benefit from an incredibly fast and feature rich solution that is much more than just a search and has become a valuable sales-driving tool for Panasonic. Features like relevancy manipulation, autosuggest, contextual filtering for properties like color or product category were implemented under not the most ideal circumstances mainly that there was no access to structured data. The search was rolled out in close to 30 countries so far also putting Solr multi-lingual handling to a test.
DealerTrack is the nation’s first and largest credit application network for the automotive industry, connecting 17,000 dealers and over 1000 lenders. Senior Director of Technology Architecture, and one of the founding members, Chris DeMeo detailed DealerTrack’s complex environment, spanning multiple geos and data centers and with the diverse architecture that comes with multiple acquisitions over the course of several years. As is common with our customers, they brought Splunk in for a unified view of their data.
“Our developers had full visibility into the anatomy of a problem to rectify quickly and avoid similar errors in the future. We’ve had so many ‘a-ha’ moments with Splunk, it’s become second nature to expect them,” Chris said.
DealerTrack has moved from reactive to proactive, and they have a much better understanding of their transaction volume, transaction mix, and watch dashboards for bunching or other challenges during load tests.
Searching for the next watershed moment for the Drupal project. This is the version of this talk I gave at the Cologne Drupal user group and Kölner WebTreff meeting on September 22nd, 2011.
1. What are the benefits of using video for prototyping?
Monday, September 26, 2011
2. “...interaction design is first and foremost the design of
behavior that occurs over time”
-Alan Cooper et. al,About Face 3
Monday, September 26, 2011
6. Video is an useful tool for designers who have to quickly represent design concepts
that often involve complex relationships or require a high level of technology. It’s
fast, cheap, easy to share and allows lots of space for faking it.
Monday, September 26, 2011
7. Anatomy of a Hollywood blockbuster
ACT 1 - 0-30 min
Beginning of the film.
Set up characters and
environment. Where is
the story going to take
place and who are the
players?
Set up problem/
conflict in the story.
Whereas ACT I
introduces the
setting, ACT II deals
with the problem
that has arisen.
Rising action,
problem gets
worse, characters
struggle to solve
problem.
Turning point.
problem becomes
something different
from expected, the
story takes an
unexpected turn.
Event turn for
the worse for the
characters.
The situation becomes
the most difficult, the
characters are faced
with impossible odds
and everything seems to
be against them.
Falling action/resolution.
Heroes conquer problem
at great risk and drama.
The story is resolved.
ACT II - 30-90 min ACT III - 90-120 min
Monday, September 26, 2011
8. ACT 1 - 0-20 sec
Beginning of the film.
Set up background and
context.
Set up problem/
mission to solve
with the concept.
Rising action,
explain the what
was actually done
step by step.
Transititon from
explaining
into showing interaction
with the invention.
Usually execution
and interaction is
a huge success
on many levels
Transition from showing
use of the object into
bragging about project goals
met.
Falling action/resolution.
Display of statistics.
Summary of awesomeness.
Case closed.
ACT II - 20-50 sec ACT III - 50-90 sec
Anatomy of a biased case study
Monday, September 26, 2011
20. Your product:
A fantastic device that enables people to transfer physical items “wireless” to
eachother.
Monday, September 26, 2011
21. The process:
1. Plan the shoot
2. Set-up shoot
3. Shoot the scenario
4. Edit using Adobe Premiere
5. Presentation/Feedback on Friday
Monday, September 26, 2011
22. Plan the shoot
1. Consider what interactions are important and how to visualize them
2. Consider required actions per shot: gestures, expressions, person-person
interaction, devices used
3. Create a storyboard of all key shots
Monday, September 26, 2011
23. Set-up shoot
1. Build devices (or use stuff that might fit)
2. Get to location and prepare the scene
3. Adjust lighting if needed
Monday, September 26, 2011
24. Shoot!
1. Check each shot for technical errors
2. Take several shots of important scenes, you can
never have too much material when editing..
Monday, September 26, 2011
25. Evaluate and edit
1. Watch all shots and take notes, what are the highlights, any errors?
Perhaps you need to retake a shot or two
2. Import the footage into Adobe Premiere
3. Have fun!!
Monday, September 26, 2011