• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Feedback Loops
 

Feedback Loops

on

  • 2,698 views

Using Feedback Loops to develop your software user interface

Using Feedback Loops to develop your software user interface

Presented at ELAG 2010
June 10th 2010

Statistics

Views

Total Views
2,698
Views on SlideShare
2,671
Embed Views
27

Actions

Likes
2
Downloads
0
Comments
0

1 Embed 27

http://www.slideshare.net 27

Accessibility

Categories

Upload Details

Uploaded via as Apple Keynote

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />

Feedback Loops Feedback Loops Presentation Transcript

  • Building a User Interface with Feedback Loops Charles Lowell Serials Solutions @cowboyd github/cowboyd
  • I am Developer
  • I think in JavaScript and Ruby
  • I am not Librarian
  • I am not Search Guru
  • I am not Business Man
  • I am not Manager
  • I am not Process Expert
  • I am Stake Holder
  • I am Stake Holder
  • Harmonious Process
  • Harmonious Process Harmonious Code
  • Harmonious Process Harmonious Code Harmonious
  • Harmonious Process Harmonious Code Harmonious Me
  • We get a review
  • Deficiencies • No way to get to the next detailed record • No way to save an item from detail screen • Email form unforgiving of common errors • Option to receive link, citation or both • Citations should show call numbers
  • Summon Mobile • “Nothing but fluff...” • “Your Designers should have thought how people might actually use this interface.” • “It looks to me as if they just rushed it out the door so they could brag.” • “Serious deficiencies...”
  • Why is he so angry?
  • Why is he so angry? Because that’s what software has taught users to feel
  • Software Development Design Release Develop 6 months
  • Software Development Design Release Develop 6 months
  • Software Development Design Release Develop 6 months wasted time
  • Software development breeds hateful users
  • Software Development Design Release Develop 6 months wasted time
  • Our Process Design Release Design Release Design Release Develop Develop Develop 3 weeks 3 weeks 3 weeks
  • Our Process Design Release Design Release Design Release Develop Develop Develop 3 weeks 3 weeks 3 weeks Still There
  • Our Process Design Release Design Release Design Release Develop Develop Develop 3 weeks 3 weeks 3 weeks Still There
  • Our Process Design Release Design Release Design Release Develop Develop Develop 3 weeks 3 weeks 3 weeks Still There
  • Lesson: Embrace the angry face. Failures are valuable. They help you triangulate on the right solution. He’s a fantastic compass of how you’re doing.
  • Deficiencies • No way to get to the next detailed record • No way to save an item from detail screen • Email form unforgiving of common errors • Option to receive link, citation or both • Citations should show call numbers
  • Important Features • No way to get to the next detailed record • No way to save an item from detail screen • Email form unforgiving of common errors • Option to receive link, citation or both • Citations should show call numbers
  • “It looks to me like they just rushed it out the door so they could brag.”
  • Rushed Yes, Brag no. • Get it into hands of power users fast • Let them steer the product, not some designer in an Ivory tower
  • Feedback Loops are the central theme of our process
  • Design Release Develop T = min(t)
  • Not Just from Users • Developer feedback loops (unit testing) • Devteam feedback loops (continuous integration) • Team-wide feedback loops(bi-weekly demos)
  • Step #1
  • Step #1 Deploy to production
  • Gall’s Law “A Complex system that works is invariably found to have evolved from a simple system that worked....”
  • Unit Feedback Write Tests Tests Pass Design Develop Release
  • Unit Feedback • Clearly defined spec for desired code • No extra code than what is required by the test • Afterwards, the test can be used in an automated regression suite.
  • Continuous Integration Check in Deploy Build
  • Continuous Integration • Full regression test with every source code change • Regressions caught within seconds • Changes are viewable and testable within minutes
  • Team Feedback Design Release Develop
  • Release Cycle Team Feedback Design Develop Release Continuous Integration riddled with potential points of failure... that’s great! Unit Tests D DR D DR D DR D DR D DR D DR 3 Weeks
  • Adaptive Path
  • Adaptive Path Failure -> Learning
  • Fail Fast = Win • Competitors change • Users change • Rely on capability, not fixed targets
  • Questions? Charles Lowell Serials Solutions @cowboyd github/cowboyd Thank You!