Most pressure to adopt a technology comes from the trend, a vendor, or your own excitement, not from a need you actually named.

There is a technology you are being pushed toward right now. A vendor is selling it, the board is asking about it, a competitor just announced it, or your own excitement is doing the pushing. The pressure feels like urgency, and urgency makes you want to move. But a great deal of technology gets adopted exactly this way, driven by the trend rather than a need, and ends up as expensive complexity that solves a problem you never actually had.

The reframe is this. Objectivity is not caution, and it is not saying no to everything new. It is judging a technology on whether it serves a need you can name without mentioning the technology at all. If you cannot state the problem without naming the tool, you are starting from the answer and working backwards, which is precisely how hype does your thinking for you. The real question is never "should we adopt this." It is "what do we actually need, and does this serve it."

If you cannot name the need without naming the tool, the trend is doing your thinking.

Objectivity is a skill, not a personality trait

The book defines this as the ability to stay neutral and unbiased when evaluating technology, putting the organization's real needs ahead of personal preference, industry hype, and vendor pressure, so you invest wisely rather than chase short-lived fads. It is what lets a leader resist the trend and still move early and confidently on the things that genuinely matter.

Starting from the need rather than the tool, judging it on evidence rather than momentum, and weighing the risk of adopting against the risk of not, is a method you can run on the technology you are being pushed toward. How to do it is what the course builds.