Concept · UX/UI · Design System · Corporate
Techiia — an enterprise tech holding, dialed in.
A holding of very different businesses had no website at all. Working from the client brief, I designed TECHIIA's first corporate site from the ground up — the structure, the prototype, the UI and the dev-ready components — so esports, IT, hardware, motorsports and a foundation read as one company, in eight languages. It shipped, and years later still runs almost exactly as designed.
Background
A sprawling holding with no front door.
TECHIIA brings together esports (WePlay), IT (JMIND, Enestech), hardware and merch (WP Merchandise), motorsports and a foundation. It had no website. The job: one credible, enterprise-grade front door for all of it — carrying businesses, team, news and CSR without feeling heavy, across eight languages. With no previous site, every structural decision was a first.
Challenge
One site, five very different readers.
- Partners and clients weigh scale, expertise and the portfolio of businesses.
- Investors look for stability, principles, leadership and track record.
- Talent judges careers, culture and the employer brand.
- Media want news, facts, contacts and press materials.
- The public reads values, CSR and memberships.
An audience map from the client brief — not researched personas. It drove the IA and the navigation.
Discovery
Learn how holdings tell a many-business story.
A light reference scan of holding and conglomerate sites — VW Group, J&J, Mars-style portfolios. The pattern is consistent: lead with the corporate story, then give each business its own clear door. Techiia follows the same logic.
| What we took | What we avoided |
|---|---|
| Lead with the corporate narrative — goal, principles | An overwhelming "list of everything" |
| Clear paths into each business | A heavy, over-corporate feel |
| Straightforward navigation | Inconsistent styling across sub-businesses |
| One flexible design system across a diverse portfolio | — |
Thinking
From a client brief to dev-ready — no guesswork left for the build.
I ran it end to end from stakeholder input — no user research. No wireframe stage either: brief → prototype → UI → handoff, with the information architecture settled first.
| Step | What happened |
|---|---|
| 1 · Client brief | Stakeholder input — the businesses, the story, the goals. |
| 2 · Information architecture | Corporate story → businesses → team → careers → media → CSR → contacts. |
| 3 · Prototype → UI | An interactive prototype, then high-fidelity UI. |
| 4 · Dev-ready handoff | A UI guide, components and specs for the client's dev team. |
Outcome
A holding that finally reads like one.
The home page tells the corporate story first — mission, principles, vectors of work. Every business then gets the same page template, so a data-centre park and an esports brand sit comfortably side by side.
One template for every business
Title and tags, the story, a video, key facts in large type, the why and the what. Built once, reused for each business, at desktop, tablet and mobile.
The story first, the system behind it
A dark, technological UI in black, greys and white with one red for errors. The UI guide fixed type, palette and buttons so the dev team could build and extend it.
What shipped
Results
Shipped — and still running almost as designed.
The site went live and, years later, still runs almost exactly as designed. The brand was later lightly refreshed, so some visual elements changed — the structure, the templates and the system held.
Shipped & durable
Went live and still runs almost exactly as designed.
What held→What heldYears later, on the live site- The holding IA
- The business-page template
- Careers, media and CSR sections
- The dark technological UI
Structured the complexity
A sprawling multi-business holding organised into one clear corporate site.
How it's organised→How it's organisedStory first, then the businesses- Corporate story: mission, principles, vectors
- One door per business
- Team, careers, media, CSR, contacts
- Five audiences, each with a fast path
Built to scale
8 languages, a repeatable business template and a component system the team could extend.
What scales→What scalesOne system, many pages- 8 language versions
- A business template reused per company
- Components with states
- Desktop, tablet and mobile
End-to-end delivery
Client brief → IA → prototype → UI → dev-ready handoff.
My part→My partLead designer, end to end- Information architecture
- Interactive prototype
- High-fidelity UI
- UI guide, components, specs
No analytics were shared, so no traffic or conversion figures are shown.
Selected screens
One dark, technological system — from home page to vacancies.
