Inherited a product with no docs? Start here with Janvi Umendra

You’ve just taken over a product. The docs were last updated years ago, the engineer who built it has left, and every “why does it work this way?” gets a shrug. You know how to operate the product; you don’t know how it actually works underneath, and you’re expected to ship changes anyway.

Bring whatever you’ve got: the repo link, the stale wiki, a Slack thread, a screen recording of the workflow you’re trying to change. In 30 minutes we’ll build a first map of how that part of the product actually behaves, separate what the docs say from what the code does, and work out the three questions to take to engineering first. I’ll show you how we do this at Scophix if it’s useful.

You leave with a one-page map of the workflow, a short list of what’s verified vs. assumed, and the questions that get you unstuck fastest. Archaeology mode, cut short.

Works best if you can share a link or a redacted doc before the call so we spend the time mapping rather than reading.