Risk floor / learning from failure
Failure exposes breaks in strategy, valuation, structure, diligence, governance and integration, building warning signals, risk judgments, switching rules and stop conditions.
METHOD SYSTEM
The method system does two things together: it studies failure to locate system breaks and protect the risk floor, then studies success to understand combinations of conditions and expand the value ceiling. Decision foundations support domain methods, which call professional modules and tools and remain open to outcome-led revision.
TWO-SIDED CASE LEARNING
Failure exposes breaks in strategy, valuation, structure, diligence, governance and integration, building warning signals, risk judgments, switching rules and stop conditions.
Success usually depends on several conditions holding together. The task is not to find one secret, but to understand how strategy, price, structure, capability, execution, context and luck combine.
Study failure
Locate system breaks
Set risk and stop conditions
Study success
Identify conditions and combinations
Design paths and execution
Test in real work
Revise through outcomes
COMMON DECISION ENGINE
Objective, owner, constraints and the actual decision
Separate facts, assumptions, disputes and pending professional views
Retain alternatives and a no-action path
Hold business, cash, capital, terms and accountability together
Specify outputs, owner, gates and stop conditions
Use results to support, narrow, challenge or revise the method
METHOD HIERARCHY
Cross-scenario: define the real problem, then return outcomes to the next choice.
Organise the full capability chain for a class of real work; M&A is the first public domain method.
Called inside a domain method rather than beside it; the full value bridge is a valuation tool within M&A.
ENTER THROUGH CONFLICT
A market window does not mean the enterprise issue has been defined.
MTH-0001 →02A complete 100-day plan, budget and KPIs do not prove execution capability.
MTH-0002 →03Even a good result must be decomposed into judgment, execution, cycle and luck.
MTH-0004 →METHOD ASSETS
Decision foundation
Define the objective, constraints, time horizon and actual decision issue before choosing tools.
Decision foundation
A cross-scenario review of judgment, execution, cycle, external shocks and luck that updates the system.
Professional modules & tools
A professional module embedded in diligence, valuation and structuring, translating risk into value, funding, terms, accountability and stop conditions.
Professional modules & tools
A professional module for funding, M&A and restructuring that compares capital paths across operating, market, tenor and funding conditions.
Professional modules & tools
A valuation tool within the M&A domain method, separating operating value, equity value, consideration, net proceeds and accounting effects.
CALL BY SCENARIO
Domain method: MTH-0002Use MTH-0001 to define the issue; enter the full M&A chain, call MTH-0006 at valuation, MTH-0003 at risk and terms, and MTH-0004 after outcomes emerge.
Module: MTH-0005The capital-structure and risk modules can be called now; a full funding domain method awaits further practice.
Domain method: MTH-0002Treat control as a special M&A setting, calling the value bridge at valuation and returning price to governance, continued funding and tail liability.
Tools: MTH-0006 + 0003Separate operating value, transaction price and net proceeds, then allocate conditions and tail risk; the domain method remains under development.
Tools: MTH-0005 + 0003Compare capital and repayment paths, then connect risk ownership and outcomes; the domain method remains under development.
PUBLIC METHOD BOUNDARY
Public pages define the facts required, outputs expected and conditions for stopping. They do not replace project data, workflow, authority, professional opinions or final accountability.