🟨⬜ [iOS] documentation of commitments


Who this article is for...

  • new team members (Onboarding)

  • existing team members

  • anyone who is interested in our Operating System


Note: This article is not finished yet!
You can read the collection of thoughts below, which could appear in the article once it is finished.



Video



Collection (to create content of later)

  • our brain is a genius in making sense of things after they have been done

    • justifying why we did something

    • altering reality so it fits to what actually happened

      • Example:
        - BEFORE: I intended to do 15 ...
        - REALITY: I did 10
        - AFTER: My brain remembers, I wanted to do just 10 anyways (= "forgets" that I committed to 15 before)

  • Documentation = necessary to uncover those patterns

    • costs a lot of time in the beginning

    • gains come mostly later, after a longer period of time (recognizing patterns)

  • Why document commitments?

    • clarity for others (transparency)

    • trust = one of the most important thing
      -> is created when you do what you say you will do
      -> documentation provides feedback for it
      -> chance to get better at it

  • Using symbols in the commitment logbook:

    Use ⭕️ for commitment made and βœ… when it is fulfilled.



Create your own

🟩❌ [Template] Documentation of commitments


Tags

English:
Deutsch:


Was this article helpful?