AI-Powered Knowledge & Productivity
Gemini Notebook (formerly NotebookLM) and GenAI for everyday project work.
Who this is for
Business analysts, project and product managers, knowledge workers and non-technical stakeholders. No coding required.
Today’s outcome
Build a checked Gemini Notebook for one project — cited answers, an action list, a risk check, a RACI and a timeline — and plan where you will use it at work.
First, the people: who’s in the room, and what work you brought with you.
Hello, I’m Azhan.
Before we open any tools, let’s meet the room.
Your trainer
Azhan Abdullah — edtech and data analytics trainer. I help teams turn everyday documents and data into decisions they can check.
Icebreaker · 20 seconds each
- Your name and role.
- One document task that eats your time — meeting notes, reports, proposals or policies.
- What a good result would look like.
More than 20 of us? Share at your table, then two volunteers tell the room.
With that task noted, let’s get your account and files ready.
Ready check: two things before we start.
Two minutes now saves twenty later. Put your hand up if either step fails; we will pair you with a neighbour.
1 · Open Gemini Notebook
- Go to notebook.google.com.
- Sign in with the Google account you will use today. A personal account is fine; some work accounts block Gemini Notebook.
- You should see Create new notebook.
2 · Download the five project PDFs
- PRJ-01 Project charter v2
- PRJ-02 Project charter v1 (draft)
- PRJ-03 Steering committee minutes
- PRJ-04 Supplier proposal
- PRJ-05 Status report and risk register
Save them somewhere easy to find, such as Downloads. No need to open them.
Everything open? Here’s how the four hours build one checked notebook.
Four hours: understand, practise, apply.
Every module follows the same pattern: explanation, worked example, exercise, debrief.
| Length | Module | Activity | What you’ll have |
|---|---|---|---|
| 10 min | Welcome, ready check and your work task | One work task | |
| 20 min | 1 | GenAI & grounding | Explain one limit |
| 30 min | 2 | Use the notebook · Exercise 1 | Right source selected |
| 35 min | 3 | Prompt & verify · Exercise 2 | Checked briefing saved as a note |
| 55 min | 4 | Work with project documents · Studio, Exercise 3 | Report started; three cited tables |
| 15 min | Break | ||
| 25 min | 5 | Save, generate & reuse · Exercise 4 | Report checked, two outputs, access set |
| 30 min | 6 | Frameworks: RACI & timeline · Exercise 5 | Two checked tables, one in Sheets |
| 20 min | 7 | Wrap-up & next steps | Exit check and action plan |
First stop on the plan: what generative AI actually is.
What are GenAI and large language models?
The difference that matters: a search tool finds what already exists. Generative AI writes something new.
A search tool finds
“What did we agree about the supplier pilot?”
It returns the file and the line that already contains the answer. Nothing new is written. If no document says it, you get nothing back.
Generative AI writes
“What did we agree about the supplier pilot?”
It produces new sentences that appear in no document. If no document says it, it can still write a fluent answer — which is why the rest of this session is about checking.
Reference: Google Cloud · Generative AI glossary
Now that you understand what GenAI is, let’s look at what happens when you ask it for help.
What happens when I ask generative AI for help?

Generative AI writes new text by predicting likely next words. It does not copy or look up the answer.
- You give it a task and material, such as meeting notes.
- The model predicts useful wording, so the result reads fluently.
- You check the facts, promises and anything it missed.
If the model only predicts wording, how do we get facts into its answers? That’s grounding.
Grounding and RAG: bring evidence into the answer.
![Five-panel comic. One, You ask a question: a worker asks, "What are the approval steps for our new project?" Two, RAG finds relevant information: a robot says, "Let me search your documents," pointing to Project Proposal, Meeting Notes, Policy Guidelines and Past Projects. Three, AI generates an answer with citations: the robot lists prepare proposal, get department review, finance approval and final sign-off, cited [1][2][3]. Four, You check the sources: the worker says, "Looks good… let me check the sources to be sure," next to three ticked sources. Five, Better answers, fewer surprises: the worker says, "Nice! Now I know where it came from," and the robot says, "Grounded answers make everyone happier!"](images/strip2.png)
RAG means Retrieval-Augmented Generation: finding relevant material and using it as context for a generated answer.
- Start with source documents, such as a charter and meeting minutes.
- Relevant passages provide context for the question.
- The model generates an answer; citations let you inspect the supporting material.
Gemini Notebook is grounding you can use every day. Here’s what it is.
What is Gemini Notebook?
An AI research assistant organised around notebooks and your source documents.
What it does
Answers questions across your documents with citations, summarises them and turns them into reusable outputs.
Business value
Less time hunting for passages, more time checking what they say and deciding what to do.
Formerly NotebookLM — renamed Gemini Notebook in July 2026. Same notebooks and features; notebooklm.google.com still opens it.
You know why answers need sources. Module 2 opens the notebook where your sources live.
Three areas, three jobs.

