Selected portfolio

Making sophisticated products easier to understand

The writing sample is only part of the story. This work shows the product, technical, and organizational problem behind each body of work—and what became possible.

Agentic AI platform

AI Agents

Documentation covering AI agent architecture, tools and resources, authentication, security, deployment, monitoring, limitations, and best practices.

The challenge: Give builders a coherent path through an emerging product while its capabilities, terminology, and interaction patterns were still evolving.
My role: Primary author and content owner
The work: Structured the complete documentation journey—from concepts and selection guidance through configuration, integration, monitoring, reliability, and reference material.
Why it mattered: Enabled a customer team to onboard during beta using the documentation without direct engineering consultation.
Published sample: Open published Appian documentation

Enterprise interoperability

Model Context Protocol

Technical documentation explaining MCP-connected systems, configuration, authentication, tools, resources, and enterprise implementation considerations.

The challenge: Explain a fast-moving interoperability standard in the context of enterprise permissions, authentication, deployment, and platform constraints.
My role: Primary author and content owner
The work: Connected protocol concepts to concrete Appian workflows, documenting verified and generic servers, tool discovery, API keys, OAuth, security, and deployment behavior.
Why it mattered: Created usable guidance for both sides of the protocol: Appian as an MCP client and as a server exposing enterprise data and logic.
Published sample: Open published Appian documentation

Enterprise AI portfolio

Artificial Intelligence

Guidance translating private AI, AI Skills, generative AI, enterprise governance, model capabilities, human oversight, and platform integration into usable product direction.

The challenge: Help varied audiences understand where AI capabilities fit, when to use them, and how to deploy them responsibly in enterprise workflows.
My role: Content owner and major contributor
The work: Built conceptual, procedural, governance, and decision-support content across the Appian AI information architecture.
Why it mattered: Made a broad, interconnected AI portfolio easier to navigate and positioned capabilities around user decisions rather than feature inventory.
Published sample: Open published Appian documentation

Applied machine learning

Intelligent Document Processing

Documentation covering document classification, structured and unstructured extraction, PII detection, reconciliation, OCR, and AI skill configuration.

The challenge: Turn probabilistic machine-learning behavior and configuration choices into workflows that non-specialists could understand and operate.
My role: Major contributor
The work: Explained model setup, extraction behavior, review workflows, and platform integration with precision for both technical and less technical readers.
Why it mattered: Supported practical adoption of document intelligence across real enterprise processes.
Published sample: Open published Appian documentation

End-to-end automation

Robotic Process Automation

Documentation for enterprise automation workflows, attended and unattended automation, platform integration, governance, and human-in-the-loop processes.

The challenge: Support the full learn-build-manage-troubleshoot journey for a mature automation platform serving developers, administrators, and operations teams.
My role: Content owner and major contributor
The work: Worked across task design, integrations, variables, robots and hosts, monitoring, credentials, high availability, APIs, upgrades, and troubleshooting.
Why it mattered: Created continuity across a large, interconnected documentation set spanning design through operations at scale.
Published sample: Open published Appian documentation

AI-assisted application development

Appian Composer

Establishing the language and documentation foundation for an emerging AI-assisted application development experience.

Overview: Composer spans planning and building in Appian Designer. In Plan, it helps teams translate requirements into a shared application plan across stories, personas, processes, business rules, data models, and screens. In Build, it acts as a developer agent that can create and modify connected Appian design objects through natural language while developers review proposed work and remain responsible for the result.
The challenge: This was not an established feature handed off after development. Product behavior, terminology, and user expectations were taking shape together. The documentation had to make a technically sophisticated, agentic workflow understandable while preserving essential ideas about dependencies, review and approval, permissions, security, governance, versioning, and recovery.
My role: As the original documentation owner, I developed the initial strategy, structure, and user-facing language. I investigated the technology as it changed, translated evolving concepts into a stable mental model, and kept the documentation aligned with the product through close collaboration with Product, Engineering, UX, and other stakeholders.
Beyond documentation: The work extended into the product's conceptual model. I contributed to terminology and feature-naming discussions, pairing technical understanding with the user's perspective so key concepts could be named and explained consistently across the experience and its documentation.
Scaling the knowledge: About a year before the ownership transition, I began mentoring an Appian technical writer based in India while I was based in the United States. With limited overlap in our working days, the relationship needed to work asynchronously as well as synchronously. I shared product knowledge and historical context, provided feedback, and progressively expanded her ownership without making her dependent on my availability. She developed deep Composer expertise and became its primary documentation author; I remained a mentor and source of product history as the transition took hold.
The outcome: The result is both a durable documentation domain and a successful succession: a complex, rapidly evolving AI product gained another writer capable of owning it independently. My contribution scaled from establishing the original foundation to enabling its continued growth beyond my direct authorship.
Published sample: Explore the Appian Composer documentation
This link opens the current public documentation. I originated and owned the Composer documentation and later helped transition primary authorship as the product and content continued to evolve; individual current pages may include work written or substantially revised by other writers.