Value Creation and Operating Architecture

Introduction

A business model becomes economically meaningful only when its promised value can be created and delivered consistently. A compelling value proposition is not sufficient by itself: an enterprise must organize activities, resources, partners, technologies, channels and customer relationships into an operating architecture that makes the promise credible. Operating architecture is the designed system through which an organization transforms inputs into customer outcomes and financial returns.

For an entrepreneur, this creates a central design challenge. Operations must be reliable enough to protect quality, flexible enough to respond to changing demand, efficient enough to support viable costs, and distinctive enough to create a defensible customer experience. These requirements may conflict. High customization can increase customer value but reduce capacity and raise costs. Excess capacity can improve responsiveness but create idle resources. Automation can improve consistency while weakening human connection. Consequently, operating architecture is not merely an implementation issue; it is a core component of business model design.

This chapter explains how entrepreneurs identify key activities, design processes, select channels, structure customer relationships, and build service-delivery systems. It also introduces practical metrics and decision tools for aligning operations with quality, capacity, cost and customer experience.

Learning Objectives

By the end of this chapter, you should be able to:

1. Explain the relationship between value creation and operating architecture.
2. Distinguish primary, support and governance activities.
3. Map and analyze processes using customer journeys, service blueprints and process measures.
4. Select channels and customer-relationship mechanisms appropriate to a business model.
5. Analyze capacity, bottlenecks, utilization, throughput and operating costs.
6. Design service-delivery systems that balance efficiency, quality and experience.
7. Evaluate technology, AI, outsourcing and partnership decisions responsibly.
8. Apply an operating-architecture framework to an entrepreneurial case.

1. Value Creation as a System

Value creation is the process of converting resources into outcomes that customers and other stakeholders regard as worthwhile. Inputs may include materials, labor, knowledge, data, capital, technology and partner capabilities. Outputs may be physical products, services, experiences, information, access, risk reduction or social outcomes.

A useful distinction is between value creation and value capture. Value creation concerns the benefits produced for customers and stakeholders. Value capture concerns how the enterprise receives revenue, reduces costs, protects margins or obtains other returns from that value. A business may create substantial customer value but capture little of it if its pricing, channel economics or cost structure is poorly designed.

Operating architecture connects the two. It determines how a promise such as “same-day repair,” “personalized learning” or “low-cost sustainable meals” is translated into repeatable activity. Its major elements are:

• Resources: people, equipment, facilities, capital, data and intellectual property.
• Activities: actions required to design, produce, market, sell, deliver and support the offering.
• Processes: connected sequences of activities with inputs, outputs, owners and performance requirements.
• Channels: routes through which customers discover, purchase, receive and obtain support for the offering.
• Relationships: patterns of interaction between the firm and its customers.
• Governance: rules, controls, responsibilities and standards that guide decisions.
• Feedback: information used to improve the offering and the operating system.

The architecture should be judged not only by internal efficiency but by its ability to deliver the customer’s desired outcome. A fast internal process is not valuable if it produces the wrong product. A low-cost channel is not advantageous if customers abandon it because it is confusing or inaccessible.

2. Designing the Activity System

2.1 Types of activities

Entrepreneurs can classify activities into three broad categories:

This classification resembles value-chain thinking, but entrepreneurial firms should avoid treating activities as isolated departments. A customer order may cross marketing, sales, inventory, payment, fulfillment and support. The customer experiences one system, not a sequence of organizational silos.

2.2 Identifying key activities

A key activity is one that is essential to delivering the value proposition, protecting a critical resource, satisfying a regulatory requirement or maintaining an important customer relationship. An activity is not “key” simply because it consumes time or appears in an organizational chart.

A practical identification process is:

1. State the customer outcome in observable terms.
2. List the conditions necessary to produce that outcome.
3. Identify activities that create, enable or verify those conditions.
4. Identify dependencies between activities.
5. Test whether each activity is performed internally, outsourced, automated or shared with a partner.
6. Define the performance standard for each activity.

For example, a meal-subscription venture promising nutritious meals delivered on schedule requires more than cooking. Key activities may include demand forecasting, menu design, supplier qualification, food-safety control, portioning, cold-chain management, route planning, subscription billing and complaint resolution.

