Contact US

Log In

Come Join Us!

Are you an
Engineering professional?
Join Eng-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Eng-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

BNET..... read alongside Dilbert,,.....

BNET..... read alongside Dilbert,,.....

BNET..... read alongside Dilbert,,.....

I stumbled across BNET some months ago and it is nice to know that it isn't me that's out of kilter.
The latest discovery there is "The 8 STupidist Management Fads of all time".
I was keen to see if "Matrix Management" featured and it does....
But don't stop there, browse and enjoy.
I can't help think engineers are the one group of employees most at risk from management stupidities so anything that helps us survive has to be good.   



RE: BNET..... read alongside Dilbert,,.....

Some pretty good stuff there, JMW.

RE: BNET..... read alongside Dilbert,,.....

I've seen a number of those.

RE: BNET..... read alongside Dilbert,,.....



...there's no idea so excellent that it can't be transformed into crap by a bad manager.
How true.

But he hits a seem of pure gold in his five dumbest management concepts with the one about HR
Number 5 - likening business to warfare... must be the source for a current really really irritating TV ad where some twit (replace I with another vowel if you like) says "Business is warfare and I'm a General."



RE: BNET..... read alongside Dilbert,,.....

Wow, these links and subequent links are perfect for those 30 minute status calls that last 2 hours.

RE: BNET..... read alongside Dilbert,,.....

The HR rant is good.

As a new graduate, HR feel like your bosses and protectors.  The managers you actually work for don't.  As time moves on, so does the balance.  As you get older, wiser and greyer, HR starts looking like a trivial function, with transient staff all looking up the tree for their next job.

- Steve

RE: BNET..... read alongside Dilbert,,.....

Yes, NIH has to be a top killer but there are few others:
RTFM<br>Read The F***g Manual<br>The great tendency of manufacturers to produce lengthy complex manuals no one reads except to find the phone number for sales - so they can get free help from sales. If they call service they'll expect to charge for any help.<br>The great change in Europe was the requirement to publish any and all manuals in all the community languages. The translation costs have resulted in greatly simplified, too greatly simplified text and lots of cartoon illustrations.
One reason for complex manuals is the OSFA (One Size Fits All) approach to manufacturing. Clients ideal is a custom design that exactly meets their unique requirements. Manufacturing want to make just one item with absolutely no variants and sell it to everyone no matter how well or not it meets any one clients needs. <br>Somewhere in the middle we get the compromise design e.g. a master software suite that handles all possible applications. This requires a manual that describes all 307 possible applications and the client only wants one.
Net result is the client may read just enough to get the thing working after a fashion but never gets it working as well as it should and concludes it is a piece of s**t. Next time buys something else.



RE: BNET..... read alongside Dilbert,,.....


   Manuals are a tough call.  The problem is that one person designs the system, and another person writes the instructions.  

   Imagine you are working on a new pickup truck and you are documenting the process for tuning it up.  You write up on how to get the truck onto a hoist, how to raise the truck, remove the suspension, the exhaust manifold and the engine bolts.  You describe how to lower the hoist, how to winch the engine out of the block, remove the water pump, and access and change the spark plugs.  If you are the technical writer, you do this.  If you are the designer, you fix the design and ensure that the spark plugs are accessible.  

   A software guy once told me that the trick to writing software is to write the manual first.  This concept is more difficult with mechanical hardware, but in my opinion, it is not impossible.  It is just so hard to persuade people.   


RE: BNET..... read alongside Dilbert,,.....

I like to leave the manual writing to a real user, someone with direct customer contact (I write engineering software).  The appendices are my territory.

- Steve

RE: BNET..... read alongside Dilbert,,.....

" A software guy once told me that the trick to writing software is to write the manual first. "

Tried that.  But if the software designer doesn't read the manual you've written...

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Eng-Tips Forums free from inappropriate posts.
The Eng-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Eng-Tips forums is a member-only feature.

Click Here to join Eng-Tips and talk with other members! Already a Member? Login


Close Box

Join Eng-Tips® Today!

Join your peers on the Internet's largest technical engineering professional community.
It's easy to join and it's free.

Here's Why Members Love Eng-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close