Four Weeks In and I'm a Beginner Again
At a Glance
- Target Audience
- M365 Content Managers, Admins, and AI Transitioning Pros
- Problem Solved
- Fear of admitting AI knowledge gaps during high-stakes M365 migrations risking business operations.
- Use Case
- AI-powered content/post migrations from legacy to new M365 systems with beginner teams.
Four weeks into my new role at Collab365, and I'm going to say it out loud: I'm a beginner again.
Mark and I have run this place as a two-person team for years. I've got decades behind me as a management accountant, starting at Tetley's, wrangling numbers and processes that didn't shift overnight. Capable. Competent. The one who keeps the books tight while Mark builds the wild ideas.
Then last week I was migrating a raft of posts from the old system to the new one, staring at the screen, and the words stuck in my throat: "I genuinely don't know how to do that."
Honestly? It felt awful.
Here's the uncomfortable bit. Saying "I don't know" about a tomato plant at the allotment is fine. Fail, replant, move on. Saying it when one wrong move could break customer access, blow up support, and tip a two-person business into a properly bad month? That's a different kind of fear. The stakes are your livelihood. That's what closes the throat up.
What I keep coming back to is this: years of experience make you expect to know everything. But AI is brand new for everybody. It doesn't care about your CV. The doctor, the lawyer, the accountant, the founder four weeks into a pivot. We've all been quietly reset to beginner - 81% of IT professionals think they can use AI, but only 12% actually have the skills.
That's such a shame in one way. In another, it's not a bad thing. Nobody gets to be the grown-up in the room anymore - 35% of professionals feel too nervous to even talk about AI at work.
What helped me wasn't pretending I knew. It was asking for a flag system on the migration. Green for done, red for problem, yellow for review. Mark built it in an afternoon and it made my life a whole heap easier. Suddenly I could see what was finished and what wasn't, and the panic dropped right down.
That was the lesson, really. The expertise I do have, decades of it, is in spotting where a process is leaking and asking for the small fix. That part still works. The AI bit I'll learn as I go.
What works now probably won't be how we do it in three months. So whatever we do, it's got to be try it and see.
The thing nobody wants to admit is that "I don't know, but I can learn" might be the only skill that holds its value from here - as 97% of organizations report AI skills gaps. Everything else gets reset every six months.
So what's the "I don't know" you've been avoiding saying out loud at work this week, and what's it costing you to keep pretending?

