Operations, Teams and Entrepreneurial Leadership

Introduction

A startup does not become scalable merely because it has a promising product. It becomes scalable when it can repeatedly create and deliver customer value with dependable quality, controlled cost, appropriate speed, and people who can coordinate effectively. Operations translate an entrepreneurial idea into a functioning system. Teams provide the knowledge, energy, and execution capacity required to operate that system. Leadership aligns both with purpose, learning, and responsible growth.

In an early venture, founders often perform several roles simultaneously: product designer, salesperson, recruiter, purchaser, service provider, and financial controller. This flexibility is valuable during experimentation, but it can create bottlenecks and dependence on particular individuals. As the venture grows, informal arrangements must be converted into clear processes, decision rights, performance measures, and cultural expectations.

This chapter examines how entrepreneurs design operating processes, supply and service systems, quality controls, and resource plans. It also addresses founder roles, team formation, organizational culture, conflict, negotiation, leadership, and performance management. The emphasis is practical: students should be able to diagnose operational weaknesses, design improvements, and lead people through periods of uncertainty and growth.

Learning Objectives

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

1. Explain the relationship between business strategy and operations.
2. Map and improve core startup processes.
3. Design suitable supply, service-delivery, quality, and resource systems.
4. Diagnose operational bottlenecks using basic quantitative tools.
5. Distinguish founder roles and develop effective entrepreneurial teams.
6. Explain how culture, conflict, negotiation, and leadership influence execution.
7. Design fair and useful performance-management practices.
8. Evaluate operational and people-related decisions ethically and strategically.

1. Operations as the Execution System of a Venture

Operations comprise the coordinated activities through which an organization obtains inputs, transforms them, and delivers products or services. Inputs may include materials, equipment, money, data, technology, time, and human expertise. Outputs include physical products, services, information, customer experiences, and social or environmental outcomes.

A useful operations model is:

Inputs → Processes → Outputs → Feedback → Improvement

For a food-delivery startup, inputs include restaurants, drivers, software, customer orders, and payment systems. Processes include order confirmation, preparation, dispatch, delivery, payment settlement, and complaint handling. Outputs include delivered meals, revenue, customer satisfaction, and operational data.

Operations must support the venture’s value proposition. A low-cost venture needs cost discipline and standardized processes. A premium service requires consistency, responsiveness, and carefully selected employees. A highly customized venture needs flexible capacity and skilled workers. Thus, operations are not merely administrative activities; they are a source of competitive advantage.

1.1 The operating model

An operating model explains how a venture organizes resources and activities to deliver value. Its principal elements are:

A strong operating model reduces unnecessary variation without preventing useful innovation. It also makes dependencies visible. For example, a service promise of “delivery within 30 minutes” depends not only on drivers but also on inventory accuracy, route planning, order batching, and customer availability.

1.2 Process mapping and standardization

Process mapping represents the sequence, responsibility, information, and decisions involved in an activity. A simple process map should identify:

• the trigger that starts the process;
• each major activity;
• the person or system responsible;
• decisions and exceptions;
• inputs and outputs; and
• the customer or internal user of the output.

A process map can reveal duplication, unclear handoffs, unnecessary approvals, and activities that do not create customer value. Entrepreneurs should distinguish value-adding work from necessary support work and avoidable waste.

Standard operating procedures (SOPs) document the best currently known method for performing a repeatable task. A useful SOP states its purpose, scope, required resources, sequence of steps, quality criteria, safety requirements, escalation rules, and revision date. SOPs should not become rigid substitutes for judgment. Employees need authority to respond to unusual situations, provided that exceptions are recorded and reviewed.

1.3 Capacity, bottlenecks, and flow

Capacity is the maximum output that a resource or process can produce during a specified period under stated conditions. A bottleneck is the activity whose capacity most constrains total process output. Improving a non-bottleneck may produce little benefit if the bottleneck remains unchanged.

For a resource operating at a stable rate, utilization can be expressed as:

