In response to my recent plugging of my daughter’s nascent contract programming business and my reference to the POTUS’ Twittering support of his own daughter’s business to justify it, a long time subscriber and correspondent wrote, “I am SICK TO DEATH of the politicization of EVERYTHING. Strike two, I unsubscribe next time.”

Huh. I thought I’d indulged in nothing more than a harmless wisecrack, and in fact, unlike various recent Oscar winners, I’ve restrained myself from political commentary in KJR in spite of near-daily temptations.

And, let me cast my vote in the same direction: I’m also sick to death of the politicization of everything, although I doubt my correspondent and I mean the same thing when we say it.

Which brings us to this week’s anti-politicized topic: dealing with politicization in the organization you work in.

But first, let’s be clear about what “politicized” means.

At the easiest-to-deal-with level, politicization means talking about politics in the office. It’s easy to deal with because given the current public political climate it’s an awful idea. Nothing good can come from it … no one will persuade anyone who isn’t already on their side of a given issue and there’s no need to persuade someone who already is.

Either way the most likely outcome of a political conversation is inflammation for all conversing parties, who all also risk damaging their personal relationships with the each other party in the bargain.

At the next level, politicization is a synonym for tribalism: Dividing the world into us and them and viewing them, not as opponents, but as enemies. In the public sphere this is what has made our political climate so toxic. In the enterprise it’s one of the root causes of organizational silos with high walls and minimal collaboration.

Worse is that tribalism almost invariably escalates, as each side views hostile behavior on the other’s part through a magnifying lens, calling for an even-more amplified response.

It’s my impression that silo-driven attitudes and behavior are, as a broad trend, becoming worse in most enterprises, although, as there is no good measure of organizational silo height I can’t prove the point. Nonetheless, whatever the trend line, politicized organizations in this sense of the word handicap themselves when competing with their more cognitive counterparts.

But not as badly as organizations that take politicization to the next level. Call it political epistemology.

Epistemology — the study of what it means to “know” something — is, in addition to being eye-glazingly opaque, quite frustrating to deal with. Peel the epistemological onion and you’ll reach two equally unsatisfying conclusions: (1) It is sensible to be more confident of some propositions than others, based on the comparative levels of evidence and logic in their favor. But (2) it isn’t sensible to be completely certain of any proposition, with the possible exception of the proposition that certainty isn’t possible.

Political epistemology is what happens when what to believe and how certain to be of it depends on an individual’s tribal inclinations.

Never mind public policy and how someone’s party affiliation shapes their beliefs about What Works. There are plenty of business examples right in front of you, from decisions about strategy, to IT’s choice of virtualization technology, to which PaaS provider is best, and whether to deploy its technology stack inside the corporate firewall or to contract for external hosting.

No, no, no, no, no. I’m not saying Democrats favor private clouds while Republicans prefer public ones. Among the metaphorical breakdowns here: Businesses tend to have more than just two major metaphorical political parties. Heck, IT tends to have more than just two, with many IT professionals enjoying at least dual citizenship besides, with such fracture lines as Windows vs Linux, COTS (commercial off-the-shelf) vs open source, Waterfall vs Agile, and Engineering-and-Architecture vs Management-and-Finance.

The hazard doesn’t come from individuals having these inclinations. They’re natural and probably inevitable.

No, the hazard comes from the close-minded certainty that starts with “my tribe is good, my tribe’s allies are good enough, and every other tribe is deluded and evil” and finishes with the by now commonplace phrase “confirmation bias,” which means, if you’re among the uninitiated, that people uncritically accept any and all inputs that affirm their pre-existing beliefs while nit-picking to death anything that appears to contradict them.

Is Keep the Joint Running becoming politicized? As the poet Robert Burns wrote,

O wad some Power the giftie gie us
To see oursels as ithers see us!
It wad frae mony a blunder free us,
An’ foolish notion

Which is to say, you’ll have to tell me.

This week we have a guest columnist — KJR’s own web developer, Kimberly Lewis:

This is a follow up to last week’s column, to explain my biggest issue in web dev — one businesses that want successful web projects should be aware of:

Spend more, not less, on software.

Yep, I’m talking about everyone’s least favorite add-on cost. And I’m going to say something other open-source devs (I am one) will probably dislike.

Free isn’t always better

In fact, IS Survivor was a great test case of exactly why you want to pay extra for certain things. I paid for an inexpensive WordPress theme. (For those unacquainted with WordPress, themes are what control the look and functionality of your site, and they come at various price points.) I started with free themes. Six different ones, to be exact. The problem with free is that you get amateurish design, and worse functionality and configurability.

While I can deal with not-so-great design, I can’t put up with bad functionality and overly limited configurability. While I could consider going in and writing custom code within the theme by making what’s called a “Child Theme,” that would add weeks of concentrated work onto the job, and therefore a serious added cost.

Long term, a premium theme would be a better option. Now it’s just a matter of determining price point.

I like some of the more expensive themes. Why? Out of the box they have a great layout, lots of added functionality and customization, and plenty of extra support for when things don’t go according to plan. In my opinion, it’s worth it to prevent some extra costs.

Here is where I drag my father on his own website like the cheeky little brat of a daughter I don’t mind being. My dad is nothing if not cheap. He really, really didn’t want a premium theme. We compromised on an inexpensive but not free theme that fit the previous site’s look and feel, had the customization I wanted, but, due to the low cost, lacked a lot of the extra functionality I would have had with a higher end theme.

We’ve been paying for the decision ever since.

The limited functionality, combined with my father’s preference for displaying the entire post in full on the home page, resulted in immediate problems displaying archive and search results. My choices: either plugins, or adding a half-dozen additional pages of code into the theme. (Once again, for non-WordPress developers, a plugin is a software add-on I can install for added functionality without coding.)

This led to me trying 25 (yes, this is accurate. I kept track) different plugins for the archive list. I got refunds for 10, and all but one was incapable of handling the sheer number of columns in the archive. I’ll give Dad credit: He’s a persistent and voluminous writer.

In this case, free was the only choice — literally the only one that wasn’t breaking. Unfortunately, it’s ugly. Sorry. Not much I can do about that.

Search was the bigger problem. We started with a free trial for the best search engine on the market: Algolia Search. It’s good. It’s really good. It’s also horrifically expensive, but I’d hoped we could get away with the free version.

For the same reasons as the archive plugin, we can’t. And paying for it on a smaller site like IS Survivor is like taking out a mosquito with a thermonuclear bomb (although I’m originally from Minnesota, so I understand the temptation): too much power, too much cost for a site this small.

So now we have a dilemma. Do I go ahead and find a free search plugin, or do I use a paid plugin?

The pros of a paid plugin are, once again, customization, support, clean integration, and no ads. Yes, often you get ads on something if you don’t pay for it.

The cons of the free ones are lack of clean integration (Google Search WP, I’m looking at you), less customization, no support except from other users, many of whom have hacked the living daylights out of the plugin, and often compromised functionality.

This is a matter of cost vs. worth, and it goes all the way back to the decision to purchase an inexpensive theme.

If we’d gone with a premium theme that out of the box had everything we needed, but was also much more expensive, we’d have ended up spending exactly the same as we’re paying now. This is what businesses have to think about. Sometimes free or inexpensive will do the job. That’s great. But in case it doesn’t, be prepared to pay more than you were planning on to fix the problems “excessive frugality” can cause.

If you’re curious: I bought a single use license for a search engine plugin. Hope you like the result.