On @mfowler blog there is this interesting Article called "Feedback Flywheel": learning from #AI sessions, feeding insights back into shared artifacts.
I've been calling it the Work-Feedback Loop. Same principle, broader frame: a system learns only when work creates feedback that changes the next work.
If your team doesn't learn sprint to sprint, AI won't fix that. You'll just be faster at not learning.
https://martinfowler.com/articles/reduce-friction-ai/feedback-flywheel.html
When I wrote the Work-Feedback Loop, I did not have AI in mind. But time and again, I see that this thinking model is very helpful for integrating AI into the development flow in a reasonable way and for discussing how to do that well. Read it. I am sure you’ll find it helpful.
Basically, my thinking model of the Work-Feedback Loop is about one thing: Organizational Learning. If this is your area of interest, I look forward to your feedback!
https://no-bullshit-agile.com/wfl/
#OrganizationalLearning #Organization #Learning #Agile #WorkFeedbackLoop
Really happy to see that the link to the Work-Feedback Loop is shared a lot in Teams Chats! Hope, I will get some feedback!
Feedback is the observable reaction of reality to work. https://no-bullshit-agile.com/wfl/#feedback
This can be:
Usage behavior
Market reactions
Qualitative feedback (e.g., from real usage situations)
A thread 🧵
#WorkFeedbackLoop #agile (1/2)
Practical value of the Work-Feedback Loop (from the chapter of the document https://no-bullshit-agile.com/wfl/#practical-value)
With this model, you can quickly clarify:
Where does feedback stop being “information”—and where does it start becoming “consequence”?
(In other words: Where does perception turn into a decision that actually changes future work?)
a thread 🧵
#agile #WorkFeedbackLoop #bottleneck #flow #learningorganization
(1/3)
Manche Leute bezeichnen die Work-Feedback-Loop als zu einfach oder einfach nur als "Agilität mit anderen Worten". Was soll ich sagen? Das freut mich sogar.
Warum? Weil es mein Ziel war, ein Denkmodell zu haben, das einfach und leicht verständlich ist! Was die meisten Leute übersehen: Mit der Work-Feedback-Loop habt ihr ein Diagnosetool in der Hand, mit dem ihr Engpässe bei euch identifizieren könnt.
Ein Thread 🧵
https://no-bullshit-agile.de/wfl/
(1/2)
Some people call the Work-Feedback Loop too simple or just agile in different words. You know what? I am very happy about that.
Why? Because my goal was to make it simple and easy to understand! What most people miss is this: with the Work-Feedback Loop, you get a diagnosis tool to identify where your bottleneck is.
A thread 🧵
https://no-bullshit-agile.com/wfl/
(1/2)
Wie ist die Work-Feedback Loop entstanden und wo ordnet sie sich ein? Dazu habe ich einen kleinen Artikel geschrieben.
https://no-bullshit-agile.de/kontext-work-feedback-loop.html
"Learning ability is not an abstract property, but rather a function of time sequences within the loop."
To me, that’s one dimension of #agile work that’s quite often underestimated. It’s not enough to get feedback on the work you deliver months later, or to have a decision about what to do with that feedback take weeks. It’s important to get feedback fast and decide fast. Otherwise, you risk delivering the wrong thing at the wrong time.
https://no-bullshit-agile.com/wfl/#time-as-a-structural-variable
Thomas
