{
  "schema_version": "1.1",
  "id": "s8:https://www.youtube.com/watch?v=1OMHGsUZiqA",
  "slug": "how-forward-deployed-engineering-is-done-at-kepler-vinoo-ganesh-0thtvuc",
  "url": "https://feed7.dev/p/how-forward-deployed-engineering-is-done-at-kepler-vinoo-ganesh-0thtvuc",
  "title": "How Forward Deployed Engineering is done at Kepler — Vinoo Ganesh",
  "why_included": "Kepler frames forward deployment as product discovery: observe real work, ship the smallest useful fix, then turn repeated pain and customer vocabulary into durable product leverage.",
  "summary": "A customer requested a **47-page specification**, 14 metrics, and a three-month BI project. On-site observation revealed the immediate need was one late-truck alert, built in **4 hours**; another pipeline reportedly fell from 17 hours to about 2.",
  "practical_implication": "Builders should watch users perform the job, ask what happens next, and solve a small repeated pain before expanding scope. Treat copied data, tab switching, recurring tasks, and overloaded terms as evidence for tools, integrations, and a product ontology.",
  "agent_context": "A customer requested a **47-page specification**, 14 metrics, and a three-month BI project. On-site observation revealed the immediate need was one late-truck alert, built in **4 hours**; another pipeline reportedly fell from 17 hours to about 2.\n\nBuilders should watch users perform the job, ask what happens next, and solve a small repeated pain before expanding scope. Treat copied data, tab switching, recurring tasks, and overloaded terms as evidence for tools, integrations, and a product ontology.\n\nSmall fixes are rarely temporary: one improvised retention script spread across a nearly **100,000-person customer** and remained in use a year later. Fast delivery therefore still needs production assumptions, ownership, and a path into the core product.",
  "source": {
    "name": "AI Engineer",
    "url": "https://www.youtube.com/watch?v=1OMHGsUZiqA",
    "published_at": "2026-07-28T16:00:00.000Z"
  },
  "source_class": "video",
  "content_type": "Video",
  "layer": "agent",
  "domains": [
    "coding",
    "data"
  ],
  "topics": [
    "harness-engineering",
    "context-engineering",
    "enterprise"
  ],
  "verification": {
    "status": "source_linked",
    "label": "Source Linked",
    "method": "source_feed",
    "verified_at": null
  },
  "uncertainty": [
    "Small fixes are rarely temporary: one improvised retention script spread across a nearly **100,000-person customer** and remained in use a year later. Fast delivery therefore still needs production assumptions, ownership, and a path into the core product."
  ],
  "connected_context": {
    "meaning": "This makes field observation the mechanism for finding the minimum useful deployment, not merely a discovery ideal: a large requested project can collapse into one production-worthy alert. It reinforces prior advice to encode real workflows and resist one-offs, while adding that even four-hour fixes need ownership and a route into the product because local tools can spread unexpectedly.",
    "corpus_size": 262,
    "generated_at": "2026-07-29T10:05:40.850Z",
    "connections": [
      {
        "title": "AI tools for Forward Deployed Engineering — Vasuman Moza, Varick Agents",
        "source_name": "AI Engineer",
        "source_url": "https://www.youtube.com/watch?v=l0FLhNqBOic",
        "feed7_url": "https://feed7.dev/p/ai-tools-for-forward-deployed-engineering-vasuman-moza-varick-agents-12kjg79",
        "reason": "Kepler supplies a concrete method for Varick’s workflow-capture principle: observe the job, follow what happens next, and automate the repeated pain actually encountered."
      },
      {
        "title": "How Forward Deployed Engineering is done at Decagon — Sunny Rekhi",
        "source_name": "AI Engineer",
        "source_url": "https://www.youtube.com/watch?v=7wu2hsRfvV0",
        "feed7_url": "https://feed7.dev/p/how-forward-deployed-engineering-is-done-at-decagon-sunny-rekhi-02myrh1",
        "reason": "The rapidly spreading retention script illustrates why Decagon warns against brittle one-offs and why repeated customer needs should migrate into product features."
      },
      {
        "title": "Do AI Agents Know When a Task Is Simple? Toward Complexity-Aware Reasoning and Execution",
        "source_name": "arXiv",
        "source_url": "https://arxiv.org/abs/2607.13034v1",
        "feed7_url": "https://feed7.dev/p/2607-13034v1-03g7ghx",
        "reason": "The four-hour alert is field evidence for the same minimum-viable-path discipline E3 applies to agent execution: start with the smallest sufficient scope and expand only when needed."
      },
      {
        "title": "How Forward Deployed Engineering is done at Factory — Eno Reyes",
        "source_name": "AI Engineer",
        "source_url": "https://www.youtube.com/watch?v=wpOA-UXynoM",
        "feed7_url": "https://feed7.dev/p/how-forward-deployed-engineering-is-done-at-factory-eno-reyes-0zgscmd",
        "reason": "Kepler’s observation-led scoping complements Factory’s instrumented delivery path by identifying the right workflow pain before validators and deployment machinery are applied."
      }
    ]
  },
  "lifecycle": "Current",
  "published_at": "2026-07-28T16:00:00.000Z",
  "modified_at": "2026-07-28T16:00:00.000Z",
  "supersedes": [],
  "expires_at": null,
  "formats": {
    "html": "https://feed7.dev/p/how-forward-deployed-engineering-is-done-at-kepler-vinoo-ganesh-0thtvuc",
    "json": "https://feed7.dev/p/how-forward-deployed-engineering-is-done-at-kepler-vinoo-ganesh-0thtvuc.json",
    "markdown": "https://feed7.dev/p/how-forward-deployed-engineering-is-done-at-kepler-vinoo-ganesh-0thtvuc.md"
  }
}