Playing a musical instrument also achieves this, it makes a game about the little things about the brain (an organ we all love), like sequencing, motor skills, etc..
Cannot emphasize this enough.
I literally built my own typing app for this reason - plateaued on monkeytype and wanted better detailed stats so I build typequicker.com
> Better when you have experiences to relate back with.
100% this. I've been teaching software design since the 1990's and it's so much easier when the audience has enough experience that I can wave my hands and say "you know when things go like this ... ?" and they do, and then we can get on with how to think about it and do better.
Without that, it's tedious. Folks with less experience have the brainpower to understand but not the context. I try to create the context with a synthetic example, but (again, waving hands...) you know how much richness your current system has compared to any example I can put on a page or a slide.
I have a groups like feature requests and backlog for catch-all tasks. Then for deadlines I use "Mid January" or "End of January" and move tasks into them, based on a rough hour estimate. Story points doesn't matter because I'm not quantifying complexity across a team members. It's just me working on it.
I work on the tasks that have the highest priority, build locally, test them in a QA instance, and then ship them to prod. I usually run smoke tests in prod just to make sure I don't break something.
I used to use GitHub tickets and JIRA, but over time I needed organization that didn't cause a lot of busy work. For myself, Todoist (paid plan) works.
If I need to add members in the future, I'll go back to using GitHub (kanban, labels, milestones). Most likely my marketing team will need a Kanban before I add another developer.
Other notes:
Use tools that get objectives done and don't create micro tasks.
Finally, create tasks during off time like during lunch, while working out, or on a walk break. I generally plan 2-3 days in advance on the exact work I need to get done. Don't over work yourself.
Right now most chatbot widgets are scripted and require forethought from the admin or business owner. So it's pretty hard figuring out the comment questions on your own or formulating them over time. Even harder when you don't know your customer journey or haven't solidified the ideal customer fit.
This is exactly why I created a bot [1] that blends chatbots and Stack Overflow together. You can have an automated first-line support system without scripting or conversational dances.
- Instead of conversations, you can reuse previous question/answers.
- Instead of guessing FAQs, you can let your users define them for you.
- When questions don't exist, they get catched in the traditional support flow (email). Then overtime, this effort declines.
