SageMaker Data Prep SQL Quickstart — Athena/S3 Query Workflow
AWS SageMaker
Quickstart guide
Product ownership instinct — documented a full new feature, identified that users would hit a dead end without a guided path, and built one without being asked. Then used the documentation as a live diagnostic tool with the PM auditing the feature.
The situation
A new SQL integration feature landed in SageMaker Studio — Athena, S3, Glue crawler setup, IAM permissions, JupyterLab connection — with no guided path for users. The setup was genuinely cumbersome: multiple services, non-obvious dependencies, no clear starting point. Users attempting this workflow would hit a dead end.
The task
Nobody assigned this. Document the full feature and build a quickstart that gives users a working path from setup to first query.
What I did
Documented the full SQL integration feature across all its components. Built the quickstart self-directed — Athena workgroup config, Glue crawler setup, IAM permissions, JupyterLab connection — into a single guided path. Then ran a two-hour screenshare with a principal PM auditing the feature, walking through the setup using only the doc. The friction was visible in real time.
What happened
The principal PM acknowledged the UX problems. The feature didn't get traction — people moved on to the next thing, which was expected. The quickstart exists. The problems were surfaced and documented. That was the outcome within reach.
Product ownership instinctActs without being toldUX diagnosis via documentationSelf-directed investigation