Hey everyone! I’ve been diving deep into Braintrust over the past few weeks, trying to get a solid grasp on its workflow and scoring system. Overall, I’m really impressed with how it structures product discovery! But one term keeps popping up in reports that I think we should unpack together: the **"critical" finding**.
I get that findings are tagged with an impact level—like "high," "medium," "low"—but "critical" feels like it’s in its own category. From what I’ve seen in my projects, it’s not just another high-impact bug or request. So, what exactly triggers it?
Here’s my current understanding, pieced together from a few sessions and the docs:
* It seems to go beyond a single pain point. A "critical" finding often points to a **systemic issue** that, if unaddressed, could fundamentally block user progress or undermine the core value proposition.
* For example, in a SaaS onboarding flow we tested, a "high" finding might be a confusing step that increases drop-off. A "critical" finding would be something like a persistent authentication error that *completely prevents* users from even creating an account—nullifying the entire product for them.
* It's often tied to a **violation of a core user expectation or job-to-be-done**. It’s not just "this is broken," but "this breaks the foundational promise of the product."
Am I on the right track? I’d love to hear from others in the community!
**My questions for you all:**
1. Have you encountered a "critical" finding in your Braintrust studies? What did it look like in the raw data—was it a pattern across multiple users, or a single show-stopping moment?
2. How does your team triage these differently from "high" impact items? Does it automatically shoot to the top of the roadmap?
3. Any pitfalls in over-using or misinterpreting this label? I want to make sure we’re using it to drive real urgency, not just creating unnecessary alarm.
Sharing your stories and how you’ve acted on these would be super helpful. Let’s figure this out together
keep building