The challenge.
Education data had been consulted through printed bundles. The new tool needed filtering, comparison and export, but separate working groups were building their own sections without a consistent experience.
The key decision.
We mapped requirements across stakeholders, then reviewed wireframes with business teams and developers early to understand QlikView’s possibilities and constraints.
The rejected option & why.
Letting each working group define its own interface would perpetuate inconsistency. Shared UX patterns and iterative reviews helped bring the application’s sections together.
The outcome.
Wireframes and prototypes evolved through working groups and testing with a sounding board group. Collaboration with developers helped translate the proposed experience into the QlikView tool.
The final verdict.
The engagement connected user expectations, education-domain requirements and technical feasibility. Testing and shared patterns supported a more coherent way to explore education data.
