Data Center is our focus

We help to build, access and manage your datacenter and server rooms

Structure Cabling

We help structure your cabling, Fiber Optic, UTP, STP and Electrical.

Get ready to the #Cloud

Start your Hyper Converged Infrastructure.

Monitor your infrastructures

Monitor your hardware, software, network (ITOM), maintain your ITSM service .

Our Great People

Great team to support happy customers.

Wednesday, February 13, 2013

Monitoring proses backup Anda via email

Monitoring backups is getting more and more complicated for service companies with many customers as well as for companies which care for their own network only: there are many kinds of different backup solutions, the amount of data rises, etc.
Not only in big companies, even in small or medium-sized companies the kinds of backup solutions rather vary; there are backups in the area of virtualization, backups of the operating system, tape backup, online backups, etc . With these various options it is difficult to keep track on all of your backups.
PRTG offers a solution to this: A specific IMAP sensor enables you to display all backup jobs at a glance and indicates if they succeeded or not.
Almost every backup software (for example, Symantec, Acronis, Norton, Genie, Backup Exec, Veeam, CA ARCserve, and many other) can send email notifications to inform you about the status of your last backups. PRTG will analyze these emails for you and keep track of all your backup jobs.

Memonitor Packet Delay untuk meningkatkan kualitas VoIP dengan PRTG


For interactive real-time applications such as VoIP, packet delay can be a serious issue. With PRTGNetwork Monitor, you can monitor quality of service parameters like packet delay, packet loss, duplicate packets and network latency and take the appropriate steps to improve VoIP quality.

How Does Packet Delay Affect VoIP Quality?

In contrast to normal telephone service, which is based on a circuit-switching technology, VoIP telephony uses packet switching for transmitting voice messages. This means that messages are divided into packets before they are sent. Some of these packets might be delayed or even lost, which can lead to poor voice quality or noise.
packet delay

What Is Packet Delay?

Packet delay is the amount of time it takes for a packet to travel from end to end. So a certain packet delay is perfectly normal. If the delay is rather short (for good voice quality, end-to-end packet delay should not be bigger than 150 ms) and constant, VoIP quality is not affected. VoIP quality is adversely affected when a considerable packet delay variation occurs, i.e. some packets arrive much later than the rest. Packet delay variation is often called jitter and can cause echo in VoIP calls. Packet delay depends on many different factors, among others the underlying network and available net bandwidth.

PRTG Network Monitor

PRTG Network Monitor has a dedicated QoS sensor, which works by sending UDP packets between two remote probes. This means that you can test any network connection in your network by simply placing a remote probe on (or near) each "end" of the connection and measuring the connection quality between them. If the network monitor detects a problem, the administrator is notified immediately and can react quickly and effectively. Thus PRTG is the perfect VoIP monitoring software as it finds network issues that can affect VoIP sound quality (packet delay, jitter, packet loss).
However, PRTG Network Monitor is far more than a VoIP monitoring manager. PRTG is a powerful bandwidth and availability monitoring solution which helps you to keep control of your network. It mainly uses the network management protocol SNMP, but also packet sniffing and supports the NetFlow / xFlow protocol and IP-SLA monitoring. PRTG is available as fully functional 30-day trial license and Freeware Edition, which is completely free for personal and commercial use. The Commercial Editions are required to monitor more than 10 sensors, with licenses starting at just $400 / €300.

Mengapa implementasi ITIL gagal ?

ITIL 'implementasi' - mengapa mereka gagal?

