Michael Oakes
Personal / Professional

Michael Oakes

I help teams manage Microsoft 365, connect their software, and understand what’s changed in the tools they use every day.

Contact Michael
01 / About

How I work

My work combines technical support and communication: I configure permissions and integrations, explain the change, and look for ways to reduce repetitive work.

Profile and professional background

A home for Michael Oakes’s working notes, projects, and carefully sourced public work.

Thoughtful systems, evidence-led decisions, and writing that respects the difference between what is known and what is still open.

Michael helps teams keep work moving by making Microsoft 365 administration, SaaS connections, and day-to-day support easier to understand.

His background spans technical operations and creative work: configuring permissions and integrations on the backend, then explaining the change clearly to the people who use it. He is especially interested in practical workflows that reduce repetition and keep a team’s tools legible.

ApproachClear scope, visible evidence, honest uncertainty.
FocusMicrosoft 365, SaaS workflows, and technical support.
StrengthConnecting systems with communication people can use.
SourceProfessional details aligned to LinkedIn.
02 / Projects
Playable project

Mosaic Together

Rotate colorful tiles to complete a shared picture. Play solo or invite friends to the same canvas.

1–6 players · Browser game · No account needed

Play Mosaic Together ↗

Case studies

Detailed accounts of the problem, the work, and what the evidence supports. Each includes its sources and remaining limitations.

Evidence coordination

Making a complex public record usable

How Cedar Lake research organizes agency records, duplicate files and unresolved questions into a public source trail.

Status
Published project · ongoing research
Evidence
Public site and dated production review
Read the case study →
Information design

A portfolio that shows its working

How this site uses concise introductions, expandable detail and explicit project status to make complex work easier to understand.

Status
Implemented · AI-assisted
Evidence
Site source and saved layout history
Read the case study →
AI coordination

Project Conductor: defining what “done” means

From missing run evidence to an accepted reporting-control run, with task outcomes kept explicitly unverified.

Status
Historical reporting-control run accepted
Evidence
Committed packet, evaluation and retained run receipts
Read the case study →
Knowledge operations

Office Space: making AI handoffs accountable

Portable operator guides, a structural validator and explicit delivery records for supervised AI work.

Status
Implemented validator · synthetic tests
Evidence
Source, manifest and retained receipts
Read the case study →
AI-assisted development

Mosaic Together: building and evaluating a cooperative browser prototype

Implemented multiplayer controls, reported historical tests and the owner’s subsequent rejection of the prototype.

Status
Published prototype · subsequently rejected
Evidence
Recovered deployed source, test suites and historical reports
Read the case study →
03 / Family history

Public family history

No public family-history links yet. Private family research stays unlinked; only specifically approved public material belongs here.

04 / Contact

Get in touch

For professional conversations: michael@dmoakes.com