While writing the content is important, it's just as important to consider how the content is organised - this is information architecture.
"Information architecture focuses on organizing, structuring, and labeling content, and how it all fits together so that users can easily find the information they need and complete tasks. If they can’t do that, they’ll simply give up and try out the competition."
Oliver Lindberg Information Architecture - Adobe Ideas
Good information architecture is based on user research - understand who you are catering to and involve users in the process as soon as you can.
When conducting competitive analysis I listed out all the features/content I wanted to include in Vetter care. I later asked 2 interviewees to carry out the same card sorting exercise, prioritising them based on what's important to them.
Listed out features
Listed out features/grouped by me
Listed out features/grouped by user
Now that I understand which features are considered necessary to each user and which would be a nice added extra, I need to look at organising this content into groups to think about platform structure.
What features can be grouped and what features need to be the most accessible to the user.
From this, I found my features could be sorted into two different pages
1️⃣The dash (where all the important info goes) - All pet medical details will flag for the pet owner, alerts on what is overdue, and today's tasks, the owner can use this dashboard to choose which pet profile they wish to view, add new pets. As “logging a trip” is the main feature of the application, as well as symptoms checker I feel as though these would be beneficial on the dashboard for easy assessibility, rather than having to direct to the profile before logging an appointment/symptom.
2️⃣The profile- From this task, I was able to determine which way was best to group the features: I came up with grouping them into 6 different tiles of information that will be available on all pet profiles, by listing out my user's features and allowing 2 primary users to group into the order of importance to determine what features should be most accessible :