Actual output and effective capacity must use the same units and time period. Effective capacity is the realistic output after allowing for breaks, maintenance, setup time, absenteeism, and other planned losses. Utilization above 100% indicates that the stated capacity assumption is inconsistent with the observed output or that work is accumulating in a queue.

A process with three sequential activities has an approximate maximum flow equal to the capacity of its bottleneck:

Here, Cᵢ is the capacity of activity i, measured in common units per period. This relationship assumes that activities are sequential, output units are comparable, and sufficient inputs are available. It is an approximation because variability, downtime, rework, and batch sizes may reduce actual flow.

Worked example. A startup assembles devices through three stages: preparation capacity 80 units per day, assembly capacity 50 units per day, and testing capacity 60 units per day. The process capacity is approximately 50 units per day because assembly is the bottleneck. Increasing testing capacity to 100 units per day does not increase total capacity. Adding a second assembly worker who raises assembly capacity to 75 units per day shifts the bottleneck to preparation, so capacity then becomes approximately 60? No: the minimum is now 75? The three capacities are 80, 75, and 60; therefore testing becomes the bottleneck and process capacity is approximately 60 units per day. This illustrates why bottleneck improvement must be followed by reassessment.

2. Supply and Service Systems

2.1 Supplier design and procurement

A startup should not select suppliers solely on quoted price. Relevant criteria include quality, reliability, lead time, flexibility, payment terms, geographic location, compliance, cybersecurity, environmental impact, and the consequences of failure. A supplier offering a low price but frequent stock-outs may impose greater total cost than a more reliable supplier.

Supplier concentration creates efficiency but also vulnerability. A single supplier may provide volume discounts and consistent specifications, yet disruption can halt operations. Entrepreneurs should assess whether dual sourcing, safety stock, substitute materials, or contractual contingency arrangements are justified.

A basic reorder point model is:

Expected demand during lead time is measured in units and depends on average demand and supplier lead time. Safety stock is additional inventory held to protect against demand or lead-time uncertainty. The formula assumes that demand and lead time are represented consistently and that replenishment is triggered when available inventory reaches the reorder point. It does not by itself determine the economically optimal safety-stock level.

For example, if a venture sells 20 units per day, supplier lead time is 5 days, and safety stock is 30 units, the reorder point is 20 × 5 + 30 = 130 units. When inventory position reaches about 130 units, a replenishment order should be initiated, subject to order quantities and supplier constraints.

2.2 Service operations

Services differ from many physical products because production and consumption may occur simultaneously, customers often participate in delivery, and unused capacity cannot always be stored. A vacant appointment slot, unused hotel room, or idle consultant hour is generally lost capacity.

Service design should address:

• customer access and booking;
• waiting and queue management;
• employee-customer interaction;
• service standards and recovery;
• information privacy;
• demand peaks and capacity flexibility; and
• the evidence customers use to judge an intangible service.

A service blueprint separates visible front-stage activities from backstage processes and support systems. For example, an online tutoring service may show the student booking and attending a session, while backstage activities include tutor matching, payment processing, curriculum preparation, and quality monitoring.

Service recovery is the planned response to failure. It may include acknowledgment, explanation, correction, refund, replacement, and prevention of recurrence. Recovery should be authorized at an appropriate level so that employees can solve ordinary problems without excessive delay.

2.3 Inventory and working capital

Inventory ties up cash and can become obsolete, damaged, or unsellable. Too little inventory creates stock-outs and lost sales; too much creates storage and financing costs. Startups should classify inventory by importance and uncertainty rather than applying identical controls to every item.

Useful measures include inventory turnover and days of inventory. Inventory turnover is commonly calculated as:

Both numerator and denominator should use monetary values for the same period, and average inventory is often calculated as beginning inventory plus ending inventory divided by two. A higher turnover may indicate efficient inventory use, but it can also indicate understocking; interpretation requires attention to service levels and stock-outs.

