Today I reported one small aspect of our work here to colleagues on the Learning From Incidents #tools slack channel. slack 
What does it mean to be "focused" on our work as programmers?
There is a feeling in our management that work slows when we lose focus.
I'm wondering if the opposite might be true.
To test this I've been keeping detailed logs of some work I am doing on a side project where I am free of any management pressure to stay focused. I hope the project itself will be interesting here someday so I seek clean, high quality solutions. But today I just want to mention that I found the need to keep multiple logs.
One log speaks to the issues of the project itself.
The second log speaks to my inquiry into focus.
Here I show pages from both logs side by side as I dig deeper from the focus-context to the project-context.
wiki
Both logs are kept as federated wiki sites that makes it possible for them to intertwine whenever that might be convenient.
The story here is one of a false assumption leading to close but not right results. Although progress stopped until I understood my mistake, I would argue that this was a period of heightened focus, not distraction.
I see that I mentioned this work here on August 1st.
Since then a small handful of us have been reviewing each others observations daily while we interpret these as if they are incidents to be understood within the context of graceful extensibility.
We promised each other we would do this for three weeks which ends tomorrow. I'm writing here to order my thoughts as we anticipate another three weeks after tweaking our process based on what we've learned to date.