Salah satu masalah yang paling mendesak bahwa departemen TI menderita hari ini adalah bahwa mereka praktik terbaik implementasi tidak memberikan manfaat yang mereka harapkan. Banyak Organisasi telah berusaha untuk meningkatkan kinerja pelayanan mereka dengan menerapkan praktek ITIL terbaik.
Praktek manajemen sesi
Sebuah kesalahan mendasar dalam menerapkan praktek terbaik adalah percaya bahwa ITIL adalah peluru perak. Sayangnya, tidak ada peluru perak seperti itu tidak ada. Praktek terbaik hanya dapat dilaksanakan dengan berhasil oleh adopsi prinsip-prinsip sepenuh hati dari bagian paling atas. Tantangan yang paling departemen TI wajah, adalah bahwa ada terlalu banyak pekerjaan dalam pekerjaan untuk memungkinkan perbaikan yang akan diadopsi berhasil. Perbaikan membutuhkan waktu, energi, usaha dan sejumlah dedikasi dari semua staf. Dalam rangka untuk memastikan bahwa tim memiliki waktu untuk melakukan perbaikan, manajer, di masa lalu, telah mengambil langkah mempekerjakan tenaga kontrak untuk mengambil pekerjaan perbaikan. Meskipun ini adalah kesalahan, dan akan telah ditunjukkan oleh tim seperti itu, hal itu setidaknya membuat upaya untuk menciptakan waktu untuk perbaikan yang akan dilakukan. Namun, staf kontrak harus digunakan untuk backfill staf yang ada untuk melaksanakan pekerjaan hari, meninggalkan staf yang ada untuk membuat perbaikan yang mereka tahu perlu terjadi.
Itu semua terdengar sangat sederhana, tetapi di mana Anda menemukan uang untuk menyewa staf kontrak untuk melaksanakan pekerjaan hari, di saat-saat diluruskan? Jadi opsi ini mungkin tidak tersedia, dan kita harus kembali ke dilema asli. Dihadapkan dengan permintaan yang signifikan untuk pendanaan, banyak manajer senior akan ragu-ragu tentang awal implementasi praktek terbaik, terutama karena reputasi dari kesuksesan mereka adalah miskin. Ini jadi bagaimana kita bisa membuat sebuah tongkat implementasi?
Ada beberapa elemen kunci untuk peningkatan praktek sukses terbaik:
- manajemen senior beli di
- Memahami apa yang ingin Anda capai
- Mengambil waktu Anda
- Memanfaatkan keahlian ketika Anda perlu
Harap dicatat, dalam daftar di atas tidak disebutkan kerangka tertentu, metodologi, atau standar. Semua implementasi praktek yang baik yang terbaik akan mengambil elemen dari kerangka kerja seperti ITIL, COBIT, CMM dan ISO / IEC 20000. Tidak ada satu standar atau kerangka kerja yang akan cocok untuk semua organisasi. Perbaikan yang diperlukan sepenuhnya ke tuntutan masing-masing departemen. Meskipun banyak orang akan memiliki hal-hal yang sama, ini tidak berarti bahwa satu ukuran cocok untuk semua.
Manajemen senior buy-in Untuk memenuhi tantangan untuk terus berhasil menjalankan pekerjaan hari, harus ada dukungan dari manajemen senior tim. Idealnya, ini harus pada tingkat tertinggi, Direktur IT atau CIO. Hanya dengan tingkat komitmen yang fokus akan dipertahankan. Inisiatif perbaikan sering jatuh di pinggir jalan setelah ledakan awal antusiasme. Setelah istirahat dengan rutin menjalankan lokakarya selesai, dan perbaikan perlu direalisasikan di tempat kerja, dan itu adalah pada titik ini bahwa dukungan dari tim manajemen senior sangat penting. Ini terlalu mudah bagi tekanan dari pekerjaan hari untuk didahulukan atas kebutuhan untuk perbaikan - dan itu adalah hanya manajer yang dapat mengambil keputusan tentang beban kerja prioritas.
Memahami apa yang ingin Anda capai Seringkali hasil akhir untuk perbaikan adalah tidak jelas - tim terhanyut dalam 'mari kita menerapkan praktek terbaik', tanpa memahami persis apa yang mereka ingin capai. Praktik terbaik bukanlah tujuan itu sendiri, atau tidak seharusnya. Apa yang diperlukan adalah pemahaman penuh tentang apa unsur-unsur praktek terbaik akan menguntungkan Bisnis. Penilaian kebutuhan bisnis harus dilakukan sebelum memutuskan di mana praktek-praktek terbaik perlu diterapkan.
Mengambil Proses mengubah waktu Anda membutuhkan waktu. Perubahan budaya membutuhkan waktu lebih lama lagi.
"Budaya tidak berubah karena kita keinginan untuk mengubahnya perubahan Budaya ketika organisasi berubah;. Budaya mencerminkan realitas orang yang bekerja bersama setiap hari."
Frances Hesselbein
Untuk mengubah hati dan pikiran dari staf mengambil dukungan manajemen dan pemahaman yang jelas tentang tujuan. Tidak ada perubahan dalam budaya organisasi dapat dicapai dengan cepat, tapi ini tidak berarti bahwa Anda tidak dapat mencapai beberapa menang cepat melalui perbaikan Anda. Beberapa menang cepat akan membantu perubahan terjadi - misalnya, meningkatkan meja layanan Anda, mendorong pengguna untuk terlibat dengan satu titik kontak. Ini semua akan membantu dengan mengubah cara Anda dan organisasi Anda bekerja sebagai sebuah tim. Terlalu sering kita mendengar berbicara tentang 'bisnis dan TI' sebagai entitas yang terpisah, jarang kita mendengar bahwa TI adalah bagian dari bisnis. Ini adalah salah satu perubahan paling signifikan dalam budaya yang perlu dicapai.
Memanfaatkan keahlian Semua ini adalah mudah, dan Anda selalu harus mengakui ketika bantuan dibutuhkan.
'Berikan saya kemampuan untuk menerima hal-hal tidak dapat mengubah, keberanian untuk mengubah hal-hal yang saya bisa; dan kebijaksanaan untuk mengetahui perbedaannya'
- Tambahkan ke ini 'dan kapan untuk mencari bantuan untuk mencapai mereka' dan Anda memiliki kasus untuk konsultasi. Dalam bentuk yang terbaik, konsultasi mendukung, mentor, mendidik dan memungkinkan perubahan. Pada terburuk, ini memberikan template hambar tanpa memahami bahwa satu ukuran tidak cocok untuk semua. IT Service Management praktek terbaik adalah semua tentang memahami persyaratan dari seluruh organisasi, dan perubahan mendorong untuk meningkatkan keseluruhan. Dengan cara ini usaha kami dapat menjadi lebih besar daripada jumlah bagian mereka, dengan tidak ada departemen yang lebih penting atau signifikansi lebih besar dari yang lain.
Keahlian konsultasi Benar mengakui hal ini, dan menyesuaikan pengalaman mereka untuk memenuhi kebutuhan organisasi, bekerja dengan klien untuk mencapai tujuan mereka. Jumlah pengalaman, konsultan Anda akan telah menemukan tantangan yang sama sebelumnya, tetapi mencari mereka yang mengajukan pertanyaan untuk memahami situasi Anda. Konsultasi yang baik mendorong dialog, memastikan bahwa Anda mendapatkan keuntungan dari seribu pengalaman, bukan pengalaman tunggal diterapkan seribu kali.
Jadi, apa yang harus Anda lakukan untuk memastikan perbaikan Anda tidak gagal dan memudar? Memahami alasan sebenarnya di balik kebutuhan untuk meningkatkan, pastikan manajemen Anda setuju dan mendukung alasan-alasan tersebut, mengakui hal itu tidak akan terjadi semalam dan rencana yang sesuai, dan pastikan Anda melibatkan bantuan yang tepat dan dukungan untuk mewujudkan tujuan Anda. Embed antusiasme Anda untuk perbaikan seluruh organisasi, bekerja dengan bisnis keseluruhan, bukan hanya IT dan menetapkan target yang realistis untuk apa yang Anda benar-benar membutuhkan. Gunakan ahli yang memahami kebutuhan untuk beradaptasi untuk kebutuhan Anda, dan Anda akan mencapai tujuan Anda.
Source: http://WEB-INF.prmob.net/views/ltr/article.jspx

