The importance of feedback loops in agile management and development
I deal in technology a lot, so my monologue on the topic is technology-centric.
There are several feedback loops that are worth looking over. (1) The feedback from developer to manager; (2) the feedback from user to developer.
It’s worth noting that the closer/tighter the feedback loop is, the more value it brings. Being able to expose errors and omissions, from user back to the developer who actually fixes the problem – the faster it happens, the less time is wasted, the faster overall development takes place.
Does it make sense to spend a decade of focus on something? When you don’t have success, how long do you try until pivoting?
Faith is a tool here. You use faith to achieve. The first success has to be bootstrapped, you kind of pull yourself out of nowhere into the success zone, and the belief that you’re actually able to do so plays a large part in that. You have to see other people’s successes and assume/believe that your own success is possible. This is the way I use faith.
Focus, effort, discipline, attention span – these are synonyms for me. I measure attention span in time segments, and I measure focus and effort in time as well. I can say, achieving such and such goal would take a two-year discipline stretch. College, for example, is a 4-year effort.
Some tasks are achievable in an hour. Some take several days. There are tasks that take months; and there are tasks that span entire careers and decades of time. What are the goals that you are looking to achieve in the next 100 years?