In the following “What makes us feel good about our work” talk by Dan Ariely, there are few points worth contemplating:
Click Here to listen to this post:
Acknowledgement is critical, and should be exercised as much as possible. Even the simplest one, like saying “Aha”, when your team member hands you over, their report, is powerful. If you want your team be as twice as productive as they are now, acknowledge them routinely. You don’t need to make up things; you do not need to exaggerate. Simply make sure you clearly show you got it – they did a job, they invested the effort, they desire feedback. If you can thank them, do it. At the end of the week, just before we all go home, I thank each one of my team members, from the bottom of my heart, for the effort they have put during the week. It does not matter how many successes they had, it is all about the time, effort and good will they have put into their work. That way they go off to their weekend, charged with good feeling.
Indeed tossing away an effort people put, is a major energy drainer. However ignoring people’s effort is putting them down, almost the same as shredding their effort in front of their eyes. That’s just to stress how much acknowledgement is important. And there is something else. When you do have to stop a project, cancel a work done, make sure you put enough energy beyond explaining why this need to be done. Make sure you acknowledge the effort put so far. People could reach 150% productivity, if you do your best to preserve their efforts, and it does not matter how much you pay them. So thank them and do the most to make use with what they built so far. Make sure this effort is communicated clearly. All this will put more fuel into your team’s emotion al engines, as they take your ship to a new destination.
It doesn’t matter how much you pay people, if you don’t acknowledge their effort. You can raise a salary once in a while, and still it would not matter as much as a much more frequent acknowledgement of people’s efforts.
If you have an advice to give or feedback to improve one’s performance, they are still considered an acknowledgement and worth more than silence. Acknowledging people does not mean you should forget about mentoring and guiding.
We value our creations much more than evaluators do – because we appreciate more what we put effort into. Make sure you kindly address this gap, as you go through a performance evaluation with your team. Otherwise people will think your review of their performance is too critical.
In the past decades we had Industrial Efficiency govern our work methodology: we preferred everyone repeatedly does just part of the complete creation process of our solution. However now we are shifting into knowledge economy. Now everybody can decide how much effort they put into their work. Consequently success depends on your team’s willingness to invest more acquiring and purifying information. You don’t have the time, and sometimes you could even lack the means to properly measure the quality of the information, your team is creating. So you want them be emotionally motivated to invest the extra effort. Even if they must focus on a repetitive job, at least give them a prospective of its overall project, and an opportunity to speak out their advice, beyond their current role. This means you have to extend into the following areas. Note that each one of those deserves a whole article.
Meaning – Creating a powerful meaning or Context for the job to be done.
Creation – Let your team feel they own the creation of the solution.
Challenge – Take your team through challenges, so they can experience personal growth.
Ownership – Make sure your team see themselves as the source of everything that happens as they ship their solution.
Identity – Make sure your team can see themselves and their job as one.
Pride – Set the opportunities for your team to see the gradual progress they gain. Acknowledge them for their uniqueness and efforts.
As you watch the video, let me know if you see more that we should look into…
Note that both Backtrack and Kali Linux contain great tools such as Nessus and Metasploit, set for “labor-intensive” use. If you want it to automatically do the work for you, across many systems, through a workflow that will save you a LOT of time, you’ll have to pay for the “Professional” variations of those tools.
Amazon has finally released its Dropbox / Google Drive / SkyDrive “killer”
Click here to listen to this post:
It lets you save files to Amazon storage systems right on your Windows or Mac desktop, through a local folder that gets synced automatically.
The first 5GB of storage are free, and then you start paying.
It is separate from the usual Amazon S3 storage.
No sharing through links exists yet, but I expect it will be added in the future
Check the terms and conditions of use…looks like they allow Amazon disclose what you put there rather easily…
Another question that becomes prevalent is “How should we address the variety of cloud storage systems running all on our desktops?”
Stick to just one? (That’s my choice for now…)
Split across several?
Use Apps that consolidate all Cloud Drives into a single unit and get into the same risks which RAID 0 has (one disk is gone, and our data is a mess…)
All this tightly coupled web accessible, cloud based, desktop integrated content highlights a relevant security risk factor: Attacks which could penetrate through one end (say through web URL exploitation tactics) and end up much easier in the other side (desktop or other user’s desktops).
Amazon Cloud Drive is a 61.8MB download (!) and you can get it right here: