A Simple DevOps Value System: Business, Architecture, Technology, People, Process, Tools, Principles, Methods, Practices

Inspired by Nicole Forsgren’s remark that “Architecture matters…Technology doesn’t,” the author reflects on how architecture should serve business needs and warns against premature architectural decisions in early‑stage startups.

Using the Business‑Architecture‑Technology (BAT) triad, the author argues that startups should start with a monolith and only move to micro‑services when the business direction becomes clearer, emphasizing the economic trade‑offs of technical debt.

The piece then introduces a “People‑Process‑Tool” model, stating that people matter more than processes, and processes matter more than tools, and highlights the importance of mindset and proper use of tools over the tools themselves.

Next, a “Principle‑Method‑Practice” hierarchy is presented, asserting that solid principles guide methods, which in turn shape practices; without strong principles, methods and practices lose their effectiveness.

Throughout, the author stresses that all nine elements—business, architecture, technology, people, process, tools, principles, methods, and practices—are inter‑dependent, and that a balanced, economically‑aware approach leads to better DevOps outcomes.

Finally, the author invites readers to discuss and adopt this simple DevOps value system, noting its relevance to micro‑services, containers, and broader agile transformations.