THE CHALLENGE

When I joined the IT team, I thought the job was simple: fix access issues, reset passwords, route tickets, and answer tech problems. I assumed my role was reactive. But that idea broke fast.

Gerald didn’t want button-pushers. He wanted contextual engineers — people who saw patterns, not just problems.

That’s when I realized: IT isn’t just about support. It’s about systems thinking.

THE EXECUTION

🔹 Step 1: Solving Tickets ≠ Solving Problems

• Help onboard users into Microsoft 365
• Fix Teams permissions
• Reset MFA and login issues

But SignalMate kept prompting:

• “What’s the root cause behind the request?”
• “Could this be solved permanently at the systems level?”

I created an internal Excel sheet called IT SignalMap – Recurring Issues & Root Systems that mapped common requests. Patterns revealed root issues like misaligned role groups and cached logins.

🔹 Step 2: Using SharePoint as an IT Memory Layer

I created structured folders like /General/Recordings and /General/Transcripts with naming logic: ProjectName_Date_Type. I also enforced security filters and created an IT Observations folder for oddities like Teams bugs or unknown login attempts.

🔹 Step 3: Security Visibility as a Habit

Guided by SignalMate prompts like:

“What signal indicates system risk before a breach?”

I regularly reviewed IP login logs, MFA logs, and closed lingering orphan accounts. I even proposed fixes to misfiring Exchange group policies — not just patched issues.

MY TAKEAWAYS

• ✅ Fixing a login is helpful. Preventing 100 of them is valuable.
• ✅ SharePoint isn’t just storage — it’s structure, context, and institutional memory.
• ✅ Security isn’t scary when you see it as pattern analysis.
• ✅ SignalMate changed how I think, not just how I click.

THE OUTCOME

• I became the go-to intern for system-level troubleshooting
• My SharePoint structure was used across departments
• I helped identify 4+ security oversights before they became problems
• My logs are now part of the SignalMate tracker system for IT signal analysis