Process conclusions

• Get started - Do not wait for the perfect version. Once you have the minimum necessary features on the site to create an order, you should expose it to the users and learn as you progress.
• Jumping around - As the process progresses the owner discovers customer needs and expectations and is exposed to new options, It is important to match expectations from start and be attuned to the customer's needs and not just their requests.
• Small steps - A cycle of design and development, shortening the design process and reducing the number of elements worked on simultaneously, thereby optimizes the progression of the project.
• Anything is possible - But it all depends on manpower, In thie specific case, a bottleneck was created because everything was done by a single developer.
• Decision making - Despite understanding the project objectives and preparing a PRD document, work was not conducted with a schedule and MVP. Task management must be mediated by a product manager in order to establish order and prevent misunderstandings.
• Initial design - The initial wireframe screens were designed on a widescreen which prolonged the responsive design process. No original text lengths were tested, an issue created a feature placement problem. Wireframing for mobile should have been done before web.