Web development mistakes

It is important to understand that any website should be user-friendly, optimized from the point of view of search engines, contain unique content and be adapted to your business processes. Only if these conditions are met, it will really bring profit to its owner and delight visitors. And any “designer” or “ready-made solution” is nothing more than some blanks created by no one knows who and no one knows where and having very limited functionality. In the most popular site designers today, there are usually no (or there are, but with errors) even such simple tools as automatic generation of a site map or generation of metadata according to certain templates.

From practical experience, I can say that designers are good either for quick and cheap creation of piece temporary pages (pages of one–time promotions or special offers, for example), or for creating websites consisting essentially of a logo and contact details. In any other case, web developers are needed, no matter how much we would like to think that we can do without them.

Any web developer, studio or agency should do a project until the edits disappear

This myth is familiar to anyone who has encountered the process of web development at least once. In almost any project, there are many additional corrections, improvements and new wishes that are not provided for in the original terms of reference. This is due, firstly, to the fact that appetite, as you know, comes during meals. Secondly, when approving the terms of reference for development, additional functionality may be needed, which will also need to be added. The third reason is even simpler – a change in requirements on the part of the customer’s management.

It should be understood that in the process of creating a website (if we are not talking about a project from the fourth myth), a large number of people are involved: a designer, front- and back-end developers, a manager – this is at least. The working hours of each of them are planned and taken into account at the stage of developing the terms of reference.

The good news here is that any modern web development agency warns the client even at the stage of creating the terms of reference that the work performed in excess of this task will be evaluated and paid separately. And the client still has the opportunity to determine the most priority tasks within the existing budget and include them in the terms of reference.

Conclusions

The most important thing is that before you create a website and wait for a profit, make sure that you are selling a good product or providing a quality service.

If you are planning a long–term project with development prospects and do not want to face alteration from start to finish – contact professionals and do not use constructors and similar solutions.

Test and verify the site both during creation and in the process of working with it. Set aside at least a couple of hours a month for this. These hours will more than pay off with the money and nerves saved.

When planning to create or redesign a website, try to imagine the functionality of the future project in your head (or on paper). When drawing up the terms of reference and approving it, do not be lazy to read it thoughtfully and ask questions.

To all customers – good and selling sites, and to all developers – ideal satisfied customers.

Without TK, fast analytics or deep analytics

Work without TK does not suit the customer, because it is unclear what budget to lay. We need a strong credit of trust — suddenly a couple of months will pass, we will have to pay millions, and the project will not be. Deep analytics is also confusing — spending hundreds of thousands and several months on the development of technical specifications, prototypes and an estimate of the cost of development may seem like a dubious idea.

I would suggest a third option, a “magic pill” for such situations — fast analytics without strong detail. I’ll tell you how we do it, using the example of several customers. In the end, I will share the methodology: if you like the approach, you can try to conduct such a study yourself, you will save money and time.

Disclaimer. At MetaLamp, for quick analytics without much detail, we use the term Discovery phase, or “Discovery” — the process of turning a customer’s idea into a technical specification and prototypes, according to which developers will evaluate the project and announce to the client the terms and cost of work.

And we say “Deep analytics” when it comes to a similar study, only very detailed and scrupulous. It’s just easier that way.

In other studios, the terminology may differ: somewhere “Discovery” may be called semi-annual research projects, and somewhere it will be a week-long study of features.

Without TK and the result is not very good. What options are there to evaluate the project in general

Meet Dima, the owner of a logistics business, which he decided to transfer online and expand, to make an analogue of Uber, but in the world of cargo transportation. Dima downloaded a TK template from the Internet, filled it out, it turned out to be some nonsense. I Googled, realized that he had a completely atypical project, it was expensive, long and difficult to recruit his staff of developers, and decided to look for a contractor.

First, Dima came to the bureau, where he was told about Agile, flexible methodologies and hourly pay. To put it simply, they offered to work without a detailed TOR: he tells the idea, the guys start developing, having agreed in advance on the cost of an hour of a programmer, designer and other specialists.

A working option, if Dima is ready to spend a lot of time on the project — he needs to be constantly in touch with the bureau, coordinate a bunch of nuances, make decisions. It is unclear how much time the project will take in the end, how much money should be given — they told him the approximate price, but the fork cost is large, perhaps even several million, because the project is large and with unclear requirements. The first release was promised to be made in a couple of months, but also without guarantees. Dima realized that he did not trust this bureau enough to take such a risk.