My go to example here is grocery lists. Most "productivity" apps have a checklist feature, but thats super bare bones. I used to use Cinnamon, but its been taken off the store (anylist is a my current meager replacement). What made it _good_ was that instead of "done/not done" state checklists offer was that it modeled an inventory flow. Pantry -> Buy List -> Shopping cart -> Pantry.

The shopping process is simple and repeatable. I start with the Pantry list, which describes all the stuff I expect in a well-stocked pantry, and step one is to confirm I have them. Anything I don't have (or need more of) I move to the buy list. Later, at the store, the Buy list is my guide to what goes in the shopping cart.

This is very similar to the original intention of Kanban, but:

- the UI is much smoother than trello. Just swiping, no drag and drop. And there's an undo button - the metadata is customized to the process, and can decorate the UI with info. Prices forecast your total at the checkout register, grouping by aisle or location makes it easier to grab the right stuff and confirm you've grabbed all the stuff in one go. - after a period of inactivity all items in the cart move back to the pantry automatically

Trello, at its core is designed for team project management, with many tasks occurring in parallel. The UI is designed to visualize the amount of work being done and where the bottlenecks live. It's very good at this! It even lets you design custom workflows to model the exact work being done. But there's always going to be a tensions in place working against it -- making apps that work for everything usually end up great at nothing, and its product market fit seems to be agile software development, so thats where its UI and feature set lean towards.

So IDK if you switch as much as slowly add to the pile of apps.