When the Pencil Was Enough

Several years ago a wonderful former colleague of mine told me the old story about NASA spending a fortune developing a pen that could write in zero gravity, while the simpler answer would have been to use a pencil. The story is not quite as clean as the legend suggests, but the lesson still holds today, just like it did when he told me in 2020.

Sometimes organisations or their technologists become so focused on building the clever answer that they forget to ask whether a simpler answer would solve the problem.

I see this all the time in technology. A business vertical has a problem. The process is slow, the data is messy, the team is frustrated, and decisions take too long. Then someone reaches for the sophisticated answer: an AI platform, a new system, an automation programme, a data lake, a dashboard suite, a transformation initiative. It sounds strategic. It sounds modern. It sounds like progress.

But often, the real answer is much simpler. The process may need to be removed, not automated. The data may not need a platform yet; it may need ownership. The dashboard problem may not be a reporting problem at all, but a definitions problem. The system may not be failing because it is old, but because nobody ever agreed how it should be used.

This is the danger of the space pen mindset. It makes sophistication look like intelligence. It rewards the impressive solution over the appropriate one. And in technology, that can become expensive very quickly.

The pencil is not always the right answer. Sometimes the space pen really is needed. Some problems require engineering, resilience, security, integration and scale. The point is not that simple is always better. The point is that simple should be considered first.

Good technology leadership is not about choosing the most advanced solution. It is about choosing the right level of solution for the problem in front of you. That requires diagnosis before design. What is actually broken? What outcome are we trying to create? What constraint are we working within? What is the simplest intervention that would materially improve the situation?

Those questions are not glamorous, but they are usually where the truth is. Many organisations do not suffer from a lack of technology. They suffer from too much complexity, poorly understood. Adding more tools, more platforms and more automation can easily make that worse.

If ownership is unclear, technology will not create accountability. If the process is badly designed, automation will simply make the bad process run faster. If nobody trusts the data, a new dashboard will not create trust. If the business has not made the decision, the system cannot make it on its behalf.

There is a strange pressure in leadership to make every answer sound transformative. Nobody wants to say, “we need to tidy this up.” They want to say, “we need a platform.” Nobody wants to say, “we need to agree the process.” They want to say, “we need automation.”

But often, the work that changes the business is not the work that sounds impressive. It is the work that removes friction, clarifies ownership, simplifies the workflow, standardises the data, stops unnecessary work, and fixes the basics before asking whether the bigger solution is still needed.

The best technologists are not the ones who always reach for the space pen. They are the ones confident enough to ask whether a pencil would do.