Monday, February 11, 2013

Apasih IT360 ?

IT360 is an Integrated IT management solution by ManageEngine, designed to monitor and manage IT Infrastructure for Small/Medium/Large Enterprises. ManageEngine IT360 adds a Business context to monitoring IT Resources, thereby helping various stakeholders understand the impact of downtimes on the business.
An easy to use Web Console guides the user to monitor the availability and performance of the Network, Servers & Applications, Network Bandwidth and Storage devices. The in-built ITIL ready Service Desk helps reduce the complexity of workflows in production, thereby allowing an IT Administrator to run the IT Operations in an effective manner.


This document will give the ManageEngine™ IT360 best practices recommended for the optimum functioning.

This comprises of the following items,
  1. System Requirements
  2. Applications and Servers
  3. Networks
  4. Console
1. System Requirements          

The software and hardware requirements for the various editions of IT360 is available in the below link.
http://www.manageengine.com/it360/help/meitms/setup-meit360/system_requirements.html

2. Applications and Servers
  1. Increase data collection threads : Applications & Server module use a separate thread for every data collection of monitor, the default number of threads used is controlled by the respective schedulers specified in the <IT360_Home>/applications/working/conf/threads.conf . The default number of threads used for URL Sequence Monitoring is 5 and other monitors are 12.
    When the number of monitors is greater than 100, you can increase the data collection threads (default is 10) by editing the 'Data Collection' attribute in the file
    <IT360_Home>/applications/working/conf/threads.conf
    The 'Data Collection' thread value can be increased to a value ranging between 20 and 25.
    Similarly, when the number of URL Sequence monitors is large in the range of 100, you can increase the URL monitoring thread count by editing the 'URL Monitor' attribute to 20 – 25. However, the total number of threads including both URL monitor and other data collection threads must not exceed 40.
    Note: Increase in the 'Data Collection' thread will lead to slight increase in CPU usage.
  2. Increase number of connections in database connection pool : When the number of monitors is greater than 100, connection pool can be increased by editing the NON_TRANS_CONNECTIONS field in <IT360_Home>/applications/working/conf/database_params.conf
    The default value of 6 can be set to 90 percent of the number of data collection threads.
    Note: Increase in the 'Connection Pool’ will lead to slight increase in CPU usage.
  3. Downtime Scheduler : When you do not need monitoring to happen during specific time period for some monitors, you can achieve this using the option ‘Downtime Scheduler’ available under ‘Admin’ tab. Monitors configured for ‘Downtime Scheduler’ does not use the data collection thread during the specified period and allows other monitors to utilize the data collection threads and hence improves performance. 
  4. Poll Intervals : When performance polling is set only the availability and health check will happen at every polling event while other performance data will be collected only at the end of scheduled number of polls. This will reduce the load on the system when you want to monitor only health and availability. 
    This option is available under ‘Admin’ -> ‘Performance Polling’ where you can set the number of polls before collecting performance data for server monitors. We recommend having a Poll Interval of 10 minutes for every monitor and a performance poll value of 3.
  5. Increase JVM heap size : Memory tuning can be achieved by editing the following parameters in "wrapper.conf" file available under the directory <IT360_Home>/applications/working/conf
    • wrapper.java.initmemory – Initial Java Heap Size
    • wrapper.java.maxmemory – Maximum Java Heap size (Optimum recommended value is 1024)
  6. Network Availability check : When the IT360 Server is out of the network or is not connected to the network, the status of all the Monitors that are currently been monitored will be shown as 'Down'. You can avoid this by enabling the 'Check for Network Availability' option. When this option is enabled, IT360 will generate alerts for the unavailability of resources only if the specified host is reachable in the network. For example, let us assume that the system/host which runs the IT360 has been isolated from the network. Enable this option and specify a hostname in the network (preferably not the hostname where IT360 runs). Now, IT360 tries to ping that machine for its availability in the network. If not available, alerts are not generated and resources are not shown as down. 
    You can also specify the IP of your routers, gateways, etc., to check the system/host which runs the IT360 is present in the network.
  7. URL Availability check : When the IT360 is out of the network or if external proxy settings are not configured, the status of all the URLs that are currently been monitored will be shown as 'Down'. You can avoid this by enabling the 'Check URL Availability' option. 
    When this option is enabled, IT360 will generate alerts for the unavailability of URL only if the other specified URL is down. For example, let us assume that the system/host which runs the IT360 has been isolated from the network. Enable this option and specify another URL which is expected to be up always. Now, IT360 tries to monitor URL for its availability. If not available, alerts are not generated and URL is not shown as down. Further a mail is sent to the configured mail address intimating the same.
  8. Consecutive polls check : You can use this option to determine the number of consecutive polls the error exists before reporting the error to system. Consecutive polls count in 'Admin' -> Action / Alert Settings can be increased from default value of 1 to 2. So that alerts will be generated after two consecutive polls which would eradicate false alarms.
  9. It is recommended to use SNMP or WMI mode for monitoring Windows machine and SSH or Telnet for monitoring UNIX based machines. SSH should be of more use as it provides much more security over Telnet.
  10. Alerting on Monitor Polling problem :
    1. Connect to the IT360 Probe webconsole. Go to the Admin --> Servers & Applications --> Action / Alarm Settings link.
    2. In that page, select/check the "Monitor Error Mail" attribute and set a proper value for "consecutive polls before sending error" .
    3. We would suggest to set the value for "consecutive polls before sending error" >= 5. This is to avoid flooding of e-mail alerts.
    4. The e-mail alert notification will be send to e-mail address of the 'admin' user.
