COMU1130 Chap.2 Platform Anatomy and Market Sides
Platform Anatomy and Market Sides
Platform power is assembled from data, algorithms, interfaces, ownership, business models and user agreements. This chapter opens that anatomy and then maps multi-sided services without collapsing every participant into the word user. Students learn to identify what each side contributes, what it receives and which information or terms the operator controls.
The result is a concrete explanation of network effects, dependency and governance. Data are the recorded, volunteered or inferred inputs from which a service builds categories. Algorithms transform those inputs into outputs, but the problem definition and available labels come first. Interfaces make the output actionable through menus, defaults, dashboards and prompts.
Ownership and the revenue model establish which outcomes the operator has reason to optimise, while agreements allocate permissions, obligations and responsibility. None of these elements explains the platform alone. A ranking becomes socially important because it appears in an interface, controls an opportunity, supports a business objective and operates under contractual rules.
Multi-sided analysis then asks what each participant group supplies. Audiences may supply attention, producers supply material, advertisers supply revenue and the operator supplies infrastructure while controlling access among them. Growth can create network effects because another participant makes the service more useful, but usefulness does not establish fair distribution.
The same growth may increase switching costs and let one rule-maker alter fees or visibility. Dependency becomes clearer when reputation, contacts or work histories cannot move elsewhere. Always distinguish formal choice from practical capacity: a participant may be free to leave while losing the accumulated value that makes participation worthwhile.
A precise answer identifies the anatomical element, the market side affected and the operator-controlled rule that links them.
What this chapter covers
- 01
data and algorithms
- 02
interfaces and user agreements
- 03
ownership and value capture
- 04
multi-sided participant groups
- 05
network effects and dependency
Worked example · free
Map a three-sided repair marketplace
- 1Separate households, tradespeople and insurers.
- 1State each contribution and benefit.
- 1Locate matching and fee rules.
- 1Judge network value and dependency.
Key terms
- Interface
- The visible and interactive layer through which users encounter platform rules and choices.
- Business model
- The arrangement through which a platform creates and captures economic value.
- Multi-sided market
- A market joining distinct participant groups whose presence creates value for one another.
Platform Anatomy and Market Sides FAQ
What belongs in platform anatomy?
A complete anatomy includes data collection, algorithmic processing, interface design, ownership, the business model and contractual rules. Their interaction explains the service more accurately than treating an algorithm as an isolated cause.
Why should participant sides be separated?
Different sides contribute different resources and face different risks. A learner, advertiser and content provider may all use one service, but they do not pay, benefit or depend on the platform in the same way.
What do network effects explain?
Network effects explain why a service can become more useful as participation grows. They can also increase switching costs and operator leverage, so usefulness and fair governance must be evaluated separately.
What evidence reveals a platform's real control point?
Look for a decision the operator can change without equivalent agreement from the participant sides. Useful evidence includes the data visible before a transaction, a ranking that allocates attention, the fee or price rule, API permissions, suspension terms and whether reputation can be exported. Connect the evidence to one anatomical layer and one market side.
A user agreement matters when it authorises an action; an interface matters when it makes that action practical; a business model matters when it supplies the incentive. The control point is rarely the algorithm in isolation. It is the assembled rule that determines how participants meet, what they know and what they can carry away.
Naming that assembly produces a stronger claim than saying the company has power because it owns the technology.
Assessment move
Take one familiar service and label its anatomy in six lines. Then create a table with participant side, contribution, promised benefit, dependency and risk. Finish by identifying one rule the operator can change unilaterally. This sequence produces a causal paragraph without relying on vague references to technology or innovation. Repeat the exercise with an unfamiliar scenario so recognition does not depend on a brand name.
Put data, algorithm, interface, ownership, revenue and agreement on separate cards. For each card, write one observable piece of evidence and one question that evidence cannot answer by itself. Next create a market-side ledger: group, contribution, benefit, information visible before action, information withheld, exit cost and appeal route. Draw arrows only after the roles are distinct.
Use the ledger to explain a network effect without equating growth with justice. Then change one rule, such as a ranking weight, transaction fee or data-access permission, and predict different outcomes for two sides. A strong revision drill alternates definition and application: define an API, apply controlled access to a case, then state a consequence for competition or dependence.
When checking a paragraph, highlight the sentence that locates the control point. If no sentence specifies who can alter the rule, the analysis is still descriptive. End with a qualified synthesis that can preserve coordination value while identifying the governance power retained by the operator.