Business models, digital value and organizational change
A business model explains how an organization creates, delivers and captures value. Separate the customer's problem from the resources, activities, partners, channels and revenue mechanism used to address it. Moving from an outright sale to a subscription changes the revenue arrangement, but does not by itself prove profitability or customer benefit. A platform connects participating groups, while a conventional pipeline transforms inputs into outputs. Positive cross-side network effects may increase value when participation on one side attracts the other. Congestion, poor matching, mistrust and switching alternatives can limit those effects. Assess incentives and unit economics rather than assuming that every digital platform succeeds.
Map value propositions to actual operating capabilities. A low subscription price can attract users while support and acquisition costs exceed receipts. Distinguish customer acquisition, retention, churn, contribution and cash collection. A fictional service has100subscribers at10currency units each month and variable service cost3per subscriber. Before fixed costs its monthly contribution is700, not1000. If20customers leave and10join, its ending customer count is90. Revenue growth driven by price increases does not prove better retention. Cloud services and robotic process automation can change resource access and transaction processing, but responsibilities for data quality, authorization, security and exception handling remain.
Organizational change concerns people, processes, structures and culture as well as technology. A planned model such as Lewin's unfreezing, movement and refreezing offers a way to organize discussion, not an immutable law requiring organizations to become static. Kotter's model emphasizes urgency, coalition, direction, enabling action and reinforcement. Compare the purpose of a model with the actual context. A communication campaign does not replace consultation about changed tasks, fair treatment, training and feedback. Resistance may reveal a legitimate operational problem rather than simple unwillingness to cooperate.
A project can deliver a system while the anticipated business benefit fails to appear. Establish an initial business case, assumptions, accountable benefit owners and measures that can reveal adverse effects. Use a limited pilot when uncertainty and reversible learning justify one. Iterative delivery can expose mistaken assumptions early, while tightly specified work may need more sequential coordination. Do not treat Agile as an absence of planning or a guarantee of success. Map interdependencies and maintain proportionate change control.
Evaluate improvement with relevant evidence. Benchmarking identifies performance differences but does not prove that another organization's practice will transfer unchanged. Lean examines waste and flow; quality management considers customer requirements, process capability and sustained learning. A short-term improvement can reverse if incentives reward old behavior or staff cannot maintain the new process. Document lessons, review benefits after implementation and distinguish measured results from a persuasive narrative. These are general management foundations, not a claim of exact current CIMA syllabus calibration.