Its a waste of time, what would you actually do with all these bullet lists? Any business process that generates information should also consume that information somewhere.
Why ask for "approx five"? If I did ten important things why can't I list all of them?
What if I did only one thing? Will I get penalized for listing only one thing?
If I did one thing but that itself was comprised of five other small interrelated things, how do I list that?
- Resolved the functional overlap with finance and accounting history calculation.
or
- Reviewed the spec with the accounts team
- Reviewed the spec with the finance team
- Simplified the QA testing scope to remove the old issues
- Identified which of the two overlapped code bases was in the best shape
- Generalized the interfaces so that external sources can be easily added
These are examples of how utterly stupid it is to pretend that this is managing people. Also a good manager knows what his team are doing if he gave them the work. Usually teams meet weekly and this stuff gets thrashed out and decisions made, no need for stupid little emails back and forth and all the confusion and so on.
If you think is good management then now wonder the Chinese are beating us at industry. I know some truly excellent managers, people who get big bonuses for managing their staff and resources well and I know that if they hired a manager that started acting like Musk, telling people to write silly little emails, they'd be out the door.