3. Quality Management and Continuous Improvement

Quality means conformance to requirements and fitness for customer use. In a startup, quality is not limited to defect-free manufacturing. It includes accurate orders, secure data handling, reliable delivery, courteous communication, and truthful marketing.

3.1 Preventive and corrective controls

Preventive controls reduce the likelihood of failure before delivery. Examples include supplier specifications, employee training, design reviews, access controls, checklists, and automated validation. Detective controls identify failure after or during execution, such as inspections, customer feedback, transaction monitoring, and audits. Corrective controls address the cause and prevent recurrence.

A practical quality cycle is:

1. Define the customer requirement.
2. Specify a measurable standard.
3. Design the process to meet the standard.
4. Measure actual performance.
5. Investigate deviations.
6. Correct the process and verify improvement.

Quality metrics should be operationally meaningful. Examples include defect rate, rework rate, on-time delivery, complaint rate, first-contact resolution, and customer retention. Metrics must have definitions, data owners, collection frequencies, and target ranges.

3.2 Root-cause analysis

When a failure occurs, teams should avoid stopping at the immediate symptom. Root-cause analysis asks why the failure became possible. Tools include the five-whys method, cause-and-effect diagrams, process observation, and analysis of incident patterns.

The five-whys method is not a requirement to ask exactly five questions. Its purpose is to continue questioning until the team identifies a controllable process, system, or organizational cause rather than blaming an individual prematurely. A good analysis may identify multiple interacting causes.

Continuous improvement should be treated as a learning process. The Plan–Do–Check–Act cycle provides a disciplined approach: plan a change, implement it on a manageable scale, compare results with the expected outcome, and standardize or revise the change.

4. Resource Planning and Startup Resilience

Resource planning aligns expected demand with people, equipment, cash, technology, facilities, and supplier capacity. It should include a base case, an optimistic case, and a downside case. The purpose is not to predict the future exactly but to prepare decisions for plausible conditions.

A resource plan should identify:

• required resource and its purpose;
• timing of need;
• acquisition or development method;
• fixed and variable cost;
• capacity contribution;
• owner of the resource;
• major dependency or risk; and
• trigger for expansion, replacement, or reduction.

Entrepreneurs should distinguish committed resources from flexible resources. Long leases, specialized equipment, and permanent hires may create operating leverage but reduce adaptability. Outsourcing, contractors, shared facilities, and cloud services may increase flexibility but create dependence and coordination risk.

Scenario planning is particularly important where demand is uncertain. A venture might define a trigger such as “hire a second support agent when weekly tickets exceed 400 for three consecutive weeks and response time exceeds the service target.” Such rules reduce emotionally driven decisions.

5. Founder Roles and Team Formation

Founders often begin with a shared mission but different expectations about ownership, authority, workload, risk, and personal goals. These assumptions should be discussed explicitly before conflict becomes expensive.

Important founder-role questions include:

• Who owns product, sales, finance, operations, and people decisions?
• Which decisions require agreement, and which may be made independently?
• How will deadlock be resolved?
• What happens if a founder leaves?
• How will equity vesting, intellectual property, confidentiality, and compensation be handled?
• What evidence will justify changing roles?

Role clarity does not mean permanent specialization. In an early venture, roles may change as evidence develops. However, one person should be accountable for each critical outcome, even when several people contribute.

5.1 Building effective teams

Team effectiveness depends on complementary competence, psychological safety, coordination, accountability, and a shared purpose. Entrepreneurs commonly overvalue technical similarity and undervalue diversity of experience, customer insight, commercial ability, and operational discipline.

A team-development process may involve:

1. Define the venture’s critical capabilities.
2. Audit the founders’ strengths and gaps.
3. Decide which gaps require hiring, partnership, training, or technology.
4. Establish responsibilities and decision rights.
5. Create working agreements for communication and conflict.
6. Review team performance as the venture evolves.

