Skip to main content
Laura Schoichet

Global technology consultancy · 2023–Present

Spec-driven platform leadership

Replaced months-long requirements cycles to clarify a multi-application platform, contributing to $11.6M in renewals.

Group Product Manager

Spec-drivenAI-nativePlatformLeadership

Client systems, agency names, and internal artifacts are omitted.

Abstract illustration of overlapping RFCs, product specs, and a prototype frame—the operating system used when client screens cannot be shown.
Renewals and expansion
$11.6M
Requirements cycle time
Months → weeks
Release cadence

Situation

I lead product strategy across a multi-application licensing platform inside a highly regulated environment. The work spans several product managers, engineering, operations, design, and executive stakeholders. Ambiguity was expensive: requirements took months, implementation intent drifted, and partners lacked a shared picture of what “done” meant.

Constraint

This is public-sector work and I cannot show internal systems, named agencies, or screenshots. What I can show is the product model enhancements that made delivery faster without lowering the quality bar.

Decision

I treated product requirements as a specification problem, not a document-volume problem.

  1. RFC-based collaboration. Replaced reactive roadmaps with written proposals that engineering, operations, and product could argue with in the open. Ambiguity had a place to go instead of hiding in slide decks.
  2. Prototype before scale. Used Figma to validate concepts with customers and partners before committing to full-scale development. The goal was risk reduction, not polish.
  3. Leadership as leverage. Mentored 5 analysts and product managers and drove alignment so the operating model survived beyond any one initiative.

Outcome

  • Combined client contract renewals and expansions of $11.6M. I did not own the commercial relationship alone. What I owned was the product operating model that made modernization measurable: RFCs, prototypes, and a shared definition of done that partners could trust enough to renew and expand.
  • Time to requirements moved from months to weeks or days.
  • Release cadence tripled, with stronger partner confidence because the written record aligned with what shipped.

What I would do again

I would certainly implement the product model practices including roadmapping and requirements documentation along with prototyping alongside stakeholders.

What I would change

This project did not allow for agentic development. If I could change it, I would write the spec as if an agent will implement it, then have the team review and prototype.