As an IT Contractor you know how difficult it can be coming up with a useful solution when your client, or your manager does not have a clear Problem Statement to begin with.
The same is true for your IT Contracting Career Plan.
Whenever you find you are not quite on track its important to get very clear.
In IT you have access to many different methodologies that ensure you get a crisp clear problem statement.
But when it comes to your own Career Development these methodologies will not quite help to the extent I would like. So I have developed a way that shifts you closer to what is required.
STILL.. I need to ask
TO WHAT EXTENT is finding a way to define your career problem more clearly IMPORTANT?
What have you found happens when you don't define your IT Career problem clearly? What IMPACT do indecision uncertainty and STRESS have in your body? COULD this be an AREA TO HEAL?
What are some methods you use to ensure clarity?
TO WHAT EXTENT IS THE FOLLOWING IMPORTANT?
Making sure your Problem Statement
- Uses better phrasing?
- Keeps your options open?
- Addresses best level of detail?
- Is focused on being responsible for Self?
- Stays neutral?
- Is stated in the positive?
Your clear DESIRE Statement
CONVERTING your IT Problem Statement to your IT Desire Statement
Who disagrees that we need to be clear on the problem by creating your Problem Statement?
Who knows we need to spend 20% of our moments on the problem and 80% of our now moments IN the solution?
Who has discovered how to use your Problem Statement to arrive at your Desire Statement?
SO let me ask you
TO what extent is converting your IT Problem statement to your IT Desire Statement an ISSUE
What is the cost of staying in the problem 100% of the time?
What is the cost of not learning how to define a clear, crisp problem statement?
What is the cost of not learning how to translate that to a proper Desire Statement?
What is the cost of not learning how to stay with that desire 80% of your now moments
Who disagrees that we need to be clear on the problem by creating your Problem Statement?
Who knows we need to spend 20% of our moments on the problem and 80% of our now moments IN the solution?
Who has discovered how to use your Problem Statement to arrive at your Desire Statement?
SO let me ask you
TO what extent is converting your IT Problem statement to your IT Desire Statement an ISSUE
What is the cost of staying in the problem 100% of the time?
What is the cost of not learning how to define a clear, crisp problem statement?
What is the cost of not learning how to translate that to a proper Desire Statement?
What is the cost of not learning how to stay with that desire 80% of your now moments
Subscribe to:
Posts (Atom)