3. Networks
  1. Before Discovery : Network module relies on other communication protocols SNMP, WMI, Telnet, and SSH for classification and monitoring. So make sure the following two configurations are done before triggering discovery,
    • Configuring the relevant SNMP, WMI, and CLI credentials
    • Defining Device Templates
  2. Configuring Discovery Parameters : IT360 Network module pings the devices for discovery and further for determining availability, and 4 ping packets are sent by default. If there is network latency, it is possible that some devices are not discovered, or post discovery, they are not polled for status. This can be addressed by configuring few ping parameters.
    Steps to achieve this.
    1. From <IT360-Home>/networks/conf folder open the file ping.properties.
    2. Un-comment (remove the # symbol) against the timeout parameter and specify the ping timeout depending on the latency.
    3. Similarly, you can increase the number of ping retries by configuring the value for retries parameter. Make sure you un-comment this parameter too for the configuration to be effected.
    4. Save the changes to the file.
    5. IT360 service requires a restart when changes are made to this file. So,restart IT360 for the changes to be effected.
    Note: The above configuration is recommended only if there is latency.
  3.  Addressing SNMP Timeout Issue : The default SNMP query timeout to variables in a device is 5 seconds. If there is a delay in the agent response for some devices, you can globally increase the SNMP timeout as follows:
    1. From <IT360-Home>/networks/conf folder, open the file NmsProcessesBE.conf
    2. Look for the following default entry in this file:
      PROCESS com.adventnet.nms.poll.Collector
       ARGS POLL_OBJECTS_IN_MEMORY 25 POLL_JDBC true MAX_OIDS_IN_ONE_POLL 15 AUTHORIZATION true DATA_COLLECTION_QUERY_INTERVAL 120000             PASS_THRO_ALL_POLLING_OBJECTS true CLEAN_DATA_INTERVAL 999999
    3. Include the additional parameter DATA_COLLECTION_SNMP_TIMEOUT 15. Now the changed entry will be as shown below:
      PROCESS com.adventnet.nms.poll.Collector
      ARGS POLL_OBJECTS_IN_MEMORY 25 POLL_JDBC true MAX_OIDS_IN_ONE_POLL 15 AUTHORIZATION true DATA_COLLECTION_QUERY_INTERVAL 12000 PASS_THRO_ALL_POLLING_OBJECTS true CLEAN_DATA_INTERVAL 999999 DATA_COLLECTION_SNMP_TIMEOUT 15
    4. Save the changes and restart IT360 Service.
  4. SNMP Data-collection : By default, IT360 uses 12 threads for SNMP polling. The assumption is that each monitored device has a minuimum of 10 polled data (monitored resources such as cpu, memory, incoming traffic, out-going traffic, errors etc). Each Interface object has 11 polleddata which include RxTraffic, TxTraffic,Bandwidth Utilization, Errors, Discards etc. Depending on the number of polleddata, you can increase the number of datapoll threads. Steps to achieve this is given below
    • From <IT360-Home>/networks/conf folder, open the file threads.conf
    • Increase the value of datapoll threads from 12 to the required number of threads for SNMP polling.
    • Save changes and restart IT360 Service.
    • Following is a reference table to increase the number of threads:
    • Number of devices/interfaces
      Number of datapoll Threads
      Number of SNMP Polled Data
      Monitoring Interval
      Upto 500 device/ 5000 interfaces
      12 (default)
      Upto 50000
      15 mins
      Beyond the above numbers
      13 - 20
      More than 50000: Additional 1 thread for every 5000 polleddata.
      15 min
  5. Database Connection Pool : If the number of PolledData is over 50000, the number of non-transaction connections can be increased in the range of 7 to 10 (default being 6 connections). Here is how you configure,
    • From <IT360-Home>/networks/conf folder, open the file database_params.conf.
    • Increase the value of NON_TRANS_CONNECTIONS parameter to the required number.
    • Save changes and restart IT360 Service.
  6. Disabling Unnecessary Polling during scheduled maintenance : Whenever a maintenance is scheduled in the network for some devices, you can suspend polling for those devices by scheduling downtime in IT360 Admin --> Networks --> Downtime Scheduler. This prevents unnecessary requests to network resources resulting in false alerts. There will be improved performance as the devices covered in the scheduled do not use the data poll threads.
  7. Disabling polling for a category  : From Admin --> Networks --> Monitoring Intervals, remove selection for the category for which you want to disable polling.
  8. Specifying Polling Intervals for Devices : From Admin --> Networks --> Monitoring Intervals, configure a smaller monitoring interval for critical categories like servers or routers and space out for the other categories like printers etc. The recommended interval for very critical devices is 5 minutes, while you can set a minimum of 1 minute interval also for a very few devices.
  9. Device Dependencies : False alerts are triggered when a set of monitored devices are behind another device (a firewall, router etc). The requests sent to the devices are routed through the firewall or router, and in the event of these dependent devices being down, all devices behind this dependent devices are deemed as down. Configuring device dependencies will prevent
    unnecessary polling to the devices behind the dependent device.
  10. Increase JVM heap size : Memory tuning can be achieved by editing the following parameters in "wrapper.conf" file available under the directory <IT360_Home>/networks/conf
    • wrapper.java.initmemory – Initial Java Heap Size
    • wrapper.java.maxmemory – Maximum Java Heap size (Below 2.5K interfaces - 2048, 2.5K to 5K interfaces - 4096, 5K to 8K interfaces - 4096)
  11. Alerting on Datacollection Problem :
    1. Go to the <IT360 Home> etworksconf directory and take a backup of the NmsProcessesBE.conf file available in that directory in some other directory say C:
    2. Check for the "PROCESS     com.adventnet.nms.poll.Collector" in that file.
    3. The next line starts with "ARGS" and add the attribute "GENERATE_DATACOLL_EVENT true" at the end of that line. Once added that line will look like as given below.
      1. ARGS  POLL_OBJECTS_IN_MEMORY 25 POLL_JDBC true MAX_OIDS_IN_ONE_POLL 15 AUTHORIZATION true DATA_COLLECTION_QUERY_INTERVAL 120000 PASS_THRO_ALL_POLLING_OBJECTS true CLEAN_DATA_INTERVAL 999999 GENERATE_DATACOLL_EVENT true
    4. Save this file and restart the IT360 Probe service for the above change to take effect.
    5. Once re-started, as when there is a problem in datacollection occurs, a alert will be generated in the Networks module. The alert can be viewed under the 'Alarms' tab.
    6. One word of caution. If there is lot of SNMP timeout or SNMP related problems during the SNMP Datacollection, then there is a possibility that lot of alerts generated in the IT360 Probe service.
4. Console
  1. User Synch Interval from ActiveDirectory : The Synchornization interval for Import users from Active Directory should be set not less than one day if the number of users is high. The setting can be found under Admin --> General --> Active Directory --> Import users from Active Directory. 




11 Simple Concepts to Become a Better Leader


Being likeable will help you in your job, business, relationships, and life. I interviewed dozens of successful business leaders for my last book, to determine what made them so likeable and their companies so successful. All of the concepts are simple, and yet, perhaps in the name of revenues or the bottom line, we often lose sight of the simple things - things that not only make us human, but can actually help us become more successful. Below are the eleven most important principles to integrate to become a better leader:
1. Listening
"When people talk, listen completely. Most people never listen." - Ernest Hemingway
Listening is the foundation of any good relationship. Great leaders listen to what their customers and prospects want and need, and they listen to the challenges those customers face. They listen to colleagues and are open to new ideas. They listen to shareholders, investors, and competitors. Here's why the best CEO's listen more.
2. Storytelling
"Storytelling is the most powerful way to put ideas into the world today." -Robert McAfee Brown
After listening, leaders need to tell great stories in order to sell their products, but more important, in order to sell their ideas. Storytelling is what captivates people and drives them to take action. Whether you're telling a story to one prospect over lunch, a boardroom full of people, or thousands of people through an online video - storytelling wins customers.
3. Authenticity
"I had no idea that being your authentic self could make me as rich as I've become. If I had, I'd have done it a lot earlier." -Oprah Winfrey
Great leaders are who they say they are, and they have integrity beyond compare. Vulnerability and humility are hallmarks of the authentic leader and create a positive, attractive energy. Customers, employees, and media all want to help an authentic person to succeed. There used to be a divide between one’s public self and private self, but the social internet has blurred that line. Tomorrow's leaders are transparent about who they are online, merging their personal and professional lives together.
4. Transparency
"As a small businessperson, you have no greater leverage than the truth." -John Whittier
There is nowhere to hide anymore, and businesspeople who attempt to keep secrets will eventually be exposed. Openness and honesty lead to happier staff and customers and colleagues. More important, transparency makes it a lot easier to sleep at night - unworried about what you said to whom, a happier leader is a more productive one.
5. Team Playing
"Individuals play the game, but teams beat the odds." -SEAL Team Saying
No matter how small your organization, you interact with others every day. Letting others shine, encouraging innovative ideas, practicing humility, and following other rules for working in teams will help you become a more likeable leader. You’ll need a culture of success within your organization, one that includes out-of-the-box thinking.
6. Responsiveness
"Life is 10% what happens to you and 90% how you react to it." -Charles Swindoll
The best leaders are responsive to their customers, staff, investors, and prospects. Every stakeholder today is a potential viral sparkplug, for better or for worse, and the winning leader is one who recognizes this and insists upon a culture of responsiveness. Whether the communication is email, voice mail, a note or a a tweet, responding shows you care and gives your customers and colleagues a say, allowing them to make a positive impact on the organization.
7. Adaptability
"When you're finished changing, you're finished." -Ben Franklin
There has never been a faster-changing marketplace than the one we live in today. Leaders must be flexible in managing changing opportunities and challenges and nimble enough to pivot at the right moment. Stubbornness is no longer desirable to most organizations. Instead, humility and the willingness to adapt mark a great leader.
8. Passion
"The only way to do great work is to love the work you do." -Steve Jobs
Those who love what they do don’t have to work a day in their lives. People who are able to bring passion to their business have a remarkable advantage, as that passion is contagious to customers and colleagues alike. Finding and increasing your passion will absolutely affect your bottom line.
9. Surprise and Delight
"A true leader always keeps an element of surprise up his sleeve, which others cannot grasp but which keeps his public excited and breathless." -Charles de Gaulle
Most people like surprises in their day-to-day lives. Likeable leaders underpromise and overdeliver, assuring that customers and staff are surprised in a positive way. There are a plethora of ways to surprise without spending extra money - a smile, We all like to be delighted — surprise and delight create incredible word-of-mouth marketing opportunities.
10. Simplicity
"Less isn't more; just enough is more." -Milton Glaser
The world is more complex than ever before, and yet what customers often respond to best is simplicity — in design, form, and function. Taking complex projects, challenges, and ideas and distilling them to their simplest components allows customers, staff, and other stakeholders to better understand and buy into your vision. We humans all crave simplicity, and so today's leader must be focused and deliver simplicity.
11. Gratefulness
"I would maintain that thanks are the highest form of thought, and that gratitude is happiness doubled by wonder." -Gilbert Chesterton
Likeable leaders are ever grateful for the people who contribute to their opportunities and success. Being appreciative and saying thank you to mentors, customers, colleagues, and other stakeholders keeps leaders humble, appreciated, and well received. It also makes you feel great! Donor's Choose studied the value of a hand-written thank-you note, and actually found donors were 38% more likely to give a 2nd time if they got a hand-written note!
The Golden Rule: Above all else, treat others as you’d like to be treated
By showing others the same courtesy you expect from them, you will gain more respect from coworkers, customers, and business partners. Holding others in high regard demonstrates your company’s likeability and motivates others to work with you. This seems so simple, as do so many of these principles — and yet many people, too concerned with making money or getting by, fail to truly adopt these key concepts.
Which of these principles are most important to you — what makes you likeable?
Dave Kerpen is the New York Times bestselling author of two books, Likeable Social Mediaand Likeable Business.