Skip to main content

Komunikasi Berkesan


Sebagai leader, jangan sesekali assume orang lain faham komunikasi kita. Kita boleh cakap pasal performance, tapi tak semua orang tahu context perbualan. Orang lain mungkin assume perbualan performance tu pasal kereta instead of application. 


Bahaya salah komunikasi dengan teammates, boleh rosak project. Aku dah senarai ciri-ciri komunikasi yang berkesan di bawah:


  • Jelasan

    • Pastikan objektif tercapai.

    • Gunakan konsep MRT (Measurable, Realistic, Timebound).


  • Lengkap

    • Gunakan formula 5W1H (Why, When, Where, Who, What, How).

    • Contoh: "Tolong buat report tentang umur pengguna sistem A dari tarikh B ke C, dalam bentuk excel, submit by Isnin pukul 4. Data ni nak guna untuk marketing ke pengguna."


  • Ringkas

    • Jangan terlalu panjang; elakkan ayat berbunga.

    • Straight to the point.


  • Kukuh & Konkrit

    • Berdasarkan bukti atau data yang spesifik (bukan general).

    • Contoh Teruk: "Ramai kata sistem slow."

    • Contoh Baik: "17 user dari Semenanjung dah komen yang sistem slow pada pukul 8-9 pagi."


  • Sopan

    • Sentiasa sopan dalam kebanyakan situasi.

    • Jika perlu mencabar zon selesa (push comfort zone), kurangkan sedikit kesopanan tetapi jangan biadap.

    • Sesuaikan ikut senario.


  • Consistent

    • Jika tukar fikiran atau arahan, mesti ada justifikasi.

    • Boleh berubah mengikut keperluan senario, bukan sekadar mahu menang.


  • Feedback

    • Buka ruang untuk persoalan atau maklum balas.

    • Mestilah quick to respond.

    • Komunikasi adalah dua hala; jika satu pihak sahaja, itu adalah pengumuman.


  • Tindakan

    • Mesti ada tindakan susulan selepas berkomunikasi.

    • Sama ada terus laksanakan hasil perbincangan atau tunda ke mesyuarat seterusnya.

    • Setkan tindakan yang jelas.


Harap ciri-ciri yang dah describe dekat atas ni dapat membantu kita semua berkomunikasi dengan lebih berkesan.
Labels:

Comments

Post a Comment

Popular posts from this blog

🗑️ Clear storage Mac OS

  🗑️ Clear storage Mac OS 1: Clear system cache: Go to Finder > Go > Go to Folder, then type in "~/Library/Caches" and hit enter. Select all the folders inside the Caches folder and delete them. 2: Clear system logs: Go to Finder > Go > Go to Folder, then type in "/var/log" and hit enter. Select all the files inside the Log folder and delete them. 3: Remove unused language files: Go to Finder > Go > Go to Folder, then type in "/Library/Languages" and hit enter. Delete all the language folders you don't need. 4: Uninstall unused apps: Go to the Applications folder and delete the apps you don't use. 5: Clean up system files: Use a system cleaning tool like CleanMyMac X to scan and remove unnecessary system files. 6: If you have npm installed, clear the caches once in a while with ‘sudo npm cache clean --force’ 7: If you have ionic projects, open the ‘.angular’ folder and delete the ‘cache’ folder inside it.
Post a Comment
Read more

Turning AIs Into Cavemen Is Actually A Good Idea

    Token limits have been the number 1 problem of vibecoding. Aside from high usage, vague prompting and inefficient context management are two key causes that contribute to this problem. Tokens are counted from two things, the user’s input and agent’s output. You can have the best prompt in the world, but if your AI puke a Shakespearean essay for each response, your token will reach its limit faster. Similarly, if your prompt is too long, your token usage will also skyrocket. Prompting Prompting seems easy enough, but the reality is, if you want quality output, the input must be of similar quality. Here are some tips you can try to achieve a better, token-efficient prompt. Stick to English language only Certain languages may use higher tokens. Switching between languages might not be a good idea. Sure you can control your input prompt, but the output may use more tokens. Extremely short input Do not use ‘please’ or ‘thank you’. Get rid of filler words. Straight to the point....
Post a Comment
Read more

Setup existing IONIC project in local

Setup existing IONIC project in local  Steps: clone git repo install ionic -  npm install -g @ionic/cli masuk folder repo project install npm dependencies -  npm install run ionic project -  ionic serve buka android studio / xcode -  ionic cap open $var  - $var = ‘android’ atau ‘ios’. ada dua je option, replace $var dgn dua option tu sync changes vscode & dkt android studio / xcode -  ionic cap sync good luck Common issues: dependency conflict check https://www.npmpeer.dev/ utk tengok version yg compatible try naikkan/turunkan version dependency yg keluar dkt error. tembak je sampai hilang error g radle issue try upgrade gradle. kalau tak boleh, try remove folder android & build semula e rror cocoapod make sure install xcode make sure install cocoapod error java  home not found utk mac, buka ~/.zshrc & masukkan chang es dkt VSC tak masuk android studio / xcode try ionic cap sync try quit & buka semula cordo va.variables.gradle no...
Post a Comment
Read more