2.3 Activity systems and strategic fit

An activity system is stronger when activities reinforce one another. A low-price retailer may combine limited product variety, high inventory turnover, simple stores, standardized processes and self-service technology. Each choice supports the others. Attempting to add extensive customization without changing the cost and process architecture can undermine the model.

Entrepreneurs should ask:

• Which activities are essential to our distinctive value proposition?
• Which activities must be performed exceptionally well?
• Which activities can be standardized?
• Where would flexibility create customer value?
• Which activities expose us to operational, legal or reputational risk?
• What capabilities would be difficult for competitors to copy?

A useful principle is fit before optimization. Improving one activity locally may damage the whole system. For instance, maximizing sales promotions may increase orders beyond fulfillment capacity, producing delays and customer dissatisfaction.

3. Process Design and Analysis

A process is a structured set of activities that transforms an input into an output for an internal or external customer. Good process design specifies the trigger, sequence, decision points, responsible roles, required resources, output and performance standard.

3.1 Process mapping

A process map should show the actual flow of work rather than the idealized organization chart. It can include:

• customer actions;
• front-stage employee or system actions visible to customers;
• back-stage activities not directly visible;
• supporting systems and suppliers;
• handoffs, queues, rework and decision points.

For services, a service blueprint is particularly useful because it separates the customer experience from the underlying delivery system. For example, an online tutoring service may map student registration, diagnostic assessment, tutor matching, lesson delivery, payment, progress reporting and renewal.

3.2 Process performance measures

Common measures include:

• Throughput: units or customers completed per period.
• Cycle time: elapsed time from process start to completion.
• Waiting time: time during which work is not actively processed.
• First-pass yield: percentage completed correctly without rework.
• Defect rate: proportion failing a defined requirement.
• Service level: percentage meeting a stated delivery or response target.

For a stable process, Little’s Law relates average work-in-process, throughput and flow time:

Here, L is average work-in-process in units, λ is average throughput in units per unit of time, and W is average time in the system. The relationship assumes a stable system over the period considered, with average inflow approximately equal to average outflow. Units must be consistent: if throughput is customers per hour and flow time is hours, work-in-process is customers.

Worked example. An online support team resolves an average of 30 cases per hour. Cases remain in the system for an average of 2 hours, including waiting. The average number of cases in the system is:

L = 30 × 2 = 60 cases.

If the firm wants to reduce the number of open cases while maintaining throughput, it must reduce total flow time, perhaps by removing approval delays, improving knowledge resources or adding appropriate capacity.

3.3 Bottlenecks and constraints

A bottleneck is a resource or process stage whose effective capacity limits the output of the whole system. The bottleneck may be a machine, employee, approval step, supplier, payment gateway or scarce specialist.

The basic capacity of a resource can be estimated as:

If a bakery has two ovens, each available for 8 hours per day, and each produces 12 trays per hour, theoretical daily capacity is 2 × 8 × 12 = 192 trays. If expected availability is 90% because of cleaning, changeovers and minor downtime, effective capacity is 192 × 0.90 = 172.8, or approximately 173 trays per day. This estimate assumes the ovens are the binding resource and that labor, ingredients, demand and downstream capacity are sufficient.

Capacity should be distinguished from demand. A system with capacity of 173 trays but demand of only 120 trays has unused capacity. A system facing demand of 200 trays has a capacity shortfall unless it adds resources, changes the process or manages demand.

The bottleneck’s utilization can be represented as:

Utilization is dimensionless and often expressed as a percentage. At high utilization, small variations in arrivals or processing times can cause queues to increase sharply. Therefore, “full utilization” is not always desirable, particularly in service systems where customers expect rapid response.

4. Quality, Cost and Capacity Alignment

4.1 Quality as conformance and experience

Quality has at least two dimensions. Conformance quality concerns whether the offering meets specified requirements. Perceived quality concerns how customers judge performance relative to expectations and alternatives. A restaurant can prepare food according to a recipe yet receive poor evaluations because service is slow or the environment is unpleasant.

Quality should be translated into measurable standards, such as accuracy, reliability, durability, response time, accessibility, safety or empathy. Standards must be meaningful to customers rather than selected only because they are easy to measure.

