# Task: Plan a business or enterprise

Connect direction, customer evidence, resources and near-term action.

## Prepare
Prepare a business overview, customer and market evidence, current goals, budget and responsibilities. Separate facts, estimates and untested assumptions.

## Produce
Produce direction and scope, customer evidence, goals and assumptions, a resource budget and near-term actions.

## Check
Check baselines, resource sources, action owners and acceptance criteria. Keep material untested assumptions explicitly unresolved.

## Conditions
Use the ten-step method to frame the work, then select resources for this project. The digital-platform playbook illustrates phased delivery for platform businesses; it is not a universal enterprise plan.
Confirm inputs, conditions, sources and versions. List missing information; do not invent it.
Identify goals, budgets, rights, permissions and final decisions that require human confirmation.

## Original text and version
- Thinking: Complexity, Simplicity, Ease, Diagram: A Method for Business Logic Design | V1.0 | https://yutengfei.com/en/journal/fan-jian-yi-tu/
  Markdown: https://yutengfei.com/en/journal/resources/fan-jian-yi-tu.md
  Map the complexity of the question, then choose the main relationships to retain.
- Methods: Enterprise Planning in Ten Steps: Connecting Direction, Resources and Execution | V1.0 | https://yutengfei.com/en/journal/enterprise-planning-ten-steps/
  Markdown: https://yutengfei.com/en/journal/resources/enterprise-planning-ten-steps.md
  Use ten steps to connect direction, customer evidence, resources and near-term action.
- Models: From Strategy to Visual Design: How Do Six Layers Carry the Same Meaning? | V1.0 | https://yutengfei.com/en/journal/strategy-to-visual-six-layer-model/
  Markdown: https://yutengfei.com/en/journal/resources/strategy-to-visual-six-layer-model.md
  Check whether strategy, business and public expression communicate the same meaning.
- Playbooks: Building an Industry Digital Platform in Verifiable Stages | V1.0 | https://yutengfei.com/en/journal/phased-industry-digital-platform/
  Markdown: https://yutengfei.com/en/journal/resources/phased-industry-digital-platform.md
  For platform projects only, consult the phased construction and acceptance arrangements.
- Tools: How to put funding sources and uses in one table | V1.0 | https://yutengfei.com/en/journal/funding-sources-uses-table/
  Markdown: https://yutengfei.com/en/journal/resources/funding-sources-uses-table.md
  Match proposed funding, actual availability conditions and payment requirements.
- Training: Explain a Business in One Sentence, One Paragraph and One Diagram | V1.0 | https://yutengfei.com/en/journal/business-positioning-one-page-exercise/
  Markdown: https://yutengfei.com/en/journal/resources/business-positioning-one-page-exercise.md
  Test whether a one-page business map explains positioning and action clearly.

## Associated Skill
The associated Skill supports initial material organization and consistent wording; it does not replace enterprise planning or business decisions.
Brand & Project Briefing: https://yutengfei.com/en/skills/brand-project-brief/

## Record results, deviations and knowledge or steps that need revision.

Version: V1.0 · 2026-11-05
https://yutengfei.com/en/journal/pathways/business-planning/

---

Select resources and sections as needed instead of indiscriminately loading every document.
Exports retain existing licenses and third-party notices. Downloading grants no additional adaptation, commercial-use or training rights.

---

# Complexity, Simplicity, Ease, Diagram: A Method for Business Logic Design

- Author: Andrew David W.Y.
- Source: https://yutengfei.com/en/journal/fan-jian-yi-tu/
- Version: V1.0
- Published: 2017-09-07
- Revised: 2026-09-18
- Content status: Full text published
- Content type: Thinking (ideas)
- Research topics: —
- Ecosystem perspectives: —

## Use this resource

**Purpose**: Map a complex business problem in full, find its structure, test the logic, then draw it. “Mapping the complexity, simplifying the complexity, making it easy, and turning it into a diagram” describes this process.

**Conditions for use**: Check that the subject, objective and constraints fit the task. Confirm any conditions that the article does not specify.

**Thinking · Premises and reasoning**

**Evidence and validation limits**: A research and methodological reflection. It does not, by itself, constitute a specific enterprise solution, institutional commitment, or effective allocation of rights. No separate external-validation result is recorded for this article. Publication does not establish effectiveness; check the evidence, assumptions and limits in the text.

This is a readable, citable knowledge resource, not an installed Skill. When using it with AI, retain its sources and limits and review the output.

## Full article

## From Cross-Disciplinary Experience to Business Logic Design

Since 2004, I have worked in computer programming, internet promotion, marketing planning, business planning and capital planning, spending roughly three years at each stage. The work changed, but I kept asking the same questions: what are the different levels of business operation? How does enterprise value form? How do these kinds of work connect?

As a programmer, I found that good software still needs to be seen, understood and promoted. Promotion then showed me that communication needs an understanding of customers, markets and value. Marketing planning needs a clear business plan behind it. Business planning also means considering how to organize resources, arrange financing and manage the risks involved.

Looking back, these experiences made me more interested in business logic: where value comes from, which relationships affect results, and how to use that understanding in operations. Understanding these questions gives action a clearer direction and helps build consistent ways of working.

I also encourage entrepreneurs to practice “descending into learning and rising into understanding”: start with specific problems and everyday work, understand the principles behind them, then use that understanding in practice to realize business value more steadily and fully.

After the first thirteen years of practice, I began combining internet thinking with blockchain’s emphasis on consensus. I used business logic diagrams and comprehensive mind maps to show these relationships more fully to entrepreneurs.

Map the complexity

→

Simplify the complexity

→

Make it easy

→

Turn it into a diagram

## I. Map the Complexity: Present the Whole Business Clearly

On the surface, every enterprise appears to have a different business logic. At a deeper level, however, different forms of business logic often contain a recurring set of design dimensions.

In the section “Business Logic Design Tools and Mind Maps,” I seek to identify the common dimensions behind the real problems encountered in enterprise operations. These dimensions can then be organized and presented through mind maps and business logic diagrams.

At first, this process is inevitably complicated, and the resulting mind map may be very large. Only by recording the problems, roles, resources, objectives, processes, relationships, and outcomes as fully as possible can we begin to see the overall business structure.

“Complexity” does not mean creating complexity for its own sake. It means resisting the urge to simplify too early. We first make visible the material scattered across experience, departments, processes, and judgments, and then classify, compare, and examine it. As the work progresses, the business logic can be divided into clearer areas, and the boundaries between key questions can become visible.

This is what it means to map the complexity: see the whole picture before deciding what truly matters.

## II. Simplify the Complexity: Distill Structure from Accumulated Information

When approaching a new field of knowledge, it is easy to become like the people in the parable of the blind men and the elephant: we mistake whatever part we have touched for the whole. To understand a subject properly, we need to invest time and patience, reading both primary sources such as books and papers and secondary materials such as online resources, and gradually build an overall view.

This process is necessarily demanding. We need to filter repeated information, distinguish facts from opinions, assess the reliability of sources, and separate valuable material from unsupported claims. As information accumulates, the underlying structure begins to emerge.

Mind maps can help us build a system of knowledge. Repeatedly adjusting a mind map is, in practice, a way of repeatedly searching for structure.

The core of simplification is not merely deleting information. It is identifying the relationships beneath the information. We may divide a problem according to different dimensions, and we may change dimensions when an analysis reaches a dead end. Whatever the approach, the focus should remain on the factors that genuinely influence the final outcome.

For example, take “a rocket successfully reaching the sky” as the final outcome. We can ask what conditions must be satisfied at the same time. The launch structure must keep the rocket stable and upright; the engines must provide sufficient thrust; the navigation system must correct its direction; and the structure and materials must withstand the heat and pressure of flight. Once these key points are separated and related items are grouped together, the overall logic of a launch begins to become clear.

Business problems can be approached in the same way. Starting from the desired result, we ask what conditions, steps, and relationships are necessary to achieve it. We then merge repeated elements, separate different kinds of elements, and gradually clarify the major categories.

This is what it means to simplify the complexity: distill a structure that can explain the result from a large body of information.

## III. Make It Easy: Turn Structure into a Clear Method

“Easy” does not mean oversimplifying a problem. It means making a complex structure easier to understand, discuss, and apply.

As our learning deepens, we develop our own judgments and interpretations, and the key points become more accurate. This requires repeated refinement: refine the questions, refine the relationships, refine the judgments, and then refine the expression.

