Skip to main content
Meytal Dahan
Back to insights

Designing for Five Audiences on One Homepage

Hacker U — High tech training institute website
The hardest constraint on the HackerU marketing site wasn't a feature — it was the audience. Prospective students, current students, graduates, recruiters, and discharged soldiers all land on the same surface, each arriving with a completely different question. As a PM, you know what happens when you try to serve everyone with one generic message: you serve no one. So my research started not with screens but with intent. I mapped what each audience was actually trying to accomplish, where their fears lived, and what a 'next step' meant to each of them. That work is what justified the personalized entry layer — letting users self-identify so the primary content card adapts to who they are. Research kept us honest about scope, too. A discharged soldier and a recruiter don't want the same proof points, and pretending otherwise would have bloated every page. For a PM, the value of this research is that it turns 'who is this for?' from a debate into a documented decision. Every prioritization call downstream — which content leads, what the homepage promises — traces back to a real audience need, not an internal preference.

Get in touch

Have a project in mind?

Drop a line. Meytalyav@gmail.com

Related articles

Hacker U
Engineering LeadersR&D Collaboration

A Modular Design System R&D Could Actually Build

Designers can hand R&D a beautiful comp that's a nightmare to build. On HackerU I tried to do the opposite. The marketing site — personalized homepage, dense course pages, a placement page — runs on one modular design system designed to be implemented, not just admired. Reusable, composable components with consistent states mean engineers stop re-solving the same layout on every page. The adaptive homepage card is one pattern, not five bespoke pages. A design system earns its keep when it makes the front end cheaper to maintain, not just nicer to look at.

Read
Hacker U
Project Managers

Backlog Prioritization in an EdTech System: How Do You Run a Project That Serves Thousands of Users Simultaneously?

Project managers in EdTech: is your backlog exploding because you're trying to serve students, instructors, and marketing all at once? In the Hacker U project we built a dual-impact matrix: recruitment versus Retention. Only features that contributed to both earned priority. 3-week Sprints with clear metrics - that's your number one guardian of the Gantt chart.

Read
Hacker U
Product Managers

Learning Experience (LX): How Do You Design a Course-Management System That Students Love?

Product managers in EdTech: students aren't rational users - they're human beings on a personal journey of learning and fear of failure. In the Hacker U project we built a Learning Experience with clear progress visualization, milestones, and positive reinforcement at moments of success. UX = LX. Design the journey, not just the screens.

Read
Meytal Dahan

About

Making complicated into easy for users.

Senior product designer with a decade of work across complex systems - financial risk platforms, legal operations, healthcare apps, manufacturing tooling and insurance portals. The common thread is depth: products where the data is rich, the users are expert, and the interface has to disappear into the work.