- Sources (left): add and inspect the material you want to work with.
- Chat (middle): ask questions, refine answers and open citations.
- Studio (right): create notes and outputs such as reports and audio overviews.
The left panel decides what Chat can see, so start there.
Add, inspect and select sources.

The answer depends on the sources you select.
- Add: upload PDFs, Google Docs, web pages or pasted text — up to 50 sources on the free plan.
- Inspect: open a source to check its title, status and version, and read its Source guide.
- Select: tick the sources Chat may use. Unticked sources stay in the notebook.
Before you add your own documents, one question: what is safe to upload?
What is safe to upload?
Today’s files are fictional. Before you upload work documents, check what belongs in a notebook.
Fine to upload
- Documents your organisation allows you to use with AI tools.
- Approved, current versions of project and policy documents.
- Public material such as published reports and web pages.
Keep out
- Personal data: IC numbers, salaries, health or performance records.
- Client-confidential or restricted documents without approval.
- Passwords, keys and other credentials.
You know what goes in and what stays out. Time to build your first notebook.
Exercise 1: set up the Learning Hub notebook.
- Goal
- Create one notebook for the project and see how the selected source changes the answer.
- Time
- 18 minutes · individual
- You need
- Gemini Notebook and the five project PDFs you downloaded in the ready check.
- Steps
- Click Create new notebook. In the pop-up, upload the five PDFs from your Downloads folder (if an upload fails, choose Copied text and paste the document’s text instead).
- Click the title at the top and rename it Learning Hub Pilot.
- Open each source and check its status and version.
- Tick only the approved charter (01) and ask “When does the pilot start, and what is the budget?” Repeat with only the draft (02).
- Save a note: which answer applies and why. Then tick all five sources again for the next exercises.
- Done when
- Both answers shown, and you can name the one that applies: 3 November 2026 and RM10,000, from PRJ-01.
- Save in notebook
- A note: which charter applies, and why
- Finished early?
- Tick both charters and ask the same question. Does Chat say which one is approved, or mix them? Note what it does with the conflict.
Stuck? Play one step, try it, then press Next step.
Notebook built and two answers compared? Let’s see what the selected source changed.
The right source gives the right answer.
What Exercise 1 showed, and where it pays off at work.
What you learned
- A notebook only knows the sources you add. One notebook per project keeps answers focused.
- Selecting a different source changes the answer: the draft charter says 1 October and RM12,000; the approved charter says 3 November and RM10,000.
- Check each source’s status and version before you rely on it.
Apply it at work
- Policies and SOPs: load only the current version; keep superseded ones clearly labelled for comparison.
- Projects and clients: one notebook each, with version and date in every file name.
- Before a meeting: untick drafts and ask questions of approved documents only.
The right sources give the right answer. Module 3 is about asking the right question.
A useful prompt specifies the job.
Choose the kind of question you need, then say who the answer is for and what shape you want.
| Question type | Use it to | Learning Hub example |
|---|---|---|
| Factual | Find one fact | “What is the budget cap in the approved charter?” |
| Summarising | Condense a source | “Summarise the steering committee minutes in three bullets.” |
| Comparative | Contrast two sources | “How does the draft charter differ from the approved charter?” |
| Synthesising | Connect sources | “Which risks in the register also appear as open issues in the minutes?” |
Using only the approved charter, write a three-bullet briefing for a new team member: when the pilot starts, the budget, and who leads the project. Cite each claim. If a detail is missing, say it is not documented.
A good prompt gets you a cited answer. Next comes checking that citation.
A citation is a place to check.

