This page describes the process of creating the first low fidelity prototype representing the main idea of how the wild boar management symulation module should be working.
Problem
How can I present to the client the way the wild boar management module should be working in our opinion at a high level, so we have a clear idea as a team if our development plan is in sync with the ideas of the stakeholders?
Answer: By creating a simple prototype, which represents the basic flow of the future module.
Based on the findings there was defined a way in which most modules worked, so we could create a core loop: (the core loop was created by a teammate, but the research helped in defining the core mechanics)
The scenario was created to showcase the core loop. Overall the idea of the prototype was to show the flow with no need for relevant data. (ex: the price of the actions, speed of boar movement etc)
Prototype scenario
AdobeXD workflow
Having previous experience with AdobeXD I knew the prototype would be fast to make. The prototype itself is having all steps as different boards, which are connected via Board press logic (no matter where the user clicks the next window will load following the Prototype scenario)
This connection makes the prototype low fidelity with the purpose of displaying how the game would work.
Prtotype Screens with the connections
Result
Prototype explanation
Prototype link
Quality of the result
The result was shown to the stakeholders in a meeting. (Showroom ~ Pitch) It succeeded in explaining to the clients the main idea of how the module would be working. As feedback the prototype "Impressive at that stage of the project". However, the data is irrelevant, so that was mentioned by the clients.
Next steps
As next steps, there would be more research to make the data about the boar movement as well as the prices of different actions more accurate.
First playable ate Unity would be started to be developed, following this prototype flow.