<aside>
My Notion includes images taken from the FigJam boards I have been using throughout my process.
If you would still like to see further details / better resolution , please view the FigJam board linked below.
</aside>
As I have not yet clearly defined the core features of my app, it is important that I do this as soon as possible in order to move the project forward effectively. Currently I have feature ideas such as avatar customisation, a “get-ready” game, QR code check-ins, a rewards system and sensory exploration activities. While each of these features could add value to the user experience, it is not realistic to implement all of them within the available timeframe. As a result, I need to prioritise and select two or three key features that will form the foundation of my product. This will allow me to focus my development efforts, manage time more effectively and ensure that the final app is cohesive and well-executed.
I began by mapping out all of the features I had identified and potentially wanted to include so far. This will allow me to see them clearly and evaluate which ones could be removed at this stage and help me identify which features can be dropped because they were are feasible within the project constraints as well as others which can be dropped as they will not significantly enhance the core purpose or user experience of the app.
I then created a feature feasibility map to evaluate potential app features based on their user value and technical feasibility.
This helped to map out which features I should prioritise based on their impact but also achievable within the project’s time and technical constraints. By visually mapping each idea, I was able to identify which features were suitable to take forward and which should be deprioritised or removed.
This ensured that development efforts were focused on delivering a small number of high-quality, meaningful features rather than attempting to implement too many unrealistic ideas.
Avatars are really powerful for my project as they are not just visual decoration but instead act as support for children and are a core emotional and narrative tool. They provide children with reassurance and companionship as they help guide them through each stage of the experience and provide calm responses to uncertainty, support emotional regulation and reduce fear, while maintaining a child-centred and clinically appropriate tone. For this reason I that that having personalised avatars as a feature is really important core feature for my app however the ability to further customise their avatar is less important and needed. While giving children a few minimal choices to give them a sense of comfort and have an avatar that relates to them, the ability to change specific features is not feasible or needed.
QR codes were the first feature I identified as unsuitable to include due to feasibility constraints. Although QR codes are already used on some hospital letters to encourage patients to download hospital apps, this is not a standard practice across all hospitals. In addition, using QR codes for appointment import, starting an in-hospital journey or check-in would require real hospital system integration and implementing this feature would therefore be complex and unrealistic within the scope of this project, as it would rely on backend functionality. Accurately integrating and prototyping these interactions in a convincing way would be challenging without access to real hospital systems, making this feature impractical to pursue at this stage.
As rewards are not necessary for a narrative journey, I have decided this would be a feature that can be implemented later if needed but is not necessary for the core journey of my app. While they acknowledge moments of bravery and courage as well as marking their progress and achievements which children can feel proud of, this can also be incorporated through other core features I want to use such as emotional check in and sensory exploration. In this context, rewards may not always be feasible as it can easily become quite gamified and competitive, creating the impression to children they must perform well to earn comfort and feel guilt or shame if they struggle
While games can enhance engagement and provide distraction during waiting periods, they are not essential to the core narrative journey. The primary value of the app lies in guiding children through the hospital experience, reducing fear through clarity, preparation and emotional reassurance. Games can end up weakening the narrative instead of supporting it by distracting users from being reassured or feeling gimmicky. For this reason I have decided to drop the games.
Sensory exploration is crucial and a very important core feature for my project as it helps to reduce anxiety within a narrative hospital journey, as many children’s fears are rooted in unfamiliar sensory experiences rather than the medical procedures themselves. By allowing children to safely and gradually explore hospital sights and sounds within a controlled narrative environment, the app supports familiarity, predictability and emotional regulation, contributing to a more child-centred and trauma-informed experience.