As usual, I make my own way in my little Myvi to PJ campus...
Dell Taiu, the speaker of the day...
A great inspirer, taught us plenty of skills which will benefit our working life in future..
I'm not really in tune for the first half of the talk...
Maybe due to Spain vs France game in the night before...
I'm just not focus enough...
And ya, I found that I tend to look at my phone more often recently...
Not a good sign...... Have to learn to control...
Learning how to identify problems may sound easy..
A tedious process but a very useful one if you could master it...
By stating the problem statement, it will let you have clear picture on what you face...
- State problems only based on FACTS, not opinions...
- Do not include Cause and Solutions while identifying your problem... (it affects your judgment later)
- Do not assign BLAME...! Solve problems not POINTING FINGERS... :)
By using Histogram, Pie Chart or whatever visual aids, it will make your picture even clearer...
A very good method to show the identified problems to the boss...
- Do not put in redundant data... Who wanna read repeating facts?
- Illustrate your graph in a clear manner
- Do not do complicated calculation.. Shows only SIGNIFICANT FIGURES...
- Highlight on the important parts in the Graph itself... eg: highlight on the comparison data
- Chart ONLY important matters
- Dangerous if graph axis not being plotted properly
- Use chart to explain but not repeating your facts..
Learn how to be specific on your problem, spend time only on the problem scope!
So always ask WHY... WHY... and WHY... You will get the ROOT CAUSE ...
Never believe in anyone until you managed to identify it with ur own eyes... :)
EVIDENCE is the only thing you could believe on...
Ask yourself few questions before coming with suggestions on solutions...
- Is it being tested?
- Will it solve all or just part of the problem?
- Will it achieve the target for improvement?
- Is it practical?
- How fast will it work?
- Is it a long term or just a short term solution?
- Does it satisfy customer requirement?
- Will it improve service quality?
- Is the solution cost effective?
So list your steps as a Working Instruction (proper documentation) for future reference...
Don't be stingy, just share what you have... State them clearly...
God knows? You might need them in future.. :)
After one day of listening, I still don't feel enough...
Obviously, one-day-talk can't make you survive in corporate forever...
The most important part, is how you bring yourself in the corporate...
Your attitude and your character will determine how fast you climb your corporate ladder :)
