[quaddo]

I do something somewhat similar which has evolved for myself and in part for my team. What follows is heavily abridged in the interest of time.

I use Obsidian as follows:

1. Daily log in bullet-point format. Title in YYYY-MM-DD format. Bottom of log has [[YYYY-MM-DD]] with tomorrow’s date.

If I get into a task that starts to get a bit ‘chatty’ and/or would benefit from capturing stdin/stdout/stderr snippets, I’ll use the [[blah]] trick and dump it there.

If a particular priority task didn’t get tended to, I copy that into tomorrow’s daily before stepping afk for the day.

Gets shared with manager, etc.

2. Weekly summary using the ![[Week ending YYYY-MM-DD]] embedded view Obsidian feature in my daily log page. For that at-a-glance warm fuzzies. This boils down to:

- retrospective - highs - lows - 1:1 notes - incoming week’s tasks/priorities

I use this page for my 1:1’s of course. I’ve only very recently started copying the retrospective to my manager via Slack to ensure he’s got the goods.

I prep my incoming week with a new weekly summary, and pre-populate the bare bones for the daily notes.