Product Strategist

Role Overview

Every venture build starts with the same questions: how does this work actually flow, and where does the value sit? The Product Strategist is the discovery and workflow-analysis spine of Studio Enablement. You lead stakeholder interviews and produce the workflow maps, value-pool analyses, and use-case sequencing that feed our Product Architects and engineers. You

convert what stakeholders need into priority questions, acceptance criteria, data contracts, and clean product specs. And you hold the decision log that keeps each venture's product thread traceable long after the meeting ends.

What You'll Own (Outcomes)

• A steady supply of discovery output for Studio's venture builds: workflow maps, value-pool analyses, and use-case sequencing that Product Architects and engineers actually build against.

• Engineer-ready specs: priority questions, acceptance criteria, data contracts, and clean product specs that land buildable.

• Evaluation groundwork: golden and evaluation datasets, with success and time-to-answer benchmarks, defined alongside users and the Applied AI Engineer.

• Real usage: demo prep, pre-reads, follow-ups, training, and feedback loops that drive

adoption on each venture's operating cadence.

• A clean decision log: crisp memos and decision records that keep each venture's product thread traceable.

What You'll Do (Responsibilities)

• Lead stakeholder and operator interviews, and make unstructured inputs legible.

Map how work actually flows at task level, and analyze where value pools sit, including for

businesses that do not exist yet.

• Sequence use cases by value at stake and feasibility, and defend the ordering.

• Translate stakeholder needs into agentic-capability requirements: workflows rebuilt, not just enhanced.

• Write the specs builders execute against: priority questions, acceptance criteria, data

contracts.

• Help define golden and evaluation datasets and success benchmarks with users and the Applied AI Engineer.

• Run the adoption cadence: demos, pre-reads, follow-ups, training, feedback loops.

• Record why calls were made, not just what was decided, in memos and decision records others act on.