Why Does a Feature-Rich Product Not Always Score High on Function?

Many submissions list functions in the Design Statement. Jury members are more likely to ask what problem each function solves and what value it creates for the user.

Build a problem–solution–value chain for every core function, then support it with scenario images, interaction details or evidence. Focus is often more convincing than quantity.

A clear submission translates features into benefits and gives every image and sentence a specific job.