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
You came to the conclusion that “agile” doesn’t work for your organization? Please invest 20 minutes and read this. I promise it will help you! The document is NOT about a framework or so. And don't forget to boost - Thanks!
Most organizations have no problem with output, but rather with responding to signals. This is a problem because when t(decision) > t(production), the system becomes structurally disconnected from reality. It is completely worthless to deliver faster if decisions take too long, because then any knowledge gained is immediately devalued.
A thread 🧵
#SystemsThinking #WorkFeedbackLoop #Flow #TheoryOfConstraints #DecisionLatency
(1/2)
Thomas
