Field Note · 2026

Your tech stack is not an operating model.

Platform architecture can support the way work happens. It should not quietly decide what that way is.

Organizations often let platform architecture dictate process, ownership, intake, workflow, reporting and approvals. The result can look coherent because every team is following the same tool logic. It may still be the wrong logic.

Technology constraints are real. Legacy systems, integrations, contracts and data structures place boundaries around what is possible. But a constraint is not an organizational design principle. The operating model should first describe how work needs to happen; the stack should then support that design as honestly as it can.

A useful test is to remove the platform names from the process map. If the work becomes impossible to explain without the tool, the tool may have become the process.