×
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.
Copying between apps, reconciling versions, chasing context — that's a job description nobody signed. Day 2 is about retiring from it.
Filter, pivot, eyeball, retype. The monthly grind isn't analysis — it's ceremony. The analysis is the five minutes at the end.
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.
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.
Tap the ☕ in the nav bar to run the timer.
Nobody's thinking about the story. They're fighting the layout. The deck ends up being the report, retyped smaller.
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.
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.
Tap the ☕ in the nav bar to run the timer.
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.
Where does Burgan's data actually go when you prompt Copilot? Not where people fear.
The real internal risk isn't data leaking out. It's data over-shared in.
What is safe to type into a prompt — and what never is.
The danger is automation bias — trusting a fluent answer blindly.
Fair, unbiased, transparent use — especially where it touches a customer.
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.
Tap the ☕ in the nav bar to run the timer.
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.
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.
portal.joincoded.com/sv/microsoft-365-copilot-skills-map-burgan-bank-post — or hit Wrap up in the hands-on lab.
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.
portal.joincoded.com/sv/burgan-workshop-microsoft-copilot-for-productivity-survey — or hit Wrap up in the hands-on lab.
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.
Pick a duration — the room sees a countdown.