software-product-advisor

To diagnose a workflow that feels off, identify the specific layer causing discomfort—such as information architecture, interaction design, or engineering architecture—and translate that fuzzy feeling into explicit evaluation criteria for actionable structural improvement.

Diagnose a complex or noisy software feature by performing a layered diagnosis to determine whether the root cause is product framing, visual design, or standards gaps, then translate that root cause into concrete critique dimensions.

The best way to turn a UX critique into actionable improvement paths is to identify the broken layer, establish professional evaluation standards, and generate two to three realistic options distinguishing between a local fix and an upstream structural change.

Yes, you can use product diagnosis to evaluate spec improvement options by identifying whether the issue is a correctness, workflow routing, or governance gap, and producing a recommended next move alongside alternative paths.

You should not use a layered diagnosis for product discomfort when the underlying problem is already precisely articulated or when the issue is purely a visual design preference rather than a structural gap in workflow routing or engineering architecture.