What you see it’s not always what you get. Iceberg.
The same problem in different contexts can be more complicated! What we see it’s not always what we get. Like an iceberg.
LinkedIn introduced innovation to its network. Reactions. What reactions will bring to us, we will see.
From the client’s point of view, reactions are simple functionality, instead of liking, we now have the ability to better define our impression for a post.
From the aspect of the development team, the reactions were a sophisticated task. We guess, but all probably started with an idea. After that, it was necessary to plan everything well with a series of meetings.
In less complex systems, this was a simple task. Here, on the other hand, it was necessary to implement a system that would gradually provide users with the ability to use it. There may be a system which determines which user groups will see the new functionality. There may be an analytical system that compares user behavior with expected behavior. And a lot more features related to this functionality.
Long story short, behind the new functionality is the entire development team that probably developed the reactions for months. As with the iceberg, what we see is just a fraction of what is there.
Even simple ideas often require a lot of work and effort to be made. In our company, we do our best to make sure the client understands all the things that we need to do when we are developing a software product and that’s the key to successful cooperation.