Noting Monthly Activities
During the mid year or any appraisal typically you need to provide the details around accomplishments. In the past it would take me a bit of work to figure out what I had accomplished and where I want to go. Not this time. For the past several months, I’ve been using a practice I’ll call Monthly Results. Each month, I create a short-list of results in a Wiki and send a link out to our management team as an FYI.
Benefits of Monthly Results
Creating a Monthly Results list has a few benefits for me:
- At a glance, I can quickly see the forest from the trees.
- It helps keep management in the loop on results.
- It helps keep my teams focused on results over activity.
- I can see interesting patterns.
Most importantly, it's my portfolio of results. If I don't like the portfolio, I can see at a glance where my time went and how I need to shift focus. Thinking in terms of a portfolio of results helps me quickly rationalize things like "Do I have my sure bets?" ... "Do I have a set of riskier projects to learn, grow and innovate with?" ... "Am I working on meaningful problems?" .... "Am I delivering value?" ... etc.
Example of Monthly Results
Here’s an example of my monthly results list. It doesn’t have to be fancy.
For Month of Nov
- Fixes applied to the codebase
- Comleted the design for elearning course
- Worked with customer support to setup the ticket logging system
- Debugged the tricky issue around the Memory leak in C# code
- Worked on documentation for the new feature
Ramping up on new module
|
|