In the end, the key points along the structure should be concise and clear, and the relationships between them should be explicit. Even then, the work is not finished. We must continue to test the logic: if we follow this structure, are there any breaks in the reasoning? Have important conditions been omitted? Can the different stages explain one another? Does the structure form a complete loop?

When these questions can be answered, a previously unwieldy mind map begins to become a clear, understandable, and reusable method.

Making a subject easy is therefore a process of continuous verification. It requires us to remove what is unimportant without losing the conditions that determine the result. True simplicity does not mean that less content is always better. It means that every retained point has a clear purpose.

## IV. Turn It into a Diagram: Make Business Logic Visible

The final step is to turn the clear structure into a diagram. This step may look simple, but it is difficult in practice.

It is simple because the key points and their relationships have already been identified, refined, and tested. It is difficult because all of them now need to be placed into a single visual structure so that the logic can be seen quickly, understood accurately, and checked repeatedly.

A good business logic diagram should meet at least three conditions:

-   **Logical rigor**: the relationships between key points should not depend on guesswork; direction, sequence, and causality should be as clear as possible.
-   **Structural clarity**: levels, categories, boundaries, and priorities should be easy to identify.
-   **Appropriate expression**: the diagram should be complete and orderly, with enough visual quality to support understanding rather than obscure the logic.

This work requires repeated attempts. The position of a shape, the direction of a connection, the number of levels, and the length of the text can all affect comprehension. No layout technique can replace a deep understanding of the system itself, and no diagram can emerge naturally without sustained thinking.

The purpose is not to force every sentence into one image. A diagram is a compressed expression of logic: readers should be able to follow its paths, find the key nodes, see the relationships, and use the structure to ask further questions or begin practical work.

This is what it means to turn the easy into a diagram: convert an understood logic into a structure that can be seen, discussed, and used.

## Conclusion: Put the Method Back to Work

“Mapping the complexity, simplifying the complexity, making it easy, and turning it into a diagram” describes how I turn experience into a method, then use that method in practice.

Map the problem fully, find its structure, test the logic, then draw it. The key points and relationships need to be explained clearly and tested in actual operations.

The value of this work is to turn scattered experience into methods people can understand, check and improve together. With entrepreneurs’ continued participation, these methods have a chance to become lasting ways of working in the company.

