Redesign the landing screen of Glean's enterprise AI search and assistant app

Quick Overview

An app critique and product design question about improving the home page of Glean, the enterprise search and AI assistant that works across a company's apps. It tests choosing an employee segment, explaining why visits fail, prioritizing ideas for the first screen, and setting adoption metrics with guardrails.

Redesign the landing screen of Glean's enterprise AI search and assistant app

Company: Glean

Role: Product Manager

Category: Product Design & Strategy

Difficulty: medium

Interview Round: Other

Glean is an enterprise search and AI assistant that lets employees find information and get answers across their company's work apps. Its home page is the screen people see when they open it. How would you improve that home page? ```hint Two kinds of arrival Picture someone who opens Glean with a question already in mind and someone who opens it with nothing to ask. Decide whose visit fails more often today, and why. ``` ### Clarifying Questions - Which surfaces count as the home page: only the start screen of the web app, or also browser and mobile entry points? - Is the goal to raise the share of licensed employees who use Glean each week, to get more out of each visit for existing users, or to drive use of the AI assistant in particular? - Should the design target a specific group, such as new hires, engineers or sales and support teams, or every employee? - Can each customer's admins and internal communications team control what appears on the page, and must the design keep that control? ### What a Strong Answer Covers - The job the home page does for Glean and for the customer company, stated as a goal. - A chosen employee segment and the reasons its visits fail or never happen. - Ideas that make the page useful before anything is typed, prioritized by impact and effort. - Metrics for adoption and successful visits, with guardrails on speed, relevance and permission safety. - Enterprise constraints: content permissions, admin controls and the cold start of a new deployment. ### Follow-up Questions - How would you make sure the page never shows a document title or summary that the employee is not allowed to see? - A new customer has connected only two apps so far. What does your home page show in its first week? - How would you show the customer's IT buyer that the redesign increased the value of the licenses they pay for?

Overview: An app critique and product design question about improving the home page of Glean, the enterprise search and AI assistant that works across a company's apps. It tests choosing an employee segment, explaining why visits fail, prioritizing ideas for the first screen, and setting adoption metrics with guardrails.

Glean logo
Glean
Sep 16, 2026
mediumProduct ManagerOtherProduct Design & Strategy
0
0

Glean is an enterprise search and AI assistant that lets employees find information and get answers across their company's work apps. Its home page is the screen people see when they open it. How would you improve that home page?

Clarifying Questions Guidance

  • Which surfaces count as the home page: only the start screen of the web app, or also browser and mobile entry points?
  • Is the goal to raise the share of licensed employees who use Glean each week, to get more out of each visit for existing users, or to drive use of the AI assistant in particular?
  • Should the design target a specific group, such as new hires, engineers or sales and support teams, or every employee?
  • Can each customer's admins and internal communications team control what appears on the page, and must the design keep that control?

What a Strong Answer Covers Guidance

  • The job the home page does for Glean and for the customer company, stated as a goal.
  • A chosen employee segment and the reasons its visits fail or never happen.
  • Ideas that make the page useful before anything is typed, prioritized by impact and effort.
  • Metrics for adoption and successful visits, with guardrails on speed, relevance and permission safety.
  • Enterprise constraints: content permissions, admin controls and the cold start of a new deployment.

Follow-up Questions Guidance

  • How would you make sure the page never shows a document title or summary that the employee is not allowed to see?
  • A new customer has connected only two apps so far. What does your home page show in its first week?
  • How would you show the customer's IT buyer that the redesign increased the value of the licenses they pay for?