Knowledge material · ~5 min read

Strategist · Learner

The senior-thinking pattern.

Overview

Strategists trade depth for breadth and judgment. You stop solving the ticket and start asking why the ticket exists. The 6-question framework, roadmap thinking, GRC (Governance, Risk and Compliance), and business translation are the four moves that turn a senior engineer into someone the executive listens to.

The 6-question framework

▸1. What problem are we solving — for whom?
▸2. What does success look like, measurably?
▸3. What are we willing to trade?
▸4. Who decides, who executes, who's affected?
▸5. What could go wrong and how would we know early?
▸6. What changes after we ship — operations, support, cost?

Roadmaps & strategy

▸Strategy = where to play & how to win. Roadmap = sequence of bets.
▸Now / Next / Later beats Gantt charts in volatile contexts.
▸Every initiative has a sponsor, an owner, and a kill criterion.
▸Saying no is strategy. Saying yes to everything is noise.

GRC essentials

▸Governance — who decides, by what rules.
▸Risk — likelihood × impact; mitigate, accept, transfer, avoid.
▸Compliance — proving you do what you said.
▸Risk register is a living document, not an annual artefact.

Translating tech to the business

Lead with outcome ('we reduced payroll downtime risk'), follow with mechanism ('by isolating the HRIS into its own subnet and quarterly DR (Disaster Recovery) test'), end with ask ('we need 6 hours of HR (Human Resources) staff time per quarter'). Never start with the protocol.

Glossary

Risk register: Tracked list of risks with owner, score, treatment.
Sponsor: Executive who funds and unblocks an initiative.
OKR: Objective + Key Results — outcome goal-setting framework.

Common pitfalls

✗Strategy decks with no kill criteria.
✗Risk registers updated only at audit time.
✗Pitching to executives in protocol terms.

Practice drills

▸Run the 6 questions on your last big change.
▸Rewrite one technical project summary as outcome → mechanism → ask.