A useful quality-control sequence is:

1. Define the customer-critical requirement.
2. Identify where failure can occur.
3. Build prevention into the process.
4. Detect errors as early as possible.
5. Record causes, not merely symptoms.
6. Correct the process and verify improvement.

The cost of quality includes prevention, appraisal, internal failure and external failure. Training and process design may increase prevention costs while reducing refunds, rework, complaints and reputational damage. Entrepreneurs should evaluate total cost rather than assuming that the cheapest immediate action is the lowest-cost choice.

4.2 Cost structure

Operating cost can be analyzed as fixed, variable and mixed cost. Fixed costs do not change directly with short-term output, whereas variable costs change with activity volume. Mixed costs contain both components.

For a simple operating period:

This formula assumes a relevant operating range in which fixed cost and unit variable cost remain approximately constant. It excludes nonlinear effects such as overtime premiums, volume discounts or capacity expansion.

If fixed cost is $20,000 per month, variable cost is $8 per order and monthly volume is 3,000 orders, total cost is:

$20,000 + ($8 × 3,000) = $44,000.

Unit cost is $44,000 ÷ 3,000 = $14.67 per order, rounded to the nearest cent. Unit cost falls as volume increases in this example because fixed cost is spread across more orders, but this should not be interpreted as an unlimited economy of scale.

4.3 Capacity choices

Entrepreneurs commonly choose among three capacity strategies:

• Lead capacity: add capacity before anticipated demand.
• Lag capacity: add capacity only after demand is demonstrated.
• Matching capacity: add capacity in smaller increments as demand develops.

Lead capacity improves responsiveness but increases the risk of idle resources. Lag capacity protects cash but may create lost sales and poor service. Matching capacity balances risk but requires reliable information and flexible resource arrangements.

Capacity can be increased through equipment, staffing, cross-training, scheduling, supplier agreements, self-service, automation or process simplification. Before adding resources, managers should confirm that the bottleneck has been correctly identified. Extra staff in a non-bottleneck area may not increase system output.

5. Channels and Customer Relationships

5.1 Channel architecture

A channel is a route through which customers become aware of, evaluate, purchase, receive and obtain support for an offering. Channels may be direct, intermediary-based, physical, digital or hybrid.

The channel decision should examine five customer jobs:

1. Discovery: How does the customer learn that the offering exists?
2. Evaluation: How does the customer assess its relevance and credibility?
3. Purchase: How is the transaction completed?
4. Delivery or access: How does the customer receive the value?
5. Support and recovery: How are questions, failures and returns handled?

A channel should be assessed for reach, control, cost, speed, data access, trust, accessibility and strategic fit. Direct digital channels may provide data and control but require the firm to develop acquisition, payment and support capabilities. Intermediaries may provide reach and credibility but reduce margin and customer visibility.

A multichannel model is not automatically customer-centered. If channels use inconsistent prices, customer records or service policies, customers may experience confusion and employees may face avoidable complexity. An omnichannel architecture aims to provide continuity across channels, such as allowing a customer to begin an application online and complete it with an advisor.

5.2 Customer relationships

Customer relationships range from automated self-service to high-touch professional support. Common forms include:

• self-service;
• automated service and recommendation;
• transactional support;
• dedicated account management;
• communities and peer support;
• co-creation and feedback partnerships.

The appropriate relationship depends on customer risk, complexity, frequency, emotional importance and willingness to pay. A low-risk routine purchase may suit self-service. A complex business implementation may require consultation, onboarding and continuing account management.

Customer relationship design should specify the moments that matter: first use, payment, delivery, renewal, failure, complaint and exit. Service recovery is particularly important because customers judge not only whether a problem occurred, but also how fairly and promptly it was handled.

6. Service-Delivery System Design

Services are often produced and consumed in interaction with the customer. This creates distinctive operating challenges: demand is variable, capacity cannot always be stored, quality may vary by employee or customer participation, and the customer may observe the process directly.

A service-delivery system should define:

• the customer promise and service standard;
• the customer’s required participation;
• front-stage and back-stage activities;
• staffing and skill requirements;
• queue and appointment rules;
• escalation and recovery procedures;
• information and privacy controls;
• feedback and improvement mechanisms.

