Who I am · How I work

Mitch Stewart

I see the big picture and the small details, I change things carefully and reversibly, and I communicate the way each person needs.

I bring a calm, curious, and practical approach to technical work. My goal is to solve the right problem, make progress people can trust, and leave behind enough context for the next person to succeed.

info@mitchellstewart.ca

My approach

Goal-first and evidence-based

Careful with systems and people

Built for clear handoffs

The way I work

Thoughtful work. Useful progress.

I start with the goal, not a preselected tool or fix. I listen to understand what is happening, look at the wider system, and work with people to choose a practical next step.

  1. 01Understand what the person is trying to accomplish and what is already known.
  2. 02Assess the issue in context: impact, urgency, risk, and who is affected.
  3. 03Choose whether to investigate further, mitigate quickly, or make a durable change.
  4. 04Use the least disruptive effective option, with a clear way back.
  5. 05Keep people informed, check the result, and document what changed and why.

What that looks like in practice

Three habits I bring to the work.

01

See the whole system and the details

I zoom out to understand how a problem fits into the wider environment, then zoom in to test the details that will reveal its cause. I learn new tools by mastering the fundamentals and mapping how the pieces connect.

When meeting-room video kept stuttering, I recorded symptoms and tests, followed a repeatable test plan, traced the issue to the root cause, implemented a solution, and set a standard for every room.

02

Make change carefully and reversibly

I understand the current state before changing it, work from the least disruptive option toward more impactful ones, and know how to return to the original state. I document both the steps and the outcome so the work can be understood and supported.

Over five years, I made more than 1,000 device policy changes without preventing people from working, rolling them out from less critical roles to more critical ones over time.

03

Communicate for the person in front of me

I listen first, explain the plain-language idea before technical terminology, and adjust the amount and format of detail to what helps each person. I set expectations, keep people updated, and follow through.

When a technical team was wary of the service desk, I learned how each person preferred to communicate and consistently did what I said I would do. Over time, they began asking me for help.

More about what I bring

The strengths behind the approach.

Explore how learning quickly, collaboration, communication, documentation, and troubleshooting show up in my work.

Explore my strengths