Microsoft Legal was migrating its internal SharePoint site to a new cloud environment. The existing site had grown organically over many years and was bloated with thousands of pages. Many were outdated, redundant, or no longer owned by anyone. The migration was both a technical project and a content problem: moving everything as-is would simply recreate the mess in a new location.

The site had approximately 5,000 pages with no consistent ownership, update cadence, or quality bar. Employees searching for legal guidance couldn’t easily distinguish current policy from years-old content that had never been removed. The migration presented a rare opportunity to reset if someone took on the content work proactively, rather than treating it as a lift-and-shift.

I led the content audit from end to end. Rather than waiting for content owners to nominate pages for migration, I built a proactive triage framework using two signals: last-updated date and page visitor data. We started with this aggressive archive list of pages that were both old and rarely visited.

We then gave every content owner the opportunity to request migration for their flagged content. We included a condition: a yes-to-migrate decision came with a commitment to a regular update cadence going forward. This turned the migration into an accountability checkpoint, not just a technical move.

My team and I also worked with stakeholders to establish governance standards for the new site: content ownership requirements, review schedules, and criteria for what warranted a new page versus an update to an existing one.

The new site launched with a fraction of the original content and a governance model designed to prevent the same bloat from recurring. Content owners clearly understood why we archived content and what we expected of them going forward.

I joined a project with a fixed client deadline to deliver detailed specifications as a freelance Technical Writer. Engineers needed to develop mobile components directly from the specifications, so clarity and precision mattered as much as completeness.

Early in the project it became clear that the volume of work and the level of detail required were not going to align with the deadline. Attempting to cover everything at the depth engineers needed would mean missing the deadline. Documenting all components by the deadline would negatively impact the engineers, increasing their development time as they figured things out or leading to inconsistency in the apps. The project needed someone to define what “done by the deadline” actually meant. I was asked to step into a lead role to work through it.

I quickly assessed the full scope and identified the highest priority areas for the engineering team’s immediate work. From that, I drafted a revised delivery plan: a tighter scope, completed to the right level of detail, by the original deadline with the remaining areas documented as a clearly scoped follow-on.

I pitched the proposal directly to the lead designer and project manager, framing it as a quality-over-coverage decision. Once I had their buy-in, I communicated the revised approach to the rest of the team, so everyone was working from the same plan.

When it came time to present to the client, I didn’t obscure the tradeoff. I explained clearly what we had delivered, why we had adjusted the scope, and what the path forward looked like for the remaining documentation.

The client responded positively, in part because of the honest conversation about scope. Proactively naming the tradeoff demonstrated the kind of judgment clients rely on from a senior contributor.

Aveda, a well-known brand with high standards for both accuracy and visual presentation, needed a 200-page curriculum and 50 pages of supporting materials produced within a compressed timeline. The deliverable was a content project and a brand artifact. Errors, inconsistencies, or missed handoffs would be visible and costly.

The timeline didn’t leave room for a traditional sequential workflow for the entire set of client-submitted content. A linear process would either miss the deadline or force quality shortcuts that weren’t acceptable. The project needed a parallel editorial operation with clearly defined stages, ownership, and handoff points built in from the start.

I designed and ran the editorial operation end to end. I created an editorial calendar that mapped content pieces to editors, review stages, and design handoff dates, which gave every contributor visibility into dependencies and deadlines. I also assisted with the project proposal and established a regular communication cadence with the client so there were no surprises on either side.

To solve the timeline problem, I devised a staggered approach: content pieces moved through editing, review, and handoff in overlapping waves rather than waiting for the full manuscript to be complete. This kept the design team continuously supplied with ready content and avoided the bottleneck of a last-minute rush.

I hired and managed a team of freelance editors, both onsite and offsite, and wrote a style guide to align everyone on voice, terminology, and formatting conventions. I presented the style guide to the full editorial team before editing began to make sure it was clear and usable, not just a document that sat unread.

Throughout the project I worked closely with the design lead to plan the flow of content into layouts, making sure editorial and design decisions stayed in sync rather than creating rework downstream.

The freelance team worked efficiently and consistently within the style guide and calendar. Aveda received an accurate, beautifully produced, and error-free curriculum they were genuinely proud of. Every handoff to design and to the client landed on schedule and at the expected quality level.