Consulting

Type 1 and Type 2 Consulting

I sat down to lambaste what I view as the outsourcing of thought by management teams, but then I got to thinking about NIHS (Not Invented Here Syndrome) in some organizations, and the (often concurrent) complete outsourcing of thought to consultants and hype mongers.

Where is the balance of internal capability and external expertise?

I think the scales get tipped one way or another by motivation. I’ve been brought onboard for two broad categories of needs. I don’t have names for these two groups, other than to say there are two of them.

Type 1 #

  • Temporarily fill capability gaps (development, security, infrastructure)
  • Provide an unbiased opinion (is our approach viable?)
  • Boost horsepower (new products and markets)
  • Train and mentor
  • App Rationalization (we have all these systems, they overlap in some places but fail to integrate in others)

Type 2 #

  • Provide plausible deniability (the consultants told us to do this thing we were probably going to do anyways)
  • Win arguments (appeals to authority)
  • Compliance or regulatory requirements (ISO 9001, SOC 2 Type 2, privacy laws, HIPAA)
  • Boost horsepower (tech debt logjams)
  • Keep the ship afloat (SRE, SysOps, Duct Tape)
  • Implement a hyped technology for marketing or shareholders (crypto, AI)
  • Fix outsourcing disasters (we found a company that would provide us developers for $40/hour, but communication has been bad and the system is faulty)

Continue reading →


Protect Others' Self Esteem

Nobody ever calls me because things are going well.

When the Outsiders arrive (consultant, contractor, new guy, whatever), they will be full of “best practices” and experiences codged from other, more fanciful clients. They look around, horrified, because they have a keen eye for the dysfunctional. I’ll be the first to admit, I see bad security, architecture, process, design, whatever it is - and my first reaction is an emotional one. Usually angry, usually self-righteous.

Continue reading →