6.1 Managing variability

Variability may arise from arrival times, customer needs, processing times, employee performance, supplier reliability or technology failures. Responses include appointments, reservations, segmentation, demand-based pricing, cross-training, flexible staffing, standard work, modular service packages and buffers.

Buffers can be time, inventory, capacity, information or cash. However, buffers have costs and can conceal structural problems. An entrepreneur should identify whether a buffer protects the customer from normal variation or merely compensates for an unstable process.

6.2 Queues and waiting

Customers experience waiting as part of the service. Perceived waiting can be improved through accurate information, fair queue rules, progress visibility, comfortable environments and meaningful engagement, but communication cannot substitute indefinitely for adequate capacity.

A simple utilization measure is:

Here, ρ is utilization, arrival rate and service capacity must use the same units, and the system must have service capacity greater than average arrival rate for a stable queue in the long run. The formula alone does not determine waiting time; queue behavior also depends on variability, number of servers and queue discipline.

6.3 Standardization and customization

Standardization improves consistency, training, forecasting and cost control. Customization can improve relevance, willingness to pay and relationship quality. Effective entrepreneurs often use modular customization: standardized components are combined in customer-specific configurations. For example, a software firm may standardize its platform while customizing implementation, data migration and training.

The design question is not whether to standardize everything or customize everything. It is where variation creates value and where it merely creates complexity.

7. Technology, Data and Artificial Intelligence

Technology can reshape the operating architecture by automating routine work, connecting channels, improving visibility and enabling new forms of personalization. Relevant technologies include cloud platforms, application programming interfaces, workflow systems, sensors, digital payments, customer relationship management systems and analytics.

AI may assist with demand forecasting, customer-service triage, recommendation, quality inspection, scheduling and document processing. Its use should be governed by the importance and risk of the decision. Entrepreneurs should ask:

• Is the data accurate, representative and lawfully obtained?
• Can the output be explained to affected users?
• What happens when the system is wrong?
• Is human review required?
• How are privacy, security and retention managed?
• Does automation create exclusion or bias?

AI should augment rather than obscure accountability. A chatbot that handles routine questions may be appropriate, but customers should have a clear route to human assistance when the issue is complex, sensitive or consequential. Automated decisions involving credit, employment, health or access to essential services may require stronger controls and legal review.

Technology should be selected because it improves a defined process or customer outcome, not because it is fashionable. A low-cost manual process may be preferable during early validation if automation would lock the venture into an untested design.

8. Make, Buy, Partner or Platform

Entrepreneurs must decide which activities to perform internally and which to obtain from suppliers, contractors, platforms or strategic partners. The decision should consider:

• strategic importance;
• required control over quality and customer experience;
• transaction frequency and uncertainty;
• specialist knowledge;
• data and intellectual-property exposure;
• switching costs and supplier dependence;
• total cost, including coordination and monitoring;
• resilience and continuity risk.

Outsourcing can provide speed, expertise and variable capacity. It can also reduce visibility, create dependency and make service failures harder to correct. A responsible arrangement defines service levels, data obligations, audit rights, incident reporting, continuity plans and exit provisions.

A platform or marketplace may allow rapid access to customers and providers, but the entrepreneur must understand its fees, ranking rules, data access, dispute policies and potential for disintermediation. Operational architecture extends beyond the firm’s legal boundary; customers experience the combined system.

9. Governance, Ethics and Resilience

Operational decisions have ethical and regulatory consequences. Relevant issues include worker safety, accessibility, truthful communication, consumer protection, data privacy, cybersecurity, product safety, environmental impact and fair treatment of customers and suppliers.

Governance should assign ownership for critical controls. Examples include approval limits, segregation of duties, quality checks, privacy impact assessments, supplier screening, incident escalation and record retention. Small ventures may not need bureaucracy, but they do need clarity about who can make decisions and who verifies important outcomes.

Resilience is the capacity to absorb disruption, continue critical operations and recover effectively. Sources of disruption include supplier failure, cyberattack, extreme weather, public-health events, labor shortages and platform outages. Resilience practices include supplier diversification, backup systems, documented procedures, cross-training, cash reserves, inventory policies and scenario exercises.