Tuckman’s forming–storming–norming–performing model is useful as a general developmental lens, but teams do not always move through stages in a fixed sequence. New members, crises, or strategic changes can return a team to earlier patterns.

Psychological safety means that people can raise concerns, admit mistakes, and offer dissent without humiliation or retaliation. It does not mean low standards. High-performing teams combine psychological safety with clear accountability and demanding goals.

6. Culture, Conflict, and Negotiation

Organizational culture consists of shared assumptions, values, norms, and practices that influence how people interpret and respond to situations. In startups, culture forms quickly through founder behavior. Employees learn what is truly valued by observing who is rewarded, whose concerns are heard, how customers are treated, and whether leaders admit mistakes.

A healthy entrepreneurial culture may support experimentation, customer learning, transparency, inclusion, and responsible risk-taking. A harmful “hustle” culture may normalize exhaustion, unsafe work, discrimination, misleading claims, or neglect of controls. Culture should therefore be designed rather than treated as an accidental personality of the founders.

Conflict is not automatically negative. Task conflict can improve decisions when it concerns evidence, priorities, or methods and remains respectful. Relationship conflict damages trust and often involves identity, status, or personal hostility. Process conflict concerns who should do what and can often be reduced through role clarity.

A constructive conflict process is:

1. State the issue in observable terms.
2. Separate interests from positions.
3. Listen and restate the other party’s concerns.
4. Generate several options.
5. Evaluate options against agreed criteria.
6. Decide, document commitments, and review outcomes.

Interest-based negotiation focuses on underlying needs rather than demands. A founder demanding total control may actually need speed, accountability, or protection of a particular vision. The other founder may need recognition, information, or safeguards against unilateral decisions. A negotiated agreement should clarify authority, information rights, review points, and consequences if assumptions change.

Ethical negotiation prohibits deception about material facts, coercion, discriminatory conditions, and promises the negotiator has no authority to make. Long-term entrepreneurial relationships depend on credibility, not merely on winning an individual exchange.

7. Entrepreneurial Leadership

Entrepreneurial leadership combines opportunity recognition, mobilization of resources, experimentation, ethical judgment, and commitment under uncertainty. It differs from command-and-control management because the leader must often act before complete information is available and must persuade people who cannot be motivated solely by formal authority.

Several leadership perspectives are relevant:

• Transformational leadership: creates commitment through purpose, inspiration, and development.
• Servant leadership: emphasizes the growth and well-being of followers and stakeholders.
• Situational leadership: adapts direction and support to task and follower readiness.
• Authentic leadership: stresses consistency between values, words, and actions.
• Shared leadership: distributes influence across a team rather than concentrating it in one formal leader.

No single model is universally superior. A founder may need directive leadership during a safety incident, participative leadership during product discovery, and coaching leadership when developing a new manager. Adaptability must not become inconsistency or avoidance of difficult decisions.

Effective entrepreneurial leaders perform four recurring activities:

1. Create direction: explain the problem, purpose, priorities, and boundaries.
2. Enable execution: secure resources, remove obstacles, and clarify decisions.
3. Develop people: give feedback, delegate, coach, and build capability.
4. Maintain integrity: protect stakeholders, tell the truth, and accept accountability.

Delegation transfers responsibility for an outcome while retaining appropriate accountability for the leader. Good delegation defines the result, authority limits, resources, deadlines, reporting expectations, and escalation conditions. Micromanagement occurs when responsibility is transferred without meaningful authority.

8. Performance Management

Performance management is a continuous process of aligning goals, observing work, giving feedback, developing capability, recognizing contribution, and addressing underperformance. It should not be reduced to an annual rating.

A useful performance system combines leading and lagging indicators. Leading indicators, such as sales calls completed, production schedule adherence, or response time, provide early signals. Lagging indicators, such as revenue, customer retention, defect rate, or profitability, show outcomes after activities have occurred.

