Jan 16
Loading video player...
In this video, I walk through how I typically brief developers — not from a non-technical product role, but as someone who writes and reviews the code myself. This is an example of a technical PRD / implementation brief that covers: API requirements Data contracts Database storage decisions Query logic Visualization behavior The goal is to show how to translate product intent into executable technical work — without ambiguity, hand-waving, or unrealistic assumptions. What this brief covers: Designing an ad platform connection flow (Facebook Ads example) Defining required API inputs and supported parameters based on official API constraints Handling OAuth-style credential input and connection initialization Persisting API responses in a structured database schema Working directly with JSON responses and mapping them to tables Supporting multiple connections / accounts cleanly Querying stored data for visualization use cases Converting query results into dataframes for plotting Using interactive visualization libraries (widgets, selectors, filters) Allowing users to dynamically choose metrics (impressions, conversions, etc.) Designing for extensibility (adding, removing, and managing connections) This is the same mental model I apply when writing code myself — and the same standard I apply when: Briefing engineers Reviewing pull requests Designing system prompts for AI agents The difference between this and a typical non-technical brief is that: Every requirement maps to real APIs Every field is validated against documentation Every step assumes actual implementation constraints Nothing relies on “the dev will figure it out later” 🧠 Why this matters Good engineering execution doesn’t start with code — it starts with clear, technically correct thinking. This video shows how I: Think like a developer Write like a product owner And hold myself to the same bar I expect from the engineers I work with 📩 Work / Collaboration If you’re looking for someone who can: Design systems Write code And brief engineers without losing technical fidelity You can reach me at: 👉 nicmrayce@gmail.com