What I Learned Writing A Product Design Report

An app design report is important because it outlines the design choices that were made during the development of an app. This includes details about the user interface (UI), user experience (UX), and overall look and feel of the app.

Having a clear design report helps to ensure that all team members are on the same page about the design direction of the app, and it can also be used as a reference for future updates or changes to the app. Additionally, a design report can be useful for demonstrating the thought process behind the design decisions to stakeholders or clients.

Writing a product report has been a valuable learning experience for me for a number of reasons. Here are some of the things that I learnt from writing a product report.

I find myself often going back to gathering and analyzing data about the product, its market, and its competitors. This helped to guide my thought process.

Writing  a formal document is not something I particularly excel at, it requires clear and concise writing. This helped me improve my writing skills.

A product report requires you to evaluate the strengths and weaknesses of a product and to make recommendations based on your findings. This part I really love doing. So I didn't struggle as much as I thought I would be.

A product report requires me to organize and present information and key findings in a logical and coherent manner. This certainly helped in improving my story telling skills.

The structure of an app design report can vary depending on the specific needs and goals of the report, as well as the preferences of the audience. That being said, here are a general outline of what you might include in an app design report:

• Introduction/Summary: This should provide an overview of the purpose of the app and it's targetted users, as well as any other relevant background information about the app.

• Design goals: This section should outline the main design goals and objectives for the app, such as improving usability or increasing engagement. Can be included in the Summary section to keep things simple if need be.

• Design process: This section should describe the design process that was followed, including any sketches, prototypes, or user testing that was done and most importantly, what was the thought process behind those decisions.

• Design solutions: This section should present the final design solutions for the app, including details about the user interface (UI) and user experience (UX).

• Conclusions: This section should summarize the key findings and how the app was evaluated, including any metrics that were used to measure its success. 

• Appendices: This section should include any additional materials that were referred to in the report, such as wireframes or user research report.

That said, while writing my product design reports, I was only able to follow those guidelines loosely. Instead I got into the flow of writing my reports by sharing the thought process I went through.

I find that is the best for me at this point. There's only a lot more to learn for me...