METHOD SYSTEM

Turn a capital-operations problem into an executable decision

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.

PUB-METHOD-0001V2.2CURRENT / PUBLIC WORKING VERSION2026.07.29

TWO-SIDED CASE LEARNING

See the causes of failure early; understand the conditions of success systemically

01

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.

02

Value ceiling / learning from success

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.

  1. 01

    Study failure

  2. 02

    Locate system breaks

  3. 03

    Set risk and stop conditions

  4. 04

    Study success

  5. 05

    Identify conditions and combinations

  6. 06

    Design paths and execution

  7. 07

    Test in real work

  8. 08

    Revise through outcomes

COMMON DECISION ENGINE

Every capital tool first passes through the same judgment spine

  1. 01

    Define the issue

    Objective, owner, constraints and the actual decision

  2. 02

    Build the facts

    Separate facts, assumptions, disputes and pending professional views

  3. 03

    Compare paths

    Retain alternatives and a no-action path

  4. 04

    Connect value & risk

    Hold business, cash, capital, terms and accountability together

  5. 05

    Form action

    Specify outputs, owner, gates and stop conditions

  6. 06

    Meet outcomes

    Use results to support, narrow, challenge or revise the method

METHOD HIERARCHY

Domain methods organise a class of work; tools solve one node inside it

ENTER THROUGH CONFLICT

Methods begin where a reasonable-looking path may fail

METHOD ASSETS

Enter by level rather than mixing domain methods with tools

CALL BY SCENARIO

Real issues usually call several methods, not one card

01

Investment & M&A

Domain method: MTH-0002

Use 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.

02

Funding & capital structure

Module: MTH-0005

The capital-structure and risk modules can be called now; a full funding domain method awaits further practice.

03

Control transactions

Domain method: MTH-0002

Treat control as a special M&A setting, calling the value bridge at valuation and returning price to governance, continued funding and tail liability.

04

Asset disposal

Tools: MTH-0006 + 0003

Separate operating value, transaction price and net proceeds, then allocate conditions and tail risk; the domain method remains under development.

05

Restructuring

Tools: MTH-0005 + 0003

Compare capital and repayment paths, then connect risk ownership and outcomes; the domain method remains under development.

PUBLIC METHOD BOUNDARY

Callable methods are public here; specific matters still require complete facts, authority and professional accountability

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.