Resilience should be balanced with efficiency. A single low-cost supplier may minimize ordinary cost but expose the enterprise to severe interruption risk. The correct decision depends on the probability and impact of disruption, the availability of alternatives and the importance of the affected activity.

10. An Integrated Design Method

The following method can be used to design or redesign an entrepreneurial operating architecture:

Step 1: Define the value promise

State the customer, problem, desired outcome, service level and conditions under which the promise is credible.

Step 2: Map the customer journey

Identify discovery, evaluation, purchase, delivery, use, support, renewal and exit. Record customer effort and likely failure points.

Step 3: Map the operating process

Show activities, resources, handoffs, systems, suppliers, queues, controls and outputs. Distinguish visible and invisible work.

Step 4: Identify critical requirements

Translate the promise into measures for quality, speed, availability, cost, accessibility, safety and experience.

Step 5: Locate constraints

Estimate demand, capacity and variability. Identify bottlenecks and dependencies before choosing technology or hiring.

Step 6: Choose channel and relationship mechanisms

Select direct, indirect, physical, digital or hybrid arrangements according to customer needs and economics.

Step 7: Decide the boundary of the firm

Evaluate internal performance against outsourcing, partnership and platform alternatives, including risk and governance.

Step 8: Pilot and learn

Test the smallest viable operating design. Measure real behavior rather than relying only on stated preferences.

Step 9: Scale deliberately

Document standard work, train staff, strengthen controls and add capacity in line with validated demand.

Step 10: Review system fit

Check whether changes in one activity have created problems elsewhere. Reassess cost, quality, capacity and customer experience together.

11. Illustrative Case: FreshRoute Meals

Background

FreshRoute Meals is a fictional early-stage venture offering weekly deliveries of affordable, diet-specific meals to university students and young professionals. Its value proposition is “nutritious meals that fit your schedule and budget.” The founders initially planned to accept unlimited orders through social media and prepare meals in a shared commercial kitchen.

Problem

After a successful promotional campaign, orders increased from 80 to 150 per week. Customers reported late deliveries, incorrect dietary substitutions and slow responses to messages. The founders considered renting a larger kitchen, but they did not yet know which part of the system constrained performance.

Analysis

The founders mapped the process from subscription to delivery. They found that menu changes were communicated manually through several messaging channels. Ingredient purchasing occurred after orders were received, and dietary labels were checked only during packing. The delivery contractor collected meals in one large batch, creating a late-afternoon bottleneck.

The key constraints were not oven capacity alone. They included poor order information, late procurement, inadequate labeling controls and synchronized delivery timing. The operating architecture had been designed for 80 orders but was being used at 150.

Suppose weekly effective kitchen capacity was 180 meals, but packing capacity was only 120 correctly labeled meals per delivery window. Packing, not cooking, was the bottleneck. Adding a larger oven would not solve the immediate problem.

Approach and solution

FreshRoute introduced a standardized digital order form with locked dietary categories and a daily order cutoff. It created a production schedule based on confirmed orders, added a two-person label verification step, divided deliveries into two windows and negotiated a backup courier arrangement. It also limited menu customization to a fixed set of modules rather than accepting free-text substitutions.

The venture chose a hybrid relationship model: self-service ordering for routine purchases, automated delivery updates and human support for dietary questions or service failures. It tracked on-time delivery, order accuracy, complaint response time, food waste and repeat purchase rate.

Outcome

In the next pilot period, effective packing capacity rose from 120 to 180 meals per delivery day because the process had fewer interruptions and clearer information. The venture delayed kitchen expansion, preserving cash while testing whether demand was durable. Customer complaints declined, and the founders gained better data for deciding when additional capacity would be justified.

Learning points

1. The visible resource, such as a kitchen, is not necessarily the bottleneck.
2. Standardization can protect quality while leaving room for valuable customization.
3. Channel design affects operations because every order format creates information requirements.
4. Service recovery and communication are part of delivery, not an afterthought.
5. Capacity investment should follow process analysis and validated demand.

12. Contemporary Developments and Best Practices

