v: Feedback loops

[AdityaNayak]

Change 2: Introducing Feedback Loops

Why this change
Only outcomes matter in the universe and hence, to the organization.
However, outcomes are a lagging indicator. By the time failure occurs, it’s game over.

State of mind is a leading indicator. There has been significant mindspace spent on mapping attributes <> success. We truly believe that if the attributes for each level exist, success for that level is inevitable.
This principle is our tenant and it’s current mapping, our hypothesis. The latter is an experiment in motion and will improve over time.

Similarly from the individual’s lens. Confirmation of progress should not have to depend on:

Having to judge your performance from your boss’s mood
This is the underlying principle behind objective scoring based feedback systems that are not limited to 1:1s. List given below.

Failure at battles
It is certain that failures will occur, they are only a problem if they break a man’s spirit. World is a random function and hence, moments of failure are a certainty.

Let your merit not be decided by things that are not in your control, but the ones that are.

Here are the loops being introduced:

Monthly 1:1 Space
Read the new format for 1:1s further below.

“Help me improve” on Daily logs routine
Whenever the individual senses that motion (not progress) is starting to rear its head, you can ask for a review. You may also add what you are sensing is occurring.

Your team lead (if doesn’t exist, then junior partner) will be available to help observe and course correct.

This will be implemented through Jarvis soon. Until then, it is done manually through DM.

ETA analytics
ETAs are useless if they are not trackable and their trend, not observable.

We will implement a feature of all your currently communicated ETAs and a post-analysis of their accuracy. This will be executed through Jarvis soon.

Default purpose of all loops is limited to self-consumption. Hence, they may occur only at the individual’s desire, not by force. Cyclical events will be scheduled by default. The individual may choose to mark them as not needed.
At the moment, this will be done by marking the respective gcal event as ‘not attending’. In due course, this would be through Jarvis.