// SYSTEM_LIBRARY // INDEX // ACCESS_LEVEL: READ_ONLY // OWNER: S. HERMANN

---

Welcome to the central repository for strategic frameworks and operating protocols.
This is not a textbook. This is the toolkit deployed to architect industrial organizations.

// CLUSTER A: STRATEGY (THE COMPASS)

STR_01 :: WHERE TO PLAY / HOW TO WIN -> Choice Cascade

My Doctrine: Strategy is not ambition; it is the act of making choices. Most roadmaps fail because they are just lists of desires.

Application: I use the «Winning Aspirations» cascade to force leadership to define what we are NOT doing. If the strategy doesn’t hurt (by excluding opportunities), it’s not a strategy, it’s a wish list.

STR_02 :: BUSINESS MODEL CANVAS -> Deep Tech Adaption

My Doctrine: Adapted for Deep Tech. The classic canvas often ignores the high cost of goods sold (COGS) in hardware/integration.

Application: I focus heavily on the «Cost Structure» vs. «Revenue Streams» block. In Industrial SaaS, we must ensure that service/integration costs (professional services) don’t eat the recurring revenue margin.

STR_03 :: THE DVF BALANCE -> Viability Check

My Doctrine: A successful product is not just technically possible; it must be the equilibrium of User Value (Desirability), Business Model (Viability), and Technical Ability (Feasibility).

Application: Deep Tech companies naturally over-index on Feasibility («Look at our cool tech»). My role is to artificially amplify the other two forces. I stop projects that are technically brilliant but commercially bankrupt.

STR_04 :: ZERO TO ONE -> Niche Monopolies

My Doctrine: In Industrial IoT, competition is for losers. We don’t try to beat the incumbents at their own game. We solve a specific, hard problem for a small niche so perfectly that we achieve a «local monopoly».

Application: I use this to push back against «Generic Platform» strategies. We must vertically integrate first (solve one problem end-to-end) before we scale horizontally.

// CLUSTER B: DISCOVERY (THE RADAR)

UX_01 :: JOBS TO BE DONE (Christensen) -> Buying Triggers

My Doctrine: In B2B, nobody buys software for fun. They buy it to reduce risk or save time.

Application: I focus on the «Switch» moment. What is the anxiety holding the customer back? In Industry, the fear of downtime (Risk) is always stronger than the promise of efficiency (Gain). Our product must address the fear first.

UX_02 :: KANO MODEL -> Prioritization

My Doctrine: In Industrial SaaS, «Stability» is the only Basic Need. Everything else is negotiable.

Application: I use KANO to discipline Sales teams. They love selling «Delighters» (AI, Dashboards) while the «Basics» (Data Availability, Uptime) are shaky. I enforce a strict «Basics First» policy.

UX_03 :: DEEP DATA / RESEARCH -> Qualitative Research

My Doctrine: We don’t have millions of users for A/B testing. We rely on «Deep Data» (Qualitative) rather than «Big Data» (Quantitative).

Application: 5 interviews with maintenance engineers are worth more than 1000 survey data points. I require Product Managers to be on the shop floor, observing the physical context of the user, not just looking at Mixpanel.

UX_04 :: RISKIEST ASSUMPTION TEST (RAT) -> Validation

My Doctrine: The MVP concept is often abused to ship buggy software. I prefer RAT. We don’t ask «What is the smallest thing we can build?», but «What is the most dangerous assumption that could kill this project?»

Application: In Industrial IoT, the risk is rarely «Can we build it?» (Feasibility). It is usually «Will IT Security let us install it?» or «Will the machine operator accept it?» (Desirability). We test these specific risks before writing production code.

// CLUSTER C: EXECUTION & LEADERSHIP

OPS_01 :: WORKING BACKWARDS (Amazon) -> Alignment / PR

My Doctrine: Code is expensive; English is cheap. We never start building without a Press Release (PR) and FAQ.

Application: This is my primary tool to align Engineering and Commercial teams. If we can’t write a compelling press release for a feature, it’s not ready to be built. It forces clarity before we burn resources.

OPS_02 :: THE PRODUCT FIELD -> Complexity Map

My Doctrine: Industrial products are complex systems of tension between User Needs, Business Goals, and Technical Constraints.

Application: I use the Product Field to visualize these tensions for stakeholders. It stops the «Sales vs. Engineering» blame game by showing that tension is a systemic property, not a personnel issue.

OPS_03 :: THE BALANCE FRAMEWORK (Investments) -> Investment Mix

My Doctrine: Engineering capacity is a zero-sum game. A healthy organization needs a balanced diet of New Things, Improvements, Productivity, and Keeping the Lights On (KTLO).

Application: I visualize where our time actually goes versus where we think it goes. I use this framework to negotiate explicit quotas (e.g., 20% budget for Productivity/Refactoring) to prevent the platform from grinding to a halt.

OPS_04 :: THE GOLDEN CIRCLE -> Resilience

My Doctrine: Engineers don’t work for specs; they work for purpose.

Application: I use the «Why» not for marketing, but for internal resilience. When refactoring takes 6 months, the «What» (fixing code) sucks. The «Why» (enabling the factory of the future) keeps the team alive.

// CLUSTER D: COMMUNICATION & METRICS

COM_01 :: STORYBRAND (Donald Miller) -> Messaging

My Doctrine: The customer is the Hero (Luke Skywalker), not our product. We are the Guide (Yoda).

Application: Especially in Deep Tech, we tend to talk about our «Force» (Tech Stack). I rewrite product messaging to focus solely on the Hero’s problem and how we give them the plan to win.

ANA_01 :: INDUSTRIAL ANALYTICS -> Retention

Application: I track «Health Metrics» and «Retention». Does the machine operator use the tool every shift? If not, we are failing, no matter how many licenses we sold. Usage is the only proxy for value.

My Doctrine: Vanity metrics (Page Views, Signups) are toxic in B2B.