Objectives should be specific enough to guide action and flexible enough to accommodate learning. A startup may use objectives and key results (OKRs), team scorecards, or carefully designed key performance indicators (KPIs). Metrics should not reward behavior that damages the broader system. For example, rewarding call-center speed alone may increase abandoned or poorly resolved interactions.

A balanced startup scorecard might include:

Feedback should be timely, specific, behavior-based, and two-way. A useful conversation identifies the observed behavior, its impact, the expected standard, the employee’s perspective, and an agreed action. Performance problems may arise from unclear expectations, inadequate resources, insufficient capability, motivation, health, discrimination, or external constraints. Fair management diagnoses the cause before selecting a remedy.

9. Technology and AI in Operations and Teams

Digital tools can improve scheduling, inventory visibility, workflow automation, customer support, collaboration, and performance analysis. AI may assist with demand forecasting, document classification, recruitment administration, quality inspection, and customer-service triage. However, technology does not eliminate the need for process design and human accountability.

Entrepreneurs should evaluate AI and automation according to:

• data quality and representativeness;
• privacy and consent;
• cybersecurity;
• explainability and reviewability;
• bias and unequal impact;
• human escalation routes; and
• the cost of errors.

An automated system that rejects applicants, changes prices, or gives health-related guidance may create legal and ethical risks if its logic is opaque or discriminatory. Human review should be meaningful rather than a symbolic approval step. Employees should also be informed when significant decisions are assisted by automated systems.

10. Illustrative Case: ReLoop Kitchen Containers

Background

ReLoop Kitchen is a fictional startup providing reusable food containers to independent restaurants. Customers pay a deposit, restaurants fill the containers, and ReLoop collects, washes, inspects, and redistributes them. The venture promises restaurants a dependable supply of hygienic containers without requiring them to purchase washing equipment.

Problem

After rapid growth, late deliveries increased, restaurants complained about missing containers, and washing defects rose. The founders responded by asking staff to work longer hours. Morale declined, and one founder wanted to purchase a larger washing machine while another argued that the real problem was poor collection scheduling.

Analysis

A process map showed five stages: restaurant ordering, container dispatch, collection, washing and inspection, and redistribution. Data revealed that washing capacity was 900 containers per day, but collection was irregular and returned containers were frequently mixed with damaged units. The washing stage was not always the bottleneck. On high-demand days, collection delays caused shortages; on other days, the washing team had idle capacity.

A second problem involved unclear founder roles. The operations founder controlled scheduling but had no authority over delivery contractors. The commercial founder promised restaurants delivery times without checking capacity. Quality standards existed informally but were not documented, and staff differed in how they classified scratches and damaged lids.

Approach and solution

The team implemented five changes:

1. It defined a standard process with named owners and escalation rules.
2. It introduced collection windows and a simple scan at dispatch and return.
3. It separated usable, repairable, and rejected containers.
4. It documented inspection criteria and sampled returned batches.
5. It created a weekly operations review using delivery reliability, container-loss rate, wash rework, and complaints.

The founders also renegotiated decision rights. Commercial staff could promise only service levels approved by operations. Operations could contract additional collection capacity within a defined budget. A joint review was required before changing the customer promise or purchasing major equipment.

Outcome

After eight weeks, the venture reduced avoidable collection delays and rework. The founders postponed the washing-machine purchase until sustained demand justified it. More importantly, the company learned that apparent capacity problems may actually be coordination and quality-control problems. The improvement was not achieved through effort alone; it resulted from process visibility, role clarity, measurement, and disciplined learning.

Learning points

The case illustrates that:

• bottlenecks must be identified with data rather than assumptions;
• customer promises must be connected to operating capacity;
• quality standards should be observable and documented;
• founder conflict often reflects unclear decision rights; and
• growth requires systems that reduce dependence on heroic individual effort.

11. Challenges, Ethics, and Governance

Entrepreneurial operations involve tensions between speed and control, flexibility and standardization, growth and sustainability, and founder discretion and stakeholder protection. Ethical governance requires attention to employees, customers, suppliers, investors, communities, and the environment.