Check that the passage supports the exact claim, including dates, amounts and conditions.
- Find the citation number after a claim, such as [1].
- Click it to open the highlighted passage in the source.
- Read it: does it support the exact date, amount or name?
- If the source is silent, write “not documented”. Do not fill the gap with a guess.
So a citation is where checking starts. Try it on four questions and a team briefing.
Exercise 2: ask, check and save.
- Goal
- Ask four kinds of question, then prove each fact in a team briefing against its source.
- Time
- 22 minutes · individual, then swap with a partner
- You need
- Your Learning Hub Pilot notebook with all five sources ticked.
- Steps
- Ask the four example questions from the “A useful prompt” slide (factual, summarising, comparative, synthesising). Open one citation for each answer.
- Paste the team-briefing prompt below, then follow up: “Make it shorter without adding facts.”
- Click each citation and check the start date, budget and project lead against the passage.
- Ask “What is the contingency budget?” Record the answer as not documented.
- Save the checked briefing as a note. Swap with a partner: can they trace one fact to its source?
- Done when
- Four question types tried, three facts checked, one gap recorded and a note saved.
- Save in notebook
- Your checked team briefing as a note
- Finished early?
- Rewrite one example question with an audience and a format, e.g. “for the sponsor, in three bullets”. Compare the two answers: what changed, and did any fact change?
Stuck? Play one step, try it, then press Next step.
Using only the approved charter, write a three-bullet briefing for a new team member: when the pilot starts, the budget, and who leads the project. Cite each claim. If a detail is missing, say it is not documented.
Briefing checked and saved? Here’s what the checking caught.
A citation is where checking starts.
What Exercise 2 showed, and where it pays off at work.
What you learned
- Factual, summarising, comparative and synthesising questions give four different kinds of answer.
- A citation shows where to look. You still compare the claim with the passage.
- “Not documented” is a useful answer: it tells you what to ask a person.
Apply it at work
- Emails and briefings: ask for cited bullet points, then spot-check names, amounts and dates.
- Questions from managers or clients: when the source is silent, say so instead of guessing.
- Save the checked answer as a note so colleagues reuse checked facts.
Asking and checking work on any document. Module 4 puts them to work on real project tasks.
One notebook, three project tasks.
The same method works on the documents every project produces.
A. Proposal vs approval
Compare a supplier proposal with the charter and minutes. A proposal is not a decision.
B. Minutes to actions
Turn minutes into actions with owners and deadlines. Keep suggestions separate from decisions.
C. Risk register check
Check every risk has a score, an owner and a response. Flag the gaps.
Three tasks, one notebook. Before you split up, meet the panel that turns sources into outputs.
Studio turns your sources into outputs.

