Beyond Glean search and chat: Getting to better AI outputs - Glean Tutorial

Welcome to our Glean Intermediate series. If you already use Glean to find information or gather context, this is the next step. The big shift is moving from asking for information to asking for usable output. In this video, I'll show you how the same source material can go from a decent answer to something you could actually use in your work. Most people start here on the homepage with a simple question. It's useful, but it usually gives you context, not a deliverable. Let's look at the difference. What should I know about Frasier Automotive? This is a very normal first prompt. I'm asking Lean to help me get oriented on an account. Now this is already helpful. I can quickly get a sense of the company, the context and what might matter. But if I stop here, I still have to do the real work myself. I still need to turn this into something usable for a meeting or an email. And that's the shift that I wanna show in this course. Instead of asking Glean to just inform me, I want to ask it to help me produce something. Create a concise account brief for a PMM preparing for a first meeting. Include company context, likely pain points, possible use cases for Glean, and three smart follow-up questions. Now with this request, I'm being much more specific. I'm telling Glean the audience, the situation, the format I want back, that usually matters more than just making the prompt longer. Now the output is more useful. Instead of a general answer, I'm getting a compact brief designed for a specific purpose. It has the shape of something I can actually work from. I'm not just asking, what is this account? I'm asking for a concrete artifact that fits the moment I'm in. And because the output is grounded in company context, I can verify where the recommendations are coming from instead of treating it like generic AI text. Now, let's push it one step further. I'm gonna go back to my thread. Once I have the brief, I can keep shaping the work in context instead of having to start over. Now turn that into a warm outreach email to their VP of digital transformation, asking to do a customer case study. keep it under 150 words, and make it sound specific, not generic. This is one of the most powerful habits to build. I'm reusing the work that Glean has already done and asking for the next deliverable in the same thread. Now I have something much closer to what I actually need. It's not just informed by the account context, it's already translated into usable communication. Notice I didn't ask for a generic email about Frasier. I asked for a warm first touch email, for a specific role, with a specific length, with a constraint. Those small constraints are what make the output feel more intentional. And if the first draft is close, but say not quite right, I don't need to start from scratch. I can just refine it conversationally. Revise the email to sound more executive ready and confident. Keep the tone pragmatic and concise. This is the part that many people miss. The fastest path to a strong output is usually not one-shot perfect prompts. It's a solid first request followed by one or two clear refinements. Notice how the tone is tighter. It feels more appropriate for a senior audience, but still stays warm and specific. And if your environment includes deeper reasoning, model selection, this is a good moment to use it. For straightforward drafting, I usually keep things simple, but for a higher stakes brief or more nuanced to rewrite, giving Glean a little room to reason can improve structure and judgment. So the real takeaway is this. Glean Assistant helps you get oriented, but the bigger value comes when you ask Glean for a deliverable, a brief, an email, a table, a report. The same information becomes so much more useful when the request is grounded in audience, objective, tone, and format. That's how you move from using Glean as a tool to using it as an agentic coworker.