WhatsApp Notes
Notes captured from WhatsApp self-messages.
Tuesday, 30 December 2025
21:53
🎤 Testing 1, 2, 3, 4.
21:53
🎤 This is another taste measure.
13:45
On second thoughts I think that the weekly meetings should not be one-on-ones. They should be group meetings but each different individual’s file gets updated. So we’ll do them as a group meeting. Another thing to ask in that group meeting so maybe make a separate file with the common things we cover as a structure for group meetings:
• What interesting thing did you learn this week? • Feedback on your metrics
We can expand it from here. So a weekly meeting will be a staple part of the meeting. Company Flow and we will use those individual focus files to update feedback from the weekly meeting
13:39
My end-of-day report for today is finishing up a very extensive round of changes to my Claude Code operating system. Mostly the WhatsApp connection so that I can take WhatsApp notes which post to my Claude Code operating system. And then a lot of tweaks and changes to file, file configuring, file hierarchies and also setting up different kinds of files such as the team focus files and researching how other people are using the Claude Code operating system and feeding that for feedback
13:33
On the focus section of the team member focus files, I think that we should have a section for weekly one-on-one meetings. In the context of that, when I do a one-on-one with them, what are we talking about? For example, in the case of Tyran, let’s talk weekly about what we can do to speed up and what metrics we covered for that week. Metrics that he is being held accountable for. So I think if we have a weekly section and then when we add to it, it can be like a running list of weeks so we can keep a history of it, just what was the feedback weekly on those on the main metrics that they are responsible for.
[processed] 11:25
Something that I have been thinking about is: I want to communicate to my team members and I also want to set this as one of my personal goals for the year. From a communication point of view, I want to communicate more directly. So when I think there’s an issue, just say it straight away. I think that this should be a predictable feedback loop. I will tell people that once a week I will give my feedback on what I think can be improved. Then they can at least expect it and understand that this is just part of the process.
We can actually incorporate this into the Markdown files under “Team” - each team member has a focus document. When I give feedback notes, I can write them there. There can be a section put there for feedback and it should be dated and timed.
[processed] 11:00
Today my EOD. I spent about two hours building a WhatsApp integration so that I can take notes on my own WhatsApp number and they automatically get updated into the Obsidian Vault Brain. I’m really happy with how this came out. This is a huge win