A risk scout looks ahead for technical unknowns before they become roadblocks. Instead of committing weeks or months to an uncertain path, propose a small, targeted experiment—a spike—to get answers early. section 2.3
Scout for questions such as:
- Can this third-party library handle our scale, and is this cloud service the right fit? section 2.3
- What happens when a network call times out, a third party goes down, or a checkout charges twice? section 10.4.1
The goal is to expose consequential unknowns before the team commits—not to assume the happy path and discover the risk during a production outage. section 2.3 section 10.4.1
