GOST Method
Goals, Objectives, Strategies, Tactics. That is how software is built: the goal defines the product, objectives are increments, strategy is the system, and tactics put it in production.
- G
Goals — the product that exists
A Goal names the user and the change the software must produce. It also names what will not be built. If the goal is wrong, every sprint pushes the wrong way. In this station we do not open the editor: we lock the product.
- O
Objectives — increments you can show
An Objective is a publishable milestone: version, date, done criterion. It cuts the goal into pieces that fit the world. What you cannot show in the product is not an objective — it is an aspiration.
- S
Strategies — the system that holds
A Strategy chooses the approach: domain, ports, how data moves, what is reused and what is left out. One approach organizes the rest. Without it, every tactic is a shortcut and the product fragments.
- T
Tactics — the craft that ships
Tactics are the daily work: model, test, integrate, deploy. Without tactics, architecture is a diagram. Without strategy, tactics are noise. This station does not improvise: it runs the line.
What it looks like on a product
A method example. Not a client and not a published case.
A team sells a service that still lives in sheets and messages. Goal: the customer runs the service without asking someone to “check the spreadsheet.” Objective v0.1: a usable flow with a done criterion. Strategy: a clear domain, an API, a web surface. Tactics: model, test, integrate, put it in production. The framework does not change when the industry does — the product does.
Software is built in four stations
GOST is not a consulting diagram. It is the line: the goal defines the product, objectives increment it, strategy holds it, and tactics put it in use.
- G
Goals
Long-term direction. In software: who it is for and what must change if it works.
- O
Objectives
Measurable milestones. In software: each published increment — version, date, a result you can prove.
- S
Strategies
The chosen approach. In software: the architecture that holds the product.
- T
Tactics
Daily actions. In software: the craft that models, tests, and integrates until production.
Tell us which station you are on
No forms. An email is enough. We read the product where it is — not where the deck says it is.