We All Clicked “No” on Clippy. Most Trade Businesses Never Got Asked.

The assistant we loved to hate

“It looks like you’re writing a letter. Would you like help?”

If you were anywhere near a computer in the late 1990s, those words will bring back a very specific feeling. The source was Clippy — officially Clippit — the animated paperclip that arrived with Microsoft Office 97 and became one of the most recognisable pieces of software ever made.

Microsoft’s idea was ambitious. Build software that works out what you’re trying to do and offers help before you ask. That was a bold concept for the time.

The execution is where it came unstuck. Clippy interrupted people at exactly the wrong moment, and most of us dealt with it the same way. We clicked “No”. We hid him. Eventually, we turned him off.

Ahead of his time

Clippy has been the punchline of technology jokes for nearly thirty years, but the thinking behind him was sound.

Understand what the user is trying to achieve. Offer help in context. Cut down the complexity. Save people time.

The idea wasn’t the problem. The technology of the 1990s simply wasn’t capable of delivering on it. Clippy could recognise certain patterns and make some educated guesses, but he couldn’t really understand what you were trying to achieve.

The part that’s different now

Here’s why I’ve been thinking about a paperclip lately.

At least Clippy asked.

He was clumsy about it, but he put the offer in front of you. You looked at it, decided it wasn’t worth your time, and clicked “No”.

Whatever you think of that decision, it was a decision.

That’s not what I see in trade businesses.

I spend most of my working life inside job management systems, and the features sitting dormant in them weren’t rejected. They were never raised.

Nobody sat down, looked at the maintenance planner and concluded it wasn’t worth the setup.

Nobody weighed up digital forms against the paper process and chose paper.

The forms were mentioned once during implementation, three years ago, by someone who has since left.

There’s no moment where anyone said no.

There’s just a feature that’s been sitting there the whole time, paid for, switched off and completely invisible.

How it happens

It’s rarely anything dramatic.

Something gets left half-configured during setup because the go-live date is close and it isn’t critical. The intention is to come back to it. Nobody does, because there’s never a week where finishing an optional configuration is the most urgent thing on the list.

The person who understood why a field existed moves on. The knowledge leaves with them, so the team works around it rather than using it.

A feature gets trialled during the worst possible week — two techs off sick, a job going sideways — and quietly shelved.

Not rejected on its merits. Just dropped.

Or new functionality gets released, an email goes out about it, and it lands on a Tuesday when there’s a leak in Riccarton to deal with.

It’s not ignored so much as never read.

None of that is a failure of judgement. It’s just what happens in a busy business where the system doesn’t chase you and the job does.

Why it’s worth going back

Here’s what makes this different from Clippy.

When we turned Clippy off, we lost nothing, because he genuinely couldn’t help us.

Your job management system can.

It knows which job you’re on, what was quoted, what’s been ordered, who’s on site and what it cost. A system with that information can do genuinely useful work — if you let it.

One caveat, and it matters.

That only holds when the information going in is accurate.

Clippy failed because the technology couldn’t keep up with the ambition. Modern tools can fail for the opposite reason: the technology is ready and the data isn’t.

Feed a good system half-entered timesheets and materials coded to the wrong job, and it will hand that straight back to you — faster and with more confidence than it deserves.

A message to Clippy

Dear Clippy,
We’re sorry for all the times we clicked “No”.
We’re sorry for hiding you.
We’re sorry for turning you off.
You weren’t wrong. You were simply early.
At least you asked.

The question worth asking

Almost every trade business I work with is paying for capability it isn’t using.

Not because someone assessed it and passed.

Because it was never put in front of them properly.

So the question isn’t whether you should buy something new.

It’s this:

What’s sitting in your system right now that nobody has ever actually shown you?

If you can’t answer that, it’s worth finding out. You’ve already paid for it.

That’s a big part of what we do at e2e: finding the switched-off, half-configured and never-mentioned parts of a system and working out whether they could actually make life easier.

Sometimes the answer is no. That’s fine. At least it’s a decision.

Clippy walked so your job management system could run. It would be a shame to leave it sitting in the corner, unasked.

If you’d like a hand working out what’s sitting unused in yours, get in touch with our team.