Important issues include fair wages and working conditions, occupational safety, truthful marketing, accessibility, data protection, intellectual-property ownership, anti-discrimination, responsible sourcing, and environmental impacts. Contractors and gig workers should not be treated as a way to evade basic ethical responsibilities. Legal requirements vary by jurisdiction, so ventures should obtain appropriate professional advice and maintain accurate records.

Governance mechanisms need not be bureaucratic. A small venture can maintain a decision log, conflict-of-interest register, approval thresholds, incident register, supplier standards, and periodic risk review. These practices increase trust and make the business more investable.

Best-Practice Checklist

Before scaling an operation, an entrepreneur should be able to answer yes to most of the following questions:

• Is the customer promise clearly connected to process capability?
• Are critical processes mapped and assigned to accountable owners?
• Is the main bottleneck known and measured?
• Are supplier risks and contingency options understood?
• Are quality standards observable and consistently applied?
• Can employees solve ordinary problems without unnecessary approval?
• Are founder roles, equity expectations, and decision rights documented?
• Does the culture reward learning, integrity, inclusion, and responsible performance?
• Are metrics balanced so that improving one target does not damage the system?
• Are technology and AI subject to privacy, fairness, security, and human oversight?
• Can the venture continue operating if a key person or supplier becomes unavailable?

Chapter Summary

Operations convert an entrepreneurial concept into repeatable customer value. An effective operating model connects the value proposition with processes, resources, governance, performance measures, and improvement routines. Process mapping, capacity analysis, bottleneck identification, supplier management, inventory controls, service design, and quality systems help startups grow without sacrificing reliability.

Resource planning should account for uncertainty, flexibility, dependencies, and resilience. Teams require complementary capabilities, clear roles, psychological safety, accountability, and shared purpose. Founder agreements should address decision rights, changing responsibilities, equity, intellectual property, and departure conditions. Culture develops through repeated behavior and must be consciously shaped.

Conflict can improve decisions when it focuses on evidence and interests, while relationship conflict damages trust. Effective negotiation seeks durable agreements rather than short-term victories. Entrepreneurial leadership combines direction, execution, development, adaptability, and integrity. Performance management works best as a continuous cycle of goals, evidence, feedback, development, and fair corrective action. Finally, technology and AI can strengthen operations only when supported by sound processes, reliable data, human oversight, and ethical governance.

Key Terms

Operations: Activities that transform resources into products, services, and customer value.

Operating model: The arrangement of processes, resources, governance, and measures used to deliver a value proposition.

Process map: A representation of activities, decisions, responsibilities, inputs, and outputs.

Standard operating procedure: Documented method for performing a repeatable task.

Capacity: Maximum feasible output of a resource or process under stated conditions.

Bottleneck: Resource or activity that most limits total process flow.

Utilization: Actual output expressed as a proportion of effective capacity.

Supply chain: Network of organizations and activities involved in sourcing, transforming, and delivering value.

Reorder point: Inventory level at which replenishment should be initiated.

Safety stock: Additional inventory held against demand or supply uncertainty.

Service blueprint: Map separating customer-facing activities from backstage and support activities.

Quality control: Activities used to measure and maintain conformity with requirements.

Root-cause analysis: Systematic investigation of underlying causes of a problem.

Psychological safety: Shared belief that people can speak up and take interpersonal risks without unfair punishment.

Organizational culture: Shared assumptions, values, norms, and practices shaping behavior.

Interest-based negotiation: Negotiation focused on underlying needs rather than fixed positions.

Delegation: Transfer of responsibility and appropriate authority for an outcome.

Key performance indicator: Defined measure used to monitor an important aspect of performance.

Leading indicator: Measure that provides an early signal of future performance.

Performance management: Continuous process of aligning goals, feedback, development, and accountability.

Review Questions

Short Answer Questions

