Company Fired Interns Story, anyone has any story? 
Apr 18 2017, 08:17 PM
QUOTE(party @ Apr 17 2017, 10:46 PM)
My company is executing this strategy. Kena scolded by boss coz problems not in procedure. I told her if like dat my procedure will reach 1000pages. She said then let it be if not how new joiners want to work smoothly.
Kinda agree with your boss on this. In the end it's about efficiency. You faced a problem before you already investigate, experiment and find out the way to overcome it, after that terus document it la. At least next time got similar problem can just follow your update and save time. If not recorded, everytime the staff need to investigate and experiment... Its just wasting time... QUOTE(party @ Apr 17 2017, 10:51 PM)
My process is loans and each companies loans is different as it tobcaters them. How to write a procedure to suit them??? Even if types of loans are well known but not the conditions...
Which is why the current gen workers being breed are textbook type..unable to think, talk and act. And people wonder why their salary so low...
Well, the thing is most companies are working towards standardizing their processes and to remove variance in any processes. This has been the aim of most companies since six sigma method was developed. It's not about whether people can think or not, I give 1 problem to 10 different people to think and figure out, I might get 10 different answers or at minimum more than 1 different answer which all answers are still correct just the solution or method different. Which is why the current gen workers being breed are textbook type..unable to think, talk and act. And people wonder why their salary so low...
Now the issue with having too many ways of handling one thing is that it creates differences in the service level and end user/customer experience. What companies want is for all customers to have the same level of service. Hence standardisation and full documentation of processes is required. If you can't document your process fully, sorry to say it means that either your own knowledge is lacking or you really don't have any technical writing skills.
QUOTE(advocado @ Apr 17 2017, 11:16 PM)
u dum engineer u no need to write out all problems, sure there will be similar cases that you can lump them together and write a general step to trouble shoot such issues without having to write out redundant problems.
ur boss is right, if you don't have a proper guidelines, don't say newbees, even experienced ones will have their own way of doing things because like ur boss said, there's no proper procedure so everything is tru trial & error.
if it's something new, trial & error is normal, but if it's something established, you expect new comers to trial & error & self learn? if problems happened before, write it down, write down how you solved the issue, then when you accumulated sufficient issues, get a junior to compile the writings into categories to reduce the number of pages on your guidelines.
juniors are not freshies, they should already know the job, so they should be the one compiling ur efforts, then u review, and add amendments or if you aren't senior enough write a proposal to your managers so they can incorporate ur proposal and update the guidelines.
if not u will open another thread ranting newbees dunno how to do their job you have to spend this much time to teach them how to troubleshoot.
in the end, u just shooting ur own foot.
ur boss is right, if you don't have a proper guidelines, don't say newbees, even experienced ones will have their own way of doing things because like ur boss said, there's no proper procedure so everything is tru trial & error.
if it's something new, trial & error is normal, but if it's something established, you expect new comers to trial & error & self learn? if problems happened before, write it down, write down how you solved the issue, then when you accumulated sufficient issues, get a junior to compile the writings into categories to reduce the number of pages on your guidelines.
juniors are not freshies, they should already know the job, so they should be the one compiling ur efforts, then u review, and add amendments or if you aren't senior enough write a proposal to your managers so they can incorporate ur proposal and update the guidelines.
if not u will open another thread ranting newbees dunno how to do their job you have to spend this much time to teach them how to troubleshoot.
in the end, u just shooting ur own foot.
QUOTE(advocado @ Apr 17 2017, 11:32 PM)
everyone started as a noob, including you. you just forgotten how noob u were when you started becoz that was long time ago. u probably though u knew everything when you just started and wonder why freshgrads nowadays sucks so bad.
it's the same reason why ur dad think ur soft & incompetent compared to folks back in his days.
Agreed with both your points.it's the same reason why ur dad think ur soft & incompetent compared to folks back in his days.
Quote
0.0180sec
0.42
6 queries
GZIP Disabled