Management Support Systems (MSS) i Managers, Decision-Making, and Technologies An Overview of Frameworks, Concepts, and Tools Case Study: Priya’s Bakery, BengaluruOverview: Management Support Systems The Business Environment * Organizations operate in turbulent Theoretical Context climate with increasing pressures * Global competition, consumer gS demands, regulations drive change © MSS emerged from need to handle increasing ‘organizational complexity & data explosion © Rapid technological change: Organizations must innovate or become obsolete (Clayton Christensen’s disruption theory) * Decision cycles compressing: Speed is competitive advantage—fast decision-making beats perfect planning * Information overload challenge: Managers face cognitive limits processing diverse data sources * Information paradox: More data available but less time to analyze itPressures-Responses-Support Model Three Core Elements Pressures Responses Support Environmental factors Strategy, collaboration, Computerized technologies creating opportunities or agility, new business models facilitate monitoring and problems: to'counter pressures executing responses Theoretical Basis © Adaptation theory: Organizations must evolve or face extinction (Hannan & Freeman's organizational ecology) ‘ Pressures as catalysts: Environmental jolts force strategic responses; no response = organizational decline ‘ Dynamic responses: Static responses fall in turbulent environments; must iterate rapidly Technology enables agility: Support systems allow testing multiple responses quickly before committing resources {@ Feedback loop: Environmental feedback informs whether responses are effective (continuous learning cycle)Goal of Management Support Systems To facilitate closing the gap between current performance and desired strategy S Priya’s Bakery Goal Gap Current Performance 20% profit decline, stagnant sales, manual decision-making , f Desired Strategy 40% growth, market leadership in healthy bakery space, data-driven scaling MSS Role Excel dashboards, BI analytics, GSS for team collaboration enable faster, smarter decisionsThe Nature of Management ZA Definition & Measurement + Management = Process of using resources (inputs) to achieve goals (outputs) + Success measured by productivity: ratio of outputs to inputs w Management Levels & Information Needs Z p< G Operational Level: Focuses on daily tasks, transactions, immediate problem-solving | Needs detailed, real-time transaction data Middle Management: Resource allocation, performance monitoring, tactical planning | Needs summary reports, variance analysis Strategic Level: Long-term positioning, competitive advantage, organizational goals | Needs external data, industry trends, forecasts R 202 Exception Principle: Managers focus on variances from expectations (manage by exception) Knowledge work challenge: Outputs often intangible (ideas, decisions); productivity measurement complex in service sectors DixMintzberg's 10 Managerial Roles Interpersonal Roles (Acting & Representing) ww Figurehead: Ceremonial & symbolic representation ] Leader: Directing, motivating, coaching team Liaison: Connecting with external networks & partners Mintzberg’s Research Insights + Based on direct observation of actual managers (not theory) * Roles are interdependent—performing one role affects others « Role emphasis varies by organization type & industry * Constant switching: Managers switch between roles every few minutes JS Priya’s Interpersonal Roles Figurehead: Hosting Diwali events, representing bakery at forums | Leader: Training bakers, motivating during slow seasons | Liaison: Negotiating with Swiggy/Zomato, partnering with suppliersMintzberg's 10 Roles (Continued) Informational Roles (Processing Information) © Monitor: Scanning environment for relevant information © Disseminator: Sharing info internally to guide team © Spokesperson: Representing organization externally v Priya’s Informational Roles Monitor: Checking delivery app reviews, competitor pricing, sales trends Disseminator: Explaining menu changes to bakers based on sales data Spokesperson: Responding to customers on Instagram/WhatsApp about brand story« @ Mintzberg’s 10 Roles (Continued) Decisional Roles (Making Strategic Choices) Entrepreneur: identifying new opportunities for growth Disturbance Handler: Managing crises & conflicts Resource Allocator: Distributing limited resources Negotiator: Conducting negotiations with external parties Priya's Decisional Roles + Entrepreneur: Launching vegan cheesecake line + Disturbance Handler: Responding to competitor price cuts + Resource Allocator: Deciding budget for marketing vs. equipment * Negotiator: Bargaining with suppliers & delivery platformsThe Core Task: Decision-Making Decision-making is central to all managerial roles. Every action boils down to: What should | do? Which option is best? ~@ Why? « Interpersonal: Decisions about representation, motivation, partnerships. + Informational: Decisions about what to gather, share, communicate * Decisional: Directly involve strategic choices Vv Without MSS Priya decides alone, based on memory & intuition > slower, riskier decisions. ith MSS BI dashboards, DSS models, team GSS > data-driven, collaborative, fast decisions.Simon's Four Phases of Decision-Making A Structured Process Intelligence: Design: Choice: Implementation: Searching Inventing & Selecting a ‘Adapting and ment for analyzing specific course executing the ns calling possible courses of action decision for decisions of action & Simon's Contributions to Decision Science + Normative vs. Descriptive: Model shows how decisions SHOULD be made; rarely describes actual practice * Intelligence phase is longest: Often 50-70% of decision time spent on problem recognition * Satisficing principle: Managers seek satisfactory solutions (satisficing), not perfect optimal solutions * Bounded rationality: Choices often made with incomplete information due to cognitive/time limits * Feedback loops crucial: Implementation reveals new information, forcing loop-back to earlier phasesSimon's Phases: Vegan Cheesecake Decision @o Q Intelligence: Design: Customers ask for 4 options analyzed— vegan options (30% premium line, limited demand), competitors offering, no action, price at 450-500 partner model. DSS model shows limited option RO! in 1 month Implementation: Select limited Source ingredients weekend vegan (Week 1), train staff cheesecake (%400/slice, (Week 2), pilot test 28,000 investment) (Week 3), launch (Week 4), monitor sales MSS Support S/S BI data revealed demand signal | DSS spreadsheet compared 4 options | GSS team discussion finalized choice | KMS stored recipe & supplier contactsWhy Use Computers for Decisions? Three Key Reasons ™ seconds Cognitive Limits: Speed: Computers Cost: Trial-and-error in Human mind limited to eg perform thousands of Su real world expensive; ~7 chunks in working computations in a simulation cheaper memory (Miller's Law) a Cognitive Science & Information Overload + Information explosion: Data volumes growing exponentially; humans can't process increase manually + Consistency: Computers don't fatigue, bias, or emotion affects precision—repeatably apply rules ‘+ Scenario analysis: Simulate 1,000 what-if situations instantly; humans can hold 3-4 scenarios mentally ‘+ Augmentation approach: Computers enhance human decision-making (not replace); best decisions combine both * Bias reduction: Decision models reduce some biases (anchoring, availability) but introduce others =a {algorithm bias)Key Capabilities of Computerized Support & Managing giant data warehouses (historical & current data) Facilitating communication & collaboration (remote teams) K ee Overcoming geographical limits via the Web és Providing agility & quality support (real-time dashboards) JS Priya’s MSS Implementation © Data Warehouse: Google Sheets storing 12 months sales by branch, product @ Collaboration: Google Meet for remote team decisions @ Web-based: Delivery platforms, Instagram provide real-time customer data @ Agility: Bl dashboard updated daily showing margin trends across branchesThe Gorry-Scott Morton Matrix Framework for Decision Support Combines two dimensions: + Degree of Structuredness: Structured (routine) > Semi-structured (mixed) > Unstructured (fuzzy) + Type of Control: Operational (daily) -> Managerial (monthly) > Strategic (yearly) Historical Significance & Nuances * Originated 1970s: Foundational framework; still relevant despite technology evolution + Structuredness is subjective: Familiar problems become structured with experience (expert pattern recognition) * Control levels need different data: Operational needs detailed transactions; strategic needs summaries & trends + Tool-problem matching critical: Mismatching wastes resources (expensive BI tool for structured decision) Purpose: Determine which support technology most appropriate for each decision typeTechnology Mapping in Gorry-Scott Morton Decision Support by Category Go %&@ &@ Structured + Structured + Semi-Structured + Unstructured + Operational: MIS Managerial: MIS Managerial: DSS Strategic: Expert (automated rules, (reports, (pricing, Systems, Group billing) dashboards) forecasting) Judgment Priya’s Pricing Decision Semi-Structured (mixed data + judgment) + Managerial (affects profit margin): Requires DSS. Excel model provides data; Priya uses judgment on market positioningDecision Support Systems (DSS) Definition Key Characteristics Interactive computer-| based systems © Couples human intellect with machine capabilities which help decision makers utilize © Focuses on semi-structured & unstructured problems data and models to solve ‘© Supports (rather than replaces) the manager semi-structured problems Umbrella term covering specific apps & broad methodologies MIS: Focuses on what happened (reporting past, structured data) DSS: Focuses on what could happen (exploring futures, scenarios) DSS vs. MIs Dialog system approach: Iterative interaction between user & system (not batch Distinction processing) Model management: Storing, organizing, reusing decision models across problemsDSS: Why Suitable for Priya's Pricing Decision? | The Synergy ip ee Machine GQ Human : =) Process costs (2175/slice), “(Judge market perception, competitor pricing (450-500), brand positioning, customer elasticity (-0.6), run 100 willingness to pay, strategic fit scenarios instantly JS Priya’s DSS Pricing Model * Excel shows: At 2450 price, 7.5% volume drop BUT 14% profit increase. * Priya decides: Health-conscious customers won't switch; premium positioning justifies £450 Result: Data-informed decision, not gut feelDSS Architecture: Major Components Four Core Elements a a Data Models. Knowledge User Interface Database or data Mathematical/ warehouse statistical Optional expert How user (internal/external models to intelligence communicates data) manipulate data component with system User is considered a component of the architecture (participative design)DSS Architecture: Priya’s Pricing Tool Components in Action EG bata: Costs (#175/slice), sales history (15 slices/week), competitor prices = Models: Price elasticity formula: Volume = Current x (1 - elasticity x % price change) QB knowledge: Historical market feedback, brand positioning insights as Interface: Excel spreadsheet (familiar, easy to adjust inputs) fo User: Priya interprets results, applies judgment Why Excel Works for Priya No coding required, fast to modify assumptions, visual output, portable. Sophisticated BI tools would be overkill for this semi-structured problemGroup Support Systems (GSS) Group Dynamics Research Foundations The Challenge & Solution Challenge: Decisions often made by _—« Process losses in groups: Groupthink, dominant groups. Assembling experts personalities, social loafing, production blocking physically is costly & slow + GSS overcomes losses through: Anonymity (honest Solution: Interactive systems input), parallel input (everyone contributes), structured facilitating unstructured problem- processes solving by multiple decision-makers + Optimal group size: Research shows 5-7 members best for most decisions (diminishing returns at larger sizes) + Distributed decision-making: Critical capability for scaling organizations across multiple locations Includes + Group Decision Support Systems (GDSS) + Collaborative Web tools (Google Meet, Slack, Docs)GSS: Enabling Priya’s Scaling Three Key Benefits . e ~ \ & ) r= e @-. | Cost & Time Asynchronous Contribution Consensus Building No Bengaluru traffic delays, Team reviews data at own Anonymous voting prevents no meeting room rent Pace, contributes thinking dominant personalities, N \ thoughtfully Si data-driven decisions @ Priya’s Real Scenario Competitor cuts vegan cake price. Without GSS: Priya makes reactive decision (drop price, damage margins). With GSS: 30-min emergency video meeting with finance, marketing, baker ~ collective decision to differentiate on quality (keep 2450, launch education campaign). Result: competitive advantage in 24 hoursBusiness Intelligence (Bl) From EIS to BI Evolution Executive Information Systems (EIS) of 1980s evolved into modern Business Intelligence + Beyond report actions) analytics * Single source of truth: Data warehouse eliminates conflicting reports from different systems + ETL Process: Extract, Transform, Load ensures data quality & consistency + Real-time BI: Streaming data enables live monitoring & immediate action (not day-old reports) Modern Bl enables predictive (forecasting) & prescriptive (recommending BI Defined Umbrella term for architectures, tools, and databases used to transform data into information, then decisions, then actionBusiness Intelligence: Core Capabilities Three Pillars Data Warehouse Analytics Dashboards Historical and current Mining and manipulati- Visual at-a-glance data repository ing data to extract performance monitors (internal + external) patterns & trends for decision-making YZ Priya’s BI Implementation Warehouse: 12 months sales by branch, product, customer segment Analytics: Identify Koramangala branch is loss-making (-10% margin) Dashboard: Real-time daily performance shows Indiranagar profit trendBI: Enabling Priya’s Scaling to 5+ Branches Without BI With BI * Manual tracking across branches * Central dashboard shows all = impossible (fragmented Excel branches live (sales, profit, sheets) margins) * Can't see real-time branch * Predictive analytics forecast profitability demand for festivals * Decisions based on memory, not * Customer segmentation reveals data most profitable segments * Competitive benchmarking informs pricing strategy @ Result:Knowledge Management Systems (KMS) Definition ey Knowledge Capture Challenges Systems to identify, select, * Tacit vs. Explicit: KMS captures explicit knowledge organize, and disseminate (recipes, processes); tacit knowledge (expertise, organizational memory and intuition) hard to capture expertise * Organizational amnesia: Knowledge loss when experts leave; KMS prevents this + Best practice sharing: Spreads successful approaches across organization (avoiding reinvention) + Communities of practice: Informal networks where knowledge shares naturally (KMS formalizes these) * Cultural barriers: Competitive silos, resistance to sharing hinder KMS adoption (requires culture shift), Purpose Preserve institutional knowledge, prevent loss when employees leave, enable learning across organizationHybrid & Integrated Systems Reality: Complex Problems Require Multiple Tools Single tool insufficient. Example: Expert System for diagnosis + DSS for scheduling =| Integration Architecture & Challenges + Enterprise systems: Integrate DSS, BI, KMS into unified platforms (SAP, Oracle) + API-based integration: Loose coupling allows mixing best-of-breed tools (flexible, modular) * Data governance critical: Multiple systems must share consistent data definitions * Change management: Integration projects often fail due to organizational resistance (adoption challenge) + ROI complexity: Integration benefits often indirect & delayed (hard to justify upfront costs) Integration Types * Loose: Tools transfer data between them (Excel exports to BI dashboard) + Tight: Unified interface where tools work seamlessly (integrated platform)Summary: MSS Ecosystem Four Core Types Technology Selection Rule DSS: Semi-structured problems with Structured problems: Management data/models (pricing, forecasting) Science & MIS (automated rules) © Bl: Data warehousing & visualization Unstructured problems: DSS, Expert (real-time dashboards) Systems (human judgment) GSS: Group decision-making for unstructured problems (collaborative meetings) © KMS: Organizational memory & expertise preservation (recipes, processes)Future Trends in MSS Three Directions Web-Based Support: s@ Artificial Intelligence: Wireless/Mobile: Support Internet = primary [= Increasing use of Al py becoming anywhere, © platform (no software 2@ (neural networks, ML) anytime (mobile installation needed) | for smarter systems. dashboards, cloud \ J \ J. decisions) aoe . eT Emerging Capabilities AI/ML augmentation: Automated pattern recognition, predictive models, autonomous decision-making ‘Natural language interfaces: Chat-based analytics (conversational BI vs. traditional dashboards) Edge computing: Local data processing reduces latency for real-time decisions Explainable Al (XAl): Making Al decisions transparent & trustworthy (addressing black-box concerns) Y |mplication for Priya Future: Al demand forecasting instead of manual analytics | Mobile dashboards for branch managers | Voice-based orders via Al | Predictive inventory. Today: Google Sheets & Meet. Tomorrow: Automated systems with human oversightKey Takeaway: MSS Enables Competitive Advantage Priya’s Bakery scaling from 1 branch (manual) to 5+ branches (data-driven) Without MSS: With MSS: Hustle & luck limit Speed + Intelligence elroy ta molar} enables sustainable Lo} g-T aera k=) 5+ branch scaling Questions?