Thanks for posting. As someone who helps a few people reach their goals, I have some questions for you. The first one should be a why for each of these goals. If you don’t tie it to an emotion, you will struggle keeping them consistent.
Here are my questions on each one, take them with a grain of salt.
Why are you currently not proud of your work? What can you do to fix that?
What does it mean to be completely planned out? Also are you going to leave margin in your plan for the unexpected?
Why did you stop in the first place?
How are you going to prioritize drumming?
If they are too personal, don’t worry about it. More curious than anything else.
I think if a person is just starting out on goal planning (like the 12 week year method), I’d suggest starting small. After the 12 weeks are up, we can get a better idea of our capacity or figure out along the way any kinks that need to be ironed out so we can get the 12 week year method going faster.
If I had to learn cooking, I’m gonna start small by learning how to bake a cake. I don’t know if I’m confident enough in handling a 12 course meal when I’m just getting started.
The four goals that @KevinR has on his plate sounds like a reasonable number to start off with.
It probably helps to have guest bloggers come in to contribute every once in a while. I’m amazed at how much work goes into writing a blog or producing a podcast on a weekly basis. @joebuhlig amazes me with how many podcasts he’s juggling. I’d be out of breath and wheezing for air.
I had a database project that went wildly out of control with complex workflows and overloaded features. I think it helps to scale back and start with one small part of the project. Get that released into the wild. Then real world experience can re-shape future goals and possibly take you down a slightly different path or even a divergent path that you didn’t see coming. Re-iterate with another new feature added on top of it to make it version 1.1 and then see where that path takes you. I know the general direction and I can plan out most of the major milestones. But I only really need to flesh out the first few miles on the map before I can think of the next leg. So I spent time planning out the first 10 next actions on my project and got that released to see what works, what needed a little more work, or to see if I need to rethink what I worked on. It’s all about the baby steps.
I remembered stalling out because I was looking so far ahead and was so scared about how much longer I had to go to get there. It felt like a marathon. I should’ve just been worried about the next mile instead of the whole 26 miles. I felt better when I only had to worry about the next mile (or the next 10 steps in the project). I had small milestones and in-progress goalposts to achieve first before I can see the final product.
@KevinR, have you tried doing a brain dump? I know that when I’m stressing out over my workload or feeling like I’m not working on the right projects that sitting down with pen and paper to clear it out helps. I’m terrible at noticing when I need to do this but when I take the time it gives me a sense of clarity that was desperately needed. In your case, I wonder if that would show you the direction to start.
Systems my dear friend. Systems.
Also, @wilsonng, looks like you’ve met the bot. For fun, send it a private message and you can play around with it.