10. Collaboration and team contributions
This chapter connects the support knowledge-base work with training, shared writing practice, and the AI authoring workflow. The recognition chapter and full feedback preserve colleagues' and managers' own words separately from my account.
10.1 Making knowledge reusable for colleagues
In Support, I helped agents format knowledge-base articles and communicated best practices with managers and team leads. In Technical Writing, I contributed review guidance, training materials, tool instructions, and onboarding feedback. The continuity is the effort to make a useful method accessible beyond the person who first discovered it.
The AI Documentation Workflow Training Guide's process and DITA Figure Wrapper instructions are concrete examples of this transfer. They package a process or utility for other writers rather than leaving its operation in an individual conversation.
10.2 Onboarding structure and product learning
In June 2025, I reviewed Jared's new-writer training material and proposed an introduction covering the four verticals, process overviews before evaluation criteria, consistent module naming and formatting, integration of reference pages into the Foundations module, and interactive progress tracking if supported. I also supplied draft introductory copy.
The career report records February 2026 maintenance of onboarding resources, including a request to add a Technical Writer Training Links document to Foundations. Separately, I contacted Anton Wingstrand to arrange EFDD training for Ammar Zafir so the new writer could gain product understanding and hands-on lab experience. Anton agreed to add him to the next cohort. That records the arrangement, not confirmation of later attendance or completion.
10.3 Working across teams
My writing and systems work involved Product Management, Development, QA and engineering SMEs, Technical Support, Web, Data Science, IT/Help Desk, Business Intelligence, People & Culture, and Global Training. The strongest examples connect those relationships to a concrete task: clarifying feature behaviour, defining migration workflows, investigating an overwrite, obtaining repository access, or developing reusable training.
I consulted SMEs including Navya Hooda, Andrei Vesselkov, Yousef Said, and Youssef Mohamed. I worked with Taylor Watson and the Web team on Umbraco, and with Mike Van Halteren/Data Science on shared tooling and repositories.
On May 13, 2026, I contacted Adam Padzik about search visibility after observing that SOTI MobiControl did not appear on the first results page for an “Android MDM” search. He replied that his team was working on the issue and invited collaboration.
10.4 Hiring and referrals
The career and writing reports describe participation in the first Technical Writer interview round alongside Darryl Orth and Michael Caro, candidate-profile review, and later interview coordination. The reports reference hiring communications across September/October 2025 and January 2026. The exact initial appointment date should be checked against the original messages if it matters to a final career timeline.
I circulated an external Technical Writer opening and helped an internal candidate navigate an application for a Technical Lab Specialist role.
10.5 Additional contributions recovered from the review record
The review transcription identifies an Oxygen XML Troubleshooting guide, a reusable DITA task template and example, interactive network-diagram work, and analysis connecting help usage with support cases. These add concrete artifact leads to the story of improving the team's writing practice. Their technical results and measurements still need the underlying files or datasets.
My accomplishment notes also describe reverse-shadowing and peer-review training, video-first task templates, legacy-help redirect work, Power Automate video detection, a lockdown-documentation intervention, standards discussions, and first-aid/fire-warden responsibilities. The copied correspondence records delivery of a Cisco ThousandEyes deployment KB by email on 9 February 2026 and a positive reply; it does not prove publication in Cisco documentation. The notes explicitly mark the certification proposal as not pursued and the AI-prompt review with Yulia as not explored further. All of these records remain separately indexed as self-report or copied correspondence.