i created a training called [[project management peace]] a couple of years ago because i kept seeing people ask for “project management systems” on facebook and getting responses that were just names of software. i know that’s what they meant – they were asking for software recs – but equating software with systems is why so many people struggle with “shiny software syndrome” and hop b/w tools over and over again. software isn’t a system. it’s a tool that displays your system to you that, ideally, makes it easier to work *within* your system. e.g, #clickup is not really a project management system. it is in the sense that it establishes a set hierarchy and organizational methods, but it’s ultimately a wrapper for whatever data you put into it. it’s an asset that helps you automate due dates, create templates for tasks, and connect documents to different items, but it isn’t on its own a *system* – the organized way in which you do something. clickup does not *manage your projects*, it just shows you which projects need managing. if you’re using clickup and are struggling to meet your deadlines, putting the same projects with the same deadlines into #asana isn’t going to fix your problem. likewise goes for other types of software; google calendar is not a calendar management solution; zapier isn’t an automation system. i’m not being pedantic to diminish the importance of a solid project management app if you need one; if you do need a p.m. tool and don’t feel satisfied with the one you have, it’s in your best interest to determine whether what you’re feeling is software-related or system-related.