Consulting work
E-ITS
DESIGN & PROTOTYPESFind the requirement.
Keep its context.
I work on the E-ITS portal’s product design and information architecture, helping people find their way through the Estonian Information Security Standard. My contribution connects search, navigation and reading context within the standard’s existing content, versions and interface constraints.
The Estonian Information Security Standard (E-ITS) is a national information security and risk management framework used in Estonia, with mandatory application defined by Estonian cybersecurity legislation.
Context & discovery
A structured standard.
A human starting point.
People arrive with different levels of familiarity: a specific requirement, a keyword or a question about their situation. The portal needs to offer a useful route into a large body of structured information without losing the source behind the answer.
I focused on making that structure easier to navigate. Search and domain navigation provide different starting points; the reading experience needs to retain the document, version and related context that help someone understand what they have found.
My contribution
Product design and information architecture: clearer entry routes, search, navigation and continuity between finding a requirement and reading it.
I worked within the existing content and system constraints, alongside the team, connecting the entry routes with the reading experience.
Design & prototypes
E-ITS / The entry point
Search in your own words. Navigate by domain.
For the Estonian Information Security Standard, I focused on the route into a large body of structured information. The homepage design gives people two starting points: a question in their own words or a route through the standard’s domains.
The design choice
A question and a map.
The search area and domain cards serve different starting points while keeping the catalogue structure visible.
I worked within the standard’s content, versioning and interface constraints. The task was to improve orientation and continuity, while keeping the requirements and their context intact.
Make the structure navigable.
Keep the source in view.
Three decisions behind the work
01Offer a starting point.Support a question in someone’s own words and a route through the standard’s domains.
MY CONTRIBUTIONI shaped the entry point around different levels of familiarity with the standard. A person should be able to begin with a question or use the catalogue structure to orient themselves.
VISIBLE IN THE DESIGNThe search area and domain cards offer two clear routes into the same body of information.
02Keep the source in view.Connect finding a requirement with the document and version needed to interpret it.
MY CONTRIBUTIONI worked on continuity across search, navigation and reading so the information architecture remains understandable as someone moves deeper into the standard.
DESIGN PRINCIPLEA route into the content should retain its source context. Finding a result does not by itself establish that a requirement applies to a particular organisation.
03Respect the structure.Improve the experience while preserving official content, identifiers and relationships.
IMPLEMENTATION CONSTRAINTSThe standard’s content and version relationships remain authoritative. Interface changes need to improve orientation within those constraints.
HOW I CONTRIBUTEI clarify hierarchy and interaction within the existing design and technical rules.
What this demonstrates
Orientation in complexity.
Product reasoning and information architecture working together: helping people find a useful starting point and follow the structure behind the information.
How I contribute
Continuity through the task.
I connect the entry point, navigation and reading experience within established content and system constraints.
