A first useful workflow can sometimes be demonstrated quickly, but production readiness depends on access, data quality, risk, integration behavior, and how fast the business can test decisions.
/ 01
Phase 1: consultation and definition
Define the problem, owner, current process, systems, sensitive information, outcome, constraints, excluded actions, and the test that will show whether the idea works. A clear narrow scope shortens every later phase. Access approval and representative data are often the actual schedule drivers.
/ 02
Phase 2: first working iteration
Build the smallest end-to-end path using representative data and safe test accounts. The purpose is to expose assumptions early, not to present a polished final system. Keep irreversible actions disabled or redirected to a sandbox.
/ 03
Phase 3: business testing
Users test normal cases and exceptions. Corrections often reveal missing business rules rather than coding defects. The schedule depends heavily on how quickly a named tester can provide specific evidence: source, expected result, actual result, and priority.
/ 04
Phase 4: controlled release
Complete permissions, logging, backups, documentation, rollback, alerts, and ownership. Release to a limited audience, monitor results, and expand only when the workflow behaves as expected. Production readiness is a set of verified controls, not a date on a proposal.
/ 05
Estimate using gates, not optimistic days
A useful plan has exit criteria. Definition ends when owner, boundaries, data, and success measures are approved. Build ends when the smallest path runs with representative data. Testing ends when agreed cases pass and known risks have owners. Release ends when access, monitoring, recovery, and handoff are verified.
Use ranges tied to dependencies: a narrow internal workflow with ready access may reach a useful test in days; cross-system or customer-facing work may take weeks; regulated or high-consequence systems may take longer because review and evidence are part of the product. Treat any estimate without access, testing, and decision-owner assumptions as incomplete.
- Who approves access, and by what date?
- Who supplies representative data?
- Who returns test results?
- What must pass before production?
- Which provider or legal review is outside the builder's control?
- Who owns operations after release?
/ Practical takeaway
Plan around evidence gates and named dependencies. The speed of a demo says little about the time needed for permissions, exceptions, security, review, and a controlled release.