SageMaker Training Plans — Full Feature Documentation
AWS SageMaker
Feature documentation
Greenfield information architecture and product-level thinking — the API shape was changed because of documentation feedback.
The situation
SageMaker's new GPU capacity reservation feature launched at re:Invent 2024. Net new feature: no existing content.
The task
Build complete documentation from scratch for a re:Invent launch — one of the most compressed, high-stakes delivery windows in the AWS calendar.
What I did
Working primarily from design docs and the API spec, I determined the full content scope and information architecture: concept introduction, IAM taxonomy, status lifecycle, instance types and pricing, quota management, and API reference across plan creation and utilization. Broke the feature into two personas — plan creators vs. plan users — and structured the entire surface around that split. Created the lifecycle and workflow diagrams to set the reader's mental model before diving into specifics. The engineering team authored code samples; everything else — scope, structure, organization, diagrams, and written content — is mine. Independent work under a tight deadline, with a lead SDE as technical POC and an SDM overseeing the launch.
What happened
Feature shipped at re:Invent 2024 with complete documentation. The API shape was changed based on documentation feedback. The two-persona structure became the organizing principle for the entire feature surface. The lifecycle and workflow diagrams were selected by the solutions architects authoring the launch blog, who used them as the primary illustration of the mental model.
Greenfield information architectureAPI comprehensionProduct thinkingTechnical depthSolo ownershipLaunch documentation