building feedback loops
DESCRIPTION
No I’m not talking about the feedback loops that you might hear over a bad PA system. I’m talking about building into your architecture the feedback gathering that will give you valuable insights into how your users are using your application, the perceived performance of your application, how the quality of your application is trending over time, how effective your development process is, and allow you to fix bugs before your users report problems. This knowledge will empower the team to make fact-based decisions based on data, rather than only being able to use the team’s intuition.This presentation will cover: the theory behind why feedback is important, the ways you can progressively build feedback into your architecture, and detail some real world examples.TRANSCRIPT
Building Feedback Loops into your Architecture
Zach Nies
Replace guessing with feedback
Where are you guessing?
Feedback creates better decisions
Feedback loops
Built to learn
Learn through reflection
Direct Experience
Inspect
Adapt
Inspect & Adapt
What has HELPED
us?!
What
HYPOTHESES
could we
draw about
how we move
forward? !
What has HINDERED us?!
Team Retrospectives
Plan
Do Check
Adjust
PDCA Cycle
A3 Process
Development Process
Iterative Feedback
Development Cycle
Build feedback
Build Trends
Code quality feedback
Stop the line
Performance
Server and client
Server side
Client side
Exceptions
Building in feedback
Data collection
request-id
request-id
Data sources
Data analysis
Reporting feedback Specific Measurable Actionable Relevant Timely
Real-time feedback
Feedback replaces guessing
What is the biggest guess you’re making?
Replace that guess with data