Studio is the right-hand panel. Pick a tile and it builds an output from the sources you ticked.
| Tile | What you get |
|---|---|
| Reports | An interactive report, or a structured text document from a template you can edit |
| Audio Overview | A podcast-style discussion of your sources |
| Video Overview | Narrated slides that explain the main points |
| Mind Map | The topics and how they connect |
| Flashcards, Quiz | Questions to test yourself on the key facts |
| Infographic, Slide Deck | A one-page visual or a draft set of slides |
| Data Table | Rows and columns you describe, ready to export to Sheets |
Three habits
- Tick first. Studio starts from the sources you ticked; each settings window shows which it will use.
- Customise. Before you generate, say who it is for and what to focus on.
- Treat it as a draft. Open the output and check its claims against the sources.
A Studio report takes a few minutes to build, so start one now.
Set a report building before Exercise 3.
Studio takes a few minutes, so start it now. It builds in the background while you work, and you check it in Exercise 4.
2 minutes · Everyone, in your Learning Hub notebook
- Sources (left): tick PRJ-01 charter, PRJ-03 minutes, PRJ-04 proposal and PRJ-05 status report. Untick PRJ-02, the old draft.
- Studio (right): click Reports. Leave the format as it is.
- Click the pencil on the template, replace its text with the prompt below, and click Generate now.
- Leave it running and carry on. If your AI Usage bar is nearly full, choose Generate later; the trainer will share a copy.
Write a steering committee briefing on the Learning Hub pilot covering budget, approvals and risks. Use a short section for each, and a table for the risks with owner and response. Use only facts from the sources and mark anything missing as "not documented".
Stuck? Play one step, try it, then press Next step.
While the report builds in the background, take the three tasks one at a time, starting with the proposal.
Exercise 3A: can we sign the supplier’s offer?
Three short tasks on the same notebook, one after another and on your own. About seven minutes each; the answer follows each task. Your Studio report keeps building in the background.
About 7 minutes · on your own
- Sources (left): untick all, then tick only PRJ-04 proposal, PRJ-01 charter and PRJ-03 minutes.
- Copy the prompt below, paste it into Chat (middle) and send.
- Click two citation numbers in the answer. Does the highlighted passage really say that?
- Ask the practice question: list the payment stages. Is staff (end-user) training included?
Compare the supplier proposal with the approved charter and the steering committee minutes. Make a table with columns: item, proposal, charter or minutes, conflict?, citation. Then answer: can we sign with Meridian now? Cite what is still missing. Do not infer approval from a proposal.
Table made and two citations checked? Compare it with the answer.
A. Proposed does not mean approved.
Meridian proposes RM12,000. The approved charter caps the budget at RM10,000.
What your table should show
- RM12,000 is RM2,000 over the RM10,000 cap.
- No purchase approval is recorded (PRJ-01, PRJ-03).
- Meridian proposes 1 October; the charter targets 3 November.
- Data migration is excluded, and nobody owns existing training records.
The proposal isn’t approved yet. So what did the minutes actually ask people to do? That’s task B.
Exercise 3B: who must do what, and by when?
About 7 minutes · on your own
- Sources (left): untick all, then tick only PRJ-03 minutes and PRJ-05 status report.
- Copy the prompt below, paste it into Chat (middle) and send.
- Click two citation numbers in the answer. Does the highlighted passage really say that?
- Ask the practice question: use the status report to give each action its current status.
From the steering committee minutes, produce a table: action, owner, deadline, status and citation. Separate decisions from suggestions. Write “not assigned” when no owner is given.
Action table done? Here’s what it should show.
B. Turn minutes into an action list.
A helpful summary keeps who does what, and by when.
What your table should show
- Aina Rahman: request revised pricing within the cap, plus support times and cancellation terms, by 18 September.
- Kumar Selvam: check staff account access by 19 September.
- The 3 November start is a suggestion in the minutes, not a decision; the charter approved it later, on 22 September.
- Existing training records: not assigned.
Every action has an owner except one. Task C shows why that gap matters.
Exercise 3C: which risk has no owner?
About 7 minutes · on your own
- Sources (left): untick all, then tick only PRJ-05 risk register and PRJ-03 minutes.
- Copy the prompt below, paste it into Chat (middle) and send.
- Click two citation numbers in the answer. Does the highlighted passage really say that?
- Ask the practice question: which decision in the status report would close R3?
- Under the answer you checked, click Save to note.
From the risk register, list each risk with its score, owner, response and citation. Flag any risk without an owner or a response, and say which open issue in the minutes it matches.
Risks listed and the gap flagged? Here’s the full register.
C. Every risk needs an owner and a response.
A risk register is only useful if the gaps are visible.
What your table should show
- R1 · 16 High · Aina · pricing requested, not received.
- R2 · 9 Medium · Kumar · six accounts to fix.
- R3 · 16 High · no owner, no response.
- R4 · 9 Medium · Dr Farah Ismail · weekly reminders.
Put the three tables side by side and a pattern appears: facts, proposals and unknowns.
Facts, proposals and unknowns are different things.
What Exercise 3 showed, and where it pays off at work.
What you learned
- A proposal is not an approval. Compare it with what was actually decided.
- An action needs an owner and a deadline, or a visible “not assigned”.
- A risk without an owner or a response is a gap to escalate, not a detail.
Apply it at work
- Quotes and contracts: check price, dates and exclusions against the budget and approvals before signing.
- Meeting minutes: turn notes into an action table and send the gaps to the owners.
- Team reviews: split the documents across people, then compare findings before the meeting.
You’ve sorted fact from proposal. Take a break while your report finishes.
Take fifteen.
Back in 15 minutes. Your Studio report keeps building while you are away.
When we’re back, your report is ready: four sources combined into one. That has a name, synthesis.
Synthesis: combine sources into something new.
Welcome back. Your report should be ready, and it is a synthesis: four sources combined into one briefing.
Summarising makes one source shorter. Synthesising puts several sources together to answer a question none of them answers alone.
Summarise or synthesise?
- Summarise: “What do the minutes say?” — one source, shorter.
- Synthesise: “Can we sign with Meridian?” — the proposal, the charter and the minutes together (PRJ-04, PRJ-01, PRJ-03).
- Task A in Exercise 3 was a synthesis: three sources, one answer to “can we sign?”.
Synthesise well
- Tick every source the question needs, and only those.
- Ask a question that needs them together, such as “can we sign?”.
- Ask for a citation per claim, so you can see which source says what.
- Look for where the sources disagree. That is often the finding.
Synthesis can take many forms. The skill is matching the form to the audience.
Which Studio output for which job?

