Please enter password
Incorrect password. Please try again.
Product and UX/UI designer, leading projects end-to-end.
Personalized Learning
Custom AI learning experiences for employees,
built for their unique role and career goals
Visual goal mapping
Goals management module providing a visual map of professional development,
organized by skill area with AI-assisted goal creation
Calories tracker mobile app
A calorie and hydration tracking feature for a sport merchandise brand,
designed to help customers fuel their performance.
I'm always open to new opportunities and collaborations.
I'm Tzuf, a product designer. I work on digital products across the full spectrum from simple, focused tools to complex systems and interfaces. I've worked across early-stage products built from scratch and mature platforms with large, cross-functional teams.
What draws me to design is the gap between how hard a problem actually is and how effortless the solution should feel to the person using it. That tension is what I find most interesting, and it's what I bring to every product I work on - from the first research session to the final UI.
What is Grow? Grow is an employee growth platform built to help people develop professionally - in the field they work in today and in adjacent areas they want to move toward. It gives employees the tools and structure to take ownership of their own development, at their own pace. This case study focuses on the learning feature: the part of Grow where employees build personalized learning sessions around any topic they choose.
The AI shift: As we moved through the design process, it became clear that AI was no longer just a nice-to-have feature, but was quickly becoming central to how modern products are built. At a certain point, we made a deliberate decision to fully embrace that shift, and the final result reflects it.
My role: I led end-to-end product design - from concept and competitive research through prototyping and final UI.
High-tech employees are motivated to grow, but the tools available rarely keep up. Generic e-learning platforms aren't built for the pace or specificity of tech roles, and internal L&D programs often feel disconnected from what people actually need day-to-day.
Employees want ownership over their growth - they just lack a structured, low-friction way to act on it. Content is too broad, not tailored to role or experience level, and there's no easy way to explore related disciplines without starting from scratch.
I audited three major L&D platforms to understand what already existed and where there was room to do something different.
Coursera
Courses are organized by subject, not by role or skill gap - so if you're a developer looking to level up in a specific area, you're left browsing a catalog and hoping something fits. There's no way to build a targeted path around what you actually need.
LinkedIn Learning
The app recommends courses based on your job title, but that's where it stops. You still get a pile of courses with no clear path through them - no structure, no order, no sense of where to start.
Udemy
Anyone can publish a course, so quality varies widely and there's no personalization. If you don't already know what you need, it's hard to know where to start.
After interviewing employees across roles including developers, PMs, and designers, we mapped out the core user flow. The user types a topic or picks from AI-suggested options, and the system automatically builds a personalized pre-session based on what it already knows about them. The learning session is then created - and the user can chat to adjust any part of it at any point.
Early concepts explored filters and recommended paths, but the friction of choosing before knowing made it feel like work before the learning even started. A free-text input - "I want to learn..." - removed that barrier entirely. The AI handles the structure; the user just expresses intent.
How to start a learning session
The early version asked users to pick a category and set filters before anything was generated - decisions most people couldn't answer before seeing any content. The final version replaces all of that with one open question, letting users say what they want in their own words, with AI suggestions to help when they're unsure where to start.
Adjusting the path mid-session
The early version relied on a traditional settings panel, where everything had to be configured upfront. In the final version, that flow was replaced with a conversational chat interface. Instead of predefined decisions, users can naturally request changes in real time, making the experience feel less like a settings menu and more like an adaptive learning tool.
The visual design is intentionally minimal - light backgrounds, dark typography, and a single restrained accent color. The interface was designed to stay quiet and distraction-free, allowing the content itself to remain the focus. In a learning environment, the UI shouldn't compete for attention.
Most importantly, the product needed to feel professional and purposeful - a tool built for people who take their work seriously. Clean, focused, and thoughtful, without feeling overly playful or visually noisy.
Learning home page
Where users kick off a new learning session and see their history. Grow lets you type any topic related to your role (or a general one) and the system generates a primary structure of the learning session.
Building the path
The AI generates a structured learning path based on the user's topic and context.
Learning segment
The in-session view where users work through content and adjust their path via chat.
The final product lets employees create learning segments on any topic - role-specific skills, cross-functional knowledge, or anything in between. The AI structures the content into digestible units, adapts to the user's context, and surfaces relevant material without requiring manual curation.
In prototype testing, participants across multiple roles responded strongly to the sense of agency the product gave them. The ability to define their own learning agenda - rather than follow a prescribed curriculum - was consistently cited as the standout differentiator.
Interested in working together or just want to chat?
Employee Goals is a feature within Grow that allows managers and mentors to set professional development goals for their employees. These goals are tied to growth within the organization, organized by skill area, and tracked over time.
My role: I led end-to-end product design - from research and information architecture through prototyping and final UI.
In most organizations, goals are set top-down and then left without a clear home. Managers assign them through performance reviews or one-on-ones, but employees have no dedicated space to track them day-to-day and no visibility into how those goals connect to their broader growth in the organization.
Employees want to know where they stand - they just have no structured place to see it.
I looked at three performance management platforms to understand how goal tracking is typically handled - and where employees are left behind.
Lattice
Lattice is built for tracking company goals - sales targets, hiring numbers, business objectives. It's a manager's tool. There's no space for an individual employee to track their own professional development.
15Five
Creating a goal means filling out a form built for company OKRs - department, owner, parent objective, key results. Personal development has no real place here, it just gets squeezed into a structure designed for business objectives.
Leapsome
Goal creation requires OKR-style key results, metric types, and parent goal hierarchies. It's a system designed for company objectives, and personal development gets squeezed into that same structure. Even basic things like who's involved in a goal are buried under "Additional settings."
I ran interviews with employees across seniority levels to understand how they currently track goals - most described a mix of spreadsheets, Notion docs, and memory. From there I moved into information architecture and wireframes, focusing on how to surface the right goals at the right time without overwhelming the view.
How goals are organized
The accordion felt like every other goal tracker - dry, functional, and not personal. One subject at a time, no full picture. The map view puts the employee at the center, all subjects visible at once. The spread is clear and intuitive.
Requesting a new goal
A blank input sounds simple, but it puts all the work on the user. Most people don't know how to articulate a learning goal when they're just starting to think about it.
My first instinct was to keep it as minimal as possible - just a text field. I was actually hesitant to add suggestion chips at all, worried they'd create a paradox of choice: too many options on a screen that was supposed to feel open and low-pressure.
But usability testing pushed back on that. When the input was completely bare, a lot of users just stopped. They'd look at it, pause, and not move forward - not because they didn't want to, but because they didn't know where to start. The chips didn't overwhelm them. They gave them something to react to, and that was enough. The input stopped feeling like a blank exam and started feeling like a conversation.
Goals home page
The main view - goals organized by skill area, with a side panel surfacing what needs attention.
Goal request form
The full flow for submitting a new goal request to a manager for approval.
The final design gives employees a clear, ongoing view of all goals assigned to them, organized by skill area, accessible in both map and list formats, and surfaced with a panel that highlights what needs attention. The employee is the one responsible for driving progress, and the interface reflects that: everything is oriented around action and accountability.
The goal request flow gives employees a formal channel to propose new goals, with the understanding that the final call belongs to their manager or mentor. In usability testing, this distinction felt natural. Participants said it gave them a sense of agency without undermining the structure they expected from their organization.
Interested in working together or just want to chat?
Blaze is a sports brand built around an active sport lifestyle. They sell gear, apparel, and equipment for serious athletes. As a natural extension of that mission, we were asked to design a calorie and hydration tracking feature inside the existing Blaze app, giving users a simple way to monitor their nutrition alongside their training. The feature gives users a place to log meals, track calories and macros, and stay on top of their water intake - all inside the Blaze app, alongside the goals they're already working toward.
My role: I designed the full mobile experience - the daily dashboard, the meal logging flow, the water tracking screen, and the loading states.
I reviewed three leading nutrition apps to understand the space - and identify where they fell short for performance-focused users.
Samsung Health
Nutrition is buried under a long list of health metrics. It's not a feature built for people who track seriously - it feels like an afterthought added to a general health app.
MyFitnessPal
Logging feels like data entry. Too many taps, a cluttered interface, and an experience that wasn't designed with active users in mind.
Noom
Built around weight loss, not performance. Heavy paywall and lots of friction before you can actually log food - and the whole product is aimed at a different kind of user.
Everything starts and ends at the daily dashboard - calories consumed out of your goal. From there, two paths: add a new item by choosing the meal type, describing what you ate, and seeing the log and nutritional breakdown; or open an existing meal to edit it and get the same breakdown. Both loop back to the dashboard so the calorie total is always up to date.
This was the primary home screen structure. A few issues led to a redesign:
Home
The daily dashboard - calorie progress, macro breakdown, and meal sections at a glance. The visual language was shaped by Blaze's existing brand identity - bold, dark, and built for performance. The color palette and typography weight were aligned with what users already knew from the app, so the new feature felt native rather than added on.
Adding a food item
The full flow for logging a meal - from selecting the type to the loading state before confirmation.
→
→
→
The final design opens with a dashboard that shows your name, your calorie progress, and your macro breakdown - all in one view. Each meal type has its own section with a quick add button, so logging stays fast.
In testing, people said the dashboard gave them clarity they were used to digging for in other apps. The meal structure felt obvious, and the water screen felt like a natural part of the experience.
Interested in working together or just want to chat?