Adoption
Exploring STD in your own work
None of our tools is needed. What is needed is to look at which information is waiting for a phase to close, and to find a way for it to reach sooner the place where it can change something.
A starting point
Before changing anything, it helps to look at the system you work in —a product, an area, a course, a work of art— and ask four questions, one per process:
- Capture: which signals from the system and its environment are we receiving, and which arrive too late to change anything?
- Ideate: which ideas are waiting for a stage to end before they can be tried?
- Execute: what is being built on something nobody has looked at again?
- Optimize: which improvements were left for «later», and what would it take to make them while the system evolves?
The answers usually show where information is held back. Synchronizing means opening those passages, at whatever pace the system allows.
Optional instruments
The formalization describes mechanisms that can help. None is mandatory. If it helps to keep a trace of how information flows (M1), these templates are a starting point.
## O-014 · 2026-11-03 · Ana
Source: call with two distributors.
Saw: neither uses the published price list; they ask for quotes over WhatsApp.
Affects: the design of the ordering portal.## I-006 · 2026-11-04 · Iván
Idea: show each distributor's real price in the portal.
If we try it to check something: we will see whether any of three distributors orders online within two weeks.
Comes from: O-014.## D-009 · 2026-11-04 · Iván
We decided: first build only the price view.
Alternatives: full portal; keep manual quotes.
Stable until a new decision: the price structure (the rest can keep changing).Scenarios
These scenarios are possible ways of exploring the proposal, not documented cases or promises of results.
A software team
What is observed from real use enters the work in progress without waiting for the sprint to close. Whoever builds can propose ideas, and whoever does research can see the version in use. If the team already works in sprints, there is no need to abandon them: synchronization happens inside them.
A systems integration
In integrations with ERP, CRM or logistics systems, running small reads against the real system while the flow is being designed lets what the system reveals change the design before it is finished.
An organization
What the operations area learns reaches whoever decides the commercial strategy without waiting for the quarterly report, and what the strategy decides reaches operations before it turns into a closed plan.
A course
What is observed in learners changes the materials and activities while the course is happening, not in next year's edition.
A creative process
What appears while executing a piece —a rehearsal, a sketch, a first mix— can change the idea of the piece. Synchronizing means letting that happen on purpose, and not only by accident.
When to separate
There are cases where processes should not overlap: irreversible actions, stages that are formal requirements for others, or a lack of available signals. The formalization describes them.