Your design insight could be "Users need a new way to schedule from home screen". However, it could be considered too specific to be an insight and would more be called a "finding".
There is no precise definition of an insight, it is a statement that summarize research and that could have an impact.
To know if it is an insight, ask these three questions :
- Does it say something about the attitude, behaviour, needs or context of your users in general (i.e. is true, regardless of your product or solution)?
- Is it a fundamental principle you’ve discovered, like a behavioural or design pattern?
- Does it say something about your brand, product or service in its entirety and not just a small part of it?
Can you answer at least one by "yes" ? It is an insight.
(source : https://www.reveall.co/blog/how-to-write-valuable-user-insights)
From a usability test, you can have different types of insight depending on the nature of the study : quantitative or qualitative. In either, there is a ton of information, findings.
For my part, to find insights, I start by sorting the problems by severity and frequency and look at the overall results.
Here are the problem severity from usability.gov :
- Critical: If we do not fix this, users will not be able to complete the scenario.
- Serious: Many users will be frustrated if we do not fix this; they may give up.
- Minor: Users are annoyed, but this does not keep them from completing the scenario. This should be revisited later.
(source : https://www.usability.gov/how-to-and-tools/methods/reporting-usability-test-results.html)
You can also use the rainbow sheet template to visually identify the more frequent issues :
