Overview
Review round 1 and 2 · 4 November 2026
Four ways to modernise the desktop header
We tested four directions, from a light refresh to a bold redesign. Each one opens as a working static preview. The recommendation is a low-risk refresh first, with a stronger direction held for a later release.
4Directions reviewed
2Review rounds
3Decisions needed
0Production changes so far
Recommended starting point
Start with Nordic A: a refined, familiar header
It modernises the look while keeping every destination where visitors expect it. It carries the lowest implementation risk, and it can ship without restructuring the site. Keep the stronger directions as options for a later brand moment.
At a glance
Our assessment, not measured data. Use it to frame the discussion.
| Direction | Look and feel | Change to site structure | Build effort | Main risk |
|---|---|---|---|---|
| Nordic ARound 1 | Light, familiar, richer Services panel | None | Low | Looks similar to today, so the gain may feel small |
| Nordic BRound 1 | Confident navy header, stronger identity | None | Low to medium | Contrast and logo treatment need checking |
| Nordic CRound 1 | Floating, compact, editorial | Regroups menu items | Medium | Visitors may not find pages where they expect |
| HelveticaRound 2 | Calm, precise, typographic | Light | Medium | Full-width panel is heavy; hover behaviour needs care |
| AtelierRound 2 | Most modern, product-like, dark mode | Adds search | Medium to high | Needs a search decision, plus blur and dark-mode work |
| AlpineRound 2 | Quiet and content-first | Light | Medium to high | Hidden header on scroll can slow visitors down |
Explore the directions
Select a card to preview it here, or open it in a new tab.
Decisions for leadership
- Confirm the direction: Nordic A now, or a bolder option.
- Decide whether the site needs a search feature (Atelier assumes one).
- Agree the timing, since a refresh can ship before a larger redesign.
Next steps once decided
- Check every label and link against the current site content.
- Test the chosen header at common desktop widths and with keyboard only.
- Build it in the site with the usual review and staging flow.