Ask HN: Anxiety and dread approaching status update meetings
If my role is primarily maintaining a large complex legacy application where you're solving scaling issues, there might not be a measurable outcome to report like delivered that feature etc. How am I supposed to give my updates without freaking out that I will be seen to have done nothing (ie solved the problem).
Secondly, if doing R&D, how do you update that you did a thing when it's not anything of note.
Secondly, if doing R&D, how do you update that you did a thing when it's not anything of note.