Many of the laws you cite seem to be holdovers from the late '80s and '90s. (Who remembers Michael Douglas in Wall Street; and "Greed is good"?). Many of them seem to be aimed at 'succeeding' regardless of merit, rather than succeeding because of it.

I think this is one of (many) things that very much depends upon the environment in which you work. And that can depend upon the type of commercial entity you work for; the cultural norms of the country or people in charge; and much else besides. Having worked in several countries and for companies from different cultural areas (US -v- EU -v- UK -v- The Orient), I've found that some cultures just "want the job done, don't bore me with the details"; whilst other cultures want to be very much in on all the details.

For example, my (brief) experience of working for a Japanese company was that suppressing technical information in reports to upper management could be viewed as 'lying by omission', whereas including them in a report for US Managers was seen as "waffling". Conversely, when things went wrong in a US company, the immediate priority seemed to be "who's to blame", but in the Japanese company "what went wrong and how do we fix it".

Generalisations both I admit, but just an example.

There also seems to be a correlation between the size of the company and the management level to which technical details are seen as important. In general, the larger the company, the sooner the details get lost in the mire of interdepartmental protectionism.

The toughest decision I ever made was to contradict another consultant, from the same company I was representing, in a meeting in front of the customer. It did not go down well with the other consultant, but I was told that my intervention had saved the contract.

Sometimes, in some places, the technical details at the back of a report, and the honesty and accuracy of those details, is more important than the glossy cover and a flowery management summary.

Were it, that that were true more often.


Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
Lingua non convalesco, consenesco et abolesco. -- Rule 1 has a caveat! -- Who broke the cabal?
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.

In reply to Re: [OT]: Putt's Law and how to climb the information technology hierarchy ladder? by BrowserUk
in thread [OT]: Putt's Law and how to climb the information technology hierarchy ladder? by lin0

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.