Back
×
Day 2 · Wednesday 22 July 2026 · 08:00 – 14:00 · CODED

Put It to Work
numbers, knowledge, the chain.

By 2:00 today you'll have analysed a worksheet, built a deck, and learned to use Copilot bank-safe — then measured how far you've come.

Recap · Yesterday

Day 1 in five lines.

The Problem

The report is due at 10. The numbers are in Excel, the context is in a thread, the last version is "somewhere in Teams." You are the integration layer.

Copying between apps, reconciling versions, chasing context — that's a job description nobody signed. Day 2 is about retiring from it.

EXCEL THREAD TEAMS YOU THE REPORT
By The End Of Today

You'll walk out able to…

The Road Today

Four sessions.

01
Excel — numbers without the grind
Analyse, add formula columns, chart — then read the working.
02
PowerPoint — report to deck
Create from a document, generate new slides, restructure a mess.
03
Bank-safe use, security & ethics
The boundary, the data rule, and who stays accountable.
04
Wrapping up
Retake the skills-map assessment, then a short feedback survey — and out.
Excel

It's the 28th. Somewhere in the bank, someone is about to spend four hours doing exactly what they did on the 28th of last month.

Filter, pivot, eyeball, retype. The monthly grind isn't analysis — it's ceremony. The analysis is the five minutes at the end.

Think Of It Like…

An analyst pulling up a chair — who shows their working.

"what's driving the dip?"
a highlighted trend, a formula you can read, a chart
The Term

Analyse → Add → Visualise.

Copilot in Excel finds trends, writes formula columns, and builds charts — on your table, with the formulas visible. That last part matters: if you can't see the working, you can't check it.

Analysefinds the trends
Addwrites formula columns
Visualisebuilds the charts
Live Demo

Ask the worksheet.

Try this prompt
Analyze this table of branch transactions. What are the top 3 trends by month and by branch? Add a column calculating month-over-month growth, and create a chart of the top 5 branches by volume.
Quick Check
Ask the room

Copilot's growth column says 4.2%; your gut says 2%. Who's right? — Open the formula it wrote and read it. That's the difference between an answer and a spell.

Pause

Break — back in 15.

Tap the ☕ in the nav bar to run the timer.

PowerPoint

The deck is due at 4. You have a 12-page report open on one screen and a blank slide on the other. The next two hours are copy, paste, shrink the font, repeat.

Nobody's thinking about the story. They're fighting the layout. The deck ends up being the report, retyped smaller.

Think Of It Like…

A designer who already read the whole report — and starts you at draft three.

a document, a topic, or a messy deck
a structured draft you edit, not originate
The Term

Create → Generate → Restructure.

Three moves in PowerPoint. Create a deck from a document. Generate new slides from a prompt and your research. Restructure a deck that grew out of control — reorder, merge, cut. You stop originating slides and start editing them.

Createa deck from a document
Generatenew slides from a prompt
Restructurereorder, merge, cut
Live Demo

Report in, deck out.

Try this prompt
Create a presentation from this report: a 6-slide management summary — headline results, key numbers, what's driving them, outlook, risks, and a closing 'so what'. Keep every figure traceable to the source, and add speaker notes.
Quick Check
Ask the room

The generated deck looks polished and shows a figure that isn't in the report. Ship it? — Open the source. A deck inherits the document's facts only if you check them. Polish is not proof.

Pause

Quick break — back in 10.

Tap the ☕ in the nav bar to run the timer.

Bank-Safe Use, Security & Ethics

The fastest way to lose the tool is to misuse it once. One real customer number in the wrong box, one answer shipped unchecked — and the whole programme is under review.

Copilot earns its place in a bank only if we use it like bankers: inside the boundary, on the right data, with a human accountable for every output.

Security · 1 of 5 — Data Sovereignty & Training

Your data stays. It never trains the model.

Where does Burgan's data actually go when you prompt Copilot? Not where people fear.

🚫
Zero model training
Your prompts and the bank's data never train the public Microsoft model. What you type is not fed back into it.
🏛️
The Copilot tenant boundary
Everything stays isolated inside Burgan's own Microsoft 365 tenant — a walled cloud, not the open internet.
CBK-aligned
This is what lets a bank use it at all: it aligns with Central Bank of Kuwait cloud-governance and data-privacy directives.
Security · 2 of 5 — Just-Enough Access

Copilot sees exactly what you see — no more, no less.

The real internal risk isn't data leaking out. It's data over-shared in.

🔑
Inherited permissions
Copilot can only open what your login already can. It respects every permission you already have — and every one you shouldn't.
🔍
"Search on steroids" risk
If you have accidental access to a sensitive HR or Q1 finance folder, Copilot will find it and use it — instantly, without you looking.
🧹
Audit your access
Review your folder permissions and stop over-sharing SharePoint links. The fix is housekeeping, not magic.
Security · 3 of 5 — Safe Prototyping & Input Sanitisation