Several developments are reshaping operating architecture:

• Embedded services: Products increasingly include subscriptions, monitoring, maintenance or digital support.
• Servitization: Firms sell outcomes or access rather than only physical goods.
• Composable operations: Cloud tools and APIs allow ventures to assemble capabilities from specialized providers.
• Sustainable operations: Circular design, repair, reuse, low-waste logistics and emissions measurement influence value creation.
• Distributed work and delivery: Digital coordination expands access to talent and customers but raises quality and governance challenges.
• Real-time operations: Sensors and analytics improve visibility but increase dependence on data quality and cybersecurity.

Best practice is context-dependent, but several principles are broadly useful:

• design from the customer outcome backward;
• make processes visible before attempting to optimize them;
• manage the bottleneck before improving non-bottleneck activities;
• define quality in customer-relevant terms;
• build prevention and recovery into the process;
• use standardization selectively;
• treat data and technology as operating capabilities, not magic solutions;
• maintain clear accountability across partners;
• measure both efficiency and experience;
• scale only after the operating logic has been tested.

Challenges and Limitations

Operating models are based on assumptions about demand, behavior, technology and partners. These assumptions may be wrong or may change rapidly. Metrics can also create unintended behavior: reducing average handling time may encourage employees to end conversations prematurely, while maximizing utilization may increase waiting and burnout.

Quantitative models simplify reality. Capacity calculations often assume stable rates, but entrepreneurial environments contain variability and learning effects. Cost estimates may omit coordination, quality failure, compliance and resilience costs. Customer-experience measures may be subjective and influenced by expectations. Therefore, entrepreneurs should combine data with observation, customer interviews, frontline judgment and controlled experiments.

Finally, efficiency should not be treated as the sole objective. A system that is efficient but unsafe, exclusionary, environmentally damaging or deceptive is not a successful operating architecture. Sustainable value creation requires economic, social and ethical considerations to be integrated into design decisions.

Chapter Summary

Value creation depends on an operating architecture that converts resources into reliable customer outcomes and captures sufficient economic value. The architecture includes activities, processes, resources, channels, customer relationships, partners, technology, governance and feedback.

Entrepreneurs should identify primary, support and governance activities; map customer journeys and service processes; locate bottlenecks; and align quality, capacity, cost and experience. Little’s Law helps relate work-in-process, throughput and flow time, while capacity and cost formulas provide useful estimates when their assumptions are understood. Channel and relationship choices must support the entire customer journey, including support and recovery. Service systems require deliberate management of variability, queues, standardization and customization.

Technology and AI can improve visibility, automation and personalization, but they require sound data, human accountability, privacy and risk controls. Make-or-buy decisions should consider strategic importance, quality, cost, resilience and dependency. The strongest operating architectures are coherent systems in which activities reinforce the value proposition and are continuously tested, measured and improved.

Key Terms

Operating architecture: The organized system of activities, resources, processes, channels, relationships and governance used to deliver value.

Value creation: The conversion of resources into benefits valued by customers or stakeholders.

Value capture: The mechanisms through which an enterprise obtains revenue, margin or other returns from created value.

Primary activity: An activity that directly creates, sells or delivers customer value.

Support activity: An activity that enables primary activities.

Governance activity: An activity involving direction, control, compliance, risk or improvement.

Process: A connected sequence of activities that transforms inputs into outputs.

Service blueprint: A map showing customer actions, visible service actions, backstage activities and support systems.

Throughput: The quantity completed by a process per unit of time.

Cycle time: The elapsed time required to complete a process or activity.

Work-in-process: Units or customers currently within a process.

Bottleneck: The constraint that limits the effective output of a system.

Capacity: The maximum or effective amount a resource or process can produce in a specified period.

Utilization: The proportion of available capacity used by actual load.

Channel: A route through which customers discover, buy, receive or obtain support for an offering.

Customer relationship: The pattern and level of interaction between an enterprise and its customers.

Modular customization: Combining standardized components in configurations suited to individual customers.

Service recovery: Actions taken to correct a failure and restore customer trust.

Resilience: The ability to absorb disruption, continue critical operations and recover.

First-pass yield: The proportion of outputs completed correctly without rework.

