What we look at
- Whether a standard product already covers the path.
- Whether an existing system already holds the fact, and just does not share it.
- Whether the process has an owner. Software will not invent one.
- Whether people will participate. A system nobody uses is not an operation.
Why this step
The useful move is often an integration or a process decision. We scope the smallest intervention that removes the named constraint. We write software when the process has no competent home. We say so when it does.
What we do
- Connect before we rebuild.
- Scope a narrow path: states, owners, required information.
- Leave the rest of the stack alone when it is already doing its job.
What we do not do
- A platform to future-proof the company.
- A rebuild of a product that already covers the path.
- Freezing a process that is still being invented.
Related problems
The other steps
How a file actually runs
Discovery, a scoped build, then scheduled reviews. That is the calendar of the file.
Describe the process as it runs. A specification is optional.