← Back to Blog

Can't Be Done Usually Means Won't Own It

An internal IT team said a project needed five developers and six months. I built a working prototype in twenty minutes while they were still saying it on the call. The problem was never whether it could be done.

By John Croucher
BusinessWar StoriesOpinion

I was on a call about a project for a large company, with their internal IT team in the room.

The client wanted something built. The internal team kept saying it wasn’t possible.

When pressed, the answer was that it would need a team of people, at least four or five developers, and six months. It was going to be a big budget. There was no way it could be financed, and no way it could be done within the deadline the client had.

4 to 5 Developers needed According to the internal team
6 months Estimated build time Well past the deadline
20 min To a working prototype Built during the same call

Ten People Saying No

I said it could be done.

I tried to make my case, but it was a virtual room of ten or so people, and every one of them was on the other side. It can’t be done. It’s too big. It’s not possible in that time. Each time I raised it, the answer came back the same, from several directions at once.

Eventually I gave up arguing.

Twenty Minutes Later

Instead, I started a new project.

I copied some existing code, wrote some new code, and put some placeholder images in. Nothing clever. Just enough to show the thing working.

The call kept going the whole time. People were still talking through options, and still saying it wasn’t possible.

About twenty minutes later I raised my solution again. This time I included a link to the prototype I had just thrown together.

Everyone went quiet.

Then the people who actually wanted the project got excited.

The team that had said it couldn’t be done said something else. It’s on you now.

It Was Never About Whether It Could Be Done

I spoke to a few people afterwards, and the picture became clear.

It wasn’t really about whether it could be done. The problem was ownership. Nobody wanted to take the project on.

In that culture, saying something can be done means you are the one who has to do it. Saying it can’t be done means you have no work to do. The answer that protects you is always no.

If you say it can't be done, you have no work to do.

Internal Versus External

This is what changes between being internal and being external.

Inside a company like that, yes means you’ve just given yourself more work, and no means you haven’t. Coming in from outside, I didn’t have that reason to say no.

Get an Outside Opinion

This is one reason I always recommend that people get external opinions.

If the only advice you’re getting comes from the people who will have to do the work, you’re not just hearing what’s possible. You’re hearing what they’re willing to take on. Those can be very different things.

You can’t always rely on the people around you when the company culture doesn’t allow them to say yes.