Working Principles & Professional Ethics.
Clear documentation depends not only on writing skill, but on judgment: what to verify, what to question, what to protect, what to disclose, and what must never be published without evidence.
How trust is built into the work.
These are not abstract values. They shape practical decisions throughout research, writing, review, delivery, and long-term documentation ownership.
I take responsibility for the final result.
AI and other tools may support research, information mapping, terminology checks, structural exploration, and quality-control tasks. They do not own the result.
Every deliverable is reviewed for accuracy, clarity, consistency, audience fit, and potential risk before it is submitted or published.
I verify before I state.
Technical claims, medical information, product behavior, statistics, commands, terminology, and references are checked against the most appropriate available sources.
Depending on the project, this may include official documentation, engineering materials, product environments, peer-reviewed research, regulatory guidance, or expert confirmation.
I work from real knowledge—not generic summaries.
Strong documentation cannot be built from surface-level content alone. I review original source material, identify contradictions, prepare focused questions, and interview engineers, clinicians, researchers, product owners, and other specialists where needed.
The goal is not to repeat what already exists, but to establish what is accurate, relevant, usable, and worth preserving.
I write for the people who must act on the information.
Developers, end users, support agents, patients, executives, and compliance reviewers need different levels of detail, context, terminology, and guidance.
I adapt the document to the audience without distorting the underlying meaning. Clarity does not mean oversimplification, and technical depth does not justify unnecessary complexity.
Confidential data stays inside the agreed environment.
Client materials are handled according to the project’s access rules, security requirements, and approved toolset.
Confidential information is not uploaded into public or unauthorized AI systems. When AI-assisted tools are permitted, I use only the data and environments explicitly approved for the project.
I follow professional standards without writing by template.
I work with relevant documentation style guides, accessibility principles, terminology standards, citation systems, and client-specific editorial requirements.
These may include plain-language principles, internal style sheets, APA, AMA, or other professional frameworks. Standards create consistency; they do not replace judgment.
I make uncertainty visible.
I distinguish confirmed facts from assumptions, open questions, unresolved contradictions, and items awaiting expert review.
Feedback is documented, revisions remain traceable where the workflow allows it, and uncertainty is not quietly hidden inside polished prose.
I explain value without overstating capability.
Product writing should help the audience understand what a feature does, which problem it solves, and how it fits into a real workflow.
I avoid exaggerated claims, vague promises, and marketing language that creates expectations the product cannot support. Accurate product communication strengthens adoption and trust.
Confidentiality is part of the work—not an obstacle to it.
Much of the most substantial senior-level documentation work involves unpublished products, proprietary systems, source code, internal processes, medical information, customer data, strategic roadmaps, or other restricted materials.
These projects are often protected by NDAs and cannot be displayed publicly. I do not disclose confidential information, use protected client work as promotional material, or upload restricted documents into unauthorized tools simply to prove that the work exists.
When a public sample is unavailable, I can demonstrate expertise through approved portfolio materials, anonymized or reconstructed examples, methodology, documentation audits, interviews, practical assessments, and a clear explanation of the decisions behind the work.
Protecting a client’s information is not a gap in the portfolio.
It is evidence of professional reliability.
Proof without disclosure.
Senior documentation expertise is visible not only in a finished page, but in the quality of the questions, decisions, sources, structure, and risk awareness behind it.
Approved public samples
Published work that can be shared without contractual or confidentiality restrictions.
Anonymized or reconstructed samples
Representative examples rebuilt without confidential data, proprietary details, or identifying information.
Methodology
A clear explanation of research, information architecture, validation, editorial judgment, and quality control.
Practical assessment
A focused and reasonably scoped writing or documentation exercise when appropriate.
References
Professional references or verified feedback where permission has been given.
What I do—and what I do not do.
Professional ethics are most visible in the limits a specialist is willing to respect.
I do not use AI output, secondary summaries, or unconfirmed claims as evidence.
I remain accountable for what is delivered, regardless of which tools support the process.
Every client-facing document receives human editorial, factual, and structural review.
I do not publish protected work to strengthen a portfolio or prove seniority.
I do not claim certainty where certainty does not exist or hide unresolved risks.
Trust is not created by saying “you can trust me.”
It is created by showing how decisions are made when accuracy, confidentiality, and risk matter.
Need documentation you can trust with complex or confidential information?
Share the context, audience, product environment, and level of confidentiality involved. I will suggest a responsible way to evaluate the work and begin the collaboration.