Definition Workflow Big Tech Best Practices

big-tech-feature

Big Tech best practices for feature-level opportunities on existing products. Starts with OpportunitySpec + OKRs, uses PR/FAQ-driven development with design docs, API-first thinking, and autonomous team practices.

Inspired by Big Tech Best Practices. The methodology is its originators’ own published work, drawn from their public writing and talks. ProductBuildersHQ has implemented it as a machine-readable workflow in VisionSpec so it can be automated — spec synthesis and LLM-as-a-Judge evaluation, built in. This encoding is an independent interpretation, not affiliated with or endorsed by its originators.

Specs in This Workflow

FAQ Required gtm Challenge assumptions, include developer FAQ

OpportunitySpec Required source 12-box opportunity canvas with OKR alignment - the starting document for features

PRD Required source Product requirements with API contracts, non-goals, and alternatives

Press Required gtm Working backwards press release for the feature

SPEC Required output

TPD Required technical Test plan with experiment design and hypothesis validation

TRD Required technical Design doc with alternatives, tradeoffs, and reversibility assessment

UXD Required source User experience with developer experience and accessibility

assumption-map Optional source Risk matrix by assumption type (DVFUE)

BMC Optional gtm Business Model Canvas extracted from MRD for stakeholder review

discovery-snapshot Optional tracking Weekly discovery summary with interviews and learnings

IRD Optional technical Infrastructure requirements

MRD Optional source

1-Pager Optional gtm Executive summary

6-Pager Optional gtm Amazon-style 6-pager for major features

OST Optional source Opportunity Solution Tree linking outcome to solutions

Pitch Optional source Shaped pitch with appetite, problem, solution, rabbit holes

shapeup-scope Optional tracking Scopes with hill chart positions for execution tracking

Synthesis Rules

How downstream specs are generated from upstream ones.

MRD BMC

Extract Business Model Canvas blocks from MRD sections 2-11. Format as standalone canvas for visual review.

OpportunitySpec +Press FAQ

Include internal stakeholder questions, customer questions, and developer/API questions (Stripe). Address risks and assumptions from OpportunitySpec.

OpportunitySpec +Press +FAQ PRD

Include API contracts (Stripe), non-goals (Google), alternatives considered (Google). Map to OpportunitySpec's critical requirements and success metrics.

OpportunitySpec Press

Write from customer perspective. Focus on the specific user value from OpportunitySpec. Frame as a bet with explicit risk (Spotify).

MRD +PRD +UXD +TRD +TPD SPEC

Unified specification consolidating all approved specs.

PRD +TRD TPD

Include experiment design with hypothesis and success criteria (Google/Spotify). Validate assumptions from OpportunitySpec. Define what 'fail fast' looks like.

PRD +UXD TRD

Google design doc format. Include alternatives considered, explicit tradeoffs, reversibility assessment (two-way vs one-way door), and scalability (10x thinking).

Methodology Principles

Customer Obsession Start with the customer and work backwards (Amazon)

Developer Experience Optimize for developer productivity (Stripe)

Accessibility First Design for everyone from the start (Microsoft)

Ten X Thinking Aim for 10x improvement, not 10% (Google)

Working Backwards Write the press release first (Amazon)

Bold Bets Take big swings on transformative ideas (Meta)

Bets Not Projects Frame work as bets with explicit risk (Spotify)

Explicit Tradeoffs Every decision has costs; make them visible (Google)

Alternatives Considered Always evaluate multiple approaches (Google)

Data Driven Decisions backed by data and experiments (Google)

Bias For Action Speed matters; two-way door decisions (Amazon)

Reversibility Prefer reversible decisions (Google)

Dri Directly Responsible Individual for every decision (Apple)

Highest Standards Relentlessly high standards (Amazon)

Api First Design the interface before implementation (Stripe)

Documentation Quality Docs are part of the product (Stripe)

Non Goals What we won't do is as important as what we will (Google)

Say No Focus means saying no to good ideas (Apple)

Peer Review RFCs ensure diverse perspectives (Google)

Disagree And Commit Truth-seeking, then commit (Amazon)

Context Not Control Provide context, not commands (Netflix)

Radical Transparency Default to open (Netflix)

Ownership Think long-term, end-to-end ownership (Amazon)

Incremental Delivery Ship small, ship often (Stripe)

Launch And Iterate Ship, measure, improve (Google)

Move Fast Speed is a competitive advantage (Meta)

Fail Fast Learn Fast Quick experiments over long planning (Spotify)

Freedom And Responsibility Freedom with accountability (Netflix)

Highly Aligned Loosely Coupled Align strategy, decouple execution (Netflix)

Autonomous Squads Small teams with ownership (Spotify)

Growth Mindset Learn from failure (Microsoft)

Frugality Constraints breed resourcefulness (Amazon)

Fixed Time Variable Scope Appetite sets time; scope flexes (Basecamp)

Appetite Not Estimates How much is it worth, not how long (Basecamp)

Shaping Define at right abstraction level (Basecamp)

Betting Not Planning No backlogs; bet on pitches (Basecamp)

Circuit Breaker Stop failures early, don't drag out (Basecamp)

Rabbit Holes Identify scope traps upfront (Basecamp)

Weekly Touchpoints Talk to customers every week (Torres)

Story Based Interviews Collect stories, not opinions (Torres)

Opportunity Solution Trees Visualize outcome to solution path (Torres)

Assumption Testing Test riskiest assumptions first (Torres)

Compare And Contrast Test multiple solutions in parallel (Torres)

Product Trio PM, Design, Engineering collaborate (Torres)

Included Assets

20 document templates · 18 LLM-as-a-Judge rubrics — embedded in visionspec.