Writing

10 cardinal sins of building software, and how to avoid them

Ten mistakes, what you notice first and what each one cost. The guide covers what I did and what happened.

Simon Piscitelli, technology director, PIMASI

Paying an agency nobody on your side can challenge

What you noticeYour software takes minutes where your customers expect seconds, and nobody on your side can say why.

What it costMore than six months on software that wasn't fit for a key client: too slow, and poor to use.

Believing more features will attract more customers

What you noticeYour time goes into building, and none of it into winning customers.

What it costMonths of building before the first customer sees it, and the market only answers at the end.

Letting opinions, not customers, set the order

What you noticeWhoever spoke last decides what gets built next, and nobody has asked your customers.

What it costMonths building what nobody asked for, while what customers need waits.

Never finishing what you started

What you noticeYour engineers start something, then get moved onto something new two days later.

What it costA year late, with 27 engineers on the project.

Buying software before you know what you are buying

What you noticeYou have quotes for your idea, and no way to tell which one is right.

What it costA price nobody on your side can judge, and the true cost, time and upkeep found out after signing.

Mistaking motion for progress

What you noticeYou get a progress update every week, never a demo, and the date keeps moving.

What it costSix months at £30,000 a month, on a build quoted at six months whose date had moved to nine.

Believing cutting corners won't have consequences

What you noticeYour team skips the checks to move fast, and your customers find the faults first.

What it costCustomers charged the wrong amount: several hundred thousand pounds in refunds and lost clients, an apology, and a team working nights.

Thinking your company's problems are unique

What you noticeYou are building your own version of a tool every other company buys.

What it costA year on a home-built system that was slow, hard to maintain and a bottleneck for the business.

Adding more people to compensate for mismanagement

What you noticeYour answer to every problem is more people, and the work goes no faster.

What it costSixty people hired after a big funding round, for work a team of ten could have done.

Ignoring the culture to keep your best performer

What you noticeYour strongest engineer is horrible with people, and the team goes quiet whenever he is in the room.

What it costThe team's combined output less than half what it had been, his included.

PDF guide

Get the full guide

What I did and what happened for all ten mistakes, sent to your inbox as a PDF.

Your details

We email you the guide and one follow-up email. We call only if you give a phone number and tick the optional box. No mailing list. We keep your details until you ask us to delete them. Privacy notice.