TECHNICAL WRITER / DOCUMENTATION SPECIALIST

Open to opportunities

Make complex work
make sense.

I’m Nick, a technical writer. I turn complex product behavior into documentation people can use—from a single feature guide to an entire release.

Read my work

01 / PUBLISHED WRITING

Clear words.
Real products.

Documentation published on Microsoft Learn, from complete release guidance to focused feature articles and migration instructions.

01

MICROSOFT LEARN / PUBLISHED EXAMPLES

From product change to a clear next step.

Intune guidance for multiple managed accounts, Windows app inventory, Power BI connector migration, and Edge for Business security, plus the complete Office LTSC 2024 documentation set.

02 / PROJECTS & TOOLS

Projects
and tools

Alongside writing documentation, I built an AI workflow to automate release work, reporting, and improvements to my tools. The assistant gathered information, carried out the steps, and saved the results.

Documentation tools

AI workflows I built for documentation, from working tools to tested prototypes.

AGENT WORKFLOW / FEATURE TO DOCUMENTATION

Atlas

I designed Atlas to carry a feature through the documentation workflow: gather its context, connect each claim to a source, draft the content, and route changes for review.

Its agent instructions work with Python tools for persistent dossiers, lifecycle decisions, affected-document planning, and ownership checks.

  1. 01 / UNDERSTANDFeature context and sources
  2. 02 / SYNTHESIZEA dossier that keeps the evidence
  3. 03 / PREPAREDrafts and document plans
  4. 04 / REVIEWDecisions, ownership, and handoffs

RELEASE & CONTENT OPERATIONS

Release and content tools

I built AI workflows to manage Intune documentation releases. The assistant gathered product context, drafted announcements, staged approved article updates, and checked publication status.

Supporting scripts checked readiness, updated monthly dashboard queries, and handled article maintenance. I defined the process and reviewed the drafts and release changes.

REPORTING

Weekly Reports

I built Weekly Reports to automate the reports I sent to my manager. The assistant captured work during sessions and gathered Git, email, Teams, and calendar activity, then organized it into the report.

The workflow generated Markdown and HTML copies covering deliverables, collaboration, lessons, and next steps. I reviewed the reports; saved weekly records also supplied material for performance-review drafts.

SOURCE REVIEW

Learn from Source

I built Learn from Source to have AI read an article, document, or repository and assess ideas against my projects. The assistant checked credibility, relevance, and the instructions already in use.

AI prepared specific changes for review, applied the accepted edits, and recorded their source. I designed the evaluation process and reviewed the proposed improvements.

SESSION REVIEW

Reflect / Daily Reflection

I built Daily Reflection to have AI review automatically saved working sessions. It processed the records, found corrections and recurring problems, and used the findings to improve the instructions.

The assistant saved the findings and added accomplishments, lessons, and tooling changes to the weekly report notes. Changes that needed my judgment came back for review.

The tools shared their working records. AI captured completed work as it happened, reflection added lessons and tooling problems, and reporting organized those inputs into the weekly update. Learn from Source also supplied reviewed improvements to the reflection instructions.

The toolkit includes adapted Agency Playground components. Its learning loop also draws on Karpathy’s autoresearch.

Independent projects

I also build projects outside my documentation work, using AI coding assistance.

03 / THE PERSON BEHIND THE WORK

A writer’s eye.
A builder’s instinct.

Nick White
Technical writer & documentation engineer
Marietta, Georgia

Nick with his family in front of an underwater backdrop at the Georgia Aquarium.
With my family at the Georgia Aquarium.

My work starts with a practical question: what does someone need to understand so they can move forward?

Across 18 years of Microsoft work, as an employee and contractor, I’ve worked in support, troubleshooting, and technical documentation. That path took me from customer questions and escalations to Office and Microsoft 365 Apps guidance, then into Intune feature and release documentation.

Read my résumé

Outside of work

I’m Nick, a husband and dad of six. My wife and I have been married for almost 12 years, and our calendar tends to fill itself. Between dance, ballet, music, and everything else the kids have going on, there isn’t much downtime.

When I do get some time to myself, I love making things. I enjoy woodworking, especially woodturning, and I can happily spend hours building tools with AI. Sometimes that means working with wood; sometimes it means figuring out how to get a new tool to do what I have in mind. Either way, I enjoy having an idea and seeing what I can make of it.

HAVE SOMETHING COMPLEX?

Let’s make it useful.

nicholas.scott.white@gmail.com

I’m open to technical writing, documentation engineering, and knowledge systems opportunities, including consulting. I can help teams connect their tools, organize their information, and build AI workflows that automate recurring work.