Skip to main content

High Performance Organization: What sucks and what rocks!



Quick list of what organizations should be doing. I am a firm believer of action. I have gained tremendous amount of [atleast I'd like to think so :0)] a sense of urgency, if you will, when it comes to getting things done from my experience at sea. Getting going with things. Moving on to the next level. Shedding skin all the time. Well you get the point, I see.

What should a typical High Performance Organization be doing and what should it stop doing right away.

Stop doing the following:
  • Prolonged meetings
  • Endless discussions
  • Brainstorm sessions
  • Planning (Strategy, Future plans whatever that falls into some category where endless hours are wasted making some drawings that die almost immediately after the first presentation)
  • Debating
  • Talking about teams and teamwork (It's really dry)
  • Stop talking about best practices (They are best for the guy who wrote for his organization's success NOT yours)
  • Standards for performance and task oriented thinking

Ok this list can go on and on. What organizations should be doing is this...
  • Identify your change activists within your organizations.
  • Install change activists across your organization (its similar to instrumenting triggers within your software code to identify, signal and eventually fix the problems while staying in the learning mode). Its like sprinkling magic dust within your organization.
  • Ask for ideas, ask just about anyone. You'll be surprised how people from different layers think sincerely about the importance of the delicate ecosystem which we so ruthlessly crush down or even worse ignore.
  • Keep asking ideas and let the information flow.
  • Install tools (including people) in order to keep your intellectual property aboard. (And not outsourcing it like the latest trend).
  • Identify your intellectual property (people).
  • Start thinking aloud and let others think aloud too (Its that loud thought that will help you rediscover your fire!).
  • Let teams form themselves (you will be amazed how smart people are drawn to each others).
  • Encourage an open and collaborative climate.
  • Use project management tools that invoke that sense of collaborative thinking. I'm using basecamp from 37signals for a virtualization project and it really rocks!
  • Standards for excellence and merit oriented thinking. Award points to successful members and keep it free for all. Let people pick their performance and run with it. They will (and yes even the amazingly lazy ones) surprise you.
  • Rely on learning. Let people prove things. Let people demonstrate the cool things they built or hacked. Help use the learning to transform from drawings to demos to deployments!
  • Do a lot of whiteboard sessions and invite people to talk and paint their visions on the whiteboard (People like drawings and people like to draw too)
  • Help develop the sense of community: Your organization in like a village and it needs to be closely knit together.
  • Let everyone write the "sucks and rocks" about your organization (No harm in biting your tongue and knowing the truth than being held at ransom by the very same disgruntled people).
  • Excite yourself and others around you. We all need a bit of that adrenaline.
These and definitely a lot more of such radical practices will help you win back those creative employees (including yourself) back. There is a lot said about "High performance Organizations" and this was my contribution to what I think will certainly help put us all back from a typical "survival mode" to a more "happy kick ass mode".

Comments

Popular posts from this blog

Security: VMware Workstation 6 vulnerability

vulnerable software: VMware Workstation 6.0 for Windows, possible some other VMware products as well type of vulnerability: DoS, potential privilege escalation I found a vulnerability in VMware Workstation 6.0 which allows an unprivileged user in the host OS to crash the system and potentially run arbitrary code with kernel privileges. The issue is in the vmstor-60 driver, which is supposed to mount VMware images within the host OS. When sending the IOCTL code FsSetVoleInformation with subcode FsSetFileInformation with a large buffer and underreporting its size to at max 1024 bytes, it will underrun and potentially execute arbitrary code. Security focus

Splunk that!

Saw this advert on Slashdot and went on to look for it and found the tour pretty neat to look at. Check out the demo too! So why would I need it? WHY NOT? I'd say. As an organization grows , new services, new data comes by, new logs start accumulating on the servers and it becomes increasingly difficult to look at all those logs, leave alone that you'd have time to read them and who cares about analysis as the time to look for those log files already makes your day, isn't it? Well a solution like this is a cool option to have your sysadmins/operators look at ONE PLACE and thus you don't have your administrators lurking around in your physical servers and *accidentally* messing up things there. Go ahead and give it a shot by downloading it and testing it. I'll give it a shot myself! Ok so I went ahead and installed it. Do this... [root@tarrydev Software]# ./splunk-Server-1.0.1-linux-installer.bin to install and this (if you screw up) [root@tarrydev Software]# /op

Virtualization is hot and sexy!

If this does not convince you to virtualize, believe me, nothing will :-) As you will hear these gorgeous women mention VMware, Akkori, Pano Logic, Microsoft and VKernel. They forgot to mention rackspace ;-) virtualization girl video I'm convinced, aren't you? Check out their site as well!