Start from the job and the audience, then pick the output. Every one comes from the same checked sources.
| You need to… | Use | Learning Hub example |
|---|---|---|
| Brief a decision-maker | Reports | Steering committee briefing on budget, approvals and risks |
| Compare or track items | Data Table | Actions with owner, deadline and status, exported to Sheets |
| Onboard a new team member | Flashcards | What a new Learning Hub team member needs to know |
| Update a busy sponsor | Audio Overview (Brief) | A two-minute status update |
| Stress-test a proposal | Audio Overview (Critique) | The Meridian proposal, critiqued against the charter |
| Explain to everyone | Video Overview (Short), Infographic | Learning Hub pilot at a glance, for all staff |
| See the whole picture | Mind Map | Workstreams, risks and decisions in one map |
| Present at a meeting | Slide Deck (Presenter Slides) | Five slides for the next steering meeting |
| Check understanding | Quiz | Ten questions after the pilot briefing |
Before you share
- Notes: save each checked answer with its source.
- Review: every output is a draft; check its claims against the sources.
- Share: Viewer for readers, Editor only for people who maintain the sources.
Choose two audiences and make one output for each, after you check the report.
Exercise 4: two audiences, two outputs.
- Goal
- Check your report, make one output for the sponsor and one for a new starter, then check who can see your work.
- Time
- 18 minutes · individual
- You need
- Your Learning Hub Pilot notebook and the Studio report you started before Exercise 3 (or the trainer’s copy).
- Steps
- Save one checked finding as a note, with its source.
- Open the Studio report you started before Exercise 3 and check two claims against their sources.
- For the sponsor: click Audio Overview, choose Brief, and type the focus “a two-minute status update for the project sponsor”. Generate now.
- For a new starter: click Flashcards (or Mind Map) and type the topic “what a new Learning Hub team member needs to know”. Generate now.
- When each is ready, check one claim against the sources. Neither should add facts the sources do not contain.
- Open Share and check the access settings. Do not invite anyone or make it public.
- Done when
- A saved note, two report claims checked, two outputs for two audiences checked, and you can say who can open the notebook.
- Save in notebook
- Your checked note; both outputs stay in Studio
- Finished early?
- Make a third output for a third audience, such as an Infographic for all staff, and check every figure on it.
Stuck? Play one step, try it, then press Next step.
Outputs made and sharing checked? Here’s why you check once and reuse many times.
Save checked work once. Reuse it carefully.
What Exercise 4 showed, and where it pays off at work.
What you learned
- A note keeps a checked finding together with its source.
- A Studio output is a draft. Customise it for its audience, then review it before it leaves your desk.
- Sharing settings decide who can open your notebook and what they can change.
Apply it at work
- Build a team notebook of checked answers to recurring questions, such as onboarding or policy queries.
- Turn a checked brief into a report or audio overview for busy stakeholders, after you review it.
- Share as Viewer by default; give Editor only to people who maintain the sources.
Your checked findings are saved. Module 6 gives them a shape everyone knows: a RACI and a timeline.
Name the framework: RACI and timeline.

