Misled

Posted by

(Disclaimer – though I do not and will not disclose identities or venues in what follows, I must say I am not writing about anything at HCL’s Products and Platforms division where I work at this writing.  Indeed, we have taken lessons learned like those which follow and get it right now.)

The most arrogant statement I have ever heard at work was spoken at a meeting where technical leaders were promoting their chosen career path for others to follow.  The group of software architects were leaders over hundreds of people and the primary technical counsel for upper management.  It was the “Don’t you want to be a technical leader like us?” meeting.  The following paraphrased dialog provided the context:

Q: Do you miss writing code, creating components that are part of a commercial offering?

A: No, I’d rather program the company (that is, the projects and people).

I didn’t take notice of the overall reaction in the room, but my stomach turned.

The leader in question has never to my knowledge conceived of or delivered any product that both shipped and was a commercial success.  So, no thanks, not being programmed by him/her.

Another technical leader I knew who could have been up there in front of people on the platform asked what I had thought of the meeting.

I answered: “I could see no one I wanted to be like,” and left it at that.  I was being nice.

The saddest part of this event and ones like it was that these people were trusted with so much power to direct the work of the masses.  They misled us all.

It’s very easy and often with compromised motives to criticize the way one has been led.  Or the way an entire organization has been led.  Because it is invariable that misleading has occurred.  But also I have found if I don’t learn from how I’ve been misled into expensive and laborious debacles, I will only be misled again.  Of course, this requires some discernment, because it’s so easy to simply be critical as an emotional vent.

What I offer is a set of bad motivations and warning signs for project initiation/execution and overall direction in the software field.  You can and should adapt it to whatever field of endeavor in which you operate:

  1. Marketing driven-ness – I didn’t say “Market” but “Marketing”. Given decent sales and marketing capabilities, the danger is to allow those capabilities devise ice cubes for Eskimos.  Or find new shades of swine lip gloss.  I love my friends in marketing, but I also know their mantras (like “perception is all that matters”) are inaccurate and harmful if taken as real direction.  Real value-based vision can be so rare that accounts of a company’s product history can be simply a hit parade of pretty marketing collateral – with nothing that was real or successful.
  2. Exaggerated or useless innovation – People love their babies. I get it; I’m the same way.  But when a creation and the creative process itself get over-promoted, the dearth of value can nest and the unwise expenditure of resources spiral.
  3. New technology – An addiction to new technologies simply because they are, well, new is a bad sign. Despite generating all manner of academic writ and discussion and giving fodder for every new generation to crow its superiority, 80-90% of new technology dies in 5 years.  It’s sound practice to use componentry that’s at least that old in building solutions.
  4. Bloat – In practice, this is mostly attitudinal. The danger gets worse with one’s promotion up the reporting chain.  Extravagance masquerades as need.  Resistance to increases in expense is touted as lack of commitment.  Thrift is for those restricted by small ideas.  No, bloat is pure hubris.  Pop that balloon wherever it flies.
  5. Tribalism – Identified by lack of consulting or failing to learn the lessons of other groups, a fledgling effort that walls off its communications with an air of superiority, particularly accompanied by:
  6. Grandiose claims – There’s nothing wrong and everything right about being enthusiastic about one’s work and newly discovered technology, but if/when it is promoted as that which shifts paradigms or overthrows kingdoms, beware of the coming waste of resources. Most real breakthroughs are achieved through healthy skepticism and hard, thorough rigor, with step-wise affirmation and verification.  It may sound like advancements are only achieved by depressed people, but I’d replace “depressed” with “sober” (in the emotional sense).
  7. Standards compliance – When standards matter, everyone knows; their  usefulness and widespread use is the source of little debate.  But everyone should also know when there’s a force-fit, and the work to comply with standards that don’t matter is often a huge waste.

The most disturbing part about being misled is when one realizes the driving motives of those in leadership.  They tend to be infantile – winning the playpen argument and getting the coveted toy is the goal.  And getting the playmate to cry and be banished – outright schadenfreude – was equally motivational.

Image result for bad direction royalty free

That’s tragic because nobody would denigrate the abilities of those leaders or duped managers who followed their lead – to the person they were and are remarkably gifted.

By no means am I suggest market success is the only measure of value in this field or any other – lessons learned provide wisdom to which all knowledge should be subordinate.  And staying up to date in one’s field of endeavor is vital because there truly is useful, disruptive innovation that happens, and it changes the playing field.

But let’s stop being misled; it’s not that hard to see when it happens, so as for me and anyone reading this, let’s learn, ok?

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s