1 · Orient
Context and constraints
Map the decision your team must make, the systems involved, and the people who hold veto power. No tooling pitch—only clarity on what success looks like.
Curriculum
A path that ends with owners, not another slide pack.
Use this sequence to choose a single program or stack a cohort. Every stage maps to a bookable Desktopbranch session.
How we sequence learning
Four stages of tech analysis practice
Teams in Vietnam often arrive mid-project. The curriculum below is the spine we use whether you join the systems studio or a shorter clinic.
2 · Investigate
Evidence over opinion
Practice interviews, observation, and document review. Capture quotes and exceptions before proposing a model.
3 · Structure
Models you can debate
Draw boundaries, flows, and decision points. Critique as-is and to-be options with the same vocabulary across roles.
4 · Decide
Briefs and owners
Leave with a decision brief, open-question register, and named owners. Training ends when the next action is assignable.