Weeklify

This tool is complementary to the dreamlinign template outlined here: https://niklasopf.github.io/ It shifts focus away form the attainment of the long-term overarching goals that you are progressing towards and redirects it to the small battles we all fight on a daily basis. By tracking your progression along a set of KPIs (Key Performance Indicators), it allows you to:

• Monitor your progress toward goals that you have set for yourself
• Prioritize more effectively when it comes to where you spend your time

1 Initial setup

Whilst the wekly usage of the tool is extremely lightweight and fast, it does require some initial configuration before it can track your progress.

1.1. Defining your goals

Keeping track of and maintaining your high-level objectives is most easily done with the dreamlining template. Once you have a clear view of the goals you would like to pursue, you need to define corresponding KPIs. I would recomend to track something between 5-10 KPIs per week. A good KPI is:

• Agnostic to external effects
• Easy to measure
• Correlated to the long-term resuts you want to attain

1.2. Defining utility functions

The tool uses utility fucntions to score your progress throughout a week. Utility functions need to be defined for the different KPIs that you have specified.

• The list of available utility functions can be found here: https://niklasopf.atlassian.net/l/cp/hUyQa0JF

1.3. Formating the input file

Once the KPIs and utility functions have been decided on, it is time to specify the input file. The input file has the following tabs:

• Records: specifies your performance on a given week by means of the KPIs
• Comments: allows you to comment on a particular result. This is not leveraged for any claculations but may be insightful whilst looking back on past record entries
• UtilityFunctions: specifies the utility funciton that goes together with a certain KPI
• PerformanceReport: contains the output from the tool with all the copring included

1.3.1. Specifying the Records tab

The records tab has the following appearance:

• The header has the form "Category - KPI"
  • The Category is used to group several KPIs, which involve similar characteristics or that are related to the same goal, together
  • The KPI uniquely identifies the record type
• The entries are numbers
• Attributes that have ben decomissioned over time should not be removed from the file. Instead they should be filled with "-"
• To avoid that attributes are accidentally left unfilled, the tool does not accept blank values in the populated excel rows. Therefore, in the event that no progress was made on a goal in a given week, the corresponding attribute should explicitly be set to 0.

1.3.2. Specifying the Comments tab

The Comments tab has the following appearance:

• The header has the form "Category - KPI"
  • The Category is used to group several KPIs, which involve similar characteristics or that are related to the same goal, together
  • The KPI uniquely identifies the record type
• The optional entries are sections of text
• Attributes that have ben decomissioned over time should not be removed from the file. Instead they should be filled with "-"
• This sheet is allowed to have blank values

1.3.3. Specifying the Configuration tab

The Configuration tab has the following appearance:

• The header has the form "Category - KPI"
  • The Category is used to group several KPIs, which involve similar characteristics or that are related to the same goal, together
  • The KPI uniquely identifies the record type
• The entries specify the utility functions for each KPI according to the format outlined in the utility functions document: https://niklasopf.atlassian.net/wiki/spaces/WEEK/pages/68452357/Utility+funcitons
• Attributes that have ben decomissioned over time should not be removed from the file. Instead they should be filled with "-"
• To avoid that attributes are accidentally left unfilled, the tool does not accept blank values in the populated excel rows. Therefore, if the utility function is not updated in a given, the corresponding field should be copied from the last week.

1.3.4. Specifying the PerformanceReport tab

The PerformanceReport tab is configured automatically by the tool

2. Running the tool

The tool is run by performing the following steps in sequence:

1. Placing the input file in the "Input" folder
2. Specifying the input parameters at the beginning of the "main.py" script
3. Running the "main.py" script

The result will then be saved to the "Output" folder

2.1. Placing the input file in the "Input" folder

The WeekTracker directory will have the following appearance:

• Please create the InputFiles directory in case it does not already exist
• Please your input file in this directory

2.2. Specifying the input parameters at the beginning of the "main.py" script

The beginning of the "main.py" file has the following appearance:

• Please ensure that the parameters in the section "# DYNAMIC CONFIGURATION PARAMETERS" are appropriately specified
• input_filename: This attribute should have the same name as the excel file you inserted to the input directory
• output_filename: This attribute specifies the name that the output file will have. This can be whatever you like.
• date_string: This attribute spcifies the date that you are interested in analyzing

2.3. Running the "main.py" script

The tool can be run in any python IDE. It should be executed using python 3