How do you use tasks in Obsidian? And how do you stop it becoming one uncontrollably long list? Every task system I have ever used worked for about a week. Then the list hits 100, it starts looking like my email inbox, and I stop opening it because it makes me feel bad. I just finished the video on how I do it now, and it comes down to two rules. RULE 1: EVERY TASK BELONGS TO A PROJECT No project, no task. If it has nowhere to go, it does not get created. The list shrinks on its own, because half of it never had a home. RULE 2: EVERY FINISHED TASK GETS A MOMENT OF REFLECTION Before you move on, ask: did I learn anything here I will need again? A process, a set of steps, a link, a way of doing it. If yes, that becomes a knowledge note that outlasts the task. Most tasks earn nothing. The ones that do are what make the next project easier. The picture shows it. Today's tasks point up to their project. Some of them leave reusable knowledge behind. Next time the same kind of project comes around, the knowledge is already there and the tasks start from it instead of from zero. POLL: How do you handle tasks right now? One question for the comments: What do you do with a task once it is done? Does anything survive it?

I am looking for a way to add three more pics to the weekly note, and to show up on my yearly review I have tried adding more photos, but it will just add them on the same line I would like it to be a 2x3 image Is there a css for this? Thanks for any help

Yeah so, I just logged in my daily note that bought a new hard drive to back stuff up. I am going to claim this as an expense in my FY2027 tax returns which will need to be done end of June 2027 I was about to create a Project - 2027 Tax Returns and just link that from the log but then I'm wondering is this too simplistic? As the year rolls on I will have car services, petrol, parking expenses.. Domain name registration expenses. Many that I want to claim.. I'm looking for a way to keep track of my expenses, but also distinguish which expense I am going to claim on tax. I'd like to do this via my Telegram Claude bot as I make the purchase or pay the bill. Any suggestions perhaps? Keen to hear how you all do this (if you do) @Dee Construct I see you already have a Youtube finance tracker tutorial which I could try. Do you think that this would do the trick? I would need to get claude to integrate it to the vault.

Last week I posted a video on how to do Task Management in Obsidian, and today I'm arguing why you shouldn't use them. I think there is something inherently broken about how we do task management. There's a few high performance, superpowered, motivated beings who manage to keep an organised list of tasks and work through it every day. Same people who hit inbox zero daily. Most of us aren't like that. Most of us are messy, procrastination loving sloths with bursts of productivity few and far between. I'm one of the sloths. I've started and stopped task management systems way too often. The list keeps growing, I stop looking at it because it hurts to see what's still open, and when I finally do look, most of it is already done. Through my work sessions. So here's the question I've been chewing on since I published the task management video: if so many people fail at keeping a clean task list, is the clean task list actually the best way? Or is it just the "passable" way, and there's a more natural shape we haven't settled on yet? Cars are a good example. They're all starting to look the same, not because every car maker developed the same taste, but because the wind tunnel keeps giving the same answer. Once you know the most aerodynamic shape, every car drifts toward it. I think knowledge management is drifting toward its own shape, and I don't think it has a task list in it. The way I see it, a task in Obsidian can live in three forms: 1. A one-line task, pulled onto the project page 2. A task note, with status, priority, subtasks 3. A work session, where the AI reads the previous sessions on the project and tells you where you left off The first two are explicit and satisfying to tick off. The third one is what I actually use. The tasks and their status get carried from session to session, so there's no list to maintain, no weekly clean-up, no thinking about what's next. Just a trail of work sessions until the project is done. Task list as drag. Work session as the shape with the least resistance.