How Products, Analysts and Designers Create Value Through Thinking (Category Product Management)

How Products, Analysts and Designers Create Value Through Thinking (Rubric #ProductManagement)

Interesting. speech Kirill Nikolaeva, my colleague, director of analytics at T-Bank. Cyril Discovers What Jobs To Be Done Really Cost (JTBD) and why it’s not always the product’s goal to “remove friction”: sometimes the product should intentionally make the user think if it improves the quality of the solution and reduces risk.

If you highlight the key ideas, then in terms of roles they look like this. Product Manager defines the framework of meaning: it formulates the “work” (JTBD) The desired behavior change, not the list of features. The goal is value, not “easier at all costs.” The analyst translates the hypothesis into testable criteria, selects the metrics of the quality of the solution. (not only)Errors, returns, LTV effects, decision time.

• Designer. (cognitive interface)Designs the right friction – clues, confirmations, micro-learning – where “thinking” is critical (Finance, security, responsibility).

Why it is not always necessary to simplify - simplifying indiscriminately, it is easy to accelerate wrong decisions. Added “meaningful effort” sometimes boosts trust, reduces errors, and improves long-term metrics.

What does this mean for engineers/techlides? Infrastructure of experiments: feature-flags, canary releases, cheap staging of the A/B system, a unified scheme of events. Decision quality telemetry: events “I understood/confirmed risks”, cancellations, returns, erroneous actions, dwell/time-to-decide. Access to Explainability: Journal of Critical Thinking Points (What tips/rules worked) to debunk and audit.

• Rituals: a single JTBD brief on 1 A general plan of experiments, a weekly “decision review” of qualitative and quantitative signals.

Anti-patterns: Click-optimization: Increases metrics but worsens decisions. Simplicity for Simplicity: Kills security/responsibility where the user needs to understand. Feature-driven without JTBD: treating symptoms, not user performance.

As a result, value arises at the intersection of user thinking and the engineering discipline of decision-making. JTBD sets meaning, analytics sets quality criteria, design sets cognitive load, and engineering sets measurement and quick checks.

#Software #Metrics #ProductManagement #Software #Design