[CC BY-NC-ND 4.0](https://creativecommons.org/licenses/by-nc-nd/4.0/)

Applies to original text unless otherwise stated; excludes third-party materials. Downloading or machine reading does not extend the existing license or separately authorize derivatives, commercial use or model training.

[AI usage guide](https://yutengfei.com/en/journal/ai/)


---

# Enterprise Planning in Ten Steps: Connecting Direction, Resources and Execution

- Author: Andrew David W.Y.
- Source: https://yutengfei.com/en/journal/enterprise-planning-ten-steps/
- Version: V1.0
- Published: 2026-10-30
- Revised: 2026-10-30
- Content status: Full text published
- Content type: Methods (methods)
- Research topics: Stakeholder Capital Governance (stakeholder-governance)
- Ecosystem perspectives: Operations & Management Ecosystem (operations) · Customer Ecosystem (customer) · Resource Ecosystem (resource)

## Use this resource

**Purpose**: A practical update of an early ten-step planning framework, with customer evidence, cash-flow checks, agreed dependencies and rolling reviews. Two diagrams connect long-term direction to near-term work with owners, resources and acceptance criteria.

**Conditions for use**: Check that the subject, objective and constraints fit the task. Confirm any conditions that the article does not specify.

**Methods · Steps, inputs and completion criteria**

**Evidence and validation limits**: This article builds on the earlier ten-step method. Testing customer assumptions, scenario-based cash planning, rolling 90-day actions, and suggestions for using AI are additions in this edition. No separate external-validation result is recorded for this article. Publication does not establish effectiveness; check the evidence, assumptions and limits in the text.

This is a readable, citable knowledge resource, not an installed Skill. When using it with AI, retain its sources and limits and review the output.

## Full article

Business planning often runs into a familiar problem. Everyone seems clear in the meeting, then returns to their department and carries on as before.

Direction, targets, budgets and performance measures all exist, yet they do not connect. Sales promises delivery that operations cannot support. A new project has no funding allocation. At year end, the team discovers that several important assumptions were never checked.

I recently revisited an early training deck called Enterprise Planning in Ten Steps. Its company figures and examples belong to another period. Its way of considering direction, markets, strategy, finance, risk and cooperation together is still useful. This article follows its practical ten-step sequence and updates the working methods.

**What matters to me is whether the team can identify its priorities, decide what to leave aside, and say who will deliver what next.**

## The whole picture: how the ten steps connect

The steps form five groups: establish direction, check the market, choose an approach, examine conditions and move into action.

Their numbers organize discussion. Real planning moves back and forth. A change in customer demand may require new targets. Funding constraints may change scope. A finding in step seven can send the team back to steps two and six.

The ten steps are ten sets of planning questions. Review continues throughout execution. It does not need to become an invented eleventh step.

[![Figure 1. Read the numbered steps within five groups. Review can return to any step that needs checking, rather than following a one-way sequence.](https://yutengfei.com/journal/enterprise-planning-ten-steps/overview-en.svg)](https://yutengfei.com/journal/enterprise-planning-ten-steps/overview/viewer-en.html)

Figure 1. Read the numbered steps within five groups. Review can return to any step that needs checking, rather than following a one-way sequence.

[Enlarge and drag to explore ↗](https://yutengfei.com/journal/enterprise-planning-ten-steps/overview/viewer-en.html)[Download editable SVG ↓](https://yutengfei.com/journal/enterprise-planning-ten-steps/overview-en.svg)

## Putting the ten steps to work

### 01 Purpose: whose problem will the business solve?

Start with ordinary language: which customers, which problem, how value is created and how the business can sustain itself.

Add clear boundaries. Which orders and markets will it decline? Which practices would damage the long-term interests of customers, employees or partners?

Test the statement against a real opportunity under discussion. Does it help the team decide whether to accept it, and why? If almost any business fits, narrow the statement.

The output is a direction card covering customers, the core problem, value proposition and operating boundaries.

### 02 Longer-term objectives: make the conditions visible

Retain a direction for three to five years, then define annual results and near-term validation points. Record the baseline, desired result, timing, measurement definition and owner.

Alongside revenue, consider continued customer use, delivery reliability, essential capabilities and cash capacity. Select measures that fit the business rather than filling every category.

State the assumptions. Entering a new region may depend on distribution, service capacity and customer acceptance. Approval of the target does not establish those conditions.

The output is an objectives table and assumptions register. Arrange validation for major unknowns before treating future capability as already available.

### 03 Customers and markets: check behaviour

Choose a specific customer group, use case and buying process. Who uses, decides, pays and bears the cost of switching? These can be different people.

Interviews help explain the problem. Trials, purchases, repeat orders and renewals provide further evidence of behaviour. A few positive responses do not establish market-wide willingness to pay, and free use does not prove paid demand.

Make each important assumption testable. Define the group, test, observation period and behaviour to observe. Agree criteria in advance and record the sample and its limits.

The output is a customer evidence table: what was observed, which judgment it supports and what remains unresolved. This is consistent with Strategyzer's approach of starting experiments from critical hypotheses. [Reference](https://www.strategyzer.com/library/how-to-test-your-idea-start-with-the-most-critical-hypotheses)

### 04 Competition: include every alternative available to customers

Customers can choose another supplier, keep their current process, do the work themselves, postpone purchasing or leave the problem unresolved.

Compare what matters to them: effectiveness, total cost, delivery time, ease of use, reliability and support. A claim such as professional expertise needs a concrete explanation and evidence.

SWOT remains useful when each finding leads to a choice. Does an opportunity match available capabilities? Could a weakness prevent delivery? Filling four boxes alone changes little.

The output is an alternatives comparison and a set of actions to pursue, improve, monitor or avoid.

### 05 Key success factors: identify essential conditions

A key success factor is a condition the business needs to work. A critical business issue is a current gap that requires attention. Keep the two distinct.

For a service needing continuous on-site support, reliable response may be essential. Having nobody on duty is a specific gap. More advertising may do nothing to close it.

Start by discussing three or four conditions. For each, state why it is necessary, the present gap and how closure will be checked. This number helps focus discussion. It is not a universal limit.

The output is a conditions-and-gaps table. Calling every initiative a top priority makes meaningful choices difficult.

### 06 Strategy and implementation: choose where resources go

Connect objectives, customer evidence and critical gaps. Then select a few priority initiatives. Explain which condition each will change, why that should affect results, what resources it needs and what will wait.

For an uncertain new business, define a limited pilot, spending ceiling, review point and conditions for the next decision. Expand after reviewing evidence. An established business can justify a different investment pace.

Keep a decision record of choices, rejected alternatives and reasons. When conditions change, the team can revisit a specific judgment.

The output is a priority portfolio with resource allocations, rather than general phrases such as improve marketing or strengthen management.

### 07 Financial analysis: distinguish profit, cash and investment

Explain how revenue arises, what remains after delivery and when cash enters and leaves.

Orders, revenue, profit and receipts are different measures. A profitable project can still run short of cash because of slow collections, inventory or initial spending. Review payment terms, delivery timing, receivables and required investment together.

Use base, favourable and stressed scenarios, with their assumptions stated. Mark estimates as estimates and identify their basis and next check. Multiplying subjective scores does not create an exact financial forecast.

The output is a financial model, cash schedule and resource gap. Appropriate specialists should check accounting, tax or financing details against the actual circumstances.

### 08 Risks: define when the plan must change

Record warning signals, responses, owners and decision authority as well as likelihood and impact. Address controllable factors and prepare alternatives for those outside the team's control.

The source deck uses impact and likelihood for prioritisation. This remains a discussion aid when scoring definitions are clear. Low-probability, high-loss events need separate attention and should not disappear beneath a multiplied score.

Agree the conditions for continuing, adjusting, reducing scope or pausing. Assign responsibility for winding down commitments and protecting customers and partners if work pauses.

The output is a risk register with triggers, rather than a broad statement that risk is controlled.

### 09 Dependencies: turn requests for support into commitments

Naming a task owner is only part of the arrangement. Specify required inputs, providers, timing and acceptance criteria.

A service launch may need product scope, operating capacity and payment terms confirmed by different teams. A date cannot be treated as secured while these prerequisites remain unresolved.

Put dependencies in one table and obtain confirmation from the people involved. Refer resource conflicts to the authorised decision-maker and record effects on objectives, scope and timing. External cooperation also needs a basis, costs, responsibilities and a change process.

The output is an agreed dependency table. Strategy deployment offers a useful model of dialogue between management and teams to reconcile targets, resources and practical conditions. [Reference](https://www.lean.org/lexicon-terms/strategy-deployment/)

### 10 The first-year plan: define work that can be accepted

Keep annual outcomes and resource limits visible, then detail the work nearest at hand. I suggest starting with the next ninety days and updating as conditions develop.

Each action needs an owner, deliverable, deadline, resources, prerequisites and reviewer. Distinguish activity from its purpose. Completing interviews is an activity. Establishing purchasing conditions is the judgment it should support.

Ninety days is this article's suggested working window, not a fixed requirement of the original method. Long sales cycles, research programmes and seasonal operations need their own review points.

The output is an annual plan with a near-term action table. After accepting a deliverable, check whether it produces the expected effect.

## Keeping planning active: responsibility and revision

The business leader owns strategic choices and resources. Business owners provide evidence and execute. Finance checks assumptions and cash. Partners confirm dependencies. Someone also needs to facilitate the process, maintain records and follow unresolved items. A small team can combine roles without omitting the work.

Review three questions: was the agreed work delivered, did business outcomes improve, and do the original assumptions still hold?

For execution gaps, check resources, dependencies and methods. When activities are complete but results do not follow, revisit the causal judgment. If outside conditions have changed, reconsider objectives, scope and spending.

Weekly blockage reviews, monthly operating reviews and quarterly or milestone resource decisions are a starting rhythm. Adjust it to the business. Keep records of evidence, decisions and assigned actions.

[![Figure 2. Review delivery, results and assumptions before deciding to continue, adjust or pause. New action needs authority and prerequisites. Paused work does not restart automatically.](https://yutengfei.com/journal/enterprise-planning-ten-steps/review-en.svg)](https://yutengfei.com/journal/enterprise-planning-ten-steps/review/viewer-en.html)

Figure 2. Review delivery, results and assumptions before deciding to continue, adjust or pause. New action needs authority and prerequisites. Paused work does not restart automatically.

[Enlarge and drag to explore ↗](https://yutengfei.com/journal/enterprise-planning-ten-steps/review/viewer-en.html)[Download editable SVG ↓](https://yutengfei.com/journal/enterprise-planning-ten-steps/review-en.svg)

## A planning table to start with

Use this table to connect the first discussion. A complex organisation may use several documents, but they should point to the same objectives and decisions.

| Step | What to check | Output |
| --- | --- | --- |
| 01 Business purpose | Whose problem, and what stays outside scope? | Direction card |
| 02 Longer-term objectives | From which baseline to which target, on what assumptions? | Objectives and assumptions |
| 03 Customers and markets | What purchasing and usage behaviour was observed? | Customer evidence table |
| 04 Competitive alternatives | What alternatives can the customer choose? | Alternatives comparison |
| 05 Key success factors | Which conditions are essential, and what is missing? | Conditions-and-gaps table |
| 06 Strategy and implementation | What comes first, and what will wait? | Priorities and resources |
| 07 Financial analysis | Does the model work, and can cash support it? | Financial model and cash schedule |
| 08 Potential risks | Which signals trigger adjustment or a pause? | Risk register with triggers |
| 09 Dependencies | Who provides what, when, and under what acceptance criteria? | Agreed dependency table |
| 10 First-year plan | Who delivers what next, and who accepts it? | Annual and near-term actions |

Choose one real business activity and complete the ten rows with the people involved. Mark unsupported assumptions for validation and unconfirmed support as pending. The next meeting can then address specific gaps.

## Where digital tools and AI fit

Dashboards help observe change. AI can help organise interviews, summarise materials, list assumptions and compare scenarios. Essential data must remain traceable, important conclusions need human review and access rules apply to sensitive information.

Tools do not take responsibility for business choices. Authority for spending, customer commitments and pausing work still needs to be explicit. NIST's AI Risk Management Framework similarly addresses governance, context, measurement and ongoing management. It is a supporting reference for AI use here. [Reference](https://airc.nist.gov/airmf-resources/airmf/5-sec-core/)

## Bring planning back to the business

Start with one activity that needs progress. Consider its direction, customers, conditions, resources, cooperation and actions together.

If the discussion clarifies current priorities, missing conditions and the circumstances requiring a new decision, planning has begun to help.

The ten-step method organises judgment and action. Market and operating results still need testing. Preserve the reasons for today's decisions and the route to tomorrow's adjustments.

### Method source and further reading

This article follows the practical sequence on slides 28 and 75 of an early Enterprise Planning in Ten Steps training deck, drawing on its customer, success-factor, finance, risk and dependency material. Hypothesis testing, cash scenarios, ninety-day rolling actions and AI guidance are additions in this article, not quotations from the deck or claims of proven results.

-   [Strategyzer: testing critical business hypotheses](https://www.strategyzer.com/library/how-to-test-your-idea-start-with-the-most-critical-hypotheses)
-   [Lean Enterprise Institute: strategy deployment](https://www.lean.org/lexicon-terms/strategy-deployment/)
-   [NIST: AI RMF Core](https://airc.nist.gov/airmf-resources/airmf/5-sec-core/)

[CC BY-NC-ND 4.0](https://creativecommons.org/licenses/by-nc-nd/4.0/)

Applies to original text unless otherwise stated; excludes third-party materials. Downloading or machine reading does not extend the existing license or separately authorize derivatives, commercial use or model training.

[AI usage guide](https://yutengfei.com/en/journal/ai/)


---

# From Strategy to Visual Design: How Do Six Layers Carry the Same Meaning?

- Author: Andrew David W.Y.
- Source: https://yutengfei.com/en/journal/strategy-to-visual-six-layer-model/
- Version: V1.0
- Published: 2026-10-19
- Revised: 2026-10-19
- Content status: Full text published
- Content type: Models (models)
- Research topics: —
- Ecosystem perspectives: Customer Ecosystem (customer) · Operations & Management Ecosystem (operations)

## Use this resource

**Purpose**: Connect strategic intent, audience tasks, value proposition, content structure, visual rules and context of use. Two diagrams, a fictional example and a decision record show how to trace design choices and revise the relevant layer.

**Conditions for use**: Check that the subject, objective and constraints fit the task. Confirm any conditions that the article does not specify.

**Models · Elements, relationships and assumptions**

**Evidence and validation limits**: The example illustrates how to analyze the situation and use the approach. When applying it, substitute actual business records for the example conditions and check the judgment and outcome. No separate external-validation result is recorded for this article. Publication does not establish effectiveness; check the evidence, assumptions and limits in the text.

This is a readable, citable knowledge resource, not an installed Skill. When using it with AI, retain its sources and limits and review the output.

## Full article

Before creating a visual system, I want to clarify a few things: what the business intends to do, who it mainly wants to reach, what those people should understand, and what they should be able to do next.

With those answers, design choices become easier to assess. What the headline should say first, which information deserves emphasis, where an image belongs, and where a button leads all have a basis.

If the intended meaning keeps changing, the visual work is hard to stabilize. Planning may describe one business, the writing emphasize another advantage, and the design suggest a third impression. Considerable work goes into each part, yet the whole remains unclear.

I find it useful to organize this process into six layers: **strategic intent, audience tasks, value proposition, content structure, visual rules, and context of use.**

Each layer should address the question passed down from the previous one and provide a usable answer for the next. The answers are then checked in the setting where the work will actually be used. This is a working model for organizing and reviewing design decisions.

## 1\. Turn the business direction into requirements people can discuss

“We want it to look more professional” can start a conversation, but it does not yet provide enough direction for design.

What should professionalism show through? A clear service scope, an understandable delivery process, or information that can be checked? Different answers lead to different content and visuals.

Strategic intent should first establish the problem the business currently addresses, the people it serves, the capabilities that support continuing operations, and the part of that work this communication should undertake.

Current capabilities and future direction also need to be separated. Services already available need supporting information; capabilities still being developed should retain their planned status. Presenting the future as the present makes a polished design more likely to mislead readers.

For a specific design task, I would narrow the scope further. A company introduction may help newcomers understand the business. A product page may help people with a defined need assess suitability. Partnership material may explain responsibilities, conditions, and the next step.

**Let one piece of communication perform one main task well.** Once the task is clear, there is a starting point for deciding what to emphasize and what to place later.

## 2\. What each of the six layers needs to clarify

[![Figure 1: The six-layer model from strategy to visual design](https://yutengfei.com/journal/strategy-to-visual-six-layer-model/model-01/diagram-en.svg)](https://yutengfei.com/journal/strategy-to-visual-six-layer-model/model-01/viewer-en.html)

Figure 1: The six-layer model from strategy to visual design

[Explore the diagram ↗](https://yutengfei.com/journal/strategy-to-visual-six-layer-model/model-01/viewer-en.html)[Download SVG ↓](https://yutengfei.com/journal/strategy-to-visual-six-layer-model/model-01/diagram-en.svg)

_Figure 1: Downward arrows represent the conversion of design inputs from one layer to the next. They do not mean that completing a layer necessarily produces business results. Feedback from use supports review and revision at the relevant layers._

### Layer 1: Strategic intent—what should this communication support?

This layer establishes direction and boundaries.

The market the business hopes to enter, the capabilities it relies on, and the communication problem it most needs to address should be clear first. At minimum, the design team needs an agreed task brief: what the work should achieve and what it cannot yet promise publicly.

The brief need not be long. Helping participants reach a similar understanding of the objective is more useful than filling it with grand concepts.

### Layer 2: Audience tasks—what question does the reader bring?

The same business may address customers, employees, suppliers, and other partners. Some concerns overlap, while others have distinct priorities.

Customers may first ask whether an offer suits them, how delivery works, and what happens when something goes wrong. Suppliers may focus on what they must provide, how coordination works, and settlement terms. Employees may want to understand roles, work standards, and available support.

So “who will read this?” should lead to “what judgment do they need to make?”

Even the same person has different tasks when first learning about an offer, comparing options, and preparing to cooperate. Making those differences explicit helps place information where it belongs.

### Layer 3: Value proposition—why is it worth learning more?

The value proposition should connect the audience’s problem with the help the business can provide.

If reliable delivery matters most, explain delivery arrangements, responsibilities, and exception handling. If the reader needs to assess suitability, clarify scope, conditions, and circumstances in which the service does not apply.

Words such as “efficient,” “professional,” and “reliable” can be used, but they need support. Relevant practices, records, and the extent to which they can be verified determine how far a claim can reasonably go.

**Review the claim and its evidence together.** Some claims have factual support, some still require validation, and some express a future direction. Distinguishing them gives the subsequent communication a sounder basis.

### Layer 4: Content structure—in what order should the reader understand?

A business usually has plenty of information. A visitor to a page may not be willing to read all of it from beginning to end.

Content structure determines which question to answer first, what evidence follows, what can be expanded, and what needs a separate entry point.

For a service page, begin with the problems it addresses, explain the way of working, then provide deliverables, conditions, and relevant information, followed by a clear next step. Readers can follow their questions or go directly to the part they need.

Headings help organize understanding. The headline, summary, diagram, body, and buttons should work together around the same task. Placing every piece of business information at the same level leaves the reader to classify it again.

### Layer 5: Visual rules—how can important relationships become visible?

At this layer, choices become specific: type size, color, spacing, shapes, images, alignment, and motion.

Size and position can signal reading order, spacing can group information, lines can explain relationships, and color can distinguish states. The role of each device should be understood before it is chosen.

A page explaining an implementation process should make steps, responsibilities, and conditions easy to distinguish. Information that needs checking requires accessible sources, explanations, and download links. Mobile text should wrap naturally, and buttons should be easy to reach.

The meaning of color and form depends on context, combinations, and actual use. A particular color cannot, on its own, establish a business’s scale, capability, or credibility.

Shared visual rules can make different pages belong to one system. Specific layouts should still follow their tasks. Introductions, process diagrams, reading pages, and operational interfaces can share a visual language while arranging information differently.

### Layer 6: Context of use—does it still work in the actual setting?

A desktop page may have a different reading order on a phone. A diagram clear on a large screen may become illegible as a chat preview. Material explained verbally at a meeting may lack necessary context when sent to someone reading alone.

These situations need checking in the actual medium.

Ask someone new to the subject to read it and explain what they understood. Ask someone with a defined task to locate information. Put the file into its real display size and check whether the text, relationships, and entry points remain clear.

Across settings, the facts and central proposition should remain consistent. Heading order, length, and interaction can change to suit the task.

## 3\. Connect the six layers through a fictional example

Suppose an equipment-maintenance business is preparing a service page. This situation is invented solely to explain the model. It represents no real project and assumes no conversion result.

The page is mainly for equipment managers assessing whether the service applies. They need to confirm the problems covered, how to submit a request, who will handle it, and which cases require separate assessment.

The six layers can connect as follows:

| Layer | What needs to be established | Specific implication for design |
| --- | --- | --- |
| Strategic intent | Help potential customers assess suitability and submit necessary information | Organize the page around suitability and preparing a service request |
| Audience tasks | Check equipment types, problem scope, conditions, and submission steps | Put answers where readers can readily find them |
| Value proposition | Receive and handle requests within a defined scope and agreed process | Support the claim with actual processes and conditions; do not promise unconfirmed response times |
| Content structure | Scope → process → required information → conditions → contact | Follow the decision process and expand details when needed |
| Visual rules | Distinguish steps, conditions, and exceptions; make key entry points visible | Use hierarchy, grouping, and a simple process diagram |
| Context of use | Managers may read on phones and forward the page to colleagues | Check narrow-screen reading, submission, and completeness after forwarding |

Now a shared basis exists for discussing button size or whether a process should run horizontally or vertically. The team can compare options against the reader’s task and device conditions.

Any new service promise on the page also needs to be traced back: can the business currently deliver it, is there a supporting process, and has the responsible person confirmed it? Each important statement in the design should have a traceable basis.

## 4\. When feedback arrives, identify the layer involved

When someone says, “The design does not quite work,” ask for more specificity.

Is the text hard to see? Is the emphasis unclear? Is the business difficult to understand? Is the next step missing? Or does a statement lack evidence? These issues need different changes.

[![Figure 2: Testing in context and revising the relevant layer](https://yutengfei.com/journal/strategy-to-visual-six-layer-model/model-02/diagram-en.svg)](https://yutengfei.com/journal/strategy-to-visual-six-layer-model/model-02/viewer-en.html)

Figure 2: Testing in context and revising the relevant layer

[Explore the diagram ↗](https://yutengfei.com/journal/strategy-to-visual-six-layer-model/model-02/viewer-en.html)[Download SVG ↓](https://yutengfei.com/journal/strategy-to-visual-six-layer-model/model-02/diagram-en.svg)

_Figure 2: Testing starts with a task defined in advance. A failed check leads to diagnosing the break, revising, and testing again. A passed check is recorded with its scope and version. This is a work-review process, not a forecast of business growth._

If text is difficult to read on a phone, inspect size, contrast, and layout. If readers still cannot explain the service, revisit content structure and the value proposition. If a claim exceeds actual capability, check the business facts first. If contact details and an entry point exist but submission fails, inspect the usage flow.

Sometimes the problem sits earlier: a page is trying to serve several very different audiences without a main task. Local adjustments cannot easily resolve the disagreement; strategic intent and audience tasks need to be reconsidered.

**Each revision should have an explicit hypothesis.** For example: “Readers cannot find service conditions because they are buried in a long paragraph.” Separate the conditions into a group and test the same task again. If the audience or task itself changes, update the test conditions first, rather than judging a new task against an old standard.

Observations from a few people can reveal problems, but cannot establish effectiveness for everyone. Clicks, time on page, and inquiries also need interpretation alongside traffic sources, tasks, and page changes. Business results depend on the service itself, price, channels, and execution as well as clarity of expression.

## 5\. Keep design decisions so others can continue the work

If each revision leaves only a new file, the reasons behind the choices become difficult to recover later.

I suggest keeping a simple record of important decisions. When someone takes over, adds pages, or introduces another language, they can continue from the same evidence.

| Record | What to clarify |
| --- | --- |
| Task and audience | Who the material primarily helps, and what judgment or action it supports |
| Claim and evidence | What is being stated, which information supports it, and what remains unconfirmed |
| Content and visual choices | Reasons for the sequence, grouping, and emphasis |
| Context and test method | Device or medium, participants, and tasks used for checking |
| Observations and limits | What was actually found and which situations remain uncovered |
| Revision and version | Which layer changed, who confirmed it, and when to check again |

There is no need to turn every detail into a report. Begin by recording decisions that affect direction, understanding, and use.

As the business changes, related content needs to change too. An old page may still look good, yet require review if its scope, data, or service conditions are outdated. Maintaining these connections is part of communication work.

## 6\. Clarify complex relationships, then draw them

This model also fits the thinking process of “map the complexity, simplify the structure, make it understandable, and express it visually.”

First lay out the business, audiences, tasks, evidence, channels, and conditions of use. Then identify the six layers and the connections that matter. Turn each layer into specific questions and checkable outputs. Finally, use diagrams to show the transmission, breaks, and feedback.

A diagram helps discussion when it compresses logic that has already been explained. Each node needs a clear meaning, and each line an explainable relationship, so readers can use it to review their own work.

I want good communication to invite attention and stand up to questions: why say this, why arrange it this way, what supports it, and who is it for?

Connecting these relationships layer by layer gives planning, writing, and design a shared basis for discussion and continuing revision.

[CC BY-NC-ND 4.0](https://creativecommons.org/licenses/by-nc-nd/4.0/)

Applies to original text unless otherwise stated; excludes third-party materials. Downloading or machine reading does not extend the existing license or separately authorize derivatives, commercial use or model training.

[AI usage guide](https://yutengfei.com/en/journal/ai/)


---

# Building an Industry Digital Platform in Verifiable Stages

- Author: Andrew David W.Y.
- Source: https://yutengfei.com/en/journal/phased-industry-digital-platform/
- Version: V1.0
- Published: 2026-10-19
- Revised: 2026-10-19
- Content status: Full text published
- Content type: Playbooks (solutions)
- Research topics: Stakeholder Capital Governance (stakeholder-governance)
- Ecosystem perspectives: Resource Ecosystem (resource) · Customer Ecosystem (customer) · Operations & Management Ecosystem (operations)

## Use this resource

**Purpose**: Define the first release around one verifiable business process, including its states, role permissions, and exception handling. Review four stages, assess system delivery and operating results separately, and use both to decide whether to expand.

**Conditions for use**: Check that the subject, objective and constraints fit the task. Confirm any conditions that the article does not specify.

**Playbooks · Objectives, combinations and implementation conditions**

**Evidence and validation limits**: The example illustrates how to analyze the situation and use the approach. When applying it, substitute actual business records for the example conditions and check the judgment and outcome. No separate external-validation result is recorded for this article. Publication does not establish effectiveness; check the evidence, assumptions and limits in the text.

This is a readable, citable knowledge resource, not an installed Skill. When using it with AI, retain its sources and limits and review the output.

## Full article

When an industry proposes a digital platform, it is easy to list functions: procurement, orders, inventory, delivery, settlement and reporting.

After making the list, we still need to answer which problem the first phase will solve, who will actually use it, how a business event will be completed, who handles errors and what will demonstrate that the work is done.

I think we can start with one real business process and make it a working system with clear boundaries and someone ready to operate it, then expand.

The first phase may cover one type of business and a small number of parties. It should still connect initiation, delivery, exceptions and reconciliation. Explain which steps the system supports and which remain manual.

**Build in stages, and assess system capability separately from business outcomes.** Here is a reference arrangement to adapt to the activity concerned.

## 1\. Identify the business problem before defining the first phase

Start with a recurring problem.

Perhaps buyers and suppliers use different specifications, confirming orders requires repeated calls, or delivery records do not match reconciliation records. Examine these situations to identify the step needing change, the roles involved and what a platform can undertake.

Be specific. Who initiates the activity, confirms supply, delivers and checks the result? What does each step receive and produce, and whose confirmation must it await?

Once those relationships are clear, determine the first-phase functions.

A “minimum scope” means a complete business process that can be examined independently. It need not include every product category or region, and effective manual practices can remain.

Within that process, however, there should be a place for normal work, changes, authorized confirmation and reconciliation. Otherwise, the pages may be built while people still have to connect the actual work informally.

State what this phase excludes. Register other requests and why they may be useful later, rather than turning every discussion directly into a new task.

A baseline record is also useful: which actions previously confirmed a transaction, where errors occurred and who carried extra coordination work. This provides a basis for later comparison.

## 2\. Connect business statuses, roles and records

For an ordinary fulfilment process, begin with four steps: request, supply confirmation, fulfilment and delivery, and reconciliation confirmation.

Each step should answer who acts, on what basis and what record remains.

A request does not mean that a supplier has committed. A delivery still requires checking receipt, discrepancies and settlement conditions. Keep these statuses separate so users can see where the activity stands.

Link related records through business IDs. A request may become several orders, an order may have partial deliveries, and several events may be reconciled together. Preserve individual records and their relationships.

I would avoid using a single “completed” status to cover all these matters. Delivery, reconciliation, receivables and cash received can be checked separately; a green indicator on a screen is insufficient.

Identify who maintains the information. If specifications, units, supply conditions or delivery dates change, who confirms the new version, which outstanding activities are affected and how will users know?

**Information reaching the next step is only part of the job. Someone must be responsible for its meaning, origin and scope.**

![Figure 1: A verifiable platform workflow around one real business process](https://yutengfei.com/journal/phased-industry-digital-platform/materials/en/asset-01.svg)

_Figure 1 is a general reference architecture. Documents are linked by their business relationships. Partial deliveries, changes and disputes require separate handling; one order need not correspond to one delivery or one receipt of payment._

[Download Figure 1 as SVG](https://yutengfei.com/journal/phased-industry-digital-platform/materials/en/asset-01.svg)

## 3\. Include permissions, exceptions and reconciliation in the first phase

A process working in a demonstration still needs to be examined against its users and possible changes.

Permission to view information does not necessarily include authority to confirm an order. Permission to enter data does not allow someone to change another party's result. Arrange viewing, entry, confirmation, amendment and export separately according to actual responsibilities.

Use only information the team is authorized to use and needs for this activity. Assign responsibility for its source, updates and error correction. Keep the corrected result distinguishable from the original evidence.

Design exception handling too. What status follows a changed requirement, insufficient supply, partial delivery, a quantity discrepancy or disagreement over reconciliation? Who takes over?

If every error can only be resolved by a developer changing data behind the scenes, frontline users struggle to understand what happened and later review loses its basis.

Provide handling routes for common exceptions. Record the facts, assign an owner, retain the handling and confirmation records, then return to the appropriate step. Keep unresolved matters pending rather than forcing confirmation to close the workflow.

Check easily missed cases: can a repeated delivery submission create a duplicate? Can other steps see a withdrawal or correction? Are old permissions adjusted when a person leaves their role?

These matters directly affect reliable operation and belong in first-phase acceptance rather than being postponed indefinitely.

## 4\. Advance through four stages, with evidence for each transition

### Stage one: define the problem and acceptance scope

Agree the problem, this phase's boundaries, participating roles, current conditions and separate system and business checks.

Confirm the scope, necessary records, permissions, principal exceptions, owners and resources together.

At this stage, the business and implementation teams should be able to use the same process diagram to explain the start and end, human confirmations and system processing.

### Stage two: complete the bounded workflow

In a controlled environment, test normal activity and the main exceptions. Actually perform each step: can it be executed, who may confirm it, does the data have corresponding evidence, and can errors be found and corrected?

When a problem appears, record what happened, the affected step and the person responsible for correction, then recheck. A ticked feature list is not enough.

Manual steps with explicit boundaries are acceptable, provided there is an owner, a recordkeeping method and a view on future adjustment. Do not move a scope into live use while gaps affecting critical activity remain unresolved.

### Stage three: trial within the confirmed scope

After system checks pass, admit limited real activity and participants.

Arrange daily support, issue response, information checks and fallback procedures for failures. During the changeover, identify the primary business record and how differences will be handled.

If short-term parallel checking is necessary, agree its purpose, owner and ending conditions. Do not indefinitely require frontline staff to enter the same activity twice while excluding the extra work from costs.

Collect system performance and business changes separately. Being able to record and confirm is one result; less rework, shorter waits and better reconciliation are another.

If critical permission, record or fulfilment problems prevent processing under the confirmed conditions, suspend the relevant new operations and use the agreed fallback for necessary work. Reconcile discrepancies, retest affected scenarios and obtain authorized confirmation before resuming.

### Stage four: establish stable ownership before reviewing expansion

Once this process is stable, someone must formally take over daily operation.

Assign actual owners and usable instructions for business rules, staff and permission changes, issue response, costs, and information export, retention and recovery.

Test the handover. Can the receiving team complete a transaction and handle the main exceptions? Can they find a fallback during a failure? Can backed-up information actually be restored and reconciled?

Then consider adding categories, participating nodes or regions. Review the new volume, information differences, support costs and responsibilities.

![Figure 2: Phased construction, separate acceptance and expansion review](https://yutengfei.com/journal/phased-industry-digital-platform/materials/en/asset-02.svg)

_Figure 2 organizes stages around delivery and acceptance conditions. Reaching a date or launching a function does not automatically authorize the next stage. A system may pass while business outcomes remain under observation._

[Download Figure 2 as SVG](https://yutengfei.com/journal/phased-industry-digital-platform/materials/en/asset-02.svg)

## 5\. System acceptance and business acceptance answer different questions

I think the key distinction is between what the system can do and what consequently happened in the business.

| Acceptance area | Main checks | Possible evidence |
| --- | --- | --- |
| System capability | Executable workflow, correct permissions, traceable records, and ways to handle exceptions and failures | Normal and exceptional operation records, permission checks, reconciliation and recovery tests |
| Business outcomes | Actual use, changes in delivery and reconciliation, rework, waiting, costs and burdens | Before-and-after records, participant feedback, inputs and issue-resolution records |

These conclusions need not be forced into one “pass.”

If the system supports the bounded process but the observation period is insufficient, retain “outcomes under observation.” Where agreed system conditions and business responsibilities are satisfied, limited use may continue while expansion is deferred.

Conversely, an apparently improved business period does not remove important permission, data or exception problems. People may have added substantial coordination effort, or other conditions may have changed. One favourable result should not conceal these issues.

Define the comparison: included activity, period, what counts as rework, and how extra hours and expenses are recorded. Use consistent definitions where possible.

Volume, order complexity, supply conditions and prices may also affect results. Record these changes to improve judgment, without expecting one limited trial to establish every causal relationship.

An acceptance conclusion can be specific: what is usable, what remains unresolved, who handles it, what cannot yet be confirmed and when the team will return to check.

## 6\. A fictional industrial-consumables example

This situation was written for illustration. It does not describe a real enterprise or an achieved implementation result.

Several manufacturers and their supply and delivery partners want to improve inquiries, delivery and reconciliation for common industrial consumables.

The first phase can be limited to one category of standard consumables, a defined group of participants and one fulfilment chain, rather than all procurement and management activities.

Clarify specifications, units and delivery conditions first. Supply confirmation creates the corresponding business record. Delivery and receipt link to it; partial arrivals, quantity differences and reconciliation opinions retain separate statuses.

| Stage | Initial deliverable in this example | How to check |
| --- | --- | --- |
| Define scope | One process from request to reconciliation, roles and acceptance definitions | Can parties explain responsibilities, inputs, outputs and phase boundaries? |
| Complete workflow | Normal ordering, supply confirmation, partial delivery and discrepancy handling | Can people act by role, and can quantities and records be reconciled? |
| Controlled trial | Limited live activity, issue support and fallback procedures | Who actually uses it, does it add duplicate work, and how are issues resolved? |
| Handover and expansion | Daily ownership, maintenance arrangements and review materials for the next scope | Can the receiving team operate independently, and does expansion have resources and evidence? |

If specifications are clearer but reconciliation still requires manual reaggregation, trace that step. Are records unlinked, definitions inconsistent or responsibilities unclear? Revise accordingly.

If one group can use the system normally while another needs extensive extra support, the conditions for use need further clarification. Examine the differences before maintaining the limited scope, retesting after changes or deferring expansion.

Feature construction, real use, daily handover and operating improvement remain connected but separately assessed.

## 7\. Revisit costs and responsibilities before expanding

A platform can usually do many more things. Every added scope may also create information maintenance, training, support and exception-handling work.

Include continuing operating costs in expansion review. Who pays for development, information preparation, role training, daily support, process changes and maintenance? Separate premises, equipment and fulfilment inputs by actual use rather than putting them all into a software-development budget.

Establish what existing systems can provide before deciding how to fill gaps. This approach does not presume that a particular software package must be replaced or that every industry needs the same technology.

More features, nodes and records still need to be assessed in actual activity. Whether they help the parties work more clearly and reliably provides a basis for further investment.

Before the next stage, ask:

1.  Which business process has this phase actually connected?
2.  Are normal and exceptional situations owned and supported by checkable records?
3.  What has been established about system capability and business outcomes separately?
4.  Who can take responsibility for daily operation, failures and information maintenance?
5.  What resources, responsibilities and authority does the next scope need?

Move forward with clear answers. Leave matters without adequate evidence pending review or validation.

A platform can be built process by process. Each part that can be delivered, used and taken over provides a basis for the functions and scale that follow.

* * *

[Download the accompanying Phased Construction and Acceptance Checklist](https://yutengfei.com/journal/phased-industry-digital-platform/materials/en/asset-03.md)

[CC BY-NC-ND 4.0](https://creativecommons.org/licenses/by-nc-nd/4.0/)

Applies to original text unless otherwise stated; excludes third-party materials. Downloading or machine reading does not extend the existing license or separately authorize derivatives, commercial use or model training.

[AI usage guide](https://yutengfei.com/en/journal/ai/)


---

# How to put funding sources and uses in one table

- Author: Andrew David W.Y.
- Source: https://yutengfei.com/en/journal/funding-sources-uses-table/
- Version: V1.0
- Published: 2026-10-19
- Revised: 2026-10-19
- Content status: Full text published
- Content type: Tools (tools)
- Research topics: —
- Ecosystem perspectives: Capital Ecosystem (capital) · Operations & Management Ecosystem (operations)

## Use this resource

**Purpose**: Use one table to distinguish budgets, indications of interest, commitments, and funds received, then connect intended uses to payments. Two reconciliations and a fictional example help identify available cash, projected gaps, and open questions.

**Conditions for use**: Check that the subject, objective and constraints fit the task. Confirm any conditions that the article does not specify.

**Tools · Fields, records and interpretation rules**

**Evidence and validation limits**: The amounts, percentages, and funding states are illustrative. For actual reconciliation, check the calculation basis, funding evidence, and records of receipts and payments separately. No separate external-validation result is recorded for this article. Publication does not establish effectiveness; check the evidence, assumptions and limits in the text.

This is a readable, citable knowledge resource, not an installed Skill. When using it with AI, retain its sources and limits and review the output.

## Full article

A total is often the most misleading part of a funding table. Budgeted expenditure, planned fundraising, an expression of willingness to invest, and cash received can make a project appear funded if they are all placed in one column.

I would hold off on adding them up. First establish where the money is now, who may use it, what it may be used for, and under what conditions.

## 1\. Define the scope before examining the figures

State the project, receiving entity, period and currency at the top of the table. Cash held by different entities cannot simply be combined because they participate in the same arrangement. Different currencies cannot be added directly. For conversions, retain the original amount and currency, the exchange-rate source and date, and the conversion basis.

Opening cash, actual inflows and outflows during the period, and closing cash must reconcile. Do not register opening cash again as new financing for the period. Record both sides of transfers between projects. When consolidating, identify internal transfers so that the same money is not counted repeatedly as new funding.

A budget shows planned expenditure. Funding records show how much has actually been obtained. The two must correspond, but neither replaces the other.

## 2\. Distinguish at least three stages for each source

For a planned source, record the expected amount and its basis. Once an agreement is signed, check payment conditions, deadlines and cancellation terms. When funds actually arrive, verify the receiving entity, amount, date and corresponding records.

Receipt raises a further question: may this money be used for the current purpose? Earmarked use, temporary custody, pledges, refund obligations and other restrictions may limit its use. Record actual receipt separately from freedom to use the money.

I suggest retaining descriptions such as “proposed”, “agreed, not yet received”, “received, conditions pending verification”, “confirmed available for specified purposes”, and “use suspended”. Enter status based on the checks performed; do not change it automatically when a date arrives.

Give each source a stable identifier and retain a history of status changes. If one source progresses from an expression of intent to actual receipt, update that source’s progress. Do not add together its amounts at different stages.

## 3\. Link uses to specific payments

“For operations” is not specific enough. Record what is being purchased, who receives payment, why payment is due now, the relevant contract or approval, the due date, and the delivery and acceptance conditions.

Keep payment requests, approval, actual payment and acceptance separate. A budget allocation does not authorize immediate payment. Approval does not mean payment has occurred. Payment does not mean the other party has completed delivery.

One source may cover several uses, and one use may draw on several sources. Keep matching records showing amounts, periods and restrictions. A connecting line without an amount cannot reveal whether the same money has been allocated twice.

![Registering sources and matching uses](https://yutengfei.com/journal/funding-sources-uses-table/materials/en/asset-01.svg)

[Download SVG: Registering sources and matching uses](https://yutengfei.com/journal/funding-sources-uses-table/materials/en/asset-01.svg)

## 4\. Examine the gap through a fictional example

Everything below is a teaching assumption. Amounts are in exercise units and do not represent real clients, accounts or financing arrangements.

Assume opening cash is 0. Source S01 has a planned contribution of 1000, but only 600 has arrived. Of that amount, 200 is subject to earmarked-use and disbursement conditions and must not fund ordinary purchases. Even expenditure for the earmarked purpose must wait until its applicable conditions are met. Source S02 is an expression of intent for 300; nothing has arrived.

As of the verification date, cash is 600 and the amount currently available for ordinary purchases is 400. Do not add 1000, 600 and 300 together, or count the intended 300 toward a payment due now.

Ordinary purchases require 450, and specified-purpose expenditure requires 150. Under the current conditions, ordinary purchases have a shortfall of 50. Although 150 is less than the restricted 200, the specified-purpose conditions still need checking. Sufficient funds alone do not authorize payment.

Total requirements of 600 exactly match cash of 600. The totals balance, but the conditions do not. The work cannot proceed on the strength of that total. This is why the matching table must retain restrictions.

Now assume 300 is actually paid for ordinary purchases. With no other cash changes, closing cash is 300. The restricted 200 is unchanged, leaving an ordinary available balance of 100. Of the original ordinary requirement of 450, 150 remains unpaid, so the ordinary funding shortfall is still 50. Do not leave the paid 300 in future unpaid requirements, as that would overstate the gap.

## 5\. Reconcile cash and allocations separately

Cash reconciliation checks whether opening cash plus actual inflows minus actual outflows equals closing cash. Allocation reconciliation checks whether proposed matching amounts exceed what each source permits, whether a use is allocated funding twice, and whether unpaid requirements exclude amounts already paid.

Perform both checks. Reconciled cash does not mean a use is approved; a balanced budget does not mean cash has arrived.

For refunds, reversals or changed conditions, record the original identifier, the basis of the change, and the affected matching rows. Do not simply delete the original entry. Other participants need to know whether the difference reflects a business change, a changed accounting or calculation basis, or a previous recording error.

## 6\. Connect gaps to the next action

When a gap appears, identify its cause: insufficient funds, a timing mismatch, restricted use, or outstanding approval or payment conditions. Each calls for a different response.

Proposed additional sources may be recorded as plans, but cannot be treated as funds already available. Deferral, a smaller scope, phased execution or an alternative source require confirmation by the appropriate authority and checks of contractual and performance implications.

If a responsible person is unconfirmed, mark the assignment as pending. Record planned dates separately from actual completion dates. Do not turn uncertain financing into a commitment or a payment awaiting approval into a completed payment just to make the table look complete.

![Cash movements and revised allocations](https://yutengfei.com/journal/funding-sources-uses-table/materials/en/asset-02.svg)

[Download SVG: Cash movements and revised allocations](https://yutengfei.com/journal/funding-sources-uses-table/materials/en/asset-02.svg)

## 7\. Trace one amount through the whole relationship

Start with the basis for a funding source. Find the receipt record, use restrictions, approval for the use, payment and closing balance. Record identifiers, versions, dates and reviewers for each link.

Putting sources and uses together connects actual cash and its conditions to operating tasks. Readers should be able to see what can be done now, what conditions remain unmet, and what to check next. This working framework does not replace actual financial books, professional review or payment authority.

[Download the blank working table](https://yutengfei.com/journal/funding-sources-uses-table/materials/en/asset-03.md)

## Related reading

- [Understanding a funding model: from rules to realized proceeds](https://yutengfei.com/en/journal/capital-rules-and-mechanism-diagnosis/)
- [How Can Industry Operations and Capital Arrangements Support Each Other?](https://yutengfei.com/en/journal/industry-operations-capital-alignment/)

[CC BY-NC-ND 4.0](https://creativecommons.org/licenses/by-nc-nd/4.0/)

Applies to original text unless otherwise stated; excludes third-party materials. Downloading or machine reading does not extend the existing license or separately authorize derivatives, commercial use or model training.

[AI usage guide](https://yutengfei.com/en/journal/ai/)


---

# Explain a Business in One Sentence, One Paragraph and One Diagram

- Author: Andrew David W.Y.
- Source: https://yutengfei.com/en/journal/business-positioning-one-page-exercise/
- Version: V1.0
- Published: 2026-10-19
- Revised: 2026-10-19
- Content status: Full text published
- Content type: Training (training)
- Research topics: —
- Ecosystem perspectives: Customer Ecosystem (customer) · Operations & Management Ecosystem (operations)

## Use this resource

**Purpose**: Choose an audience and explain one business through a positioning sentence, a short explanation, and a one-page relationship diagram. Ask someone new to restate it, then use their reading to check the value proposition and the diagram.

**Conditions for use**: Check that the subject, objective and constraints fit the task. Confirm any conditions that the article does not specify.

**Training · Learning goals, practice and feedback**

**Evidence and validation limits**: This exercise uses fictional materials. Compare how participants reached their judgments and review the evidence they used after the exercise. No separate external-validation result is recorded for this article. Publication does not establish effectiveness; check the evidence, assumptions and limits in the text.

This is a readable, citable knowledge resource, not an installed Skill. When using it with AI, retain its sources and limits and review the output.

## Full article

A business can produce a great deal of material: introductions, plans, processes and strengths, each with plenty to say. Yet someone encountering it for the first time may still be unable to explain whom you help and what you do.

Adding more material may not solve that problem.

I would step back and ask four questions: whom do we serve, what problem do we solve, how does it work, and what evidence supports it?

Once those are clear, try a positioning sentence, an explanatory paragraph and a one-page diagram. Then ask someone unfamiliar with the business to explain it back in their own words.

Does their account describe the same thing we intended?

That is the focus of this exercise.

## 1\. Fix the audience first

A clear explanation needs a specific reader.

Customers want to know whether it addresses their problem. Partners want to know how to participate and what they undertake. Internal staff need the next actions and confirmation responsibilities.

These versions may have different emphases without changing the core facts. A capability still being designed must not become a mature service in the customer version. An internal target must not become an achieved result on a promotional page.

The wholly fictional business for this exercise is a **store campaign-material coordination service**.

It proposes to serve small retail teams with several stores and limited design-coordination staff. The reader is a team leader encountering the proposal for the first time, deciding whether it is relevant.

Requirements scattered across chats, different prices and dates by store, and difficulty identifying the final version are problems the team has proposed for validation. At this stage there is only a plan and desktop samples, with no real-store trial.

Put those limits on the table. None of the three forms of expression should quietly remove them.

[Open source cards E01–E08](https://yutengfei.com/journal/business-positioning-one-page-exercise/materials/en/asset-01.md)

## 2\. Lay out the material before seeking an impressive phrase

Starting with a grand positioning phrase can quickly lead to “empowerment,” “ecosystem” or “growth platform.” Readers may still have no idea how the business relates to them.

I suggest placing the materials under four questions.

**Whom do we serve?** Break down “all enterprises” into specific people, organizations and situations. A diffuse audience makes a sentence vague.

**What do we solve?** Describe the reader's actual difficulty: unclear information, disconnected handovers or no one confirming the final version? What we like doing is not automatically a confirmed customer need.

**How does it work?** Follow the process from what the other party supplies to what we deliver. Explain who handles it, who confirms it and where a problem returns.

**What evidence supports it?** Examine the materials individually. A plan shows intended work; a sample allows format checks; a real trial provides use records. They support different judgments.

One material may answer several questions, but every judgment needs a corresponding source. Record what must be obtained when it is missing.

Do not invent a customer, an effect or a capability to fill four boxes.

![Figure 1: Iteration from four questions to three forms of expression](https://yutengfei.com/journal/business-positioning-one-page-exercise/materials/en/asset-02.svg)

Figure 1: Organize the facts through four questions, then express them in three forms. Route reader feedback separately to communication problems and evidence gaps.

[Download Figure 1 as SVG](https://yutengfei.com/journal/business-positioning-one-page-exercise/materials/en/asset-02.svg)

## 3\. Give each form one clear job

The sentence, paragraph and diagram may differ in length while describing the same business.

### A sentence: show the reader why it matters to them

Identify the audience and problem, adding the key approach and current stage where necessary.

The sentence need not contain every detail. Evidence, process and limits can follow immediately. But if removing “being trialled” makes a proposal sound like an established service, retain that qualification.

Positioning and a slogan are also different. A slogan may express an attitude; positioning should tell people what the business does. A universally agreeable phrase still leaves the explanation to be done.

### A paragraph: explain operation and evidential limits

For an interested reader, explain where a service starts, what happens, what they receive and who confirms it.

State what can currently be examined. If there are only desktop samples, show those. If there is no real-use record, retain that fact rather than replacing it with “widely recognized.”

“We hope to automate synchronization” and “we synchronize automatically” can lead to very different judgments.

### A page: draw the relationships

Show who delivers what to whom, where confirmation occurs and how a problem returns.

The campaign owner supplies confirmed requirements, the service team returns drafts for checking, and the final handover is a version directory with IDs and statuses. Information, actions and confirmation responsibilities give arrows a meaning.

A network of large circles labelled “resources,” “platform,” “customers” and “growth” may still fail to explain a single service interaction.

**For every arrow, ask what is actually passing along it.**

[Open the expression and reader-retelling worksheet](https://yutengfei.com/journal/business-positioning-one-page-exercise/materials/en/asset-03.md)

## 4\. Clarify relationships before choosing colours and style

Visual quality matters to me too. Start by placing participants, deliverables and confirmation points correctly.

Then distinguish roles with colour, use solid lines for the proposed handovers in this diagram, and use dashed lines or separate notes for unvalidated or undeveloped items. Include a legend and words rather than relying on colour alone.

The feeling conveyed by a colour is an expressive choice. A technological appearance does not establish a working system; a professional appearance does not show that the business chain has run successfully.

Automatic synchronization remains an idea here and must not appear as an operating core capability. “Confirmed usable” in a desktop record means only that simulated fields passed a check. It is not real customer acceptance or formal publication.

The diagram explains the design. Reliable delivery, willingness to pay and business outcomes need separate validation.

## 5\. Let an unfamiliar reader respond before helping them

“Unfamiliar” means unfamiliar with the activity, not necessarily a stranger.

Give the reader the three forms and let them read independently. Do not explain terms or point to the intended emphasis yet.

Ask them to explain four things in their own words:

1.  Who uses this business, and what problem do they face?
2.  How does cooperation start, who confirms along the way and what is received?
3.  What exists now, and what remains a proposal or idea?
4.  What is unclear, and which effects lack evidence?

Record their actual words before correcting them.

An omission may mean the information was buried. Reversed roles may signal an unclear responsibility diagram. An invented system or guarantee calls for checking whether a word or line implied more than intended.

To examine the sentence, paragraph and diagram independently, use different readers. With one reader, present them in that order and record the added understanding each time. Later responses are influenced by earlier material and are not independent tests.

Accurate retelling is more informative than “What do you think?” followed by “Looks good.”

## 6\. Revise along two different paths

Some problems are in the explanation.

An overbroad audience, a late mention of the deliverable or an arrow without a confirmer can be corrected in text and diagrams. Ask someone to read again and see whether misunderstanding decreases.

Other problems concern missing business evidence.

Whether customers have the problem, how much labour a trial requires and what they will pay for cannot be solved by changing words. Conduct interviews, trials or further recording, then update the explanation.

A problem can involve both. If a reader thinks synchronization already works, correct the misleading expression and retain the fact that the capability has not been developed.

Clear retelling tests whether an explanation is understood. It does not establish demand, service effectiveness or profitability.

[Open the simulated samples and evidence boundaries](https://yutengfei.com/journal/business-positioning-one-page-exercise/materials/en/asset-04.md)

## 7\. Leave a version that can be maintained

I hope the exercise produces more than three attractive finished pieces.

Keep a source table: which statement corresponds to which material, its current status, who checks it and what future changes trigger an update.

When a sentence changes, check the paragraph and diagram too. An unchanged target audience should not become “all industries” in one figure. An undeveloped system should not become an automated platform in another promotional context.

A reference set appears after the exercise. It illustrates one way to organize the material rather than prescribing identical wording. Complete your version first, then compare facts, responsibilities and evidence.

![Figure 2: Reference mechanism for coordinating store campaign materials](https://yutengfei.com/journal/business-positioning-one-page-exercise/materials/en/asset-05.svg)

Figure 2: A reference for the same exercise, showing proposed handovers, checks and returns. The entire service remains at the proposal and desktop-sample stage.

[Download Figure 2 as SVG](https://yutengfei.com/journal/business-positioning-one-page-exercise/materials/en/asset-05.svg)

[After drafting and independent retelling, consult the reference expressions and review](https://yutengfei.com/journal/business-positioning-one-page-exercise/materials/en/asset-06.md)

## Exercise materials

Lay out the materials, identify the four questions, turn them into concrete expression, and test it through diagrams and retelling. Organizing complexity, simplifying, making action easier and drawing the relationships become a practical piece of work.

1.  [Exercise plan and instructions](https://yutengfei.com/journal/business-positioning-one-page-exercise/materials/en/asset-07.md)
2.  [Source cards E01–E08](https://yutengfei.com/journal/business-positioning-one-page-exercise/materials/en/asset-01.md)
3.  [Simulated samples and evidence boundaries](https://yutengfei.com/journal/business-positioning-one-page-exercise/materials/en/asset-04.md)
4.  [Expression and retelling worksheet](https://yutengfei.com/journal/business-positioning-one-page-exercise/materials/en/asset-03.md)
5.  [Reference expressions and review](https://yutengfei.com/journal/business-positioning-one-page-exercise/materials/en/asset-06.md)
6.  [Download the blank four-question and retelling exercise diagram as SVG](https://yutengfei.com/journal/business-positioning-one-page-exercise/materials/en/asset-08.svg)

The business, materials, samples and records are independently written fictional teaching materials. The four questions, exercise process and diagrams were designed for this edition. Their effectiveness still needs testing in actual use.

[CC BY-NC-ND 4.0](https://creativecommons.org/licenses/by-nc-nd/4.0/)

Applies to original text unless otherwise stated; excludes third-party materials. Downloading or machine reading does not extend the existing license or separately authorize derivatives, commercial use or model training.

[AI usage guide](https://yutengfei.com/en/journal/ai/)