1. What is an operating model, and why should it reflect the venture’s value proposition?
2. Define a bottleneck and explain why improving a non-bottleneck may have little effect.
3. What is the purpose of safety stock?
4. How does psychological safety support team performance?
5. Distinguish a leading indicator from a lagging indicator.

Long Answer Questions

1. Explain how a startup can map, standardize, and continuously improve a core process.
2. Discuss the major criteria an entrepreneur should use when selecting and managing suppliers.
3. Analyze how founder role ambiguity can create operational and interpersonal problems.
4. Compare directive, participative, coaching, and shared approaches to entrepreneurial leadership.
5. Explain how a balanced performance-management system can prevent dysfunctional behavior caused by narrow targets.

Analytical / Application Questions

1. A startup has preparation capacity of 120 units per day, production capacity of 90 units per day, and inspection capacity of 100 units per day. Identify the bottleneck and propose two interventions. What new bottleneck might appear after each intervention?
2. Design a process map in prose for an online repair service, identifying at least six activities, two decision points, process owners, and three quality measures.
3. Two founders disagree about whether to hire staff or outsource delivery. Develop an interest-based negotiation plan that identifies their likely interests, objective decision criteria, governance arrangements, and review triggers.

Multiple Choice Questions with Answers

Question 1

Which statement best defines a bottleneck?

A. The activity with the highest labor cost

B. The activity that most limits total process output

C. The activity with the largest physical workspace

D. The activity performed last in every process

Correct Answer: B. The activity that most limits total process output

Question 2

A startup sells 20 units per day, has a supplier lead time of 5 days, and maintains 30 units of safety stock. What is its reorder point?

A. 70 units

B. 100 units

C. 130 units

D. 150 units

Correct Answer: C. 130 units

Question 3

Which is primarily a preventive quality control?

A. Customer complaint analysis

B. Post-delivery refund

C. Design review before production

D. Incident investigation after failure

Correct Answer: C. Design review before production

Question 4

What is the main purpose of psychological safety?

A. To eliminate accountability

B. To ensure that employees never disagree

C. To enable people to raise concerns and admit mistakes without unfair punishment

D. To replace formal performance measures

Correct Answer: C. To enable people to raise concerns and admit mistakes without unfair punishment

Question 5

Which practice best reflects interest-based negotiation?

A. Insisting on a preferred position without discussion

B. Identifying the underlying needs behind each party’s demands

C. Withholding material information to gain leverage

D. Allowing the most senior person to decide immediately

Correct Answer: B. Identifying the underlying needs behind each party’s demands

Question 6

Which of the following is a leading indicator?

A. Annual profit

B. Customer retention after one year

C. Weekly response time to customer inquiries

D. Total defects recorded at year-end

Correct Answer: C. Weekly response time to customer inquiries

Question 7

A process has capacities of 80, 50, and 60 units per day in three sequential stages. What is its approximate capacity?

A. 50 units per day

B. 60 units per day

C. 80 units per day

D. 190 units per day

Correct Answer: A. 50 units per day

Question 8

Which founder-governance practice most directly reduces decision deadlock?

A. Avoiding written agreements

B. Giving every decision equal veto power

C. Defining decision rights and escalation procedures in advance

D. Allowing decisions to remain informal indefinitely

Correct Answer: C. Defining decision rights and escalation procedures in advance

Question 9

Why can measuring call-center speed alone create dysfunctional behavior?

A. It always increases employee training costs

B. It may encourage quick but poorly resolved interactions

C. It prevents any use of technology

D. It makes customer demand impossible to estimate

Correct Answer: B. It may encourage quick but poorly resolved interactions

Question 10

Which principle is most appropriate when introducing AI into startup operations?

A. Remove human review from all automated decisions

B. Use AI without checking data quality because speed is more important

C. Assess privacy, bias, security, explainability, and human escalation

D. Assume that automated outputs are objective by definition

Correct Answer: C. Assess privacy, bias, security, explainability, and human escalation