
Sign up to save your podcasts
Or


In this episode of Beneficial Intelligence, I discuss price transparency. In the U.S., a coronavirus test can cost $56 if you pay yourself, but $450 if your health insurance pays it. This lack of price transparency makes the U.S. healthcare system the most expensive in the world, costing the US 17% of GDP. Every other industrialized country is below 12%. There are now laws requiring hospitals to publish their prices, but they deliberately hide them from the search engines.
You see the same kind of price obfuscation with cloud vendors, who carefully charge separately for CPU, RAM, storage, network traffic, and make sure that one vendor's CPU is not equivalent to another vendor's CPU.
When you buy proprietary software, you have better price transparency, unless you sign up for one of the "unlimited" licenses the vendors are pushing. Open source has an initial cost of zero, but unless you go with a well-known and popular tool, the true cost can be hard to gauge.
When you are looking for IT products, avoid vendors who wilfully obfuscate their prices. If they are not willing to be honest about the cost, what else will they not be honest about? As a CIO or CTO, make sure your evaluation criteria for software also include price transparency.
Beneficial Intelligence is a weekly podcast with stories and pragmatic advice for CIOs, CTOs, and other IT leaders. To get in touch, please contact me at [email protected]
In this episode of Beneficial Intelligence, I discuss blaming the humans. It often happens that a system failure is attributed to fallible humans. In that way, you don't have to admit embarrassing shortcomings in your system.
A recently declassified report showed that a weapons officer blamed for accidentally firing a missile back in the 1980s was actually the victim of a system error. Boeing initially tried to pin the blame for the 737 MAX-8 crashes on pilot error. Last year, Citibank accidentally paid out $900 million instead of just the few million they intended. They blame a back employee, not the archaic bank system that allowed the error.
If we look only at the last link of an accident chain, we find a human. But behind the human error is a system that created the situation where the human could err. The Harpoon missile system was eventually fixed. The Boeing 737 flight control software was fixed. And Citibank is looking at a long-overdue replacement of their arcane backend systems.
As a CIO or CTO, you need to make sure your organization extracts maximum learning when something goes wrong. Check some of the post-mortem reports from unfortunate incidents. If the error is blamed on a human that should just have acted differently, the analysis has not reached the root cause.
Beneficial Intelligence is a weekly podcast with stories and pragmatic advice for CIOs, CTOs, and other IT leaders. To get in touch, please contact me at [email protected]
In this episode of Beneficial Intelligence, I discuss wasting money. The business always complains that IT is costing too much. That is because we are wasting so much money. We're on track for worldwide IT spending of about 4 trillion, and surveys show that at least 25% of that is wasted. That's one trillion dollars we waste.
IT organizations waste money in two ways: With what we build, and with what we run.
It's a time-honored tradition in IT to never retire an old system. We keep everything running forever, even though the business benefit has long since evaporated. We might suspect that a specific system is not providing business benefit. But we don't know if anybody might be using the system for something. So we keep it running. To address this kind of waste, have someone examine the system logs to find who uses the system. If you have an old system without proper instrumentation, you might need have your network people to look at the network traffic to identify unused or barely-used systems.
But old systems is only one way we waste money on the systems we are running. The new and much more efficient way to lose money running systems is to move something to the cloud. In the history of cloud computing, there has never ever once been a case where the cloud resource cost was less than anticipated. More often it is 50%, 100% or 200% larger than expected. Cloud pricing will charge you for CPU cycles, storage, data traffic, messages passed, API calls, and a million other things. Nobody is able to calculate all the costs, and there are always surprises. Your business case for moving something to the cloud needs to show a dramatic cost saving in order to justify the move.
It's bad enough we lose a lot of money running things. But the money we waste running things pales in comparison with the money we waste building things. If you are still running waterfall projects, you know that they will never build what the customer wants. Many agile IT organizations don't fare much better, because the business can't be bothered to pay attention to the biweekly demonstrations of new features. Only the few organizations where both IT and business is agile don't waste money building something nobody needs.
I've saved the largest money-waster for last: Unnecessarily building your own. IT organizations want to build systems. They don't want to buy systems. The reason is that the business always wants something changed, and if you have all of the code in your own repository, you can change anything you like. If you have a standard system, you will sometimes have to tell the business that something cannot be changed. Because of this, and because we don't calculate the business benefit of IT systems, we default to always building our own.
Building your own is correct for systems of differentiation and innovation where you can do things differently from your competition. But building your own accounting system because you want to accomodate a very specific kind of invoicing you have in your business will never pay off.
You can save some money by finding and retiring under-utilized systems. You can some some more by being very careful about doing lift-and-shift of existing systems to the cloud. You can save some more by getting the business on board with Agile. And you can really save money by not building your own.
------
Beneficial Intelligence is a weekly podcast with stories and pragmatic advice for CIOs, CTOs, and other IT leaders. To get in touch, please contact me at [email protected]
In this episode of Beneficial Intelligence, I discuss moving fast. Mark Zuckerberg is famous for saying "Move fast and break things." That was his way of communicating a preference for high speed, accepting high risk. It has become an unofficial motto of Silicon Valley, but Facebook now has billions of users and today have a different risk profile.
Elon Musk, on the other hand, moves fast and breaks things. He is launching SpaceX Starships as a furious pace, and the landings often end up in spectacular fireballs. He had one rocket blow up on landing in December, and another in February. This month, he managed to get one to land, only to blow up shortly after landing. But he is in a hurry, and he can afford to lose dozens of rockets.
As CIO or CTO, you also need to move fast. Speed is what the business most wants from IT, and what we are least able to deliver. If we don't deliver speed, the business will run crucial business processes in faulty spreadsheets, or swipe a credit card in an impulsive purchase of some cloud service. You want to know what the worst thing that could happen is. If nobody will get hurt, and you can handle the financial and reputational effects of failure, that risk is below your speed limit. And you need to move as close to your speed limit as you can.
------
Beneficial Intelligence is a weekly podcast with stories and pragmatic advice for CIOs, CTOs, and other IT leaders. To get in touch, please contact me at [email protected]
In this episode of Beneficial Intelligence, I discuss User Experience disasters. Danes consistently rank among the happiest people in the world, but I can tell you for sure that it is not the public sector IT we use that make us happy. We have a very expensive welfare state financed with very high taxes, but all that money does not buy us good user experience.
Good User Experience (UX) is not expensive, but it does require that you can put yourself in the user's place and that you talk to users. That is a separate IT specialty, and many teams try to do without it. It doesn't end well. Systems with bad UX do not deliver the expected business value, and sometimes are not used at all. A system that is functionally OK but that the users can't or won't use is known as a user experience disaster.
We have a web application for booking coronavirus testing here in Denmark. First you choose a site, then you chose a data, and then you are told there are no times available at that site on that date. If a UX professional had been involved, the site would simply show the first available time at all the testing centers near you. We now also have a coronavirus vaccination booking site. It is just as bad.
As CIO or CTO, some of the systems you are responsible for offer the users a bad experience. To find these, look at usage statistics. If you are not gathering usage, you need to start doing so. If systems are under-utilized, the cause is most often a UX issue. Sometimes it is easy to fix. Sometimes it is hard to fix. But IT systems that are not used provide zero business value.
------
Beneficial Intelligence is a weekly podcast with stories and pragmatic advice for CIOs, CTOs, and other IT leaders. To get in touch, please contact me at [email protected]
In this episode of Beneficial Intelligence, I discuss contingency plans. Texas was not prepared for the cold, and millions lost power. Amid furious finger-pointing, it turns out that none of the recommendations from the report after the last power outage have been implemented, and suggestions from the report after the outage in 1989 were not implemented either.
As millions of Texas turned up the heat in their uninsulated homes, demand surged. At the same time, wind turbines froze. Then the natural gas wells and pipelines froze. Then the rivers where the nuclear power plants take cooling water from froze. And finally the generators on the coal-powered plants froze. They could burn coal, but not generate electricity. You can built wind turbines that will run in the cold, and you can winterize other equipment with insulation and special winter-capable lubricants. But that is more expensive, and Texas decided to save that money.
The problem could have been solved if Texas could get energy from its neighbors, but it can't. The US power grid is divided into three parts: Eastern, Western, and Texas. They decided to go it alone but apparently decided to ignore the risk.
In all systems, including your IT systems, you can handle risks in two ways: You can reduce the probability of the event occurring, or you can reduce the impact when it occurs. For IT systems, we reduce the probability with redundancy. We have multiple power supplies, multiple internet connections, multiple servers, replicated databases, and mirrored disk drives. But we run into Texas-style problems when we believe the claims of vendors that their ingenious solutions have completely eliminated the risk. That leads to complacency where we do not create contingency plans for what to do if the event does happen.
Texas did not reduce the probability, and was not prepared for the impact. Don't be like Texas.
------
Beneficial Intelligence is a weekly podcast with stories and pragmatic advice for CIOs and other IT leaders. To get in touch, please contact me at [email protected]
In this episode of Beneficial Intelligence, I discuss risks and rewards. Humans are a successful species because we are good at calculating risks and rewards. Similarly, organizations are successful if they are good at calculating the risks they face and the rewards they can gain.
Different people have different risk profiles, and companies also have different appetite for risk. Industries like aerospace and pharmaceuticals face large consequences if something goes wrong and have a low risk tolerance. Hedge funds, on the other hand, takes big risks to reap large rewards.
It is easy to create incentives for building things fast and cheap, but it is harder to create incentives that reward quality. Most organizations don't bother with quality incentives and try to ensure quality through QA processes instead. As Boeing found out, even a strong safety culture does not protect against misaligned incentives.
As an IT leader at any level, it is your job to consider the impact of your incentive structure. If you can figure out a way to incentivize user friendliness, robustness and other quality metrics, you can create a successful IT organization. If you depend on QA processes to counterbalance powerful incentives to ship software, corners will be cut.
------
Beneficial Intelligence is a weekly podcast with stories and pragmatic advice for CIOs and other IT leaders. To get in touch, please contact me at [email protected]
In this episode of Beneficial Intelligence, I discuss doing the right thing. Google started out with a motto of "Don't be evil," but that has fallen by the wayside. Occasionally, employees remind Google of the old motto as when they forced Google to stop working on AI for the Pentagon. But they don't seem terribly committed, and their highly touted Ethical AI Team is falling apart after they fired the head researcher.
Amazon never promised not to be evil, and they are forcing their delivery drivers to do 10-hour graveyard shifts starting before sunrise and going until mid-day. They are trying to avoid tired drivers causing accidents by installing cameras and AI in the vans so the computer can detect when the worker is falling asleep behind the wheel and can wake him up.
Consulting giant McKinsey don't consider themselves evil either. They are just good at increasing profits for companies. While they claim no wrongdoing, they just settled a lawsuit paying $600 million for the advice they gave Purdue Pharma about aggressively encouraging doctors to over-prescribe opioids.
As a CIO, you're engaged in a war for talent. But you also need to meet your budget, implement hot new technologies like AI and maintain IT security. There is always an opportunity to cut a corner, roll out inadequately tested technology, or squeeze employees so you can hit your goals this quarter. But if you want to be able to attract and keep top IT talent, you need to do the right thing.
------
Beneficial Intelligence is a weekly podcast with stories and pragmatic advice for CIOs and other IT leaders. To get in touch, please contact me at [email protected]
In this episode of Beneficial Intelligence, I discuss amateurs and professionals. Recently, Gamestock shares have gone through the roof. That's because professionals were betting that the stock would fall, and amateur investors meeting on the internet decided to buy up all the stock they could. The amateurs seem to have won this battle, inflicting billions of dollars of losses on the professionals.
Amateurs also build IT systems, but in IT, the amateurs always lose. At JP Morgan, a trader built a model in Excel. He made a small error in his formula, made bad trades, and the bank lost $6 billion. In the UK health service, a coronavirus tracking system was built on an ancient version of Microsoft Excel, and people got ill and died because of bad contact tracing.
The amateurs build systems because they can do it faster than IT. They are faster because they have less testing, failure handling and other things professionals implement.
As the CIO, it is your job to establish a good collaboration between the IT amateurs in the business and the IT professionals in the IT department. Some systems you can safely let business users build themselves. Other systems need a bit of IT supervision to make sure they are tested and robust. And some systems are critical and should be left to the professionals.
------
Beneficial Intelligence is a weekly podcast with stories and pragmatic advice for CIOs and other IT leaders. To get in touch, please contact me at [email protected]
In this episode of Beneficial Intelligence, I discuss robustness. Robustness is a system's ability to keep running when parts of it are knocked out. This week we saw Parler, a social media platform used by Trump supporters, being taken out by their cloud provider Amazon. They did not have robustness.
The Pirate Bay, on the other hand, has robustness. Governments and big media companies have tried to put them out of business for two decades, and they are still up and running.
On-premise systems had a certain robustness built in - even if you got into an argument with your database vendor over licensing, your application would continue to run. But if you get into a dispute with a cloud vendor, your system can be terminated at any time.
As the CIO, you need to take a look at your systems list and determine which systems are the priority systems that are essential for your business to run. Then as your architects to verify that these systems are robust, and ask what it would take to move them to another platform. If you cannot easily take your application and your data elsewhere, you don't have robustness.
------
Beneficial Intelligence is a weekly podcast with stories and pragmatic advice for CIOs and other IT leaders. To get in touch, please contact me at [email protected]
From the publisher's feed