Name a familiar structure: RACI shows who does what; a timeline shows when.
| Role | Meaning | Learning Hub example |
|---|---|---|
| R · Responsible | Does the work. | Aina Rahman requests revised pricing (minutes). |
| A · Accountable | Owns the outcome or final sign-off. | Dr Farah Ismail for the pilot as a whole (charter); not documented per action. |
| C · Consulted | Provides input through discussion. | Not documented; confirm with the sponsor. |
| I · Informed | Receives progress or outcome updates. | Not documented; confirm recipients. |
Naming the framework is most of the prompt. Build both tables in Studio.
Exercise 5: a RACI and a timeline as Data Tables.
- Goal
- Build two framework tables in Studio, check them against the sources and send one to Sheets.
- Time
- 17 minutes · individual
- You need
- Your Learning Hub Pilot notebook with all five sources ticked.
- Steps
- In Studio, click Data Table, paste the RACI description below and click Generate now.
- Click Data Table again, paste the timeline description and click Generate now.
- Open the RACI table. Check one row against the minutes: any role they do not state must say “not documented”.
- Open the timeline table. Check three dates and their status: decided, proposed or completed.
- On one table, open ⋮ and choose Export to Sheets.
- Done when
- Two tables built, one RACI row and three dates checked, the gaps still visible, and one table in Sheets.
- Save in notebook
- Both tables stay in Studio; one is also in Sheets
- Finished early?
- Make an Audio Overview in the Critique format: “Critique the Meridian proposal against the approved charter.” Note one point the hosts make that you would check.
One row per follow-up action in the steering committee minutes. Columns: action, Responsible, Accountable, Consulted, Informed. Write “not documented” in any cell the minutes do not state.
One row per key date across all sources, oldest first. Columns: date, event, status (decided, proposed or completed).
Tables built? Compare them with what the sources actually support.
What your RACI and timeline should show.
Compare your two tables with these. Every gap should still say “not documented”.
RACI
- Revised pricing: R · Aina Rahman.
- Staff access check: R · Kumar Selvam.
- Existing training records: not documented.
- Every A, C and I cell: not documented. Dr Farah Ismail is accountable for the pilot as a whole, not per action.
Timeline
- 1 Sep · draft charter
- 14 Sep · supplier proposal
- 15 Sep · steering committee decisions
- 19 Sep · access check done
- 22 Sep · charter approved
- 1 Oct · supplier’s proposed start (proposed only)
- 3 Nov · target pilot start
Look at the empty cells. They’re the most useful part of the table.
Name the framework. Then check the result.
What Exercise 5 showed, and where it pays off at work.
What you learned
- Naming a framework such as RACI or a timeline gives structure with a one-line prompt.
- A framework organises the facts in your sources. It does not supply missing ones.
- A timeline separates decided, proposed and completed dates; empty RACI cells show who to ask.
Apply it at work
- Project kick-offs: draft a RACI from the minutes, then confirm owners with the team.
- Status updates: build a dated timeline across documents before a steering meeting.
- Keep prompts short: source + framework + outcome. Add detail only when the result needs it.
That’s the whole method: sources, questions, checks, outputs, frameworks. Can you explain it yourself?
What can you now do on your own?
Answer these four questions aloud with a partner, or in a note in your notebook.
- What are GenAI and an LLM, and what is one limit?
- How does grounding help, and why must you still check a citation?
- Which prompt did you improve, and what changed?
- Which checked finding and which “not documented” gap can you show from your notebook?
If you can explain it, you can use it. Pick one task to try this week.
Your next step at work.
Use today’s method on one real task this week.
- Pick one work topic or project.
- Gather the three to five current documents, with version and date in each file name.
- Write the first three questions you would ask.
- Choose one framework to try: a RACI or a timeline.
- Open two citations before you share anything.
- Save the topic and your three questions as a note.
For that first real task, keep these guides close.
Keep the working guides nearby.
Practise with the sample project before using workplace material.
- Exercise pack: the five Learning Hub project PDFs
- Studio guide: use cases, prompts and steps for every Studio output
- Google: answers and citations
- Google: create a notebook
Last slide: the course handout, the feedback form, and how to stay in touch.
Terima kasih — let’s stay in touch.
Before you go: save the course handout, and give us two minutes of feedback.
