|
Showing posts with label Management. Show all posts
Showing posts with label Management. Show all posts
Friday, December 9, 2011
Six Minutes to Management Excellence...
Via my mom:
Labels:
Humor,
Management
Monday, October 31, 2011
Motivation...
Via my colleague Aleck L.:
The video is new to me, though the studies it's reporting on are not. One of the big mysteries of managing engineers (or other knowledge workers, I'm sure) is how to motivate them to do what you want them to do.
Much of what this video articulates matches my own experiences – but there are motivations controllable by managements (some of them involving money) that my experience tells me actually do work. All of these involve two elements not explored by these studies: recognition (that is, letting peers – inside or outside the company – know what good thing you've accomplished) and spot cash (that is, cash bonuses awarded not according to some rules or formulae, but rather at the moment some good behavior needs to be rewarded). I've also seen the power of negative motivation. I once used a stuffed monkey with a dunce's cap as a motivational tool. Whenver someone did something dumb, they got the monkey – and it sat on their desk until the next person did something dumb. That damned monkey was one of the best tools I ever found for getting engineers to behave the way I wanted them to, and it was negative reinforcement. I'm pretty sure it only worked because the culture we had at that job was right for it, though...
The video is new to me, though the studies it's reporting on are not. One of the big mysteries of managing engineers (or other knowledge workers, I'm sure) is how to motivate them to do what you want them to do.
Much of what this video articulates matches my own experiences – but there are motivations controllable by managements (some of them involving money) that my experience tells me actually do work. All of these involve two elements not explored by these studies: recognition (that is, letting peers – inside or outside the company – know what good thing you've accomplished) and spot cash (that is, cash bonuses awarded not according to some rules or formulae, but rather at the moment some good behavior needs to be rewarded). I've also seen the power of negative motivation. I once used a stuffed monkey with a dunce's cap as a motivational tool. Whenver someone did something dumb, they got the monkey – and it sat on their desk until the next person did something dumb. That damned monkey was one of the best tools I ever found for getting engineers to behave the way I wanted them to, and it was negative reinforcement. I'm pretty sure it only worked because the culture we had at that job was right for it, though...
Labels:
Management,
Motivation
Saturday, September 17, 2011
Akin's Laws of Spacecraft Design...
Via reader Eric J., who points out that some of them are applicable to software design as well. I'll add that many of them are applicable to any kind of engineering – certainly any kind of engineering I've been involved with (electrical, software, optical, mechanical, thermal, and civil)...
Original source is Dr. David Akin of the University of Maryland.
- Engineering is done with numbers. Analysis without numbers is only an opinion.
- To design a spacecraft right takes an infinite amount of effort. This is why it's a good idea to design them to operate when some things are wrong.
- Design is an iterative process. The necessary number of iterations is one more than the number you have currently done. This is true at any point in time.
- Your best design efforts will inevitably wind up being useless in the final design. Learn to live with the disappointment.
- (Miller's Law) Three points determine a curve.
- (Mar's Law) Everything is linear if plotted log-log with a fat magic marker.
- At the start of any design effort, the person who most wants to be team leader is least likely to be capable of it.
- In nature, the optimum is almost always in the middle somewhere. Distrust assertions that the optimum is at an extreme point.
- Not having all the information you need is never a satisfactory excuse for not starting the analysis.
- When in doubt, estimate. In an emergency, guess. But be sure to go back and clean up the mess when the real numbers come along.
- Sometimes, the fastest way to get to the end is to throw everything out and start over.
- There is never a single right solution. There are always multiple wrong ones, though.
- Design is based on requirements. There's no justification for designing something one bit "better" than the requirements dictate.
- (Edison's Law) "Better" is the enemy of "good".
- (Shea's Law) The ability to improve a design occurs primarily at the interfaces. This is also the prime location for screwing it up.
- The previous people who did a similar analysis did not have a direct pipeline to the wisdom of the ages. There is therefore no reason to believe their analysis over yours. There is especially no reason to present their analysis as yours.
- The fact that an analysis appears in print has no relationship to the likelihood of its being correct.
- Past experience is excellent for providing a reality check. Too much reality can doom an otherwise worthwhile design, though.
- The odds are greatly against you being immensely smarter than everyone else in the field. If your analysis says your terminal velocity is twice the speed of light, you may have invented warp drive, but the chances are a lot better that you've screwed up.
- A bad design with a good presentation is doomed eventually. A good design with a bad presentation is doomed immediately.
- (Larrabee's Law) Half of everything you hear in a classroom is crap. Education is figuring out which half is which.
- When in doubt, document. (Documentation requirements will reach a maximum shortly after the termination of a program.)
- The schedule you develop will seem like a complete work of fiction up until the time your customer fires you for not meeting it.
- It's called a "Work Breakdown Structure" because the Work remaining will grow until you have a Breakdown, unless you enforce some Structure on it.
- (Bowden's Law) Following a testing failure, it's always possible to refine the analysis to show that you really had negative margins all along.
- (Montemerlo's Law) Don't do nuthin' dumb.
- (Varsi's Law) Schedules only move in one direction.
- (Ranger's Law) There ain't no such thing as a free launch.
- (von Tiesenhausen's Law of Program Management) To get an accurate estimate of final program requirements, multiply the initial time estimates by pi, and slide the decimal point on the cost estimates one place to the right.
- (von Tiesenhausen's Law of Engineering Design) If you want to have a maximum effect on the design of a new engineering system, learn to draw. Engineers always wind up designing the vehicle to look like the initial artist's concept.
- (Mo's Law of Evolutionary Development) You can't get to the moon by climbing successively taller trees.
- (Atkin's Law of Demonstrations) When the hardware is working perfectly, the really important visitors don't show up.
- Space is a completely unforgiving environment. If you screw up the engineering, somebody dies (and there's no partial credit because most of the analysis was right...)
Labels:
Engineering,
Management
Friday, February 11, 2011
The More Workers a Company Has...
It's an old business maxim, oft-repeated in the engineering world: the bigger your team is, the less productive each individual worker is. Everybody in the software business recognizes this as one of the fundamental challenges to scaling a software company. The company I'm working for is facing this very challenge right now, as we are growing very rapidly (and today we're packing to move into our new, much bigger building).
But I've never seen anyone seriously attempt to quantify this effect, until I read this post. Interesting stuff. And a little scary...
But I've never seen anyone seriously attempt to quantify this effect, until I read this post. Interesting stuff. And a little scary...
Labels:
Management
Wednesday, August 11, 2010
Those Were the Days...
There was a time, not so very long ago, when a boss or owner could speak his mind plainly to his employees. Shaun Usher at Letters of Note somehow found a collection of memos demonstrating this; they make fascinating reading. Here's one example from the collection:
Tiger Oil CompanyAwesome. I'm filled with envy for those earlier, more candid, less politically-correct times...
MEMORANDUM
Date: January 11, 1978
To: All Employees
From: Edward Mike Davis (Owner)
Subject: Idle Conversation
Idle conversation and gossip in this office among employees will result in immediate termination.
Don't talk about other people and other things in this office.
DO YOUR JOBS AND KEEP YOUR MOUTH SHUT!
Labels:
Management
Monday, May 31, 2010
Good Bosses Believe...
According to Robert Sutton, good bosses believe twelve things. Lots of ground truth here, I think...
Labels:
Management
Subscribe to:
Posts (Atom)