14. Enterprise Strategy and Managerial Decision-MakingIntroduction and ContextNeural networks are often introduced through architectures, activation functions, optimization, and performance metrics. In an enterprise, however, technical capability is only one part of the decision. A neural network may achieve high predictive accuracy and still fail to create value if it addresses the wrong problem, depends on unavailable data, cannot be integrated into operations, violates regulatory expectations, or is rejected by employees and customers. Enterprise strategy therefore requires a translation between organizational objectives and machine-learning initiatives. Managers must determine which business problems merit neural-network investment, whether the organization is prepared to support the system, and how benefits, risks, costs, and responsibilities will be distributed. The central managerial question is not simply, “Can a neural network solve this problem?” It is, “Under what conditions will a neural-network capability improve organizational performance in a responsible and sustainable manner?” This chapter examines neural networks as strategic assets rather than isolated software components. It presents methods for identifying suitable opportunities, evaluating feasibility, choosing between building and buying, assessing economic value, managing risk, developing talent, leading organizational change, and constructing a digital-transformation roadmap. A detailed illustrative case demonstrates how technical and managerial considerations must be combined. Learning ObjectivesAfter studying this chapter, students should be able to: 1. Translate organizational objectives into well-defined neural-network initiatives. 2. Evaluate technical, economic, organizational, and regulatory feasibility. 3. Compare build, buy, and hybrid sourcing strategies. 4. Assess costs, benefits, risk, return on investment, and option value. 5. Design governance, talent, change-management, and operating models for AI initiatives. 6. Construct a phased roadmap for neural-network adoption. 7. Critically evaluate strategic choices through case analysis. From Organizational Problems to Neural-Network InitiativesThe starting point for enterprise AI should be an organizational problem, not a fashionable algorithm. A useful problem statement specifies the decision to be improved, the people who make or receive the decision, the current process, the measurable consequence of poor performance, and the constraints under which the decision occurs. For example, “use deep learning in customer service” is too broad to guide investment. A stronger formulation might be: “Prioritize incoming support cases so that urgent service failures are routed to specialist teams within ten minutes, reducing avoidable customer downtime.” This formulation identifies the operational decision, the users, the expected benefit, and an initial performance target. A neural network is strategically appropriate when the problem contains patterns that can be learned from data and when predictions or representations can improve an action. Neural networks are particularly useful for unstructured or high-dimensional data, including images, audio, text, sensor streams, and complex transactional histories. They are not automatically appropriate for every forecasting or classification problem. A simpler statistical model, rules engine, optimization method, or process redesign may be cheaper, more interpretable, and equally effective. A practical translation process contains five linked questions: - What strategic objective is affected—growth, cost, quality, resilience, safety, compliance, or customer experience?
- What decision or workflow influences that objective?
- What prediction, recommendation, generation, or detection capability would improve the workflow?
- What data, infrastructure, and human expertise are required?
- How will success be measured after deployment?
This process prevents a common error: optimizing model performance without establishing operational value. A model with excellent area under the ROC curve may have little value if the organization cannot act on its predictions. Conversely, a moderately accurate model may generate substantial value when it supports a high-volume decision and is embedded effectively in a workflow. Strategic Fit and the AI Opportunity PortfolioOrganizations rarely have resources to pursue every promising use case. Portfolio thinking helps managers compare initiatives according to strategic value, feasibility, risk, and learning potential. An opportunity portfolio can classify projects into four broad groups. High-value, high-feasibility initiatives are candidates for immediate implementation. Examples include image-based quality inspection when labeled images already exist and a human inspector can verify outputs. High-value but low-feasibility initiatives may require foundational investments in data quality, infrastructure, or talent. Low-value but easy projects should not automatically be pursued merely because they are technically convenient. High-risk initiatives require stronger governance, independent review, and staged experimentation. A weighted scoring model can support prioritization. A possible score is: Strategic priority = 0.25 business value + 0.20 feasibility + 0.15 data readiness + 0.15 adoption potential + 0.15 risk-adjusted return + 0.10 learning value. The weights are not universal. A hospital, bank, manufacturer, and online retailer may assign different importance to safety, compliance, speed, or experimentation. The value of the framework lies in making assumptions visible and enabling comparison, not in producing an apparently precise number. Managers should distinguish between a use case and a capability. A fraud-detection project is a use case; reusable feature pipelines, model-monitoring services, secure deployment processes, and governance procedures are organizational capabilities. Early projects should ideally create reusable assets without allowing platform construction to become an end in itself. Feasibility: Beyond Technical PossibilityFeasibility assessment should be multidimensional. A technically successful prototype is not evidence that an enterprise solution is feasible. Data feasibilityData feasibility concerns availability, relevance, quality, representativeness, ownership, access rights, labeling, and historical stability. Neural networks often require large datasets, but quantity alone is insufficient. Label noise, missing subgroups, changes in operational definitions, and sampling bias may undermine performance. Managers should ask whether the training data reflect the population and conditions in which the system will operate. Data lineage is equally important. The organization should know where data originated, how they were transformed, who may access them, and whether their use is legally and ethically justified. In regulated environments, undocumented data preparation may make a system difficult to defend or audit. Technical feasibilityTechnical feasibility includes model performance, latency, scalability, integration, cybersecurity, reliability, and maintainability. A model designed for batch processing may be unsuitable for a real-time decision. A system that requires expensive graphics processors may not fit the organization’s infrastructure. Inference cost, retraining frequency, model size, and dependency on external services should be estimated before deployment. Economic feasibilityEconomic analysis considers development costs, cloud or hardware costs, licensing, data preparation, integration, staff time, monitoring, incident response, and retirement. Benefits may include additional revenue, reduced operating costs, lower error rates, reduced losses, improved capacity, or avoided regulatory penalties. Benefits should be connected to a credible mechanism rather than treated as a percentage improvement chosen for convenience. Organizational feasibilityA project may be technically and financially attractive but organizationally infeasible if no business unit owns the outcome. Feasibility depends on executive sponsorship, process ownership, employee capability, decision rights, incentives, and willingness to change established practices. The organization must identify who acts on the model, who can override it, and who is accountable when it fails. Legal and ethical feasibilityThe organization must assess privacy, intellectual-property rights, discrimination risk, explainability expectations, sector-specific obligations, records retention, and contractual restrictions. Legal review should occur during problem definition, not only immediately before launch. Ethical feasibility also includes questions of dignity, autonomy, surveillance, accessibility, and the distribution of benefits and harms. Choosing Between Build, Buy, and Hybrid ApproachesThe build-versus-buy decision is a strategic choice about control, differentiation, speed, and capability development. Building internally can provide customization, control over data and model behavior, deeper organizational learning, and potential differentiation. It also requires sustained investment in engineering, data operations, security, governance, and talent. Buying or subscribing to an external solution can accelerate deployment, provide access to specialized expertise, and convert some capital expenditure into operating expenditure. However, it can create vendor dependence, limit transparency, constrain customization, expose sensitive data, and increase switching costs. Vendor claims should be tested using the organization’s own data and operating conditions. A hybrid model is often appropriate. An organization may purchase cloud infrastructure and a foundation model while building its own domain-specific data pipelines, retrieval systems, evaluation methods, workflow integration, and governance controls. Alternatively, it may buy a mature component such as optical character recognition but develop its own decision-support layer. A sound sourcing evaluation examines: - Strategic distinctiveness: Is the capability central to competitive advantage?
- Time sensitivity: Is rapid deployment more important than internal learning?
- Data sensitivity: Can information safely be shared with a provider?
- Total cost of ownership: What are the costs over several years, not only at launch?
- Interoperability: Can the system be replaced or integrated with existing platforms?
- Service-level commitments: What availability, latency, support, and incident obligations apply?
- Transparency and auditability: Can the organization evaluate and explain the system?
- Exit feasibility: Can data, models, prompts, and workflows be migrated if the relationship ends?
The build-versus-buy decision should be revisited. A purchased service may be suitable for experimentation but inadequate when usage expands, or an internal prototype may reveal that a commercial service is more economical at scale. Economic Evaluation and the Logic of Risk-Adjusted ReturnTraditional return on investment is often expressed as: ROI = (Net benefits − Investment cost) / Investment cost. For neural-network initiatives, this formula must be interpreted carefully. Costs extend beyond initial development. They include data acquisition, annotation, infrastructure, integration, testing, monitoring, retraining, governance, user training, and decommissioning. Benefits may be uncertain, delayed, or dependent on adoption. Managers should construct multiple scenarios rather than rely on a single forecast. A conservative case may assume slower adoption, higher operating costs, and limited performance improvement. A base case reflects the most defensible assumptions, while an optimistic case represents favorable but plausible conditions. Sensitivity analysis can show which variables—volume, precision, labor savings, conversion rate, or infrastructure cost—most influence the result. Risk-adjusted value incorporates the probability and impact of adverse outcomes. A project with high expected benefit may be unattractive if a small probability of a severe safety, privacy, or legal event is ignored. Real-options thinking is useful for uncertain initiatives. A small pilot can be viewed as purchasing information: it limits immediate exposure while generating evidence about data quality, user acceptance, and operational value. Managers should also account for the cost of false decisions. In medical triage, a false negative may be more serious than a false positive. In marketing, the reverse may be true because unnecessary outreach increases cost and customer irritation. Therefore, business thresholds should be selected according to the consequences of errors rather than according to a default probability cutoff. Operating Model, Governance, and AccountabilityAn enterprise neural-network system requires an operating model that connects technical teams with business, legal, risk, security, and frontline stakeholders. Common roles include a business owner accountable for outcomes, a product manager responsible for requirements and adoption, data scientists and machine-learning engineers responsible for development, data stewards responsible for data quality, security specialists, legal and compliance reviewers, and operational users who validate workflow fit. Governance should be proportionate to risk. A low-risk recommendation system may require basic documentation and monitoring. A system affecting credit, employment, healthcare, safety, or access to essential services requires stronger controls, including impact assessments, subgroup evaluation, human oversight, appeal mechanisms, audit trails, and formal approval gates. A model card or equivalent system record should describe intended use, limitations, training data characteristics, evaluation results, known failure modes, and prohibited uses. Monitoring should cover not only accuracy but also data drift, concept drift, subgroup performance, calibration, latency, cost, user overrides, and outcome disparities. A model can remain technically accurate while becoming strategically harmful if the surrounding process changes. Human oversight must be meaningful rather than ceremonial. If employees are expected to challenge a model but are penalized for disagreeing with it, nominal human review becomes automation bias. Conversely, excessive manual override may indicate poor model quality, weak training, or an unsuitable workflow. Decision rights and escalation procedures should be explicit. Talent, Change Management, and AdoptionNeural-network transformation is a socio-technical process. Talent requirements include machine learning, data engineering, software engineering, cloud operations, product management, domain expertise, risk management, and communication. Organizations should avoid assuming that hiring a small number of data scientists will resolve structural data and process problems. A capability-building strategy may combine recruitment, internal reskilling, partnerships with universities or vendors, communities of practice, and carefully governed experimentation. Career paths and incentives should reward reliable deployment and responsible use, not merely the publication of models or improvement on benchmark datasets. Change management begins with a clear explanation of the problem the system is intended to solve. Employees need to understand how responsibilities will change, what the system can and cannot do, how performance will be evaluated, and how concerns can be raised. Involving users in design and pilot evaluation improves both usability and legitimacy. Resistance is not always irrational. Employees may identify risks that technical teams overlook, such as unworkable alert volumes, unfair performance targets, or loss of professional discretion. Managers should treat such feedback as evidence about implementation quality. Adoption metrics may include usage, appropriate override rates, time saved, user confidence, outcome improvement, and the distribution of benefits across groups. A Roadmap for Neural-Network TransformationA transformation roadmap should progress from evidence to scale. A useful sequence has six stages. First, define strategic themes and establish governance. The organization identifies priority outcomes, risk appetite, sponsorship, funding principles, and decision rights. Second, discover and rank use cases. Cross-functional teams document opportunities, estimate value, assess feasibility, and select a small portfolio rather than an unbounded list. Third, establish foundations. This may involve data cataloguing, access controls, quality improvement, cloud or on-premises infrastructure, model registries, security practices, and responsible-AI procedures. Fourth, conduct controlled pilots. Pilots should test the complete workflow, including user interaction, integration, monitoring, and business outcomes. A technically impressive demonstration is insufficient. Fifth, industrialize successful initiatives. Production deployment requires reliability engineering, automated testing, version control, observability, incident response, retraining procedures, and service ownership. Sixth, scale and renew. The organization measures realized value, retires ineffective systems, reuses components, and updates the portfolio as technology, regulation, and business strategy change. Stage gates should specify evidence required to proceed. For example, a project may need to demonstrate minimum subgroup performance, a viable operating cost, user acceptance, security approval, and a documented fallback process before production deployment. Illustrative Case: Neural Inspection at Meridian ComponentsBackgroundMeridian Components, a fictional mid-sized manufacturer, produces precision components for industrial equipment. Quality inspection was performed primarily by experienced inspectors using visual examination and measurement tools. Management observed variation across shifts, rising rework costs, and difficulty recruiting inspectors. A proposal was made to deploy a neural-network vision system. Situation and ProblemThe initial proposal focused on achieving at least 98 percent classification accuracy on a collection of sample images. The operations director, however, required a broader analysis. False negatives could allow defective components to reach customers, while excessive false positives would slow production and increase manual inspection. The system also had to operate within the cycle time of the production line and remain effective when lighting, camera position, and product batches changed. AnalysisA cross-functional team mapped the process and found that historical inspection records were incomplete. Images existed for recent defects, but many images were unlabeled, and defect definitions had changed over time. Inspectors also disagreed about borderline cases. The team therefore concluded that data preparation and label governance were major risks. The strategic value was potentially high because avoided warranty claims, lower rework, and increased throughput could affect several plants. Nevertheless, the team rejected an immediate full-scale deployment. It compared three options: buying a packaged vision system, building a model internally, and using a hybrid approach. The packaged system offered speed but limited control over defect categories and uncertain performance under Meridian’s conditions. Internal development would create learning and customization but require capabilities the company did not yet possess. The hybrid option—commercial cameras and inference infrastructure combined with internally governed data, model evaluation, and workflow integration—provided the best balance. Approach and StrategyMeridian launched a twelve-week pilot on one production line. Inspectors helped define defect categories and reviewed disputed labels. The team established a holdout test set representing different shifts, materials, lighting conditions, and product variants. Evaluation included recall for critical defects, false-positive rate, inspection latency, subgroup-like comparisons across product variants, and the proportion of cases requiring human review. The system did not automatically reject every item. High-confidence normal items proceeded, high-confidence defects were diverted for review, and uncertain cases were routed to inspectors. Every decision was logged. A fallback manual process remained available if cameras failed, data drift was detected, or performance fell below the agreed threshold. The business case included hardware, integration, annotation, training, maintenance, and periodic recalibration. Rather than claiming labor elimination, the proposal described a shift in inspector work toward exception handling, root-cause analysis, and process improvement. This approach reduced resistance and preserved critical expertise. OutcomeThe pilot demonstrated that the model could support the line, but it also revealed that performance declined when a new surface finish was introduced. The system was therefore not approved for unrestricted deployment. Meridian expanded the training data, added a change-control requirement for new materials, and introduced a monitoring dashboard. After a second evaluation, the system was deployed on two additional lines with formal review gates. The most important outcome was not merely improved detection. Meridian developed a reusable process for image governance, model validation, operational monitoring, and cross-functional approval. The initiative created a foundation for later applications while preventing premature scaling. Learning PointsThe case illustrates five principles. First, the business problem must be defined in operational terms. Second, accuracy is only one dimension of value. Third, data and process changes can invalidate a model even when the original test results were strong. Fourth, hybrid sourcing can balance speed and control. Fifth, a staged pilot can generate valuable information while limiting risk. Challenges, Risks, and Common Managerial MistakesA frequent mistake is treating a prototype as a product. Prototypes usually use curated data, tolerate manual intervention, and omit security, monitoring, support, and failure recovery. Production systems require all of these capabilities. Another mistake is using aggregate metrics that conceal unequal performance. A model may perform well overall while failing for a minority product type or demographic group. Managers should require disaggregated evaluation where relevant and investigate the reasons for differences. Data leakage, label leakage, distribution shift, adversarial manipulation, cybersecurity vulnerabilities, and silent pipeline failures can all undermine a system. Vendor lock-in is another strategic risk, especially when proprietary formats, interfaces, or model dependencies make exit expensive. Automation bias, deskilling, surveillance, and job redesign raise human risks. There is also a danger of accountability diffusion: business leaders blame the model, technical teams blame the data, and vendors refer to contractual limitations. Clear ownership must exist before deployment. Neural networks may also create environmental and financial costs through intensive training or inference. Efficient architectures, model compression, appropriate hardware, batching, and careful retraining schedules can reduce these costs. The relevant question is not whether a system uses advanced AI, but whether the value justifies its complete resource footprint. Ethical, Regulatory, and Professional ConsiderationsResponsible managerial decision-making requires lawful and legitimate data use, proportionality, fairness, transparency appropriate to context, security, and mechanisms for contesting consequential decisions. Explainability should be matched to the decision: a technical explanation may support debugging, while an affected person may require a meaningful reason and a route to correction. Privacy-by-design principles include data minimization, purpose limitation, retention controls, access management, pseudonymization where appropriate, and secure deletion. Organizations should distinguish consent from mere notice and should not assume that technically possible data use is ethically acceptable. Professional practice requires documentation, reproducible evaluation, version control, incident reporting, and continuing monitoring. Governance frameworks and regulations differ across jurisdictions and sectors, so organizations should obtain appropriate legal advice rather than relying on generic compliance claims. Ethical review is strongest when it is integrated into product design, procurement, engineering, and operational management. Current Developments and Emerging DirectionsEnterprise neural-network strategy is increasingly influenced by foundation models, multimodal systems, retrieval-augmented applications, smaller domain-specific models, and machine-learning operations platforms. These developments may reduce the cost of experimentation but introduce new concerns involving copyright, data provenance, hallucination, prompt injection, model supply chains, and evaluation of generated outputs. Organizations are also moving toward continuous evaluation rather than one-time validation. Model registries, feature stores, automated monitoring, privacy-enhancing technologies, and standardized documentation support more disciplined scaling. Edge inference can reduce latency and data transfer in industrial and mobile settings, while specialized accelerators may improve cost efficiency. The strategic trend is toward composable AI capabilities. Instead of treating each model as an isolated project, mature organizations build reusable data, evaluation, security, and governance services. This approach can improve speed and consistency, but central platforms must remain responsive to business needs and must not become bureaucratic barriers to experimentation. Best Practices for ManagersManagers should begin with measurable organizational outcomes, appoint accountable owners, and evaluate alternatives to neural networks. They should fund data quality and integration, not only model development. Business users, risk specialists, security teams, and affected stakeholders should participate early. Every initiative should have explicit success criteria, a baseline, a pilot design, a total-cost estimate, monitoring indicators, escalation rules, and a retirement plan. Build-versus-buy decisions should include exit costs and contractual protections. Deployment should be staged, with evidence-based gates and a fallback process. Finally, leaders should judge AI maturity by realized and responsibly sustained value. A smaller number of well-governed systems is strategically superior to a large inventory of demonstrations that cannot be trusted, maintained, or connected to organizational decisions. Chapter SummaryEnterprise neural-network strategy connects technical possibilities with organizational outcomes. Effective initiatives begin by defining the decision or workflow to be improved and then assessing strategic fit, data, technical, economic, organizational, legal, and ethical feasibility. Portfolio methods help prioritize opportunities, while build, buy, and hybrid choices balance control, speed, cost, and learning. Economic evaluation must include total cost of ownership, uncertainty, error consequences, adoption, and risk-adjusted value. Production success requires governance, monitoring, human accountability, talent, change management, and a staged transformation roadmap. The Meridian Components case shows why pilots should test complete workflows rather than model accuracy alone. Responsible enterprise AI is therefore a managerial discipline as much as a technical one. Key TermsStrategic fit: The degree to which an AI initiative supports organizational priorities and competitive objectives. Use case: A specific organizational application in which a model supports a decision or workflow. AI capability: A reusable organizational competence, such as model monitoring or governed data engineering. Data feasibility: The suitability, availability, quality, legality, and representativeness of required data. Technical feasibility: The practicality of achieving required performance, integration, reliability, and scalability. Total cost of ownership: All direct and indirect costs incurred throughout a system’s lifecycle. Build-versus-buy: The strategic choice between internal development and acquisition from an external provider. Hybrid sourcing: Combining purchased components with internally developed data, models, or workflows. Risk-adjusted return: Expected value considered together with the probability and impact of adverse outcomes. Pilot: A limited, controlled implementation designed to test value and feasibility. Stage gate: An evidence-based decision point controlling progression between project phases. Model drift: Decline in model suitability caused by changes in data or relationships over time. Human oversight: Meaningful human ability to review, challenge, override, or escalate model-supported decisions. Model card: Documentation describing a model’s intended use, evaluation, limitations, and risks. Automation bias: The tendency to over-trust automated recommendations. Data lineage: A record of data origins, transformations, ownership, and usage. Change management: Structured actions that support adoption of new systems, roles, and processes. Operating model: The distribution of responsibilities, processes, governance, and resources supporting a capability. Exit feasibility: The practical ability to replace a vendor or migrate data and workflows. Responsible AI: The design and operation of AI systems according to legal, ethical, social, and professional obligations. Review QuestionsShort Answer Questions1. Why should enterprise neural-network initiatives begin with an organizational problem rather than an algorithm? 2. What is meant by total cost of ownership in a neural-network project? 3. Distinguish a use case from an AI capability. 4. Why is human oversight important in consequential decisions? 5. What is the purpose of a stage gate? Long Answer Questions1. Explain the dimensions of feasibility that managers should assess before approving a neural-network initiative. 2. Compare build, buy, and hybrid sourcing strategies, including their principal trade-offs. 3. Discuss how governance, monitoring, and accountability contribute to responsible deployment. 4. Explain how talent development and change management influence the success of enterprise AI. 5. Describe a phased roadmap for moving from neural-network experimentation to organizational scale. Analytical / Application Questions1. A bank has a highly accurate loan-default model but cannot explain decisions to applicants and has incomplete demographic data. Should deployment proceed? Develop a reasoned decision using the feasibility and governance frameworks in this chapter. 2. A retailer can buy a general customer-service model or build a domain-specific system. Identify the information required to make the sourcing decision and recommend evaluation criteria. 3. Design a pilot for a neural-network system that detects defects in a food-processing plant. Specify the business objective, data requirements, performance measures, human roles, risks, and stage-gate conditions. 22. Multiple Choice Questions with AnswersQuestion 1Which statement best expresses the correct starting point for an enterprise neural-network initiative? A. Select the newest available architecture and search for a use later. B. Define the organizational decision or workflow that must improve. C. Maximize benchmark accuracy before consulting business users. D. Purchase infrastructure before estimating business value. Correct Answer: B. Define the organizational decision or workflow that must improve. Question 2Which factor is primarily a data-feasibility concern? A. Whether inference meets the required latency. B. Whether employees accept changed responsibilities. C. Whether training data represent the operating population. D. Whether the vendor offers a service-level agreement. Correct Answer: C. Whether training data represent the operating population. Question 3A hybrid sourcing strategy usually means that an organization: A. Avoids all external technology providers. B. Combines purchased components with internally governed capabilities. C. Builds two identical systems and selects one randomly. D. Uses a model without integrating it into operations. Correct Answer: B. Combines purchased components with internally governed capabilities. Question 4Why should a neural-network business case include a pilot? A. A pilot guarantees the final system will be profitable. B. A pilot eliminates the need for governance review. C. A pilot generates evidence while limiting initial exposure. D. A pilot replaces the need for production monitoring. Correct Answer: C. A pilot generates evidence while limiting initial exposure. Question 5Which measure is most appropriate for evaluating a high-risk defect-detection system? A. Overall accuracy alone. B. Training time alone. C. Critical-defect recall together with false-positive and operational measures. D. Number of layers in the neural network. Correct Answer: C. Critical-defect recall together with false-positive and operational measures. Question 6What does model drift refer to? A. Unauthorized access to model files. B. Declining suitability because data or relationships change. C. The use of several models in one workflow. D. A deliberate reduction in model size. Correct Answer: B. Declining suitability because data or relationships change. Question 7Which practice most directly reduces automation bias? A. Removing all human review from the workflow. B. Making model recommendations mandatory in every case. C. Defining meaningful review, override, and escalation procedures. D. Reporting only aggregate accuracy to users. Correct Answer: C. Defining meaningful review, override, and escalation procedures. Question 8Why is total cost of ownership more useful than launch cost alone? A. It excludes maintenance and monitoring costs. B. It captures lifecycle costs such as integration, retraining, and retirement. C. It assumes that vendor prices never change. D. It measures only the cost of data annotation. Correct Answer: B. It captures lifecycle costs such as integration, retraining, and retirement. Question 9In the Meridian Components case, why was immediate full-scale deployment rejected? A. The organization had no possible business benefit. B. The model used no image data. C. Data quality and performance under changing conditions had not been sufficiently established. D. Inspectors refused to participate in any pilot. Correct Answer: C. Data quality and performance under changing conditions had not been sufficiently established. Question 10Which condition is most suitable as a production stage gate? A. The prototype has an attractive user interface. B. The model uses a deep architecture. C. The system has demonstrated required performance, monitoring, security, and fallback controls. D. The project team has completed its first experiment. Correct Answer: C. The system has demonstrated required performance, monitoring, security, and fallback controls.
|