FA Get in Touch
UM Methodology

Business growth methodology as a living system

A business is not a collection of separate parts. Market, strategy, product, customer, marketing, sales, technology, data, people and business economics constantly affect one another. The problem begins when the systematic integrity of the business collapses under the fragmented activity of its parts — that’s when the interaction between different departments toward one shared goal becomes decisive.

UM was built to work with exactly this complexity — a system-centered methodology for understanding, diagnosing, designing, implementing, measuring, and continuously evolving a business. To answer this question:

How, in a world that is always changing, do we move beyond managing growth — and build a system that continuously creates and recreates its own growth?
The Gap

Why aren’t the existing strategic models enough?

Business growth is usually managed with a set of models, frameworks, and KPIs — each designed for a specific problem and each still valuable. But a business manager is not obliged to steer every problem separately. Because different departments affect each other, and managing each one in isolation does not create guaranteed growth. For example, for each problem, the following models are typically used:

Strategy

  • Porter
  • SWOT
  • PESTEL
  • BCG Matrix
  • Ansoff

Business & Growth

  • Business Model Canvas
  • Lean Startup
  • Growth Hacking
  • AARRR
  • North Star Metric

Execution

  • OKR
  • Balanced Scorecard
  • Agile
  • Lean

Customer & Product

  • Design Thinking
  • Jobs-to-be-Done
  • Customer Journey
  • Product-led Growth
In such cases, a drop in conversion rate might not really be a marketing problem — it can stem from the factors below:
Positioning → Product → Pricing → Sales Process → UX → Trust → Technology → Customer Fit
Signal vs. Cause

A growth problem is not always a growth problem.

A metric only tells you something changed — not why. Before designing any solution, UM’s analysis follows a precise chain from signal to business impact.

Signal Pattern Relationship Cause Constraint Business Impact
The goal is not to find the most problems. The goal is to find the constraint that actually limits the system.
Growth Economics

Growth is not a single number; it’s an economy.

Revenue
Revenue = Customers × ARPU
Customer Base
Customers = Leads × Conversion
Unit Economics
LTV / CAC
If conversion rate goes up but CAC goes up too — did growth really improve? If revenue grows but contribution margin falls — what have you actually gained?

Quality of Growth

Revenue Gross Margin CAC LTV Retention Payback Capacity
From Framework to Methodology

UM is not here to remove or replace frameworks.

Existing frameworks usually explain a specific part of a problem. UM is not here to remove or replace them. Our question is: what does each model explain? Where is its boundary? What remains outside the model? And how does this part connect to the rest of the business system?

For this reason, UM moves from framework thinking toward an integrated methodology. That is, instead of seeing each problem separately, we also bring relationships, dependencies, constraints, and the mutual effects of business parts into the analysis.
UM System Thinking

The business as an interconnected system

In UM, growth is not a single output, nor is it just a revenue increase. High revenue does not necessarily mean a more valuable business. Revenue may grow, yet acquisition cost rises, retention drops, or margin falls. So the main question of UM is not only “how to grow faster” — but: what actually limits the system’s growth, and what effect does that growth have on the entire business economy?

In fact, a business is not a collection of separate parts; it is a collection of relationships. Dependencies, feedback loops, constraints, and causal relationships all determine the real behavior of the system.

Market Strategy Product Customer Marketing Sales Operations Technology Data Economics
From Framework to Methodology

Fundamental differences of the UM methodology

UM (Umbrella Method) is not here to add another framework to the list of management frameworks. It does not replace established business knowledge; rather, it integrates, tests, and operationalizes knowledge related to a business system within one unified architecture. A framework helps us see a problem from a specific angle. But a methodology specifies:

✓

What to understand, examine, and prove

What must be understood, what must be examined, and what evidence is required.

✓

How hypotheses are tested and decisions connect to execution

How hypotheses are tested and how decisions connect to execution.

✓

How results are measured — and when the system must be reviewed again

How results are measured, and when the system itself must be reviewed again.

Umbrella aims at this layer:
From data to understanding → from understanding to diagnosis → from diagnosis to design → from design to execution → from execution to evidence → and from evidence back to understanding.
This cycle is the core of the UM methodology. In UM, three major steps are constantly happening.
01 — DECOMPOSITION

Decomposition

The business is broken into analyzable parts — each one mapped and understood within its own context.

02 — RELATIONSHIP MAPPING

Relationship Mapping

Dependencies, feedback loops, and causal relationships between parts are examined — not just the parts themselves.

03 — RECOMPOSITION

Continuous Recomposition

As data and conditions change, the business model is reconstructed and updated — continuously, not once.

UM Methodology Formula

The core of the UM method is built on three logics.

01

System Thinking

We see the business as an interconnected system, not a collection of independent units.

02

Alignment

Strategy, resources, people, processes, technology, data and metrics must move within one shared logic.

03

Evolution

The business system is not fixed. Market, customer, technology and economic conditions change; therefore the system itself must always be revisable and adaptable.

Umbrella Method = System Thinking × Alignment × Evolution
UM Method

Not eight separate services; eight operational layers of one unified methodology.

The eight layers have a logical order — but the path is not linear. Each stage can re-activate a previous one based on new evidence. Returning to a previous stage is not failure — it’s part of the method itself.

01Understand 02Map 03Diagnose 04Align 05Design 06Implement 07Measure 08Adapt Umbrella Method™ Adaptive Growth Loop
01

Understand

Understand the context and build a real model of the business.

02

Map

Map relationships, dependencies and system flows.

03

Diagnose

Root-cause analysis and identification of real constraints.

04

Align

Align strategy, organization and resources.

05

Design

Design the growth system for the real conditions.

06

Implement

Turn design into structured execution.

07

Measure

Measure, analyze evidence and performance.

08

Adapt

Continuous review and evolution of the system.

UM is not a linear method. The eight layers have a logical order, but their execution path is not a straight line. Each stage can re-activate previous ones based on new evidence.

  • Measurement may call the previous diagnosis into question.
  • Execution may reveal a new constraint.
  • A market shift may change the entire decision context.
So returning to a previous stage is not failure — it’s part of the method.
The Intelligence Layer

AI is not a side tool; it is an intelligence layer across the entire methodology.

Observe Understand Analyze Detect Hypothesize Decide Measure Learn Adapt
Human Intelligence × Artificial Intelligence
Umbrella Method is not a fixed method for a fixed problem. As knowledge evolves, the market shifts, and technology advances — the method itself evolves too. We inject the concept of a Living Business System into the business.