Nothing can bring you peace but yourself. Nothing can bring you peace but the triumph of principles.- Ralph Waldo Emerson
*This photo was from the first time I went skiing last Winter. I was tired, scared and wimpy. All because I didn't trust myself. I set my heart to believe I will crash into a tree or a fence and I will hurt myself bad. That was enough to stop me from even "giving it a chance". I think the first step to defeat is accepting defeat even before facing it. That day I was ashamed of myself - for setting myself up for failure.
Write down a major life goal(s) you have yet to achieve or even begin to take action on.
I have several major goals, but let's just pick two from top of the pile:
- Build a world class mobile app
- Write a book
For each goal, write down three uncertainties (read: fears) you have relating to each goal.
What are my resistances to building a mobile app?
1) I know nothing about programming mobile apps
2) Where do I get started? Should I worry about "having it all" before I start?
3) How will users react to this? Will this be a hit or a miss?
What are my resistances to writing a book?
1) I know nothing about writing/publishing a book
2) Am I a good enough writer?
3) What should I write about? I think my ideas are too random and not sorted for a book
Break it down further, and write down three reasons for each uncertainty.
I suffer from the "I know nothing" syndrome. This is strangely only in selected areas. For example, if I am cooking a regular dish (I love to cook) and I experiment with the ingredients, I don't fear about the uncertainty. I guess I think to myself "What's the worse that could happen? The dish turns bad? I can always order a pizza then!". It is funny how that does not apply to my goals though.
So how do we solve this "I know nothing" syndrome. Like a true engineer, break it down into manageable pieces. Solve each piece and put together (why do I feel like I am talking about Merge Sort algorithm, haha) the final product. Sounds daunting if we think about the final solution, but is not, if you focus on each little piece. So let's take my fears for "writing a book goal" and break it apart.
1) I know nothing about writing/publishing a book
Take inspiration from your surroundings. New York City is a great place to be. Specially if you are a writer who soaks up stuff happening around you. I should find myself lucky to be here. I have to start making notes of stuff around me. And again, just write.
When you have three reasons for your fear, you’ll be able to start processing the change because you know where the fear stems from. Now you’ll be able to make a smaller changes that push you towards your larger goal. So begins the process of “trusting yourself.”
This post is part of the #Trust30 Project. #Trust30 is an online initiative and 30-day writing challenge from TheDominoProject that encourages you to look within and trust yourself. Learn more at RalphWaldoEmerson.me
Write down a major life goal(s) you have yet to achieve or even begin to take action on.
I have several major goals, but let's just pick two from top of the pile:
- Build a world class mobile app
- Write a book
For each goal, write down three uncertainties (read: fears) you have relating to each goal.
What are my resistances to building a mobile app?
1) I know nothing about programming mobile apps
2) Where do I get started? Should I worry about "having it all" before I start?
3) How will users react to this? Will this be a hit or a miss?
What are my resistances to writing a book?
1) I know nothing about writing/publishing a book
2) Am I a good enough writer?
3) What should I write about? I think my ideas are too random and not sorted for a book
Break it down further, and write down three reasons for each uncertainty.
I suffer from the "I know nothing" syndrome. This is strangely only in selected areas. For example, if I am cooking a regular dish (I love to cook) and I experiment with the ingredients, I don't fear about the uncertainty. I guess I think to myself "What's the worse that could happen? The dish turns bad? I can always order a pizza then!". It is funny how that does not apply to my goals though.
So how do we solve this "I know nothing" syndrome. Like a true engineer, break it down into manageable pieces. Solve each piece and put together (why do I feel like I am talking about Merge Sort algorithm, haha) the final product. Sounds daunting if we think about the final solution, but is not, if you focus on each little piece. So let's take my fears for "writing a book goal" and break it apart.
1) I know nothing about writing/publishing a book
Start writing few words a day. That can't be tough, can it? I feel like all my thoughts float into ether and I do not capture them at the time when it strikes me. Make a point of jotting down ideas-on-the-go. Use Evernote. Hmm. And then turn that into a tiny story for the day. I still don't have to worry about later. Just write. And do not fear the BIG goal.
2) Am I a good enough writer?
Let's just assume I am. Things go smooth if you trust yourself. Each time this fear stares at you, think of the time you got that one compliment from your well-wisher or reader. That should keep me going. Hmm.
3) What should I write about? I think my ideas are too random and not sorted for a book
Take inspiration from your surroundings. New York City is a great place to be. Specially if you are a writer who soaks up stuff happening around you. I should find myself lucky to be here. I have to start making notes of stuff around me. And again, just write.
When you have three reasons for your fear, you’ll be able to start processing the change because you know where the fear stems from. Now you’ll be able to make a smaller changes that push you towards your larger goal. So begins the process of “trusting yourself.”
This post is part of the #Trust30 Project. #Trust30 is an online initiative and 30-day writing challenge from TheDominoProject that encourages you to look within and trust yourself. Learn more at RalphWaldoEmerson.me
2 comments:
Go for it! Now you are talking like Manju! btw...looks like your goin the Agile way by breakin it down into small pieces.. trust me it works more often than not;) So, good luck :)
:(
Post a Comment