Never paste raw customer data. Anonymise first.

What is safe to type into a prompt — and what never is.

🛑
The golden rule
Never paste raw PII: Civil ID numbers, account numbers, balances, or passwords. Ever.
🎭
The anonymisation technique
Swap real names for placeholders. "Analyze customer Khalid Al-Sabah's loan history" → "Analyze Customer A's loan history."
🏷️
DLP & Purview labels
Sensitivity labels like "Burgan Highly Confidential" let Data Loss Prevention block Copilot from extracting the data at all.
Security · 4 of 5 — Human in the Loop

The AI is an intern. You stay accountable.

The danger is automation bias — trusting a fluent answer blindly.

🤖
Treat it like an intern
Eager, fast, capable — and it makes confident mistakes. Supervise every output the way you'd supervise a new hire.
✔️
Verification is mandatory
You are professionally and legally responsible for the final output — not the AI. Sign-off is yours.
⚠️
Know the blind spots
It struggles with complex financial math, local Kuwaiti market nuance, and PDFs with dense tables. Double-check those hardest.
Security · 5 of 5 — Ethics & Algorithmic Bias

It drafts. It never decides.

Fair, unbiased, transparent use — especially where it touches a customer.

⚖️
No autonomous decisions
Copilot never decides who gets a loan, a credit card, or a job interview. It drafts summaries; a human decides.
👁️
Spot the bias
Watch for biased or loaded language when it summarises customer complaints or performance reviews.
📝
Be transparent
If content or analysis was heavily assisted by Copilot — for an internal audit, say — note that it was.
Use Case · HR

Copilot in HR — privacy, recruiting, policy compliance.

✔ Safe productivity boosters

  • Draft job descriptions
  • Summarise policy manuals
  • Format interview templates

✕ Strict guardrails

  • Employee performance scores
  • Salary data
  • Medical-leave records
Ethical risk: automation bias when filtering CVs and evaluating candidates. A human reads the shortlist and owns the call.
Use Case · Retail Banking

Copilot in retail — protect customer PII & NPI.

✔ Permitted

  • Analyse general market trends
  • Draft customer email responses
  • Structure product FAQs

✕ Prohibited

  • Actual Civil IDs
  • Account numbers
  • Loan balances
The golden rule: abstract and anonymise every customer profile before you ask Copilot for analysis.
Use Case · IT & Developers

Copilot for IT & Dev — code security & governance.

✔ Permitted

  • Explain legacy code
  • Draft basic scripts
  • Generate documentation

✕ Prohibited

  • Proprietary app architecture
  • Security keys & secrets
  • Feeding either into public / unverified AI
The truth on hallucinations: Copilot can write broken code — and introduce security vulnerabilities. Review every line.
Before You Hit "Send"

Your day-to-day checklist.

Identification check
Did I strip out every specific name, ID, and financial number?
Sensitivity check
Is this document tagged "Burgan Highly Confidential"? If yes — handle it manually.
Logic check
Am I blindly trusting this output, or did I double-check the math and the facts?
Quick Check
Ask the room

Copilot drafts a crisp rejection letter for a loan applicant. Ship it? — No. A model can draft the words, but a human owns the decision and checks it for fairness. Boundary, data rule, accountability — all three, every time.

Pause

Lunch & prayer — back at 1:00.

Tap the ☕ in the nav bar to run the timer.

Wrapping Up

Two days ago Copilot was an icon you scrolled past. Now it works for you.

Before you go, two quick things — both take a few minutes, both matter. First we measure how far the room has moved. Then you tell us how the workshop landed.

1 · Post-Workshop Assessment

Retake the skills map.

It's the same skills-map assessment you took on Day 1 — so we can see the shift, not just the finish line. Answer honestly: it's a measure of the two days, not a test of you. Open it from the lab or scan the link below.

Open now

portal.joincoded.com/sv/microsoft-365-copilot-skills-map-burgan-bank-post — or hit Wrap up in the hands-on lab.

2 · Workshop Feedback

Tell us how it landed.

A short survey while the two days are still fresh — what worked, what didn't, what you'd change. It's how the next cohort gets a better version of this workshop. A few minutes, and you're done.

Open now

portal.joincoded.com/sv/burgan-workshop-microsoft-copilot-for-productivity-survey — or hit Wrap up in the hands-on lab.

Day 2 · Close

You are no longer the integration layer.

Two days ago Copilot was an icon. Now it drafts your documents, reads your numbers and builds your decks — and you know how to keep it inside the bank's walls. Keep the cheat sheet open, keep the checker's eye — and ship.

1 / 1
next back F full

Break timer

Pick a duration — the room sees a countdown.

Break
05:00
Back at 00:00