The system was fine. Nobody fucking used it.

I have built systems at previous jobs that people did not use. Good systems, in my judgment. Useful systems. They sat there while the same people kept doing the same shit that prompted the project.

Some of that was laziness. I am not turning the memory into a tender parable in which every ignored responsibility was secretly a request for another workshop. Sometimes people did not want to bother, and the company tolerated it.

What stayed with me was how little the completed project had to do with the work actually happening.

The demonstration has perfect employees

A demo contains a cooperative person, a clean example and a sequence followed in the right order. Of course it works. Even a haunted house behaves during the property inspection.

Then the system meets Tuesday. Somebody forgets. Somebody refuses. Somebody has a legitimate competing priority. The tidy sequence turns into an argument about whose responsibility the missing step was. The business owns a capability it is not consistently capable of using.

That gap is not a minor implementation detail. It is the difference between an asset and an expensive account nobody logs into. Yet installation can still receive more attention than participation, because installation has a date and a vendor can call it complete.

The organization wants the announcement

There is a kind of corporate enthusiasm reserved for the moment before behavior has to change. The launch is exciting. The ordinary repetition afterward is less photogenic.

A company can demand a better process and continue rewarding the habits that undermine it. The staff learns which version of the instruction matters. Eventually the new system becomes optional in practice while remaining essential in the presentation.

Everyone gets to say the company invested. The people responsible for the work get to explain why the investment is not producing the promised result. Another neat distribution of credit and consequence.

Being right did not make it happen

As a designer, I cannot ignore the effort a system demands from the humans using it. As someone who has watched those humans ignore useful work, I refuse to pretend interface design explains every failure to participate.

Both realities are annoying. Neither disappears because the other is true. A better experience can remove unnecessary effort; it cannot manufacture commitment wherever the organization has decided neglect carries no consequence.

This is what the effortless-success pitch leaves out. Actual people are involved, including people who will not do the part everyone agreed they would do. The system is purchased once. The behavior has to happen again tomorrow.

A completed project can be a beautiful object. It can also be a monument to the meeting where everyone said they were on board.