The following is a brief system design specification using an iceberg as a metaphor. We'll examine the relationship between what surfaces to the user and the depths of invisible work.
We'll consider "Fleek" an iceberg. The website is the visible part above the water, which only constitutes a small fraction of it, in contrast with the invisible part underneath it, which constitutes most of it.
To comprehend it, let's start by diving into the model.
What the user sees is the best curation possible at the time of delivery. The user does not see the iterative process as limited to effort, research, and talent and has unspoken, hidden issues at any given time. The mental model, from ideation to delivery, is an organizational matter that should be well-designed so that every piece works together efficiently.
The user's experience is at the tip of the model above. The user maintains applications in Fleek's darkest depth and rides waves over the organization board. This user experience highlights the importance and impact of our work on the end user, what it cares about and doesn’t care about, and how we should utilize the model for our betterment.
Since we're getting internal feedback to improve the landing page, let's do a short exercise to determine our current circumstances.
An external team has handled all previous requirements for presenting Fleek as a Platform and Fleek Network as a protocol. However, these do not replace the original fleek.co. In the case of the fleek.network website, the second overrode the original as a Decentralized Content Delivery Network, due to the discovery of Edge networking possibilities. This advancement promises the delivery of a decentralized CDN and many other services.
In both cases, it entails an upgrade over a replacement. Furthermore, it reveals the move from a known user experience that users acculturated to another. Content can be conflicting and meddle in how it ranks on search engines. This creates the illusion of poor SEO. The fact is that searching for “something fleek” ranks fleek.co vs fleek.xyz highly against similarly named companies, such as getfleek.dev (software) or joinfleek.com (marketplace). Moreover, Fleek’s ranking should be expected to vary, given the concurrency of two supported versions, until further notice of deprecation and correct handling.
Considering these points, the organisation and human resources, the landing page's next direction should be integrated into a better system to succeed. Before we design such a system, let’s try to comprehend how the current human resources work together.