Subash Natarajan

Challenge a proposed solution by identifying and testing consequential assumptions. Use when the brief feels too certain or discovery reveals contradictions.

中文简介正在准备中。当前显示原文说明。

Compare feasible approaches to a customer problem and recommend a path with costs, constraints and evidence. Use for an architecture or delivery decision, not implementation.

中文简介正在准备中。当前显示原文说明。

Draft a board or executive summary of an engagement using outcomes, risks and investment decisions. Use when the sponsor needs to brief senior leadership.

中文简介正在准备中。当前显示原文说明。

Review the portfolio across existing engagement records. Use for status across customers; requires accessible permitted records and does not create missing client histories.

中文简介正在准备中。当前显示原文说明。

Trace a customer workflow and identify the problem, baseline and evidence gaps. Use for discovery or an unclear customer brief, before choosing a solution.

中文简介正在准备中。当前显示原文说明。

Assess a field lesson for reuse or product feedback without exposing customer context. Use for recurring deployment lessons; distinguish a hypothesis from a validated pattern.

中文简介正在准备中。当前显示原文说明。

Review a proposed customer code change against its intended outcome and operational risks. Use for a diff or PR review; report evidence and actionable findings.

中文简介正在准备中。当前显示原文说明。

Assess the impact of a proposed change on dependencies and shared infrastructure. Use before touching unfamiliar or consequential systems.

中文简介正在准备中。当前显示原文说明。

Choose up to three immediate priorities from competing initiatives. Use when everything is urgent and the customer needs a defensible order with explicit deferrals.

中文简介正在准备中。当前显示原文说明。

Switch between existing customer engagements and triage competing needs. Use when context switching causes confusion; requires engagement records and preserves one client per write.

中文简介正在准备中。当前显示原文说明。

Develop a business case for an initiative using costs, benefits, risks and evidence. Use when a sponsor needs budget or timeline justification.

中文简介正在准备中。当前显示原文说明。