Enterprise Development Workflows
The practices that let larger teams move quickly without making decisions or product context harder to inspect.
Product and platform · · 8 min read
Ambiguity compounds with team size. At five people a vague objective gets resolved in a hallway; at fifty it becomes three teams building slightly different things and discovering it at integration.
Clarity scales better than communication
The instinct when coordination gets hard is to add communication: more standups, more channels, more status. That scales linearly at best, and it taxes exactly the people whose focus is most valuable.
What scales better is making the work itself legible. A visible objective, a named owner, and a reviewable output mean most questions can be answered by looking rather than asking.
The test is simple: can someone determine the state of a piece of work without interrupting a person? If not, the coordination cost is being paid in meetings.
If the state of a piece of work requires interrupting someone, you are paying coordination cost in meetings.
Put approvals where judgment is required
Approval gates get a bad reputation because they are usually applied uniformly — everything needs sign-off, so sign-off becomes a rubber stamp and stops protecting anything.
Applied selectively they do the opposite. Preparing a brief, running a scan, or drafting a plan needs no gate. Promoting to production, changing a permission model, or touching customer data does. Concentrating the gates on those moments makes them meaningful again.
This matters more with agents in the loop, not less. The same rule should apply whether a human or an agent initiated the action — an agent-initiated production deploy is not a different category of risk.
Governance is mostly about reconstruction
Most compliance requirements reduce to one question: can you reconstruct what happened and why, months later, without relying on anyone's memory. Audit logs answer the what. The why is usually missing.
Keeping the reasoning attached to the work — the finding, the decision, the approval, the evidence — turns an audit from an investigation into a query.
What a reviewable trail contains
- The objective, and who owned it.
- The evidence considered, with sources intact.
- The decision taken and the alternatives rejected.
- Who approved it, and what they saw at the time.
- The validation that the change did what it claimed.
Local execution is a real requirement
For a lot of organisations, the question of whether source code leaves the machine it was written on is not a preference. It is a procurement blocker, and no amount of capability compensates for failing it.
Local, sandboxed execution with a granular permission model is a deliberate trade: you give up cloud parallelism to keep work inside the boundary. Teams that need the parallelism should weigh that honestly rather than discovering it late.
Key takeaways
- Make work legible instead of adding communication overhead.
- Concentrate approvals where judgment matters so they stay meaningful.
- Apply the same gates to agent-initiated actions as to human ones.
- Governance is reconstruction — keep the why, not just the what.