iTranslated by AI
Does Man-Month Pricing Corrupt IT? NWMA: Eliminating Absurdity Through Design
This article is not merely a critique of the absurdities created by the "man-month unit price"—a pricing model deeply rooted in the IT industry. It is a treatise defining a design philosophy and an implementable responsibility model to replace it from the structural level: NWMA (Net Worth Management Architecture).
The target audience consists of designers, technical leads, and decision-makers who bear responsibility for outcomes. It answers the question, "Why is no one happy even though man-hours are being managed?" through structural logic.
The "Man-Month Model" as a Device for Skipping Thought
The man-month unit price model converted complex IT development into simple addition by selling human "time." However, this convenience also served as a device for skipping thought, causing the abandonment of "value design."
Structural Flaws Bound by Time
In a structure where "hours worked" becomes the reward, efficiency and automation actually act as incentives that worsen revenue. Here, there is no variable to evaluate the "design capability" that engineers have honed.
What is NWMA? — Three Design Layers
NWMA is not mere idealism or abstract theory. It is a design architecture meant to preserve the "true value" of a system by rewiring three elements: contract, responsibility, and technology.
1. Contract Layer: Inhibiting Value Decay
The fatal flaw of man-month contracts lies in pricing "time," which is unrelated to outcomes. In NWMA, the unit of contract is replaced from working hours to "value maintenance and decay inhibition."
The deliverable an engineer provides is not lines of code. It is the "robust structure that resists failure and continues to withstand future changes" itself. This design is defined as a "prepayment of costs that would have occurred in the future" and an investment to prevent debt before it happens.
2. Responsibility Layer: Eliminating Absurdity through Design
Killing the fantasy of a design-less workplace where "all defects are the engineer's responsibility" through structure. In NWMA, the boundaries of responsibility are clearly separated into the following three points:
- Autonomous Domain (Managed Service): Cloud vendors guarantee the availability of the infrastructure.
- Design Judgment Domain (Human): Responsible for the validity and scalability of the architecture.
-
Decision-Making Domain (Management): Adopts the final risk tolerance and investment decisions.
Clearly specifying these boundaries in an Architecture Diagram serves as a shield that protects engineers and excludes absurd pursuits of responsibility.
3. Technical Layer: Practical Solutions Supporting NWMA
The implementation of NWMA necessitates the use of advanced managed services like Google Cloud.
- Platform: Abstraction of operations using GKE Autopilot or Cloud Run.
- Data Infrastructure: Selection of managed databases that require no administration.
-
Governance: Automatic application of decisions via IaC (Infrastructure as Code).
The criterion for technical selection is not peak performance. "The degree to which human intervention is unnecessary" is the highest priority metric in NWMA.
Practice: Implementing NWMA in the Field—Three Steps
NWMA is not a mere ideal. It can be introduced step-by-step even within existing organizations and projects.
STEP 1 | Expelling "Man-hours" from KPIs
First, eliminate working hours and consumed man-months from the metrics used to measure the success of a project. Instead, adopt the following metrics:
- Toil (manual work) reduction rate
- Shortening of Mean Time To Recovery (MTTR)
- Reduction in change failure rate
By establishing these as KPIs, the team's efforts will be forced to shift from "putting in time" to "improving the structure."
STEP 2 | Writing "Responsibility Boundaries" into the Design Documents
Rather than increasing Runbooks (manuals), clearly state the ownership of responsibility in the configuration diagrams. Reach an agreement with stakeholders during the design phase: "The cloud side ensures the availability of this layer, and humans ensure the logic changes in this layer."
STEP 3 | Redefining Price as an "Uncertainty Absorption Fee"
In estimation, abandon explanations like "X people for Y months." Instead, present the amount of value preserved: "How much of the future operational costs and system downtime risks can be absorbed by this design?"
Conclusion: Killing Absurdity and Reclaiming Design Sovereignty
No matter how excellent the code you write, you cannot break an absurd structure on top of an old OS called "man-month unit price."
Migrating to the new OS called NWMA is a "survival strategy" for engineers and "business continuity rationality" for management. It means mastering the system and not surrendering the final decision-making authority to it.
Maintaining design sovereignty and guaranteeing value through structure—that is the sole and strongest defense against letting IT rot.
Discussion