Hello! 
I read the weekly updates every week (redundancy!) and every time there’s something about “took longer than expected” or “this is why it is being delayed”. Let’s get real - due to the nature of development and simply being human beings there’s no point in assigning completion dates to anything, publicly i mean.
Instead, i suggest some sort of progress tracker that is updated every week, with a “+23%” change from last week. List features by major releases, such as Alpha 1.0, Alpha 1.1, Alpha 1.2, Beta 0.9, Beta 1.0, Release Candidate 1, Release Candidate 2, etc… Once all features of a release are complete we move onto the next release with more features, not including the ones already “done” in previous releases. It would be somewhat similar to this progress report.
For example, this latest Weekly Update #96 could have the following progress bars as an example:
(some progress bars are missing, ignore that 
)
All this sounds somewhat arbitrary but it would be focused on progress done rather than delays. I understand that the smaller the team the more impactful delays are because when one of you is focusing on fixing an issue other things are put on hold. Also there’s the issue of interdependent systems: most of the work happens on the back-end and there’s little to show simply because things aren’t connected yet, and only at the very end do things come together and backers can actually see the result and exclaim “finally, progress!”
Don’t get me wrong, i love reading about the insights of internal development, it makes me feel connected. But i feel communication could be more interesting perhaps? What do you guys think? 