Review Questions

Short Answer Questions

1. What is meant by operating architecture, and why is it a core element of a business model?
2. Distinguish between a primary activity, a support activity and a governance activity.
3. What is a bottleneck, and why may adding resources elsewhere fail to increase output?
4. State the meaning of each variable in Little’s Law L = λW.
5. Give two advantages and two risks of outsourcing a key operational activity.

Long Answer Questions

1. Explain how a value proposition should influence process design, channel selection and customer-relationship design.
2. Discuss the trade-offs among quality, capacity, cost and customer experience in a service business.
3. Compare standardization, full customization and modular customization as operating choices.
4. Explain how technology and AI can improve operating architecture, and discuss the governance risks involved.
5. Describe an integrated method for designing and scaling an entrepreneurial operating architecture.

Analytical / Application Questions

1. A tutoring venture receives 24 student requests per hour, and each request remains in the system for an average of 1.5 hours. Use Little’s Law to calculate average work-in-process. State the assumptions behind your calculation.
2. A fulfillment process has fixed monthly costs of $12,000, variable cost of $5 per order and monthly volume of 2,400 orders. Calculate total cost and average cost per order. Explain one reason why actual cost may differ from the estimate.
3. Using FreshRoute Meals or a venture of your choice, identify the likely bottleneck, propose two process changes and explain how you would measure whether the changes improved both efficiency and customer experience.

Multiple Choice Questions with Answers

Question 1

Which statement best defines operating architecture?

A. A firm’s legal ownership structure

B. The system of activities, resources, processes and relationships used to deliver value

C. A promotional plan for acquiring customers

D. A forecast of annual revenue

Correct Answer: B. The system of activities, resources, processes and relationships used to deliver value

Question 2

According to Little’s Law, if throughput is 40 customers per hour and average time in the system is 0.5 hours, average work-in-process is:

A. 20 customers

B. 40 customers

C. 80 customers

D. 0.5 customers

Correct Answer: A. 20 customers

Question 3

Which activity is most likely a bottleneck?

A. A resource with substantial unused capacity

B. A resource whose effective capacity limits total system output

C. Any activity performed by a manager

D. An activity that has no customer impact

Correct Answer: B. A resource whose effective capacity limits total system output

Question 4

A service blueprint primarily helps an entrepreneur to:

A. Calculate corporate income tax

B. Map customer actions and the visible and invisible activities supporting service delivery

C. Determine shareholder voting rights

D. Replace all human employees with software

Correct Answer: B. Map customer actions and the visible and invisible activities supporting service delivery

Question 5

A bakery has two ovens, each available for 6 hours per day, producing 10 trays per hour. Ignoring downtime, theoretical daily capacity is:

A. 20 trays

B. 60 trays

C. 120 trays

D. 160 trays

Correct Answer: C. 120 trays

Question 6

Which is a likely advantage of modular customization?

A. It eliminates all process variation

B. It combines standardized components with selected customer-specific configurations

C. It requires every customer to receive an identical offering

D. It prevents the use of technology

Correct Answer: B. It combines standardized components with selected customer-specific configurations

Question 7

Which statement about high utilization is most accurate?

A. High utilization always improves customer experience

B. High utilization can increase queues when arrivals and processing times vary

C. High utilization means that capacity is unlimited

D. High utilization eliminates the need for forecasting

Correct Answer: B. High utilization can increase queues when arrivals and processing times vary

Question 8

Which factor is least appropriate as the sole basis for an outsourcing decision?

A. Strategic importance of the activity

B. Quality and customer-experience requirements

C. Total cost including coordination and monitoring

D. The supplier’s logo design

Correct Answer: D. The supplier’s logo design

Question 9

A responsible use of AI in customer service should include:

A. No route to human assistance

B. Accountability, privacy controls and procedures for handling errors

C. Automatic acceptance of every system recommendation

D. Use of any available customer data without permission

Correct Answer: B. Accountability, privacy controls and procedures for handling errors

Question 10

If fixed cost is $10,000, variable cost is $4 per order and output is 2,000 orders, total cost is:

A. $8,000

B. $10,004

C. $12,000

D. $18,000

Correct Answer: D. $18,000